From 0da2942dd369c0cf30c9dc907c20411b355b644d Mon Sep 17 00:00:00 2001
From: Rachael Sewell <rachmari@github.com>
Date: Thu, 6 Jan 2022 12:11:58 -0800
Subject: [PATCH 01/13] remove storybook (#24122)

---
 middleware/render-page.js |   4 -
 pages/storybook.tsx       | 223 --------------------------------------
 2 files changed, 227 deletions(-)
 delete mode 100644 pages/storybook.tsx

diff --git a/middleware/render-page.js b/middleware/render-page.js
index 6998c03293bb..d1442f53205f 100644
--- a/middleware/render-page.js
+++ b/middleware/render-page.js
@@ -88,10 +88,6 @@ export default async function renderPage(req, res, next) {
   const { page } = context
   const path = req.pagePath || req.path
 
-  if (path.startsWith('/storybook')) {
-    return nextHandleRequest(req, res)
-  }
-
   // render a 404 page
   if (!page) {
     if (process.env.NODE_ENV !== 'test' && context.redirectNotFound) {
diff --git a/pages/storybook.tsx b/pages/storybook.tsx
deleted file mode 100644
index fa589d55229a..000000000000
--- a/pages/storybook.tsx
+++ /dev/null
@@ -1,223 +0,0 @@
-import React from 'react'
-import ReactDomServer from 'react-dom/server'
-import { BumpLink, BumpLinkPropsT } from 'components/ui/BumpLink/BumpLink'
-import { Callout, CalloutPropsT } from 'components/ui/Callout/Callout'
-import { Lead, LeadPropsT } from 'components/ui/Lead/Lead'
-import {
-  MarkdownContent,
-  MarkdownContentPropsT,
-} from 'components/ui/MarkdownContent/MarkdownContent'
-import { ScrollButton, ScrollButtonPropsT } from 'components/ui/ScrollButton/ScrollButton'
-import { TruncateLines, TruncateLinesPropsT } from 'components/ui/TruncateLines/TruncateLines'
-import { Picker, PickerPropsT } from 'components/ui/Picker/Picker'
-
-const markdownExample = (
-  <>
-    <h1>Header Level 1: Steps example</h1>
-    <ol>
-      <li>Start with step 1</li>
-      <li>Continue with step 2</li>
-      <li>Finish with step 3</li>
-    </ol>
-    <h2>Header Level 2: Highlighted code example</h2>
-    <pre>
-      <code className="hljs language-yaml">
-        <span className="hljs-attr">steps:</span>
-        {'\n'}
-        <span className="hljs-bullet">-</span> <span className="hljs-attr">uses:</span>{' '}
-        <span className="hljs-string">actions/checkout@v2</span>
-        {'\n'}
-        <span className="hljs-bullet">-</span> <span className="hljs-attr">uses:</span>{' '}
-        <span className="hljs-string">actions/setup-java@v2</span>
-        {'\n  '}
-        <span className="hljs-attr">with:</span>
-        {'\n    '}
-        <span className="hljs-attr">java-version:</span> <span className="hljs-string">'11'</span>
-        {'\n    '}
-        <span className="hljs-attr">distribution:</span>{' '}
-        <span className="hljs-string">'adopt'</span>
-      </code>
-    </pre>
-    <h3>Header Level 3: Table example</h3>
-    <table>
-      <thead>
-        <tr>
-          <th>Qualifier</th>
-          <th>Example</th>
-        </tr>
-      </thead>
-      <tbody>
-        <tr>
-          <td>
-            <code>sort:interactions</code> or <code>sort:interactions-desc</code>
-          </td>
-          <td>
-            <a href="https://github.com/search?q=org%3Agithub+sort%3Ainteractions&amp;type=Issues">
-              <strong>org:github sort:interactions</strong>
-            </a>{' '}
-            matches issues in repositories owned by GitHub, sorted by the highest combined number of
-            reactions and comments.
-          </td>
-        </tr>
-        <tr>
-          <td>
-            <code>sort:interactions-asc</code>
-          </td>
-          <td>
-            <a href="https://github.com/search?utf8=%E2%9C%93&amp;q=org%3Agithub+sort%3Ainteractions-asc&amp;type=Issues">
-              <strong>org:github sort:interactions-asc</strong>
-            </a>{' '}
-            matches issues in repositories owned by GitHub, sorted by the lowest combined number of
-            reactions and comments.
-          </td>
-        </tr>
-      </tbody>
-    </table>
-    <h4>Header Level 4: Procedural image example</h4>
-    <img
-      alt="Group assignment"
-      className="procedural-image-wrapper"
-      src="/assets/images/help/classroom/assignment-group-hero.png"
-    />
-  </>
-)
-
-// Trying to keep these alphabetical order
-const stories = [
-  {
-    name: 'BumpLink',
-    component: BumpLink,
-    variants: [
-      { title: 'Think basic', href: 'http://example.com' } as BumpLinkPropsT,
-      {
-        title: 'Think different',
-        href: 'http://example.com',
-        children: 'This is child text',
-      } as BumpLinkPropsT,
-      {
-        as: 'div',
-        title: 'Think as div',
-        href: 'http://example.com',
-        className: 'color-bg-attention',
-      } as BumpLinkPropsT,
-    ],
-  },
-  {
-    name: 'Callout',
-    component: Callout,
-    variants: [
-      { variant: 'success', children: 'Yay you did it!', className: '' } as CalloutPropsT,
-      { variant: 'info', children: 'Captain I have information.', className: '' } as CalloutPropsT,
-      { variant: 'warning', children: 'Warning... warning...', className: '' } as CalloutPropsT,
-      { variant: 'success', children: 'I am a little font', className: 'f6' } as CalloutPropsT,
-    ],
-  },
-  {
-    name: 'Lead',
-    component: Lead,
-    variants: [
-      { children: 'Lead by example' } as LeadPropsT,
-      { children: 'Lead by blue', className: 'color-bg-accent' } as LeadPropsT,
-      {
-        children: (
-          <>
-            You can personalize Codespaces by using a <code>dotfiles</code> repository on GitHub.
-          </>
-        ),
-      } as LeadPropsT,
-    ],
-  },
-  {
-    name: 'MarkdownContent',
-    component: MarkdownContent,
-    variants: [{ children: markdownExample } as MarkdownContentPropsT],
-  },
-  {
-    name: 'Picker',
-    component: Picker,
-    variants: [
-      {
-        defaultText: 'Choose color',
-        options: [
-          { text: 'Red', item: <span>Red</span> },
-          { text: 'Green', item: <span>Green</span> },
-          { text: 'Blue', item: <span>Blue</span> },
-        ],
-      } as PickerPropsT,
-      {
-        defaultText: 'Choose color',
-        variant: 'inline',
-        options: [
-          { text: 'Red', item: <span>Red</span> },
-          { text: 'Green', item: <span>Green</span> },
-          { text: 'Blue', item: <span>Blue</span> },
-        ],
-      } as PickerPropsT,
-    ],
-  },
-  {
-    name: 'ScrollButton',
-    component: ScrollButton,
-    variants: [{ className: '', ariaLabel: 'Scroll to top' } as ScrollButtonPropsT],
-  },
-  {
-    name: 'TruncateLines',
-    component: TruncateLines,
-    variants: [
-      {
-        as: 'p',
-        maxLines: 2,
-        children:
-          'Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.',
-        className: 'color-bg-subtle',
-      } as TruncateLinesPropsT,
-    ],
-  },
-]
-
-function displayProps(props: Object) {
-  const xprops = Object.fromEntries(
-    Object.entries(props).map(([key, value]) => [
-      key,
-      React.isValidElement(value) ? ReactDomServer.renderToString(value) : value,
-    ])
-  )
-  return JSON.stringify(xprops, null, 2)
-}
-
-export default function Storybook() {
-  return (
-    <div className="p-4 mx-auto" style={{ maxWidth: 1200 }}>
-      <h1>GitHub Docs Storybook</h1>
-      <Lead>This page lists React components unique to the GitHub docs.</Lead>
-      <div className="my-4 d-lg-flex flex-items-start">
-        <nav className="menu col-12 col-lg-3 mr-4 color-bg-subtle position-lg-sticky top-0">
-          {stories.map(({ name }) => (
-            <a key={name} className="menu-item" href={`#${name}`}>
-              {name}
-            </a>
-          ))}
-        </nav>
-        <div className="col-12 col-lg-9">
-          {stories.map(({ name, component, variants }) => (
-            <div id={name} key={name} className="mb-8">
-              <h2 className="position-sticky top-0 color-bg-default border-bottom z-2">{name}</h2>
-              {variants.map((props) => (
-                <div className="my-4" key={JSON.stringify(props)}>
-                  {/* @ts-ignore */}
-                  {React.createElement(component, props)}
-                  <pre
-                    className="mt-2 p-2 color-bg-subtle border rounded-2"
-                    style={{ whiteSpace: 'pre-wrap' }}
-                  >
-                    {displayProps(props)}
-                  </pre>
-                </div>
-              ))}
-            </div>
-          ))}
-        </div>
-      </div>
-    </div>
-  )
-}

From 5893ae32b39937437e24ebd7baba2f5b3ff5585e Mon Sep 17 00:00:00 2001
From: Peter Bengtsson <peterbe@github.com>
Date: Thu, 6 Jan 2022 15:59:47 -0500
Subject: [PATCH 02/13] don't let the href depend on the router hash in
 client-side rendering (#24106)

---
 components/page-header/LanguagePicker.tsx | 8 +++++++-
 1 file changed, 7 insertions(+), 1 deletion(-)

diff --git a/components/page-header/LanguagePicker.tsx b/components/page-header/LanguagePicker.tsx
index 0994eb24bcd6..0fb6663d729c 100644
--- a/components/page-header/LanguagePicker.tsx
+++ b/components/page-header/LanguagePicker.tsx
@@ -14,6 +14,12 @@ export const LanguagePicker = ({ variant }: Props) => {
   const langs = Object.values(languages)
   const selectedLang = languages[locale]
 
+  // The `router.asPath` will always be without a hash in SSR
+  // So to avoid a hydraration failure on the client, we have to
+  // normalize it to be without the hash. That way the path is treated
+  // in a "denormalized" way.
+  const routerPath = router.asPath.split('#')[0]
+
   return (
     <Picker
       variant={variant}
@@ -25,7 +31,7 @@ export const LanguagePicker = ({ variant }: Props) => {
           text: lang.nativeName || lang.name,
           selected: lang === selectedLang,
           item: (
-            <Link href={router.asPath} locale={lang.code}>
+            <Link href={routerPath} locale={lang.code}>
               {lang.nativeName ? (
                 <>
                   <span lang={lang.code}>{lang.nativeName}</span> (

From ad150e0cc876d363f7ac758ec3f3109f18396f67 Mon Sep 17 00:00:00 2001
From: docubot <67483024+docubot@users.noreply.github.com>
Date: Thu, 6 Jan 2022 13:19:28 -0800
Subject: [PATCH 03/13] New translation batch for pt (#24116)

* Add crowdin translations

* Run script/i18n/homogenize-frontmatter.js

* Run script/i18n/fix-translation-errors.js

* Run script/i18n/lint-translation-files.js --check parsing

* Run script/i18n/lint-translation-files.js --check rendering

* run script/i18n/reset-files-with-broken-liquid-tags.js --language=pt

* run script/i18n/reset-known-broken-translation-files.js

* Check in pt CSV report

Co-authored-by: Rachael Sewell <rachmari@github.com>
---
 translations/log/pt-resets.csv                |  23 +-
 .../managing-your-theme-settings.md           |   4 +-
 ...on-levels-for-a-user-account-repository.md |   6 +-
 ...iewing-peoples-roles-in-an-organization.md |  48 +++-
 .../about-continuous-integration.md           |  10 +-
 .../building-and-testing-java-with-ant.md     |   8 +-
 .../building-and-testing-java-with-gradle.md  |   8 +-
 .../building-and-testing-java-with-maven.md   |   8 +-
 .../building-and-testing-net.md               |   6 +-
 .../building-and-testing-nodejs.md            |   8 +-
 .../building-and-testing-python.md            |   8 +-
 .../building-and-testing-ruby.md              |   6 +-
 .../building-and-testing-swift.md             |   6 +-
 .../creating-a-javascript-action.md           |   6 +-
 .../metadata-syntax-for-github-actions.md     |  46 +++-
 .../about-continuous-deployment.md            |   2 +-
 ...g-openid-connect-in-amazon-web-services.md |   4 +-
 translations/pt-BR/content/actions/guides.md  |   2 +-
 ...using-self-hosted-runners-in-a-workflow.md |   9 +-
 translations/pt-BR/content/actions/index.md   |   2 +-
 ...starter-workflows-for-your-organization.md |  99 ++++++++
 .../learn-github-actions/expressions.md       |  30 ++-
 .../actions/learn-github-actions/index.md     |   4 +-
 .../managing-complex-workflows.md             |   4 +-
 .../learn-github-actions/reusing-workflows.md |   6 +-
 ...rets-and-runners-with-your-organization.md |  10 +-
 .../using-starter-workflows.md                |  54 +++++
 .../workflow-syntax-for-github-actions.md     |   2 +-
 .../adding-a-workflow-status-badge.md         |   4 +-
 .../pt-BR/content/actions/quickstart.md       |   2 +-
 .../about-github-hosted-runners.md            |   4 +-
 ...ucing-github-actions-to-your-enterprise.md |   6 +-
 ...e-ecosystem-support-for-your-enterprise.md |  34 +--
 .../roles-in-an-enterprise.md                 |   2 +-
 .../troubleshooting-the-codeql-workflow.md    |   4 +-
 .../github-security-features.md               |  16 +-
 .../securing-your-organization.md             | 133 ++++++-----
 .../securing-your-repository.md               |  29 ++-
 ...nvironment-variables-for-your-codespace.md |  40 ++++
 .../developing-in-codespaces/index.md         |   1 +
 .../troubleshooting-codespaces-clients.md     |  32 ++-
 .../scopes-for-oauth-apps.md                  |   2 +-
 .../about-github-advanced-security.md         |  46 ++--
 .../get-started/quickstart/github-flow.md     |   2 +-
 .../get-started/quickstart/set-up-git.md      |  10 +
 ...se-settings-for-your-private-repository.md |  24 +-
 .../about-writing-and-formatting-on-github.md |  40 ++--
 .../basic-writing-and-formatting-syntax.md    |   2 +
 .../creating-and-highlighting-code-blocks.md  |  38 +--
 .../organizing-information-with-tables.md     |  71 +++---
 .../closing-a-project-board.md                |   2 +-
 .../reopening-a-closed-project-board.md       |  25 +-
 .../archiving-cards-on-a-project-board.md     |  25 +-
 .../creating-an-issue.md                      |   2 +-
 ...-and-searching-issues-and-pull-requests.md |   2 +-
 .../creating-a-project.md                     |   2 +-
 .../using-the-api-to-manage-projects.md       |   4 +-
 ...analysis-settings-for-your-organization.md | 152 ++++++------
 ...ing-the-audit-log-for-your-organization.md |  27 ++-
 .../repository-roles-for-an-organization.md   |  14 +-
 ...-security-managers-in-your-organization.md |  12 +-
 .../about-permissions-for-github-packages.md  |   2 +-
 .../deleting-a-package.md                     |  37 +--
 .../deleting-and-restoring-a-package.md       | 224 ++++++++++--------
 .../introduction-to-github-packages.md        |   2 +-
 .../working-with-the-apache-maven-registry.md |   2 +-
 .../working-with-the-docker-registry.md       |   2 +-
 .../working-with-the-gradle-registry.md       |   2 +-
 .../working-with-the-npm-registry.md          |   4 +-
 .../working-with-the-nuget-registry.md        |   2 +-
 .../working-with-the-rubygems-registry.md     |   2 +-
 ...ing-your-custom-domain-for-github-pages.md |  14 +-
 ...uring-your-github-pages-site-with-https.md |  55 +++--
 .../requesting-a-pull-request-review.md       |  39 +--
 .../about-pull-request-reviews.md             |  49 ++--
 .../working-with-forks/about-forks.md         |   2 +-
 .../about-protected-branches.md               |  14 +-
 .../managing-a-branch-protection-rule.md      |  14 +-
 .../troubleshooting-required-status-checks.md |   3 +-
 ...d-analysis-settings-for-your-repository.md |  24 +-
 .../setting-repository-visibility.md          |   2 +-
 ...erprise-owners-visible-for-org-members.yml |   7 +
 .../features/fixed-width-font-gfm-fields.yml  |   8 +
 .../github-ae/2021-06/2021-12-06.yml          |   2 +-
 .../actions/actions-group-concurrency.md      |   2 +-
 .../reusables/actions/cd-templates-actions.md |   2 +-
 .../workflow-organization-templates.md        |   2 +-
 .../actions/workflow-template-overview.md     |   4 +-
 .../advanced-security/ghas-availability.md    |  10 +
 .../note-org-enable-uses-seats.md             |   2 +-
 .../security-feature-availability.md          |   1 +
 .../github-actions/example-github-runner.md   |   2 +-
 .../github-actions/java-jvm-architecture.md   |   2 +-
 .../data/reusables/organizations/people.md    |   2 +-
 .../pages/twenty-minutes-to-publish.md        |   2 +-
 .../reusables/repositories/actions-tab.md     |   2 +-
 .../private_forks_inherit_permissions.md      |   2 +-
 .../partner-secret-list-private-repo.md       |  12 +-
 .../user_settings/appearance-settings.md      |   3 +
 .../enabling-fixed-width-fonts.md             |   5 +
 .../webhooks/issue_event_api_properties.md    |   6 +-
 .../pull_request_event_api_properties.md      |   6 +-
 translations/pt-BR/data/ui.yml                |   2 +
 translations/pt-BR/data/variables/product.yml |   2 -
 104 files changed, 1174 insertions(+), 647 deletions(-)
 create mode 100644 translations/pt-BR/content/actions/learn-github-actions/creating-starter-workflows-for-your-organization.md
 create mode 100644 translations/pt-BR/content/actions/learn-github-actions/using-starter-workflows.md
 create mode 100644 translations/pt-BR/content/codespaces/developing-in-codespaces/default-environment-variables-for-your-codespace.md
 create mode 100644 translations/pt-BR/data/features/enterprise-owners-visible-for-org-members.yml
 create mode 100644 translations/pt-BR/data/features/fixed-width-font-gfm-fields.yml
 create mode 100644 translations/pt-BR/data/reusables/advanced-security/ghas-availability.md
 create mode 100644 translations/pt-BR/data/reusables/advanced-security/security-feature-availability.md
 create mode 100644 translations/pt-BR/data/reusables/user_settings/appearance-settings.md
 create mode 100644 translations/pt-BR/data/reusables/user_settings/enabling-fixed-width-fonts.md

diff --git a/translations/log/pt-resets.csv b/translations/log/pt-resets.csv
index 79f3895574d6..05f819483409 100644
--- a/translations/log/pt-resets.csv
+++ b/translations/log/pt-resets.csv
@@ -33,6 +33,7 @@ translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-gith
 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
@@ -97,7 +98,7 @@ translations/pt-BR/content/actions/hosting-your-own-runners/using-self-hosted-ru
 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-workflow-templates.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
@@ -110,7 +111,7 @@ translations/pt-BR/content/actions/learn-github-actions/reusing-workflows.md,ren
 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-workflow-templates.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
@@ -269,6 +270,7 @@ translations/pt-BR/content/admin/overview/about-enterprise-accounts.md,rendering
 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
@@ -413,6 +415,7 @@ translations/pt-BR/content/code-security/code-scanning/using-codeql-code-scannin
 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
@@ -441,6 +444,7 @@ translations/pt-BR/content/codespaces/customizing-your-codespace/setting-your-ti
 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
@@ -460,6 +464,7 @@ translations/pt-BR/content/codespaces/setting-up-your-project-for-codespaces/set
 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
@@ -641,18 +646,22 @@ translations/pt-BR/content/github/site-policy/guide-to-submitting-a-dmca-counter
 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
@@ -666,8 +675,10 @@ translations/pt-BR/content/issues/organizing-your-work-with-project-boards/manag
 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
@@ -700,10 +711,12 @@ translations/pt-BR/content/organizations/granting-access-to-your-organization-wi
 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
@@ -772,6 +785,8 @@ translations/pt-BR/content/organizations/restricting-access-to-your-organization
 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
@@ -788,12 +803,14 @@ translations/pt-BR/content/pages/configuring-a-custom-domain-for-your-github-pag
 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
@@ -827,7 +844,9 @@ translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/propos
 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
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 dcf87636030a..d8335fc89f6f 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
@@ -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/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 ad89e7310248..08fa6a78913b 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
@@ -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/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 89dca98c00cb..28c8a5dcf863 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,6 +1,7 @@
 ---
-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)".'
+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."
 redirect_from:
   - /articles/viewing-people-s-roles-in-an-organization
   - /articles/viewing-peoples-roles-in-an-organization
@@ -13,16 +14,53 @@ versions:
   ghec: '*'
 topics:
   - Accounts
-shortTitle: Visualizar pessoas em uma organização
+shortTitle: View people in an organization
 ---
 
+## View organization roles
+
+{% 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)
+
+{% 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 %}
 
-**Observação:** você precisa ser integrante da organização para ver as funções das pessoas na sua organização.
+**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** |
+|----|----|----|----|
+| 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. |
+
+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. 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)
+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
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 393d8c7c6096..5c660e6ecb4d 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
@@ -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/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 e064761894fb..ccf04b5c79d6 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
@@ -40,11 +40,11 @@ We recommend that you have a basic understanding of Java and the Ant framework.
 
 {% 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. For more information, see the "[{% data variables.product.prodname_actions %} quickstart](/actions/quickstart)."
 
 You can also add this workflow manually by creating a new file in the `.github/workflows` directory of your repository.
 
@@ -76,7 +76,7 @@ This workflow performs the following steps:
 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.
 
-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 %}
 
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 74fb4ffb74e7..53d817480689 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
@@ -40,11 +40,11 @@ We recommend that you have a basic understanding of Java and the Gradle framewor
 
 {% 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. For more information, see the "[{% data variables.product.prodname_actions %} quickstart](/actions/quickstart)."
 
 You can also add this workflow manually by creating a new file in the `.github/workflows` directory of your repository.
 
@@ -79,7 +79,7 @@ This workflow performs the following steps:
 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.
 
-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 %}
 
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 a8403ce752a3..bc44e08de5a3 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
@@ -40,11 +40,11 @@ We recommend that you have a basic understanding of Java and the Maven framework
 
 {% 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. For more information, see the "[{% data variables.product.prodname_actions %} quickstart](/actions/quickstart)."
 
 You can also add this workflow manually by creating a new file in the `.github/workflows` directory of your repository.
 
@@ -76,7 +76,7 @@ This workflow performs the following steps:
 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.
 
-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 %}
 
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 ba114a3e7400..774d75755679 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
@@ -28,11 +28,11 @@ You should already be familiar with YAML syntax and how it's used with {% data v
 
 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).
 
-## 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
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 8460d3973098..ecb2e61aa864 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
@@ -36,11 +36,11 @@ We recommend that you have a basic understanding of Node.js, YAML, workflow conf
 
 {% 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. The workflow shown below assumes that the default branch for your repository is `main`.
 
 {% raw %}
 ```yaml{:copy}
@@ -81,7 +81,7 @@ The easiest way to specify a Node.js version is by using the `setup-node` action
 
 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`.
 
-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. 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.
 
 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)."
 
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 bdbeef71ff49..c67f6a545b7f 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
@@ -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/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 6da09a7717a9..09d888b8394a 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
@@ -29,11 +29,11 @@ We recommend that you have a basic understanding of Ruby, YAML, workflow configu
 - [Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)
 - [Ruby in 20 minutes](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. The workflow shown below assumes that the default branch for your repository is `main`.
 
 ```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 8bbcaef74718..c343875e70cf 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
@@ -31,11 +31,11 @@ You should already be familiar with YAML syntax and how it's used with {% data v
 
 We recommend that you have a basic understanding of Swift packages. For more information, see "[Swift Packages](https://developer.apple.com/documentation/swift_packages)" in the Apple developer documentation.
 
-## Starting with the Swift workflow template
+## 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}
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 72621a7252ee..be64353589b5 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
@@ -37,9 +37,9 @@ Once you complete this project, you should understand how to build your own Java
 
 Before you begin, you'll need to download Node.js and create a public {% data variables.product.prodname_dotcom %} repository.
 
-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)."
 
@@ -73,7 +73,7 @@ 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'
 ```
 
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 4e9757aec376..2c0ebd6eafa3 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
@@ -140,11 +140,11 @@ For more information on how to use context syntax, see "[Contexts](/actions/lear
 
 **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'
 ```
 
@@ -152,8 +152,8 @@ runs:
 
 **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`
 
@@ -167,7 +167,7 @@ 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'
@@ -175,7 +175,8 @@ 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()`.
+**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.
+
 Note that the `step` context is unavailable, as no steps have run yet.
 
 In this example, `cleanup.js` only runs on Linux-based runners:
@@ -193,7 +194,7 @@ 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'
 ```
@@ -202,7 +203,7 @@ The `post:` action always runs by default but you can override this using `post-
 
 ### `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()`.
+**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.
 
 For example, this `cleanup.js` will only run on Linux-based runners:
 
@@ -265,6 +266,35 @@ For more information, see "[`github context`](/actions/reference/context-and-exp
 **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.
 {% 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.
+
+{% 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`.
+
+ ```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 %}
+```
+
+**Example: Using status check functions**
+
+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.
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 cf534d337e6f..e941449aa814 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
@@ -40,7 +40,7 @@ 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 %}
 
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 d7dcd598529a..33a04c0e1847 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
@@ -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/pt-BR/content/actions/guides.md b/translations/pt-BR/content/actions/guides.md
index 3a445c387b5b..f6cec21fcb37 100644
--- a/translations/pt-BR/content/actions/guides.md
+++ b/translations/pt-BR/content/actions/guides.md
@@ -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/pt-BR/content/actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow.md b/translations/pt-BR/content/actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow.md
index 8b533bffd420..f744a1c36f13 100644
--- a/translations/pt-BR/content/actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow.md
+++ b/translations/pt-BR/content/actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow.md
@@ -70,8 +70,13 @@ These labels operate cumulatively, so a self-hosted runner’s labels must match
 
 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:
 
-{% 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.
+{% 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.
+- If the job remains queued for more than 24 hours, the job will fail.
+{% elsif ghes = 3.3 %}
+- {% data variables.product.prodname_dotcom %} first searches for a runner at the repository level, then at the organization level, 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.
diff --git a/translations/pt-BR/content/actions/index.md b/translations/pt-BR/content/actions/index.md
index 874053eb2b6b..8828a7a41ca7 100644
--- a/translations/pt-BR/content/actions/index.md
+++ b/translations/pt-BR/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:
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
new file mode 100644
index 000000000000..861365c0ec20
--- /dev/null
+++ b/translations/pt-BR/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 %}
+
+## Overview
+
+{% 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. 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.
+
+   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.
+
+   For example, this file named `octo-organization-ci.yml` demonstrates a basic workflow.
+
+   ```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. Create a metadata file inside the `workflow-templates` directory. The metadata file must have the same name as the workflow file, but instead of the `.yml` extension, it must be appended with `.properties.json`. For example, this file named `octo-organization-ci.properties.json` contains the metadata for a workflow file named `octo-organization-ci.yml`:
+   ```yaml
+   {
+       "name": "Octo Organization Workflow",
+       "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` - **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.
+
+To add another starter workflow, add your files to the same `workflow-templates` directory. For example:
+
+![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)."
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 2c8cd63dc3cc..43a4e14853a3 100644
--- a/translations/pt-BR/content/actions/learn-github-actions/expressions.md
+++ b/translations/pt-BR/content/actions/learn-github-actions/expressions.md
@@ -266,9 +266,9 @@ Creates a hash for any `package-lock.json` and `Gemfile.lock` files in the repos
 
 `hashFiles('**/package-lock.json', '**/Gemfile.lock')`
 
-## Job status check functions
+## 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)."
+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)".
 
 ### success
 
@@ -316,6 +316,32 @@ steps:
     if: {% raw %}${{ failure() }}{% endraw %}
 ```
 
+### Evaluate Status Explicitly
+
+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:
+
+#### 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.
+
 ## Object filters
 
 You can use the `*` syntax to apply a filter and select matching items in a collection.
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 e45322bcff4d..a6a2c0622676 100644
--- a/translations/pt-BR/content/actions/learn-github-actions/index.md
+++ b/translations/pt-BR/content/actions/learn-github-actions/index.md
@@ -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/pt-BR/content/actions/learn-github-actions/managing-complex-workflows.md b/translations/pt-BR/content/actions/learn-github-actions/managing-complex-workflows.md
index e44a1d367c85..ed8322bb5a08 100644
--- a/translations/pt-BR/content/actions/learn-github-actions/managing-complex-workflows.md
+++ b/translations/pt-BR/content/actions/learn-github-actions/managing-complex-workflows.md
@@ -170,7 +170,7 @@ To learn more about {% data variables.product.prodname_dotcom %}-hosted runner l
 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)."
 {% endif %}
 
-## Using a workflow template
+## Using starter workflows
 
 {% data reusables.actions.workflow-template-overview %}
 
@@ -178,7 +178,7 @@ You can configure environments with protection rules and secrets. Each job in a
 {% 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**.
+1. Under the name of the starter workflow you'd like to use, click **Set up this workflow**.
   ![Set up this workflow](/assets/images/help/settings/actions-create-starter-workflow.png)
 
 ## Next steps
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 9bf5bb7bdf8e..33a4d0e6a961 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
@@ -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
 
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 f48ee6acd800..7ce98f56132b 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 workflow templates, secrets, and self-hosted runners.'
+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:
@@ -17,11 +17,11 @@ type: how_to
 
 ## 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.
+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.
 
-## 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 %}
 
@@ -51,4 +51,4 @@ For more information, see "[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/pt-BR/content/actions/learn-github-actions/using-starter-workflows.md b/translations/pt-BR/content/actions/learn-github-actions/using-starter-workflows.md
new file mode 100644
index 000000000000..9af782bd9778
--- /dev/null
+++ b/translations/pt-BR/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. 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.
+
+## Further reading
+
+- "[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)"
+{% ifversion fpt or ghec %}
+- "[Managing billing for {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions)"
+{% endif %}
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 c0d591e31188..f3586ab25196 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
@@ -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/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 c55f5363fd82..da7ac4443b3c 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
@@ -39,8 +39,8 @@ This Markdown example adds a status badge for a branch with the name `feature-1`
 
 ## Using the `event` parameter
 
-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/pt-BR/content/actions/quickstart.md b/translations/pt-BR/content/actions/quickstart.md
index 38bf3fdf1346..28d20b78f782 100644
--- a/translations/pt-BR/content/actions/quickstart.md
+++ b/translations/pt-BR/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/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 60e791ab95e9..662d33b84ffa 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
@@ -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/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 6114f313f604..126b397d3aa0 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
@@ -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)."
 
@@ -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)."
 
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 d64daac515b3..7ee3e6fde674 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: 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.'
+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.'
 redirect_from:
   - /enterprise/admin/packages/configuring-packages-support-for-your-enterprise
   - /admin/packages/configuring-packages-support-for-your-enterprise
@@ -10,39 +10,43 @@ type: how_to
 topics:
   - Enterprise
   - Packages
-shortTitle: Configurar os ecossistemas dos pacotes
+shortTitle: Configure package ecosystems
 ---
 
 {% data reusables.package_registry.packages-ghes-release-stage %}
 
-## Habilitar ou desabilitar os ecossistemas de cada pacote
+## Enabling or disabling individual package ecosystems
 
-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.
+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. Em "Alternância de ecossistema", para cada tipo de pacote, selecione **habilitado**, **somente leitura** ou **Desabilitado**. ![Alternância de ecossistemas](/assets/images/enterprise/site-admin-settings/ecosystem-toggles.png)
+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 %}
 {% data reusables.enterprise_management_console.save-settings %}
 
 {% ifversion ghes = 3.0 or ghes > 3.0 %}
-## Conectar ao registro oficial do npm
+## Connecting to the official npm registry
 
-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.
+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.
 
-{% 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.
+{% 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.
 
-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:
+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:
 
-| Fonte                                              | Destino              | Porta   | Tipo  |
-| -------------------------------------------------- | -------------------- | ------- | ----- |
+| Source | Destination | Port | Type |
+|---|---|---|---|
 | {% data variables.product.prodname_ghe_server %} | `registry.npmjs.com` | TCP/443 | HTTPS |
 
-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/.
+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/.
+
+If you wish to enable npm upstream sources, select `Enabled` for `npm upstreaming`.
 
 {% endif %}
 
-## Próximas etapas
+## Next steps
 
-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)".
+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)."
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 e1586d12d05b..9fb394b311e3 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
@@ -42,7 +42,7 @@ Enterprise owners have complete control over the enterprise and can take every a
 
 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.
+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 members
 
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 bf886eac2f61..322a5f346e86 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
@@ -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 %}.
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 174275d17803..646ed3ccd55b 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
@@ -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/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 87ab284dc48f..92361d61a268 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: 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.'
+title: Securing your organization
+intro: 'You can use a number of {% data variables.product.prodname_dotcom %} features to help keep your organization secure.'
 permissions: Organization owners can configure organization security settings.
 versions:
   fpt: '*'
@@ -13,112 +13,129 @@ topics:
   - Dependencies
   - Vulnerabilities
   - Advanced Security
-shortTitle: Proteger a sua organização
+shortTitle: Secure your organization
 ---
 
-## 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)".
+## 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)."
 
-Alguns recursos de segurança estão disponíveis apenas {% ifversion fpt or ghec %}para repositórios públicos e para repositórios privados pertencentes a organizações com {% else %}se você tiver {% endif %}uma licença de {% data variables.product.prodname_advanced_security %}. {% data reusables.advanced-security.more-info-ghas %}
+{% data reusables.advanced-security.security-feature-availability %}
 
-## Gerenciando o acesso à sua organização
+## Managing access to your 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)".
+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)."
 
 {% ifversion fpt or ghes > 3.0 or ghec %}
 
-## Criando uma política de segurança padrão
+## Creating a default security policy
 
-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)."
+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)."
 
 {% endif %}
 
 {% ifversion fpt or ghes > 2.22 or ghae-issue-4864 or ghec %}
-## Gerenciar {% data variables.product.prodname_dependabot_alerts %} e o gráfico de dependências
+## Managing {% data variables.product.prodname_dependabot_alerts %} and the dependency graph
 
-{% ifversion fpt or ghec %}Por padrão, {% data variables.product.prodname_dotcom %} detecta vulnerabilidades nos repositórios públicos, gera {% data variables.product.prodname_dependabot_alerts %} e um gráfico de dependência. Você pode habilitar ou desabilitar {% data variables.product.prodname_dependabot_alerts %} e o gráfico de dependência de todos os repositórios privados da sua organização.
+{% ifversion fpt or ghec %}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.
 
-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**.
+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**.
 {% endif %}
 
 {% data reusables.dependabot.dependabot-alerts-beta %}
 {% data reusables.dependabot.dependabot-alerts-dependency-graph-enterprise %}
 
-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)".
+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)."
 {% endif %}
 
 {% ifversion fpt or ghes > 3.1 or ghae-issue-4864 or ghec %}
 
-## Gerenciando revisão de dependências
+## Managing 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.
-{% ifversion fpt or ghec %}A revisão de dependência está disponível em todos os repositórios públicos. Para repositórios privados e internos você precisa de uma licença para {% data variables.product.prodname_advanced_security %}. Para habilitar a revisão de dependências para uma organização, habilite o gráfico de dependências e habilite {% data variables.product.prodname_advanced_security %}.
-{% 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 %}
-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 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 %}
 
 {% endif %}
 
 {% ifversion fpt or ghec or ghes > 3.2 %}
-## Gerenciar {% data variables.product.prodname_dependabot_security_updates %}
+## Managing {% data variables.product.prodname_dependabot_security_updates %}
 
-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.
+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.
 
-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**.
+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**. 
 
-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)".
+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)."
 
-## Gerenciar {% data variables.product.prodname_dependabot_version_updates %}
+## Managing {% data variables.product.prodname_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)".
+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)."
 
-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)".
+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)."
 
 {% endif %}
 
-{% ifversion fpt or ghes > 2.22 or ghae or ghec %}
-## Gerenciar {% data variables.product.prodname_GH_advanced_security %}
+{% ifversion ghes > 2.22 or ghae or ghec %}
+## Managing {% data variables.product.prodname_GH_advanced_security %}
 
-{% ifversion fpt or ghes > 2.22 or ghec %}
-Se sua organização tiver uma licença de {% data variables.product.prodname_advanced_security %}, você poderá habilitar ou desabilitar funcionalidades de {% data variables.product.prodname_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.
 {% elsif ghae %}
-Você pode habilitar ou desabilitar funcionalidades de {% data variables.product.prodname_advanced_security %}.
+You can enable or disable {% data variables.product.prodname_advanced_security %} features.
+{% 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**. 
+
+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 %}
 
-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**.
+{% 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 an {% data variables.product.prodname_advanced_security %} feature that scans repositories for secrets that are insecurely stored.
 
-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)".
+{% 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 %}
 
-## Configurar o {% data variables.product.prodname_secret_scanning %}
-{% data variables.product.prodname_secret_scanning_caps %} está disponível {% ifversion fpt or ghec %}para todos os repositórios públicos e para repositórios privados pertencentes a organizações com {% else %}se você tiver {% endif %}uma licença de {% data variables.product.prodname_advanced_security %}.
+{% ifversion ghes or ghae %}{% data variables.product.prodname_secret_scanning_caps %} is available if your enterprise uses {% data variables.product.prodname_advanced_security %}.{% endif %}
 
-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.
+{% 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. 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 %}**.
+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 %}**. 
 
-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)".
+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 %}
 
-## 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 %}
+## 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 %}
 
-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)."
+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)."
 
-{% 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)".
+{% 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)."
 {% 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 7cbdb8a96fa2..eb7b4888b26c 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
@@ -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)."
 
+{% 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_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**. 
+{% 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/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
new file mode 100644
index 000000000000..1eb32e030fc8
--- /dev/null
+++ b/translations/pt-BR/content/codespaces/developing-in-codespaces/default-environment-variables-for-your-codespace.md
@@ -0,0 +1,40 @@
+---
+title: Default environment variables for your codespace
+shortTitle: Default environment variables
+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
+
+| 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
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 0558dd88ff3e..64e671622bf7 100644
--- a/translations/pt-BR/content/codespaces/developing-in-codespaces/index.md
+++ b/translations/pt-BR/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/pt-BR/content/codespaces/troubleshooting/troubleshooting-codespaces-clients.md b/translations/pt-BR/content/codespaces/troubleshooting/troubleshooting-codespaces-clients.md
index 0e2ab64fbf63..e5460831a92a 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: 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.'
+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.'
 product: '{% data reusables.gated-features.codespaces %}'
 versions:
   fpt: '*'
@@ -8,19 +8,31 @@ versions:
 type: reference
 topics:
   - Codespaces
-shortTitle: Clientes de codespaces
+shortTitle: Codespaces clients
 ---
 
-## Solução de problemas de {% data variables.product.prodname_vscode %}
+## {% data variables.product.prodname_vscode %} troubleshooting
 
-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 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 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 %}.
+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.
 
-É 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).
+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.
 
-## Solução de problemas do navegador
+### {% data variables.product.prodname_vscode %} Insiders
 
-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).
+{% 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.
 
-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).
+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.
+
+## 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).
+
+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.
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 bdf4b1997dd2..8471eadaa4bf 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
@@ -70,7 +70,7 @@ Name | Description
 &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 %}
+**`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 %}
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 d99e76f16a62..c8b27e59dfad 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
@@ -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 %}
-
-{% ifversion not ghae %}
-## Enabling {% data variables.product.prodname_advanced_security %} features on {% data variables.product.prodname_dotcom_the_website %}
+{%- elsif ghec %}
+For public repositories these features are permanently on and can only be disabled if you change the visibility of the project so that the code is no longer public. 
 
-For public repositories 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. 
 
-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 %}
+{%- 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)."
 
-{% 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/pt-BR/content/get-started/quickstart/github-flow.md b/translations/pt-BR/content/get-started/quickstart/github-flow.md
index 0ae27c41792d..e555ed5d9f21 100644
--- a/translations/pt-BR/content/get-started/quickstart/github-flow.md
+++ b/translations/pt-BR/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/pt-BR/content/get-started/quickstart/set-up-git.md b/translations/pt-BR/content/get-started/quickstart/set-up-git.md
index 2b916a6abb01..f8272f9fc359 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
@@ -40,6 +40,16 @@ If you don't need to work with files locally, {% data variables.product.product_
 ## Setting up Git
 
 1. [Download and install the latest version of 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. 
+
+{% 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).
 
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 9d4bd93d2bf2..e2b617a11c78 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: 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.'
+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.'
 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,24 +10,26 @@ versions:
 topics:
   - Policy
   - Legal
-shortTitle: Gerenciar o uso de dados para repositório privado
+shortTitle: Manage data use for private repo
 ---
 
-## Sobre o uso de dados para seu repositório privado
+## About data use for your private repository
 
-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)"
+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)."
 
-## Habilitar ou desabilitar os recursos de uso de dados
+## Enabling or disabling data use features
 
 {% 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. 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-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 %}
 
-## Leia mais
+## Further reading
 
-- "[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)"
+- "[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)"
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 3859db5fec97..f9a01951007b 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: 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.
+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.
 redirect_from:
   - /articles/about-writing-and-formatting-on-github
   - /github/writing-on-github/about-writing-and-formatting-on-github
@@ -9,24 +9,36 @@ versions:
   ghes: '*'
   ghae: '*'
   ghec: '*'
-shortTitle: Escrever & formatar no GitHub
+shortTitle: Write & format on GitHub
 ---
+[Markdown](http://daringfireball.net/projects/markdown/) is an easy-to-read, easy-to-write syntax for formatting plain text.
 
-[Markdown](http://daringfireball.net/projects/markdown/) é uma sintaxe de leitura e gravação fáceis para formatação de texto sem formatação.
+We've added some custom functionality to create {% data variables.product.prodname_dotcom %} Flavored Markdown, used to format prose and code across our site.
 
-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.
+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).
 
-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).
+## Text formatting toolbar
 
-## Barra de ferramentas de formatação de texto
+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.
 
-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 %}
 
-![Barra de ferramentas de markdown](/assets/images/help/writing/markdown-toolbar.gif)
+## 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.
 
-## Leia mais
+![Screenshot showing the {% data variables.product.product_name %} comment field with fixed-width fonts enabled](/assets/images/help/writing/fixed-width-example.png)
 
-- [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/)"
+{% 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 %}
+
+## 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/)"
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 5753951e64b4..f3c22ea38e68 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
@@ -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/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 ae7da47bf1be..71616f8e104e 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: 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.
+title: Creating and highlighting code blocks
+intro: Share samples of code with fenced code blocks and enabling syntax highlighting.
 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: Crie blocos de código
+shortTitle: Create code blocks
 ---
 
-## Blocos de código isolados
+## Fenced code blocks
 
-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.
+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.
 
 <pre>
 ```
@@ -24,48 +24,48 @@ function test() {
 ```
 </pre>
 
-![Bloco de código isolado renderizado](/assets/images/help/writing/fenced-code-block-rendered.png)
+![Rendered fenced code block](/assets/images/help/writing/fenced-code-block-rendered.png)
 
 {% tip %}
 
-**Dica:** para preservar sua formatação em uma lista, certifique-se de recuar blocos de código não isolados em oito espaços.
+**Tip:** To preserve your formatting within a list, make sure to indent non-fenced code blocks by eight spaces.
 
 {% endtip %}
 
-Para mostrar aspas tripas em um bloco de código isolado, envolva-os dentro de aspas quádruplas.
+To display triple backticks in a fenced code block, wrap them inside quadruple backticks.
 
 
 <pre>
 ```` 
 ```
-Look! Você pode ver minhas aspas.
+Look! You can see my backticks.
 ```
 ````
 </pre>
 
-![Código isolado interpretado como um bloco de aspas inversas](/assets/images/help/writing/fenced-code-show-backticks-rendered.png)
+![Rendered fenced code with backticks block](/assets/images/help/writing/fenced-code-show-backticks-rendered.png)
 
+{% data reusables.user_settings.enabling-fixed-width-fonts %}
 
-## Realce de sintaxe
+## Syntax highlighting
 
 <!-- If you make changes to this feature, update /getting-started-with-github/github-language-support to reflect any changes to supported languages. -->
 
-Você pode adicionar um identificador de linguagem opcional para habilitar o realce de sintaxe no bloco de código isolado.
+You can add an optional language identifier to enable syntax highlighting in your fenced code block.
 
-Por exemplo, para código Ruby do realce de sintaxe:
+For example, to syntax highlight Ruby code:
 
     ```ruby
     require 'redcarpet'
     markdown = Redcarpet.new("Hello World!")
     puts markdown.to_html
-    coloca markdown.to_html
     ```
 
-![Bloco de código renderizado com realce de sintaxe Ruby](/assets/images/help/writing/code-block-syntax-highlighting-rendered.png)
+![Rendered code block with Ruby syntax highlighting](/assets/images/help/writing/code-block-syntax-highlighting-rendered.png)
 
-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).
+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).
 
-## Leia mais
+## Further reading
 
-- [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)"
+- [{% data variables.product.prodname_dotcom %} Flavored Markdown Spec](https://github.github.com/gfm/)
+- "[Basic writing and formatting syntax](/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 67b2c462ccb6..4c5738d5f522 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: Organizar informações com tabelas
-intro: 'Você pode criar tabelas para organizar as informações em comentários, problemas, pull requests e wikis.'
+title: Organizing information with tables
+intro: 'You can build tables to organize information in comments, issues, pull requests, and wikis.'
 redirect_from:
   - /articles/organizing-information-with-tables
   - /github/writing-on-github/organizing-information-with-tables
@@ -9,72 +9,73 @@ versions:
   ghes: '*'
   ghae: '*'
   ghec: '*'
-shortTitle: Dados organizados com tabelas
+shortTitle: Organized data with tables
 ---
+## Creating a table
 
-## 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.
+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.
 
 ```markdown
 
-| 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 |
+| First Header  | Second Header |
+| ------------- | ------------- |
+| Content Cell  | Content Cell  |
+| Content Cell  | Content Cell  |
 ```
 
-![Tabela construída](/assets/images/help/writing/table-basic-rendered.png)
+![Rendered table](/assets/images/help/writing/table-basic-rendered.png)
 
-As barras verticais em cada extremo da tabela são opcionais.
+The pipes on either end of the table are optional.
 
-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.
+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.
 
 ```markdown
-| Comando | Descrição |
+| Command | Description |
 | --- | --- |
-| git status | Lista de todos os arquivos modificados ou novos |
-| git diff | Mostra as diferenças do arquivo que não foram preparadas |
+| git status | List all new or modified files |
+| git diff | Show file differences that haven't been staged |
 ```
 
-![Tabela construída com largura de célula variada](/assets/images/help/writing/table-varied-columns-rendered.png)
+![Rendered table with varied cell width](/assets/images/help/writing/table-varied-columns-rendered.png)
+
+{% data reusables.user_settings.enabling-fixed-width-fonts %}
 
-## Formatar conteúdo dentro da tabela
+## Formatting content 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:
+You can use [formatting](/articles/basic-writing-and-formatting-syntax) such as links, inline code blocks, and text styling within your table:
 
 ```markdown
-| Comando | Descrição |
+| Command | Description |
 | --- | --- |
-| `git status` | Lista de todos os arquivos *modificados ou novos* |
-| `git diff` | Mostra as diferenças do arquivo que **não foram** preparadas |
+| `git status` | List all *new or modified* files |
+| `git diff` | Show file differences that **haven't been** staged |
 ```
 
-![Tabela construída com texto formatado](/assets/images/help/writing/table-inline-formatting-rendered.png)
+![Rendered table with formatted text](/assets/images/help/writing/table-inline-formatting-rendered.png)
 
-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.
+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
-|   Esquerda   |  Centralizado  |    Direita    |
+| Left-aligned | Center-aligned | Right-aligned |
 | :---         |     :---:      |          ---: |
 | git status   | git status     | git status    |
 | git diff     | git diff       | git diff      |
 ```
 
-![Tabela construída com alinhamento de texto à esquerda, centralizado e à direita](/assets/images/help/writing/table-aligned-text-rendered.png)
+![Rendered table with left, center, and right text alignment](/assets/images/help/writing/table-aligned-text-rendered.png)
 
-Para incluir uma barra vertical `|` como conteúdo dentro de sua célula, use `\` antes da barra vertical:
+To include a pipe `|` as content within your cell, use a `\` before the pipe:
 
 ```markdown
-| Nome   | Caractere |
-| ---    | ---       |
-| Crase  | `         |
-| Barra  | \|        |
+| Name     | Character |
+| ---      | ---       |
+| Backtick | `         |
+| Pipe     | \|        |
 ```
 
-![Tabela construída com barra vertical solta](/assets/images/help/writing/table-escaped-character-rendered.png)
+![Rendered table with an escaped pipe](/assets/images/help/writing/table-escaped-character-rendered.png)
 
-## Leia mais
+## Further reading
 
-- [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)"
+- [{% data variables.product.prodname_dotcom %} Flavored Markdown Spec](https://github.github.com/gfm/)
+- "[Basic writing and formatting syntax](/articles/basic-writing-and-formatting-syntax)"
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 868b241f5917..4dbbbda93125 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
@@ -20,7 +20,7 @@ When you close a project board, any configured workflow automation will pause by
 
 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)."
 
-1. Navigate to list of project boards in your repository or organization, or owned by your user account.
+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**.
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 e205e503c695..b290d300bc7d 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: Reabrir um quadro de projeto fechado
-intro: Você pode reabrir um quadro de projeto reaberto e reiniciar qualquer automação do fluxo de trabalho que tenha sido configurada para o quadro de projeto.
+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.
 redirect_from:
   - /github/managing-your-work-on-github/managing-project-boards/reopening-a-closed-project-board
   - /articles/reopening-a-closed-project-board
@@ -12,21 +12,22 @@ versions:
   ghec: '*'
 topics:
   - Pull requests
-shortTitle: Reabrir quadro de projeto
+shortTitle: Reopen project board
 ---
-
 {% data reusables.projects.project_boards_old %}
 
-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 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ê 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.
+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. Navegue até o quadro de projeto que deseja reabrir.
+1. Navigate to the project board you want to reopen.
 {% data reusables.project-management.click-menu %}
-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)
+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)
 
-## Leia mais
+## Further reading
 
-- "[Configurar a automação para quadros de projeto](/articles/configuring-automation-for-project-boards)"
+- "[Configuring automation for project boards](/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/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 06fcd9ce6a8f..b7d8e6e244e6 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: 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.
+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.
 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,20 +12,23 @@ versions:
   ghec: '*'
 topics:
   - Pull requests
-shortTitle: Arquivar cartões no quadro
+shortTitle: Archive cards on board
 ---
-
 {% data reusables.projects.project_boards_old %}
 
-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.
+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.
 
-## Arquivar cartões em um quadro de projeto
+## Archiving cards on a project board
 
-1. Em um quadro de projeto, encontre o cartão que desejar 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)
+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)
 
-## Restaurar cartões em um quadro de projeto usando a barra lateral
+## Restoring cards on a project board from the sidebar
 
 {% data reusables.project-management.click-menu %}
-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)
+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)
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 cb346ba1815a..d4ad5f88aee8 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
@@ -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/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 6f847a592769..2b2ad52ec4ca 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
@@ -234,4 +234,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/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 e68a41f2ed1d..c3e5acb97476 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
@@ -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/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 07843a55d942..4b00391366db 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
@@ -310,7 +310,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.
+A project may contain items that a user does not have permission to view. In this case, the response will include a redacted item.
 
 ```shell
 {
@@ -373,7 +373,7 @@ 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
 
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 34080c82cb78..3053a0a101b5 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: 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 %}.'
+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 %}.'
 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,146 +13,164 @@ versions:
 topics:
   - Organizations
   - Teams
-shortTitle: Gerenciar segurança & análise
+shortTitle: Manage security & analysis
 ---
 
-## Sobre a gestão de configurações de segurança e análise
+## About management of security and analysis settings
 
-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 fpt or 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 %}
+{% 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 %}
 
-## Exibir as configurações de segurança e análise
+## Displaying the security and analysis settings
 
 {% data reusables.profile.access_org %}
 {% data reusables.profile.org_settings %}
 {% data reusables.organizations.security-and-analysis %}
 
-A página exibida permite que você habilite ou desabilite todas as funcionalidades de segurança e análise dos repositórios na sua organização.
+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 %}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 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 %}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 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 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 %}
+{% 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 %}
 
-## Habilitar ou desabilitar um recurso para todos os repositórios existentes
+## Enabling or disabling a feature for all existing repositories
 
-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:
+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:
 
-- **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.
-- **{% 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 %}
+- **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 %}
+
+{% endif %}
 
 {% data reusables.advanced-security.note-org-enable-uses-seats %}
 
-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 fpt or 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 or ghec %}
-   ![Botão "Habilitar tudo" ou "Desabilitar tudo" para os recursos de "Configurar segurança e análise"](/assets/images/help/organizations/security-and-analysis-disable-or-enable-all-ghas-dotcom.png)
+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 %}
+   {% 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 %}
-   ![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)
+   !["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)
    {% endif %}
    {% ifversion ghes = 3.1 or ghes = 3.2 %}
-   ![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)
+   !["Enable all" or "Disable all" button for "Configure security and analysis" features](/assets/images/enterprise/3.1/help/organizations/security-and-analysis-disable-or-enable-all-ghas.png)
    {% endif %}
    {% ifversion ghes = 3.0 %}
-   ![Botão "Habilitar tudo" ou "Desabilitar tudo" para os recursos de "Configurar segurança e análise"](/assets/images/enterprise/3.0/organizations/security-and-analysis-disable-or-enable-all-ghas.png)
+   !["Enable all" or "Disable all" button for "Configure security and analysis" features](/assets/images/enterprise/3.0/organizations/security-and-analysis-disable-or-enable-all-ghas.png)
    {% endif %}
    {% ifversion ghae %}
-   ![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)
+   !["Enable all" or "Disable all" button for "Configure security and analysis" features](/assets/images/enterprise/github-ae/organizations/security-and-analysis-disable-or-enable-all-ghae.png)
    {% endif %}
    {% ifversion fpt or ghes = 3.0 or ghec %}
-3. Opcionalmente, habilite o recurso para novos repositórios na organização por padrão.
+3. Optionally, enable the feature by default for new repositories in your organization.
    {% ifversion fpt or ghec %}
-   ![Opção de "Habilitar por padrão" para novos repositórios](/assets/images/help/organizations/security-and-analysis-enable-by-default-in-modal.png)
+   !["Enable by default" option for new repositories](/assets/images/help/organizations/security-and-analysis-enable-by-default-in-modal.png)
    {% endif %}
    {% ifversion ghes = 3.0 %}
-   ![Opção de "Habilitar por padrão" para novos repositórios](/assets/images/enterprise/3.0/organizations/security-and-analysis-secret-scanning-enable-by-default.png)
+   !["Enable by default" option for new repositories](/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. Clique em **Desabilitar RECURSO** ou **Habilitar RECURSO** para desabilitar ou habilitar o recurso para todos os repositórios da sua organização.
+4. Click **Disable FEATURE** or **Enable FEATURE** to disable or enable the feature for all the repositories in your organization.
    {% ifversion fpt or ghec %}
-   ![Botão para desabilitar ou habilitar recurso](/assets/images/help/organizations/security-and-analysis-enable-dependency-graph.png)
+   ![Button to disable or enable feature](/assets/images/help/organizations/security-and-analysis-enable-dependency-graph.png)
    {% endif %}
    {% ifversion ghes = 3.0 %}
-   ![Botão para desabilitar ou habilitar recurso](/assets/images/enterprise/3.0/organizations/security-and-analysis-enable-secret-scanning.png)
+   ![Button to disable or enable feature](/assets/images/enterprise/3.0/organizations/security-and-analysis-enable-secret-scanning.png)
    {% endif %}
    {% endif %}
    {% ifversion ghae or ghes > 3.0 %}
-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)
+3. Click **Enable/Disable all** or **Enable/Disable for eligible repositories** to confirm the change.
+   ![Button to enable feature for all the eligible repositories in the organization](/assets/images/enterprise/github-ae/organizations/security-and-analysis-enable-secret-scanning-existing-repos-ghae.png)
    {% endif %}
 
    {% data reusables.security.displayed-information %}
 
-## Habilitar ou desabilitar uma funcionalidade automaticamente quando novos repositórios forem adicionados
+## Enabling or disabling a feature automatically when new repositories are added
 
-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 or ghec %}
-   ![Caixa de seleção para habilitar ou desabilitar um recurso para novos repositórios](/assets/images/help/organizations/security-and-analysis-enable-or-disable-feature-checkbox-dotcom.png)
+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 %}
+   ![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 %}
-   ![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)
+   {% 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 %}
-   ![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)
+   ![Checkbox for enabling or disabling a feature for new repositories](/assets/images/enterprise/3.1/help/organizations/security-and-analysis-enable-or-disable-feature-checkbox.png)
    {% endif %}
    {% ifversion ghes = 3.0 %}
-   ![Caixa de seleção para habilitar ou desabilitar um recurso para novos repositórios](/assets/images/enterprise/3.0/organizations/security-and-analysis-enable-or-disable-secret-scanning-checkbox.png)
+   ![Checkbox for enabling or disabling a feature for new repositories](/assets/images/enterprise/3.0/organizations/security-and-analysis-enable-or-disable-secret-scanning-checkbox.png)
    {% endif %}
    {% ifversion ghae %}
-   ![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)
+   ![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 -->
 
-## Permitir que {% data variables.product.prodname_dependabot %} acesse dependências privadas
+## Allowing {% data variables.product.prodname_dependabot %} to access private dependencies
 
-{% 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)".
+{% 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)."
 
-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.
+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.
 
-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)".
+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)."
 
-Para permitir que {% data variables.product.prodname_dependabot %} acesse um repositório privado de {% data variables.product.prodname_dotcom %}:
+To allow {% data variables.product.prodname_dependabot %} to access a private {% data variables.product.prodname_dotcom %} repository:
 
-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. 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. 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)
+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)
 {% endif %}
 
-{% ifversion fpt or ghes > 3.0 or ghec %}
+{% ifversion ghes > 3.0 or ghec %}
 
-## Remover acesso a {% data variables.product.prodname_GH_advanced_security %} de repositórios individuais em uma organização
+## Removing access to {% data variables.product.prodname_GH_advanced_security %} from individual repositories in an 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.
+You can manage access to {% data variables.product.prodname_GH_advanced_security %} features for a repository from its "Settings" tab. For more information, see "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)." However, you can also disable {% data variables.product.prodname_GH_advanced_security %} features for a repository from the "Settings" tab for the organization.
 
-1. 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 %}.
+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 %}.
 
 {% note %}
 
-**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.
+**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.
 
 {% endnote %}
 
 {% endif %}
 
-## Leia mais
+## Further reading
 
-- "[Protegendo o seu repositório](/code-security/getting-started/securing-your-repository)"
-- "[Sobre a varredura de segredos](/github/administering-a-repository/about-secret-scanning)"{% ifversion fpt or ghec %}
-- "[Manter as suas dependências atualizadas automaticamente](/github/administering-a-repository/keeping-your-dependencies-updated-automatically)"{% 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 %}
+- "[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 %}
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 08a2b3eb702e..c6eb09d51919 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
@@ -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 %}
@@ -662,15 +662,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 +697,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/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 7a0e4bbd0d08..0a64d782c971 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
@@ -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** |
@@ -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/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 5da023dcd8eb..ad9f8d0d0002 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
@@ -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/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 e74604311164..761cda09ece3 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
@@ -47,7 +47,7 @@ To use or manage a package hosted by a package registry, you must use a token wi
 
 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 %}."
+- {% 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 %}."
 
 | Scope | Description | Required permission |
 | --- | --- | --- |
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 713c26fdaa89..b1e3ac123094 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,35 +1,38 @@
 ---
-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 %}.'
+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 %}.'
 product: '{% data reusables.gated-features.packages %}'
 versions:
   ghes: '>=2.22 <3.1'
-  ghae: '*'
 ---
 
 {% data reusables.package_registry.packages-ghes-release-stage %}
 {% data reusables.package_registry.packages-ghae-release-stage %}
 
-{% 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 %}
+{% ifversion not ghae %}At this time, {% data variables.product.prodname_registry %} on {% data variables.product.product_location %} does not support deleting public packages.{% endif %}
 
-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.
+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.
 
-## Excluir uma versão de um pacote {% ifversion not ghae %}privado {% endif %}em {% data variables.product.product_name %}
+## Deleting a version of a {% ifversion not ghae %}private {% endif %}package on {% data variables.product.product_name %}
 
-Para excluir uma {% ifversion not ghae %}versão do pacote privado {% endif %}, é necessário ter permissões de administrador no repositório.
+To delete a {% ifversion not ghae %}private {% endif %}package version, you must have admin permissions in the repository.
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.package_registry.packages-from-code-tab %}
-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)
+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)
 
-## Excluindo uma versão de um {% ifversion not ghae %}pacote privado {% endif %}com o GraphQL
+## Deleting a version of a {% ifversion not ghae %}private {% endif %}package with GraphQL
 
-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)."
+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)." 
 
-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.
+Here is an example cURL command to delete a package version with the package version ID of `MDIyOlJlZ2lzdHJ5UGFja2FnZVZlcnNpb243MTExNg`, using a personal access token.
 
 ```shell
 curl -X POST \
@@ -39,8 +42,8 @@ curl -X POST \
 HOSTNAME/graphql
 ```
 
-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.
+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 obter mais informações sobre a mutação `deletePackageVersion`, consulte "[`deletePackageVersion`](/graphql/reference/mutations#deletepackageversion)".
+For more information about the `deletePackageVersion` mutation, see "[`deletePackageVersion`](/graphql/reference/mutations#deletepackageversion)."
 
-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 %}.
+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 %}.
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 3020efae0f89..26d0725a9ba0 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: Excluir e restaurar um pacote
-intro: Saiba como excluir ou restaurar um pacote.
+title: Deleting and restoring a package
+intro: Learn how to delete or restore a package.
 product: '{% data reusables.gated-features.packages %}'
 redirect_from:
   - /github/managing-packages-with-github-packages/deleting-a-package
@@ -11,84 +11,91 @@ versions:
   fpt: '*'
   ghes: '>=3.1'
   ghec: '*'
-shortTitle: Excluir & restaurar um pacote
+  ghae: '*'
+shortTitle: Delete & restore a package
 ---
 
 {% data reusables.package_registry.packages-ghes-release-stage %}
 
-## Exclusão de pacote e suporte de restauração em {% data variables.product.prodname_dotcom %}
+## Package deletion and restoration support on {% data variables.product.prodname_dotcom %}
 
-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
+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
 
 {% note %}
 
-**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.
+**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.
 
 {% endnote %}
 
-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.
+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.
 
-## Suporte de API de pacotes
+{% ifversion fpt or ghec or ghes %}
+## Packages API support
 
 {% ifversion fpt or ghec %}
 
-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)".
+You can use the REST API to manage your packages. For more information, see the "[{% data variables.product.prodname_registry %} API](/rest/reference/packages)."
 
 {% endif %}
 
-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 %} A {% data variables.product.prodname_registry %} API do GraphQL API não é compatível com contêineres ou imagens Docker que usam o namespace do pacote `https://ghcr.io/OWNER/PACKAGE-NAME`. Para obter mais informações sobre o suporte do GraphQL, consulte "[Excluir uma versão de um pacote com escopo de repositório com 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 %}
 
-## Permissões necessárias para excluir ou restaurar um pacote
+## Required permissions to delete or restore a package
 
-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.
+For packages that inherit their access permissions from repositories, you can delete a package if you have admin permissions to the repository.
 
-Os pacotes com escopo de repositório em {% data variables.product.prodname_registry %} incluem estes pacotes:
+Repository-scoped packages on {% data variables.product.prodname_registry %} include these packages:
 - npm
 - RubyGems
 - maven
 - Gradle
 - NuGet
-{% ifversion not fpt or ghec %}- Imagens do Docker em `docker.pkg.github.com/OWNER/REPOSITORY/IMAGE-NAME`{% endif %}
+{% ifversion not fpt or ghec %}- Docker images at `docker.pkg.github.com/OWNER/REPOSITORY/IMAGE-NAME`{% endif %}
 
 {% ifversion fpt or ghec %}
 
-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.
- <!--PLACEHOLDER - once packages restructuring is done this is a good place to link to the access control and visibility article.-->
+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)."
 
 {% endif %}
 
-## Excluir a versão de um pacote
+## Deleting a package version
 
-### Excluir uma versão de um pacote com escopo de repositório em {% data variables.product.prodname_dotcom %}
+### Deleting a version of a repository-scoped package on {% data variables.product.prodname_dotcom %}
 
-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)".
+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)."
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.package_registry.packages-from-code-tab %}
 {% data reusables.package_registry.package-settings-option %}
-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)
+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)
 
-### Excluir uma versão de um pacote com escopo do repositório com o GraphQL
+{% ifversion fpt or ghec or ghes %}
+### Deleting a version of a repository-scoped package with GraphQL
 
-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.
+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 %}
-O GraphQL não é compatível com contêineres ou imagens Docker em `ghcr.io`.
-{% 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 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)."
+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 %}
+
+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)."
 
-O exemplo a seguir demonstra como excluir uma versão do pacote, usando um `packageVersionId` de `MDIyOlJlZ2lzdHJ5UGFja2FnZVZlcnNpb243MTExNg`.
+The following example demonstrates how to delete a package version, using a `packageVersionId` of `MDIyOlJlZ2lzdHJ5UGFja2FnZVZlcnNpb243MTExNg`.
 
 ```shell
 curl -X POST \
@@ -98,121 +105,148 @@ 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 `registryPackagesForQuery` connection. 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.
+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.
 
-Para obter mais informações sobre a mutação `deletePackageVersion`, consulte "[`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)."
 
-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 %}.
+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 %}
-### Excluindo uma versão de pacote com escopo do usuário em {% data variables.product.prodname_dotcom %}
+### Deleting a version of a user-scoped package on {% data variables.product.prodname_dotcom %}
 
-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 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 revisar quem pode excluir uma versão de pacote, consulte "[Permissões necessárias](#required-permissions-to-delete-or-restore-a-package)".
+To review who can delete a package version, see "[Required permissions](#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. À 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)
+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)
 
-### Excluir uma versão de um pacote com escopo da organização no GitHub
+### Deleting a version of an organization-scoped package on {% data variables.product.prodname_dotcom %}
 
-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 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 revisar quem pode excluir uma versão de pacote, consulte "[Permissões necessárias](#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 %}
-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)
+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)
 {% endif %}
 
-## Excluindo um pacote inteiro
+## Deleting an entire package
 
-### Excluindo um pacote com escopo de repositório completo em {% data variables.product.prodname_dotcom %}
+### Deleting an entire repository-scoped package on {% data variables.product.prodname_dotcom %}
 
-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)".
+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)."
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.package_registry.packages-from-code-tab %}
 {% data reusables.package_registry.package-settings-option %}
-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)
+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)
 
 {% ifversion fpt or ghec %}
-### Excluir um pacote inteiro com escopo do usuário em {% data variables.product.prodname_dotcom %}
+### Deleting an entire user-scoped package on {% data variables.product.prodname_dotcom %}
 
-Para revisar quem pode excluir um pacote, consulte "[Permissões necessárias](#required-permissions-to-delete-or-restore-a-package)".
+To review who can delete a package, see "[Required permissions](#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. À 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)
+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)
 
-### Excluir um pacote inteiro com escopo da organização em {% data variables.product.prodname_dotcom %}
+### Deleting an entire organization-scoped package on {% data variables.product.prodname_dotcom %}
 
-Para revisar quem pode excluir um pacote, consulte "[Permissões necessárias](#required-permissions-to-delete-or-restore-a-package)".
+To review who can delete a package, see "[Required permissions](#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. À 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)
+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)
 {% endif %}
 
-## Restaurando pacotes
+## Restoring packages
 
-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.
+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.
 
-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.
+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.
 
-Você também deve atender a um destes requisitos de permissão:
-  - 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 %}
+{% 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 %}
 
-Para obter mais informações, consulte "[Permissões necessárias](#required-permissions-to-delete-or-restore-a-package)".
+For more information, see "[Required permissions](#required-permissions-to-delete-or-restore-a-package)."
 
-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.
+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.
 
-### Restaurando um pacote de uma organização
+### Restoring a package in an organization
 
-Você pode restaurar um pacote excluído por meio das configurações da conta da sua organização, desde que o pacote esteja em um dos seus repositórios{% ifversion fpt or ghec %} ou tenha permissões granulares e tenha o escopo na conta da organização{% 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 %}.
 
-Para revisar quem pode restaurar um pacote em uma organização, consulte "[Permissões necessárias](#required-permissions-to-delete-or-restore-a-package)".
+To review who can restore a package in an organization, see "[Required permissions](#required-permissions-to-delete-or-restore-a-package)."
 
 {% data reusables.organizations.navigate-to-org %}
 {% data reusables.organizations.org_settings %}
-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)
+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)
 
 {% ifversion fpt or ghec %}
 
-### Restaurar um pacote com escopo de conta de usuário
+### Restoring a user-account scoped 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)".
+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)."
 
 {% data reusables.user_settings.access_settings %}
-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)
+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)
 
 {% endif %}
 
-### Restaurando uma versão do pacote
+### Restoring a package version
 
-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)".
+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)."
 
-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)
+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)
diff --git a/translations/pt-BR/content/packages/learn-github-packages/introduction-to-github-packages.md b/translations/pt-BR/content/packages/learn-github-packages/introduction-to-github-packages.md
index 63268fe2a232..aa1182e2f8cf 100644
--- a/translations/pt-BR/content/packages/learn-github-packages/introduction-to-github-packages.md
+++ b/translations/pt-BR/content/packages/learn-github-packages/introduction-to-github-packages.md
@@ -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/pt-BR/content/packages/working-with-a-github-packages-registry/working-with-the-apache-maven-registry.md b/translations/pt-BR/content/packages/working-with-a-github-packages-registry/working-with-the-apache-maven-registry.md
index a494c22c1126..74d94bffcfa9 100644
--- a/translations/pt-BR/content/packages/working-with-a-github-packages-registry/working-with-the-apache-maven-registry.md
+++ b/translations/pt-BR/content/packages/working-with-a-github-packages-registry/working-with-the-apache-maven-registry.md
@@ -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/pt-BR/content/packages/working-with-a-github-packages-registry/working-with-the-docker-registry.md b/translations/pt-BR/content/packages/working-with-a-github-packages-registry/working-with-the-docker-registry.md
index e27195ffd4db..4abbabae7099 100644
--- a/translations/pt-BR/content/packages/working-with-a-github-packages-registry/working-with-the-docker-registry.md
+++ b/translations/pt-BR/content/packages/working-with-a-github-packages-registry/working-with-the-docker-registry.md
@@ -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/pt-BR/content/packages/working-with-a-github-packages-registry/working-with-the-gradle-registry.md b/translations/pt-BR/content/packages/working-with-a-github-packages-registry/working-with-the-gradle-registry.md
index 92f12983f8e9..3db0070fdbc4 100644
--- a/translations/pt-BR/content/packages/working-with-a-github-packages-registry/working-with-the-gradle-registry.md
+++ b/translations/pt-BR/content/packages/working-with-a-github-packages-registry/working-with-the-gradle-registry.md
@@ -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/pt-BR/content/packages/working-with-a-github-packages-registry/working-with-the-npm-registry.md b/translations/pt-BR/content/packages/working-with-a-github-packages-registry/working-with-the-npm-registry.md
index 6f606db0cbb4..1163c54a5f6e 100644
--- a/translations/pt-BR/content/packages/working-with-a-github-packages-registry/working-with-the-npm-registry.md
+++ b/translations/pt-BR/content/packages/working-with-a-github-packages-registry/working-with-the-npm-registry.md
@@ -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/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 347a099de337..24357fc22311 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
@@ -233,4 +233,4 @@ Your NuGet package may fail to push if the `RepositoryUrl` in *.csproj* is not s
 
 ## 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/pt-BR/content/packages/working-with-a-github-packages-registry/working-with-the-rubygems-registry.md b/translations/pt-BR/content/packages/working-with-a-github-packages-registry/working-with-the-rubygems-registry.md
index 7afbca5c42b3..22d46ba47ad5 100644
--- a/translations/pt-BR/content/packages/working-with-a-github-packages-registry/working-with-the-rubygems-registry.md
+++ b/translations/pt-BR/content/packages/working-with-a-github-packages-registry/working-with-the-rubygems-registry.md
@@ -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/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 68f72e10b669..df0ef33659dd 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,6 +1,6 @@
 ---
 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.
+intro: 'You can increase the security of your custom domain and avoid takeover attacks by verifying your domain.'
 product: '{% data reusables.gated-features.pages %}'
 versions:
   fpt: '*'
@@ -23,12 +23,13 @@ It's also possible to verify a domain for your organization{% ifversion ghec %}
 ## Verifying a domain for your user site
 
 {% data reusables.user_settings.access_settings %}
-1. Na barra lateral esquerda, clique em **Pages** (Páginas). ![Pages option in the settings menu](/assets/images/help/settings/user-settings-pages.png)
+1. In the left sidebar, click **Pages**.
+![Pages option in the settings menu](/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.
   ```
   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
@@ -37,10 +38,11 @@ Organization owners can verify custom domains for their organization.
 
 {% data reusables.profile.access_org %}
 {% data reusables.profile.org_settings %}
-1. Na barra lateral esquerda, clique em **Pages** (Páginas). ![Pages option in the settings menu](/assets/images/help/settings/org-settings-pages.png)
+1. In the left sidebar, click **Pages**.
+![Pages option in the settings menu](/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.
   ```
   dig _github-pages-challenge-ORGANIZATION.example.com +nostats +nocomments +nocmd TXT
-  ```
-{% data reusables.pages.settings-verify-domain-confirm %}
+  ``` 
+{% data reusables.pages.settings-verify-domain-confirm %}
\ No newline at end of file
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 08b9ba581756..b0a0606bd748 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: 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.'
+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.'
 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: Site seguro com HTTPS
+shortTitle: Secure site with HTTPS
 ---
 
-Pessoas com permissões de administrador para um repositório podem exigir HTTPS para um site do {% data variables.product.prodname_pages %}.
+People with admin permissions for a repository can enforce HTTPS for a {% data variables.product.prodname_pages %} site.
 
-## Sobre HTTPS e o {% data variables.product.prodname_pages %}
+## About HTTPS and {% data variables.product.prodname_pages %}
 
-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)".
+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 reusables.pages.no_sensitive_data_pages %}
 
@@ -25,39 +25,46 @@ Todos os sites do {% data variables.product.prodname_pages %}, incluindo os site
 
 {% note %}
 
-**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.
+**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.
 
 {% endnote %}
 
-## Exigir HTTPS para o site do {% data variables.product.prodname_pages %}
+## Enforcing HTTPS for your {% data variables.product.prodname_pages %} site
 
 {% data reusables.pages.navigate-site-repo %}
 {% data reusables.repositories.sidebar-settings %}
 {% data reusables.pages.sidebar-pages %}
-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)
+3. Under "{% data variables.product.prodname_pages %}," select **Enforce HTTPS**.
+  ![Enforce HTTPS checkbox](/assets/images/help/pages/enforce-https-checkbox.png)
 
-## Resolver problemas com conteúdo misto
+## Troubleshooting certificate provisioning ("Certificate not yet created" error")
 
-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.
+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.
 
-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.
+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.
 
-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>`.
+## 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.
+
+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.
+
+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.
 
 {% tip %}
 
-**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 %}.
+**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 %}.
 
 {% endtip %}
 
-### Exemplos de ativos referenciados em um arquivo HTML
+### Examples of assets referenced in an HTML file
 
-| 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>` |  
+| 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>`  
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 bdb6303dfb19..d791c9592310 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: 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.'
+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.'
 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,29 +13,32 @@ versions:
   ghec: '*'
 topics:
   - Pull requests
-shortTitle: Solicitar revisão de PR
+shortTitle: Request a PR review
 ---
+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.
 
-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. For more information, see "[Managing code review settings for your team](/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team)."{% endif %}
+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 %}
 
 {% note %}
 
-**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.
+**Note:** Pull request authors can't request reviews unless they are either a repository owner or collaborator with write access to the repository.
 
 {% endnote %}
 
-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.
+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.
 
 {% data reusables.repositories.sidebar-pr %}
-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)
-
-## Leia mais
-
-- "[Sobre revisões de solicitação pull](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)"
+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)
+
+## Further reading
+
+- "[About pull request reviews](/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/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 9b0f11d6e2ce..41d86814c407 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: 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.'
+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.'
 redirect_from:
   - /github/collaborating-with-issues-and-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews
   - /articles/about-pull-request-reviews
@@ -13,54 +13,53 @@ versions:
   ghec: '*'
 topics:
   - Pull requests
-shortTitle: Sobre revisões de PR
+shortTitle: About PR reviews
 ---
+## About pull request reviews
 
-## Sobre revisões de pull request
+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)."
 
-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)".
+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 %}
 
-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. For more information, see "[Managing code review settings for your team](/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team)."{% endif %}
+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/)."
 
-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/)".
+{% 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 %}
 
-{% 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 %}
+![Header of review requesting changes with line comments](/assets/images/help/pull_requests/review-header-with-line-comment.png)
 
-![Header de revisão solicitando alterações com comentários em linha](/assets/images/help/pull_requests/review-header-with-line-comment.png)
+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.
 
-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)
+![Image of review statuses](/assets/images/help/pull_requests/pull-request-review-statuses.png)
 
 {% data reusables.repositories.request-changes-tips %}
 
-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.
+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.
 
-![Imagem de revisões em uma caixa de merge](/assets/images/help/pull_requests/merge_box/pr-reviews-in-merge-box.png)
+![Image of reviews in a merge box](/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 %}
 
-## Ressolicitar uma revisão
+## Re-requesting a review
 
 {% data reusables.pull_requests.re-request-review %}
 
-## Revisões obrigatórias
+## Required reviews
 
-{% 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)".
+{% 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)."
 
 {% tip %}
 
-**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)".
+**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)."
 
 {% endtip %}
 
-## Leia mais
+## Further reading
 
-- "[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)"
+- "[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)"
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 6e91cda0c6f7..f9a5eda3a696 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
@@ -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/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 2d760fe6f2ca..08f567b7b363 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
@@ -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/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 fe9eb1dd68d4..e8587b730661 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
@@ -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/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 fd64a80a8175..04e3abaa6d43 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
@@ -111,8 +111,9 @@ Now the checks will always pass whenever someone sends a pull request that doesn
 
 {% 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/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 0181b7ae84e7..1619c037aa9e 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
@@ -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/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 60c27fc3591c..96c2ccfa4b27 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
@@ -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/pt-BR/data/features/enterprise-owners-visible-for-org-members.yml b/translations/pt-BR/data/features/enterprise-owners-visible-for-org-members.yml
new file mode 100644
index 000000000000..1b0a06a45fe2
--- /dev/null
+++ b/translations/pt-BR/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/pt-BR/data/features/fixed-width-font-gfm-fields.yml b/translations/pt-BR/data/features/fixed-width-font-gfm-fields.yml
new file mode 100644
index 000000000000..2c9ea31ac655
--- /dev/null
+++ b/translations/pt-BR/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/pt-BR/data/release-notes/github-ae/2021-06/2021-12-06.yml b/translations/pt-BR/data/release-notes/github-ae/2021-06/2021-12-06.yml
index 7c19b8eedab7..aea2e802a8a3 100644
--- a/translations/pt-BR/data/release-notes/github-ae/2021-06/2021-12-06.yml
+++ b/translations/pt-BR/data/release-notes/github-ae/2021-06/2021-12-06.yml
@@ -53,7 +53,7 @@ sections:
       heading: 'GitHub Package Registry'
       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/pt-BR/data/reusables/actions/actions-group-concurrency.md b/translations/pt-BR/data/reusables/actions/actions-group-concurrency.md
index 70ceb5655810..c7470259c4dd 100644
--- a/translations/pt-BR/data/reusables/actions/actions-group-concurrency.md
+++ b/translations/pt-BR/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/pt-BR/data/reusables/actions/cd-templates-actions.md b/translations/pt-BR/data/reusables/actions/cd-templates-actions.md
index 81b5134f9b57..f369e1e2e1b7 100644
--- a/translations/pt-BR/data/reusables/actions/cd-templates-actions.md
+++ b/translations/pt-BR/data/reusables/actions/cd-templates-actions.md
@@ -1,3 +1,3 @@
-{% data variables.product.product_name %} oferece modelos de CD para vários serviços populares, como o Azure Web App. Para aprender como começar a usar um modelo de fluxo de trabalho, consulte "[Usando modelos de fluxo de trabalho](/actions/learn-github-actions/using-workflow-templates)" ou [pesquise a lista completa dos modelos de fluxo de implantação](https://github.com/actions/starter-workflows/tree/main/deployments). Você também pode conferir nossos guias mais detalhados de fluxos de trabalho específicos para implantação como, por exemplo, "[Efetuando a implantação no 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). Você também pode conferir nossos guias mais detalhados de fluxos de trabalho específicos para implantação como, por exemplo, "[Efetuando a implantação no Azure App Service](/actions/deployment/deploying-to-azure-app-service)".
 
 Muitos prestadores de serviço também oferecem ações em {% data variables.product.prodname_marketplace %} para implantar no seu serviço. Para a lista completa, consulte [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace?category=deployment&type=actions).
diff --git a/translations/pt-BR/data/reusables/actions/workflow-organization-templates.md b/translations/pt-BR/data/reusables/actions/workflow-organization-templates.md
index 9b357870efff..6255219110e0 100644
--- a/translations/pt-BR/data/reusables/actions/workflow-organization-templates.md
+++ b/translations/pt-BR/data/reusables/actions/workflow-organization-templates.md
@@ -1 +1 @@
-Os modelos do fluxo de trabalho permitem que todos na sua organização com permissão para criar fluxos de trabalho façam de forma mais rápida e fácil. Ao criar um novo fluxo de trabalho, você pode escolher um template e um ou todo o trabalho de escrita do fluxo de trabalho será feito para você. Você pode usar os modelos do fluxo de trabalho como um ponto de partida para criar o fluxo de trabalho personalizado ou usá-los como se apresentam. Isso não só poupa tempo, como promove consistência e práticas recomendadas na sua organização.
+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. Isso não só poupa tempo, como promove consistência e práticas recomendadas na sua organização.
diff --git a/translations/pt-BR/data/reusables/actions/workflow-template-overview.md b/translations/pt-BR/data/reusables/actions/workflow-template-overview.md
index 57ca5ec12cec..8a795aa420c4 100644
--- a/translations/pt-BR/data/reusables/actions/workflow-template-overview.md
+++ b/translations/pt-BR/data/reusables/actions/workflow-template-overview.md
@@ -1,3 +1,3 @@
-{% data variables.product.prodname_dotcom %} fornece modelos de fluxo de trabalho pré-configurados que você pode personalizar para criar o seu próprio fluxo de trabalho de integração contínua. {% data variables.product.product_name %} analisa seu código e mostra modelos de CI que podem ser úteis para o seu repositório. Por exemplo, se o seu repositório contiver o código Node.js, você verá sugestões para projetos Node.js. Você pode usar os modelos do fluxo de trabalho como um ponto de partida para criar o fluxo de trabalho personalizado ou usá-los como se apresentam.
+{% 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. Por exemplo, se o seu repositório contiver o código Node.js, você verá sugestões para projetos Node.js. You can use starter workflow as a starting place to build your custom workflow or use them as-is.
 
-Você pode navegar pela lista completa dos modelos de fluxo de trabalho no repositório {% ifversion fpt or ghec %}[actions/starter-workflows](https://github.com/actions/starter-workflows) {% else %} `actions/starter-workflows` em {% data variables.product.product_location %}{% 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/pt-BR/data/reusables/advanced-security/ghas-availability.md b/translations/pt-BR/data/reusables/advanced-security/ghas-availability.md
new file mode 100644
index 000000000000..ad4315d7c13b
--- /dev/null
+++ b/translations/pt-BR/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/pt-BR/data/reusables/advanced-security/note-org-enable-uses-seats.md b/translations/pt-BR/data/reusables/advanced-security/note-org-enable-uses-seats.md
index ca6cafe0e0c4..390034e79797 100644
--- a/translations/pt-BR/data/reusables/advanced-security/note-org-enable-uses-seats.md
+++ b/translations/pt-BR/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 %}
 **Observação:** Se você habilitar
 
diff --git a/translations/pt-BR/data/reusables/advanced-security/security-feature-availability.md b/translations/pt-BR/data/reusables/advanced-security/security-feature-availability.md
new file mode 100644
index 000000000000..ef965ceae37e
--- /dev/null
+++ b/translations/pt-BR/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/pt-BR/data/reusables/github-actions/example-github-runner.md b/translations/pt-BR/data/reusables/github-actions/example-github-runner.md
index 496764e7e9d5..91e3c5b64f0e 100644
--- a/translations/pt-BR/data/reusables/github-actions/example-github-runner.md
+++ b/translations/pt-BR/data/reusables/github-actions/example-github-runner.md
@@ -1,6 +1,6 @@
 ### Executando em um sistema operacional diferente
 
-O modelo de fluxo de trabalho inicial configura trabalhos para executar no Linux, usando o {% data variables.product.prodname_dotcom %}-executores hospedados `ubuntu-latest`. Você pode alterar a tecla `runs-on` para executar seus trabalhos em um sistema operacional diferente. Por exemplo, você pode usar os {% data variables.product.prodname_dotcom %}-executores Windows hospedados.
+The starter workflow configures jobs to run on Linux, using the {% data variables.product.prodname_dotcom %}-hosted `ubuntu-latest` runners. Você pode alterar a tecla `runs-on` para executar seus trabalhos em um sistema operacional diferente. Por exemplo, você pode usar os {% data variables.product.prodname_dotcom %}-executores Windows hospedados.
 
 {% raw %}
 ```yaml
diff --git a/translations/pt-BR/data/reusables/github-actions/java-jvm-architecture.md b/translations/pt-BR/data/reusables/github-actions/java-jvm-architecture.md
index 19a27247f2e5..edc3207ad065 100644
--- a/translations/pt-BR/data/reusables/github-actions/java-jvm-architecture.md
+++ b/translations/pt-BR/data/reusables/github-actions/java-jvm-architecture.md
@@ -1,6 +1,6 @@
 ### Especificando a versão e a arquitetura da JVM
 
-O modelo de fluxo de trabalho inicial configura o `PATH` para conter OpenJDK 8 para a plataforma x64. Se você quiser usar uma versão diferente do Java, ou escolher uma arquitetura diferente (`x64` or `x86`), você pode usar a ação `setup-java` para escolher um ambiente de execução Java diferente.
+The starter workflow sets up the `PATH` to contain OpenJDK 8 for the x64 platform. Se você quiser usar uma versão diferente do Java, ou escolher uma arquitetura diferente (`x64` or `x86`), você pode usar a ação `setup-java` para escolher um ambiente de execução Java diferente.
 
 Por exemplo, para usar a versão 11 do JDK fornecido pelo Adoptium para a plataforma x64, você pode usar a ação `setup-java` e configurar os parâmetros `java-version`, `distribution` e `arquitetura` para `'11'`, `'adopt'` e `x64`.
 
diff --git a/translations/pt-BR/data/reusables/organizations/people.md b/translations/pt-BR/data/reusables/organizations/people.md
index a8107cafac00..cc23a1088d47 100644
--- a/translations/pt-BR/data/reusables/organizations/people.md
+++ b/translations/pt-BR/data/reusables/organizations/people.md
@@ -1,5 +1,5 @@
 1. Abaixo do nome da sua organização, clique em
-{% octicon "organization" aria-label="The People icon" %} **People**.
+{% octicon "person" aria-label="The Person icon" %} **People**.
   {% ifversion fpt or ghes > 3.2 or ghec %}
   ![A aba Pessoas](/assets/images/help/organizations/organization-people-tab-with-overview-tab.png)
   {% else %}
diff --git a/translations/pt-BR/data/reusables/pages/twenty-minutes-to-publish.md b/translations/pt-BR/data/reusables/pages/twenty-minutes-to-publish.md
index cd5f83499ad5..a7b22a5cc33a 100644
--- a/translations/pt-BR/data/reusables/pages/twenty-minutes-to-publish.md
+++ b/translations/pt-BR/data/reusables/pages/twenty-minutes-to-publish.md
@@ -1 +1 @@
-**Observação:** podem ser necessários até 10 minutos para que as alterações no site sejam publicadas após o push delas no {% data variables.product.product_name %}.  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
+**Observação:** podem ser necessários até 10 minutos para que as alterações no site sejam publicadas após o push delas no {% data variables.product.product_name %}.  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/pt-BR/data/reusables/repositories/actions-tab.md b/translations/pt-BR/data/reusables/repositories/actions-tab.md
index d70ee6b5979b..3c058e44cf25 100644
--- a/translations/pt-BR/data/reusables/repositories/actions-tab.md
+++ b/translations/pt-BR/data/reusables/repositories/actions-tab.md
@@ -1 +1 @@
-1. No nome do seu repositório, clique em **Ações**. ![Aba Ações na navegação principal do repositório](/assets/images/help/repository/actions-tab.png)
+1. Under your repository name, click {% octicon "play" aria-label="The Play icon" %} **Actions**. ![Aba Ações na navegação principal do repositório](/assets/images/help/repository/actions-tab.png)
diff --git a/translations/pt-BR/data/reusables/repositories/private_forks_inherit_permissions.md b/translations/pt-BR/data/reusables/repositories/private_forks_inherit_permissions.md
index 5d0272fbbd96..62cfaf932176 100644
--- a/translations/pt-BR/data/reusables/repositories/private_forks_inherit_permissions.md
+++ b/translations/pt-BR/data/reusables/repositories/private_forks_inherit_permissions.md
@@ -1 +1 @@
-As bifurcações privadas herdam a estrutura de permissões do repositório ascendente ou principal. Por exemplo, se o repositório ascendente é privado e fornece acesso de leitura/gravação a uma equipe, essa equipe terá acesso de leitura/gravação para qualquer bifurcação do repositório privado ascendente. Isso ajuda os proprietários de repositórios privados a manter o controle sobre seus códigos.
+As bifurcações privadas herdam a estrutura de permissões do repositório ascendente ou principal. Isso ajuda os proprietários de repositórios privados a manter o controle sobre seus códigos. Por exemplo, se o repositório ascendente é privado e fornece acesso de leitura/gravação a uma equipe, essa equipe terá acesso de leitura/gravação para qualquer bifurcação do repositório privado ascendente. Only team permissions (not individual permissions) are inherited by private forks.
diff --git a/translations/pt-BR/data/reusables/secret-scanning/partner-secret-list-private-repo.md b/translations/pt-BR/data/reusables/secret-scanning/partner-secret-list-private-repo.md
index 7146a6157283..3a537f280525 100644
--- a/translations/pt-BR/data/reusables/secret-scanning/partner-secret-list-private-repo.md
+++ b/translations/pt-BR/data/reusables/secret-scanning/partner-secret-list-private-repo.md
@@ -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/pt-BR/data/reusables/user_settings/appearance-settings.md b/translations/pt-BR/data/reusables/user_settings/appearance-settings.md
new file mode 100644
index 000000000000..8cdc9ed93dc5
--- /dev/null
+++ b/translations/pt-BR/data/reusables/user_settings/appearance-settings.md
@@ -0,0 +1,3 @@
+1. Na barra lateral de configurações do usuário, clique em **Aparência**.
+
+   ![Aba "Aparência" na barra lateral de configurações do usuário](/assets/images/help/settings/appearance-tab.png)
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/user_settings/enabling-fixed-width-fonts.md b/translations/pt-BR/data/reusables/user_settings/enabling-fixed-width-fonts.md
new file mode 100644
index 000000000000..b40ae916b5d7
--- /dev/null
+++ b/translations/pt-BR/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/pt-BR/data/reusables/webhooks/issue_event_api_properties.md b/translations/pt-BR/data/reusables/webhooks/issue_event_api_properties.md
index 8ba92018f74b..34c02ba18dc9 100644
--- a/translations/pt-BR/data/reusables/webhooks/issue_event_api_properties.md
+++ b/translations/pt-BR/data/reusables/webhooks/issue_event_api_properties.md
@@ -1,3 +1,3 @@
-| Tecla  | Tipo     | Descrição                                                                                                              |
-| ------ | -------- | ---------------------------------------------------------------------------------------------------------------------- |
-| `Ação` | `string` | A ação que foi executada. Pode ser `opened`, `closed`, `reopened`, `assigned`, `unassigned`, `labeled` ou `unlabeled`. |
+| Tecla  | Tipo     | Descrição                                                                                                                              |
+| ------ | -------- | -------------------------------------------------------------------------------------------------------------------------------------- |
+| `Ação` | `string` | A ação que foi executada. Can be one of `opened`, `edited`, `closed`, `reopened`, `assigned`, `unassigned`, `labeled`, or `unlabeled`. |
diff --git a/translations/pt-BR/data/reusables/webhooks/pull_request_event_api_properties.md b/translations/pt-BR/data/reusables/webhooks/pull_request_event_api_properties.md
index f864fac8fdb2..3afb1c6c21db 100644
--- a/translations/pt-BR/data/reusables/webhooks/pull_request_event_api_properties.md
+++ b/translations/pt-BR/data/reusables/webhooks/pull_request_event_api_properties.md
@@ -1,3 +1,3 @@
-| Tecla  | Tipo     | Descrição                                                                                                                                                                          |
-| ------ | -------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `Ação` | `string` | A ação que foi executada. Pode ser `opened`, `closed`, `reopened`, `assigned`, `unassigned`, `review_requested`, `review_request_removed`, `labeled`, `unlabeled` e `synchronize`. |
+| Tecla  | Tipo     | Descrição                                                                                                                                                                                            |
+| ------ | -------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `Ação` | `string` | A ação que foi executada. Can be one of `opened`, `edited`, `closed`, `reopened`, `assigned`, `unassigned`, `review_requested`, `review_request_removed`, `labeled`, `unlabeled`, and `synchronize`. |
diff --git a/translations/pt-BR/data/ui.yml b/translations/pt-BR/data/ui.yml
index b7806ff31d24..c75a4dc3510c 100644
--- a/translations/pt-BR/data/ui.yml
+++ b/translations/pt-BR/data/ui.yml
@@ -13,6 +13,8 @@ header:
     ghes_release_notes_upgrade_patch_only: '📣 This is not the <a href="#{{ latestPatch }}">latest patch release</a> of Enterprise Server.'
     ghes_release_notes_upgrade_release_only: '📣 This is not the <a href="/enterprise-server@{{ latestRelease }}/admin/release-notes">latest release</a> of Enterprise Server.'
     ghes_release_notes_upgrade_patch_and_release: '📣 This is not the <a href="#{{ latestPatch }}">latest patch release</a> of this release series, and this is not the <a href="/enterprise-server@{{ latestRelease }}/admin/release-notes">latest release</a> of Enterprise Server.'
+picker:
+  toggle_picker_list: Toggle picker list
 release_notes:
   banner_text: GitHub began rolling these changes out to enterprises on
 search:
diff --git a/translations/pt-BR/data/variables/product.yml b/translations/pt-BR/data/variables/product.yml
index 483a7a84b0db..d4ea5b8b5990 100644
--- a/translations/pt-BR/data/variables/product.yml
+++ b/translations/pt-BR/data/variables/product.yml
@@ -97,8 +97,6 @@ prodname_matching_fund: 'Fundo Correspondentes para Patrocinadores do GitHub'
 #GitHub Advanced Security
 prodname_GH_advanced_security: 'Segurança Avançada GitHub'
 prodname_advanced_security: 'Segurança Avançada'
-#Security Center
-prodname_security_center: 'Security Center'
 #Codespaces
 prodname_codespaces: 'Codespaces'
 prodname_github_codespaces: 'GitHub Codespaces'

From f614948654af9edaf7665f5341fb90f84682c35b Mon Sep 17 00:00:00 2001
From: docubot <67483024+docubot@users.noreply.github.com>
Date: Thu, 6 Jan 2022 13:23:19 -0800
Subject: [PATCH 04/13] New translation batch for ja (#24124)

* Add crowdin translations

* Run script/i18n/homogenize-frontmatter.js

* Run script/i18n/lint-translation-files.js --check parsing

* Run script/i18n/lint-translation-files.js --check rendering

* run script/i18n/reset-files-with-broken-liquid-tags.js --language=ja

* run script/i18n/reset-known-broken-translation-files.js

* Check in ja CSV report

Co-authored-by: Rachael Sewell <rachmari@github.com>
---
 .../managing-your-theme-settings.md           |   4 +-
 ...on-levels-for-a-user-account-repository.md |   6 +-
 ...iewing-peoples-roles-in-an-organization.md |  46 +++-
 .../about-continuous-integration.md           |  10 +-
 .../building-and-testing-java-with-ant.md     |   8 +-
 .../building-and-testing-java-with-gradle.md  |   8 +-
 .../building-and-testing-java-with-maven.md   |   8 +-
 .../building-and-testing-net.md               |   6 +-
 .../building-and-testing-nodejs.md            |   8 +-
 .../building-and-testing-python.md            |   8 +-
 .../building-and-testing-ruby.md              |   6 +-
 .../building-and-testing-swift.md             |   6 +-
 .../creating-a-javascript-action.md           |   6 +-
 .../metadata-syntax-for-github-actions.md     |  46 +++-
 .../about-continuous-deployment.md            |   2 +-
 ...g-openid-connect-in-amazon-web-services.md |   4 +-
 translations/ja-JP/content/actions/guides.md  |   2 +-
 ...using-self-hosted-runners-in-a-workflow.md |   9 +-
 translations/ja-JP/content/actions/index.md   |   2 +-
 ...starter-workflows-for-your-organization.md |  99 ++++++++
 .../learn-github-actions/expressions.md       |  30 ++-
 .../actions/learn-github-actions/index.md     |   4 +-
 .../managing-complex-workflows.md             |   4 +-
 .../learn-github-actions/reusing-workflows.md |   6 +-
 ...rets-and-runners-with-your-organization.md |  10 +-
 .../using-starter-workflows.md                |  54 +++++
 .../workflow-syntax-for-github-actions.md     |   2 +-
 .../adding-a-workflow-status-badge.md         |   4 +-
 .../ja-JP/content/actions/quickstart.md       |   2 +-
 .../about-github-hosted-runners.md            |   4 +-
 ...ucing-github-actions-to-your-enterprise.md |   6 +-
 ...e-ecosystem-support-for-your-enterprise.md |  32 +--
 .../roles-in-an-enterprise.md                 |   2 +-
 .../troubleshooting-the-codeql-workflow.md    |   4 +-
 .../github-security-features.md               |  16 +-
 .../securing-your-organization.md             |  33 ++-
 .../securing-your-repository.md               |  29 ++-
 .../about-managing-vulnerable-dependencies.md |  24 +-
 ...nvironment-variables-for-your-codespace.md |  40 ++++
 .../developing-in-codespaces/index.md         |   1 +
 .../troubleshooting-codespaces-clients.md     |  18 +-
 .../scopes-for-oauth-apps.md                  |   2 +-
 .../about-github-advanced-security.md         |  46 ++--
 .../get-started/quickstart/github-flow.md     |   2 +-
 .../get-started/quickstart/set-up-git.md      |  10 +
 ...se-settings-for-your-private-repository.md |   5 +-
 .../about-writing-and-formatting-on-github.md |  38 +--
 .../basic-writing-and-formatting-syntax.md    |   2 +
 .../creating-and-highlighting-code-blocks.md  |  31 +--
 .../organizing-information-with-tables.md     |  45 ++--
 .../closing-a-project-board.md                |   2 +-
 .../reopening-a-closed-project-board.md       |  25 +-
 .../archiving-cards-on-a-project-board.md     |  25 +-
 .../creating-an-issue.md                      |  96 ++++----
 ...-and-searching-issues-and-pull-requests.md |   2 +-
 .../creating-a-project.md                     |  88 +++----
 .../using-the-api-to-manage-projects.md       |  82 +++----
 ...analysis-settings-for-your-organization.md | 152 ++++++------
 ...ing-the-audit-log-for-your-organization.md |  27 +--
 .../repository-roles-for-an-organization.md   |  14 +-
 ...-security-managers-in-your-organization.md |  20 +-
 .../about-permissions-for-github-packages.md  |  86 ++++---
 .../deleting-a-package.md                     |   3 +-
 .../deleting-and-restoring-a-package.md       | 220 ++++++++++--------
 .../introduction-to-github-packages.md        |   2 +-
 .../working-with-the-apache-maven-registry.md |   2 +-
 .../working-with-the-docker-registry.md       |   2 +-
 .../working-with-the-gradle-registry.md       |   2 +-
 .../working-with-the-npm-registry.md          |   4 +-
 .../working-with-the-nuget-registry.md        |   2 +-
 .../working-with-the-rubygems-registry.md     |   2 +-
 ...uring-your-github-pages-site-with-https.md |  53 +++--
 ...ery-parameters-to-create-a-pull-request.md |  26 +--
 ...ng-dependency-changes-in-a-pull-request.md |  52 ++---
 .../working-with-forks/about-forks.md         |   2 +-
 .../about-protected-branches.md               |  14 +-
 .../managing-a-branch-protection-rule.md      |  14 +-
 .../troubleshooting-required-status-checks.md |   3 +-
 ...d-analysis-settings-for-your-repository.md |  24 +-
 .../setting-repository-visibility.md          |   2 +-
 ...erprise-owners-visible-for-org-members.yml |   7 +
 .../features/fixed-width-font-gfm-fields.yml  |   8 +
 .../github-ae/2021-06/2021-12-06.yml          |   2 +-
 .../actions/actions-group-concurrency.md      |   2 +-
 .../reusables/actions/cd-templates-actions.md |   2 +-
 .../workflow-organization-templates.md        |   2 +-
 .../actions/workflow-template-overview.md     |   4 +-
 .../advanced-security/ghas-availability.md    |  10 +
 .../note-org-enable-uses-seats.md             |   2 +-
 .../security-feature-availability.md          |   1 +
 .../github-actions/example-github-runner.md   |   2 +-
 .../github-actions/java-jvm-architecture.md   |   2 +-
 .../data/reusables/organizations/people.md    |   2 +-
 .../pages/twenty-minutes-to-publish.md        |   2 +-
 .../reusables/repositories/actions-tab.md     |   2 +-
 .../private_forks_inherit_permissions.md      |   2 +-
 .../partner-secret-list-private-repo.md       |  12 +-
 .../user_settings/appearance-settings.md      |   3 +
 .../enabling-fixed-width-fonts.md             |   5 +
 .../webhooks/issue_event_api_properties.md    |   6 +-
 .../pull_request_event_api_properties.md      |   6 +-
 translations/ja-JP/data/ui.yml                |   2 +
 translations/ja-JP/data/variables/product.yml |   2 -
 translations/log/ja-resets.csv                |  25 +-
 104 files changed, 1247 insertions(+), 714 deletions(-)
 create mode 100644 translations/ja-JP/content/actions/learn-github-actions/creating-starter-workflows-for-your-organization.md
 create mode 100644 translations/ja-JP/content/actions/learn-github-actions/using-starter-workflows.md
 create mode 100644 translations/ja-JP/content/codespaces/developing-in-codespaces/default-environment-variables-for-your-codespace.md
 create mode 100644 translations/ja-JP/data/features/enterprise-owners-visible-for-org-members.yml
 create mode 100644 translations/ja-JP/data/features/fixed-width-font-gfm-fields.yml
 create mode 100644 translations/ja-JP/data/reusables/advanced-security/ghas-availability.md
 create mode 100644 translations/ja-JP/data/reusables/advanced-security/security-feature-availability.md
 create mode 100644 translations/ja-JP/data/reusables/user_settings/appearance-settings.md
 create mode 100644 translations/ja-JP/data/reusables/user_settings/enabling-fixed-width-fonts.md

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 dcf87636030a..d8335fc89f6f 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
@@ -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/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 b/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
index ad89e7310248..08fa6a78913b 100644
--- a/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
+++ b/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
@@ -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/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 57fdffd93b77..28c8a5dcf863 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,6 +1,7 @@
 ---
-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)."'
+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."
 redirect_from:
   - /articles/viewing-people-s-roles-in-an-organization
   - /articles/viewing-peoples-roles-in-an-organization
@@ -16,13 +17,50 @@ topics:
 shortTitle: View people in an organization
 ---
 
+## View organization roles
+
+{% 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)
+
+{% 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 %}
 
-**メモ:** Organization における人のロールを表示するには、Organization のメンバーでなければなりません。
+**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** |
+|----|----|----|----|
+| 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. |
+
+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. Organization 内の人のリストが表示されます。 ロールでリストをフィルタリングするには、[**Role**] をクリックします。 ![click-role](/assets/images/help/organizations/view-list-of-people-in-org-by-role.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
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 393d8c7c6096..5c660e6ecb4d 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
@@ -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/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 e064761894fb..ccf04b5c79d6 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
@@ -40,11 +40,11 @@ We recommend that you have a basic understanding of Java and the Ant framework.
 
 {% 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. For more information, see the "[{% data variables.product.prodname_actions %} quickstart](/actions/quickstart)."
 
 You can also add this workflow manually by creating a new file in the `.github/workflows` directory of your repository.
 
@@ -76,7 +76,7 @@ This workflow performs the following steps:
 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.
 
-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 %}
 
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 74fb4ffb74e7..53d817480689 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
@@ -40,11 +40,11 @@ We recommend that you have a basic understanding of Java and the Gradle framewor
 
 {% 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. For more information, see the "[{% data variables.product.prodname_actions %} quickstart](/actions/quickstart)."
 
 You can also add this workflow manually by creating a new file in the `.github/workflows` directory of your repository.
 
@@ -79,7 +79,7 @@ This workflow performs the following steps:
 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.
 
-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 %}
 
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 a8403ce752a3..bc44e08de5a3 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
@@ -40,11 +40,11 @@ We recommend that you have a basic understanding of Java and the Maven framework
 
 {% 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. For more information, see the "[{% data variables.product.prodname_actions %} quickstart](/actions/quickstart)."
 
 You can also add this workflow manually by creating a new file in the `.github/workflows` directory of your repository.
 
@@ -76,7 +76,7 @@ This workflow performs the following steps:
 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.
 
-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 %}
 
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 ba114a3e7400..774d75755679 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
@@ -28,11 +28,11 @@ You should already be familiar with YAML syntax and how it's used with {% data v
 
 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).
 
-## 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
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 8460d3973098..ecb2e61aa864 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
@@ -36,11 +36,11 @@ We recommend that you have a basic understanding of Node.js, YAML, workflow conf
 
 {% 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. The workflow shown below assumes that the default branch for your repository is `main`.
 
 {% raw %}
 ```yaml{:copy}
@@ -81,7 +81,7 @@ The easiest way to specify a Node.js version is by using the `setup-node` action
 
 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`.
 
-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. 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.
 
 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)."
 
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 bdbeef71ff49..c67f6a545b7f 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
@@ -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/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 6da09a7717a9..09d888b8394a 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
@@ -29,11 +29,11 @@ We recommend that you have a basic understanding of Ruby, YAML, workflow configu
 - [Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)
 - [Ruby in 20 minutes](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. The workflow shown below assumes that the default branch for your repository is `main`.
 
 ```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 8bbcaef74718..c343875e70cf 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
@@ -31,11 +31,11 @@ You should already be familiar with YAML syntax and how it's used with {% data v
 
 We recommend that you have a basic understanding of Swift packages. For more information, see "[Swift Packages](https://developer.apple.com/documentation/swift_packages)" in the Apple developer documentation.
 
-## Starting with the Swift workflow template
+## 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}
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 72621a7252ee..be64353589b5 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
@@ -37,9 +37,9 @@ Once you complete this project, you should understand how to build your own Java
 
 Before you begin, you'll need to download Node.js and create a public {% data variables.product.prodname_dotcom %} repository.
 
-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)."
 
@@ -73,7 +73,7 @@ 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'
 ```
 
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 4e9757aec376..2c0ebd6eafa3 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
@@ -140,11 +140,11 @@ For more information on how to use context syntax, see "[Contexts](/actions/lear
 
 **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'
 ```
 
@@ -152,8 +152,8 @@ runs:
 
 **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`
 
@@ -167,7 +167,7 @@ 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'
@@ -175,7 +175,8 @@ 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()`.
+**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.
+
 Note that the `step` context is unavailable, as no steps have run yet.
 
 In this example, `cleanup.js` only runs on Linux-based runners:
@@ -193,7 +194,7 @@ 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'
 ```
@@ -202,7 +203,7 @@ The `post:` action always runs by default but you can override this using `post-
 
 ### `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()`.
+**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.
 
 For example, this `cleanup.js` will only run on Linux-based runners:
 
@@ -265,6 +266,35 @@ For more information, see "[`github context`](/actions/reference/context-and-exp
 **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.
 {% 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.
+
+{% 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`.
+
+ ```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 %}
+```
+
+**Example: Using status check functions**
+
+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.
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 cf534d337e6f..e941449aa814 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
@@ -40,7 +40,7 @@ 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 %}
 
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 d7dcd598529a..33a04c0e1847 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
@@ -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/ja-JP/content/actions/guides.md b/translations/ja-JP/content/actions/guides.md
index 3a445c387b5b..f6cec21fcb37 100644
--- a/translations/ja-JP/content/actions/guides.md
+++ b/translations/ja-JP/content/actions/guides.md
@@ -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/ja-JP/content/actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow.md b/translations/ja-JP/content/actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow.md
index 8b533bffd420..f744a1c36f13 100644
--- a/translations/ja-JP/content/actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow.md
+++ b/translations/ja-JP/content/actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow.md
@@ -70,8 +70,13 @@ These labels operate cumulatively, so a self-hosted runner’s labels must match
 
 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:
 
-{% 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.
+{% 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.
+- If the job remains queued for more than 24 hours, the job will fail.
+{% elsif ghes = 3.3 %}
+- {% data variables.product.prodname_dotcom %} first searches for a runner at the repository level, then at the organization level, 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.
diff --git a/translations/ja-JP/content/actions/index.md b/translations/ja-JP/content/actions/index.md
index 874053eb2b6b..8828a7a41ca7 100644
--- a/translations/ja-JP/content/actions/index.md
+++ b/translations/ja-JP/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:
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
new file mode 100644
index 000000000000..861365c0ec20
--- /dev/null
+++ b/translations/ja-JP/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 %}
+
+## Overview
+
+{% 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. 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.
+
+   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.
+
+   For example, this file named `octo-organization-ci.yml` demonstrates a basic workflow.
+
+   ```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. Create a metadata file inside the `workflow-templates` directory. The metadata file must have the same name as the workflow file, but instead of the `.yml` extension, it must be appended with `.properties.json`. For example, this file named `octo-organization-ci.properties.json` contains the metadata for a workflow file named `octo-organization-ci.yml`:
+   ```yaml
+   {
+       "name": "Octo Organization Workflow",
+       "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` - **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.
+
+To add another starter workflow, add your files to the same `workflow-templates` directory. For example:
+
+![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)."
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 2c8cd63dc3cc..43a4e14853a3 100644
--- a/translations/ja-JP/content/actions/learn-github-actions/expressions.md
+++ b/translations/ja-JP/content/actions/learn-github-actions/expressions.md
@@ -266,9 +266,9 @@ Creates a hash for any `package-lock.json` and `Gemfile.lock` files in the repos
 
 `hashFiles('**/package-lock.json', '**/Gemfile.lock')`
 
-## Job status check functions
+## 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)."
+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)".
 
 ### success
 
@@ -316,6 +316,32 @@ steps:
     if: {% raw %}${{ failure() }}{% endraw %}
 ```
 
+### Evaluate Status Explicitly
+
+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:
+
+#### 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.
+
 ## Object filters
 
 You can use the `*` syntax to apply a filter and select matching items in a collection.
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 e45322bcff4d..a6a2c0622676 100644
--- a/translations/ja-JP/content/actions/learn-github-actions/index.md
+++ b/translations/ja-JP/content/actions/learn-github-actions/index.md
@@ -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/ja-JP/content/actions/learn-github-actions/managing-complex-workflows.md b/translations/ja-JP/content/actions/learn-github-actions/managing-complex-workflows.md
index e44a1d367c85..ed8322bb5a08 100644
--- a/translations/ja-JP/content/actions/learn-github-actions/managing-complex-workflows.md
+++ b/translations/ja-JP/content/actions/learn-github-actions/managing-complex-workflows.md
@@ -170,7 +170,7 @@ To learn more about {% data variables.product.prodname_dotcom %}-hosted runner l
 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)."
 {% endif %}
 
-## Using a workflow template
+## Using starter workflows
 
 {% data reusables.actions.workflow-template-overview %}
 
@@ -178,7 +178,7 @@ You can configure environments with protection rules and secrets. Each job in a
 {% 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**.
+1. Under the name of the starter workflow you'd like to use, click **Set up this workflow**.
   ![Set up this workflow](/assets/images/help/settings/actions-create-starter-workflow.png)
 
 ## Next steps
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 9bf5bb7bdf8e..33a4d0e6a961 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
@@ -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
 
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 f48ee6acd800..7ce98f56132b 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,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.'
+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:
@@ -17,11 +17,11 @@ type: how_to
 
 ## 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.
+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.
 
-## 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 %}
 
@@ -51,4 +51,4 @@ For more information, see "[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/ja-JP/content/actions/learn-github-actions/using-starter-workflows.md b/translations/ja-JP/content/actions/learn-github-actions/using-starter-workflows.md
new file mode 100644
index 000000000000..9af782bd9778
--- /dev/null
+++ b/translations/ja-JP/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. 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.
+
+## Further reading
+
+- "[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)"
+{% ifversion fpt or ghec %}
+- "[Managing billing for {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions)"
+{% endif %}
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 c0d591e31188..f3586ab25196 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
@@ -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/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 c55f5363fd82..da7ac4443b3c 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
@@ -39,8 +39,8 @@ This Markdown example adds a status badge for a branch with the name `feature-1`
 
 ## Using the `event` parameter
 
-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/ja-JP/content/actions/quickstart.md b/translations/ja-JP/content/actions/quickstart.md
index 38bf3fdf1346..28d20b78f782 100644
--- a/translations/ja-JP/content/actions/quickstart.md
+++ b/translations/ja-JP/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/ja-JP/content/actions/using-github-hosted-runners/about-github-hosted-runners.md b/translations/ja-JP/content/actions/using-github-hosted-runners/about-github-hosted-runners.md
index 60e791ab95e9..662d33b84ffa 100644
--- a/translations/ja-JP/content/actions/using-github-hosted-runners/about-github-hosted-runners.md
+++ b/translations/ja-JP/content/actions/using-github-hosted-runners/about-github-hosted-runners.md
@@ -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/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 6114f313f604..126b397d3aa0 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
@@ -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)."
 
@@ -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)."
 
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 e64a40ef052d..7ee3e6fde674 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: Enterprise 向けのパッケージエコシステムサポートを設定する
-intro: 'Docker、RubyGems、npm、Apache Maven、Gradle、NuGet など、Enterprise の個々のパッケージエコシステムをグローバルに有効または無効にすることで、Enterprise の {% data variables.product.prodname_registry %} を設定できます。 特定のパッケージエコシステムをサポートするための他の設定要件について学びます。'
+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.'
 redirect_from:
   - /enterprise/admin/packages/configuring-packages-support-for-your-enterprise
   - /admin/packages/configuring-packages-support-for-your-enterprise
@@ -15,34 +15,38 @@ 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. [Ecosystem Toggles] の下で、パッケージの種類ごとに [**Enabled**]、[**Read-Only**]、または [**Disabled**] を選択します。 ![エコシステムの切り替え](/assets/images/enterprise/site-admin-settings/ecosystem-toggles.png)
+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 %}
 {% data reusables.enterprise_management_console.save-settings %}
 
 {% ifversion ghes = 3.0 or ghes > 3.0 %}
-## 公式 npm レジストリに接続する
+## Connecting to the official npm registry
 
-Enterprise で npm パッケージを有効にしていて、公式の npm レジストリと {% data variables.product.prodname_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.
 
-{% data variables.product.prodname_registry %} は、`registry.npmjs.com` の公式 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.
 
-npm レジストリへのネットワーク接続を許可するには、{% data variables.product.prodname_ghe_server %} がポート 443 を介して `registry.npmjs.com` に HTTPS トラフィックを送信できるようにするネットワーク ACL を設定する必要があります。
+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:
 
-| 資料                                                 | 宛先                   | ポート     | 種類    |
-| -------------------------------------------------- | -------------------- | ------- | ----- |
+| Source | Destination | Port | Type |
+|---|---|---|---|
 | {% data variables.product.prodname_ghe_server %} | `registry.npmjs.com` | TCP/443 | HTTPS |
 
-`registry.npmjs.com` への接続は、Cloudflare ネットワークを通過した後、単一の静的 IP アドレスに接続しませんので、ご注意ください。代わりに、https://www.cloudflare.com/ips/ にリストされている CIDR 範囲内の IP アドレスに接続されます。
+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/.
+
+If you wish to enable npm upstream sources, select `Enabled` for `npm upstreaming`.
 
 {% endif %}
 
-## 次のステップ
+## Next steps
 
-次のステップとして、パッケージのホスト URL の TLS 証明書を更新またはアップロードする必要があるかどうかを確認することをお勧めします。 詳しい情報については、「[Enterprise 向けの GitHub Packages を使ってみる](/admin/packages/getting-started-with-github-packages-for-your-enterprise)」を参照してください。
+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)."
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 e1586d12d05b..9fb394b311e3 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
@@ -42,7 +42,7 @@ Enterprise owners have complete control over the enterprise and can take every a
 
 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.
+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 members
 
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 bf886eac2f61..322a5f346e86 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
@@ -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 %}.
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 174275d17803..646ed3ccd55b 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
@@ -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/ja-JP/content/code-security/getting-started/securing-your-organization.md b/translations/ja-JP/content/code-security/getting-started/securing-your-organization.md
index f88ddfd5050f..92361d61a268 100644
--- a/translations/ja-JP/content/code-security/getting-started/securing-your-organization.md
+++ b/translations/ja-JP/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/ja-JP/content/code-security/getting-started/securing-your-repository.md b/translations/ja-JP/content/code-security/getting-started/securing-your-repository.md
index 7cbdb8a96fa2..eb7b4888b26c 100644
--- a/translations/ja-JP/content/code-security/getting-started/securing-your-repository.md
+++ b/translations/ja-JP/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)."
 
+{% 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_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**. 
+{% 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/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 77fcfc06d95a..ee0c826d039e 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: 脆弱性のある依存関係の管理について
-intro: '{% data variables.product.product_name %} は、既知の脆弱性を含むサードパーティソフトウェアの使用を回避するのに役立ちます。'
+title: About managing vulnerable dependencies
+intro: '{% data variables.product.product_name %} helps you to avoid using third-party software that contains known vulnerabilities.'
 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: 脆弱性のある依存関係
+shortTitle: Vulnerable dependencies
 ---
-
 <!--Marketing-LINK: From /features/security/software-supply-chain page "Managing vulnerabilities in your project’s dependencies ".-->
 
-{% data variables.product.product_name %} は、脆弱性のある依存関係を削除および回避するための次のツールを提供しています。
+{% data variables.product.product_name %} provides the following tools for removing and avoiding vulnerable dependencies.
 
-## 依存関係グラフ
-依存関係グラフは、リポジトリに保存されているマニフェストファイルおよびロックファイルのサマリーです。 コードベースが依存するエコシステムとパッケージ（依存関係）、およびプロジェクトに依存するリポジトリとパッケージ（依存関係）が表示されます。 依存関係グラフの情報は、依存関係のレビューと {% data variables.product.prodname_dependabot %} によって使用されます。 詳しい情報については、「[依存関係グラフについて](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)」を参照してください。
+## 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)."
 
-## 依存関係のレビュー
+## Dependency review
 
 {% data reusables.dependency-review.beta %}
 
-プルリクエストの依存関係のレビューを確認することで、依存関係からコードベースに脆弱性が発生するのを防ぐことができます。 プルリクエストが脆弱性のある依存関係を追加したり、依存関係を脆弱性のあるバージョンに変更した場合、これは依存関係のレビューで強調表示されます。 プルリクエストをマージする前に、依存関係をパッチを適用したバージョンに変更できます。 For more information, see "[About dependency review](/code-security/supply-chain-security/about-dependency-review)."
+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)."
 
 ## {% data variables.product.prodname_dependabot_alerts %}
-リポジトリ内の脆弱性のある依存関係を検出すると、{% 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)」を参照してください。
+{% 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)."
 
 {% ifversion fpt or ghec or ghes > 3.2 %}
 ## {% data variables.product.prodname_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)」を参照してください。
+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.prodname_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)」を参照してください。
+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)."
 {% endif %}
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
new file mode 100644
index 000000000000..1eb32e030fc8
--- /dev/null
+++ b/translations/ja-JP/content/codespaces/developing-in-codespaces/default-environment-variables-for-your-codespace.md
@@ -0,0 +1,40 @@
+---
+title: Default environment variables for your codespace
+shortTitle: Default environment variables
+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
+
+| 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
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 0558dd88ff3e..64e671622bf7 100644
--- a/translations/ja-JP/content/codespaces/developing-in-codespaces/index.md
+++ b/translations/ja-JP/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/ja-JP/content/codespaces/troubleshooting/troubleshooting-codespaces-clients.md b/translations/ja-JP/content/codespaces/troubleshooting/troubleshooting-codespaces-clients.md
index 88b1433d1f6b..e5460831a92a 100644
--- a/translations/ja-JP/content/codespaces/troubleshooting/troubleshooting-codespaces-clients.md
+++ b/translations/ja-JP/content/codespaces/troubleshooting/troubleshooting-codespaces-clients.md
@@ -11,15 +11,27 @@ topics:
 shortTitle: Codespaces clients
 ---
 
-## {% data variables.product.prodname_vscode %} のトラブルシューティング
+## {% data variables.product.prodname_vscode %} troubleshooting
 
-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.
 
 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.
+
+## 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/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 bdf4b1997dd2..8471eadaa4bf 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
@@ -70,7 +70,7 @@ Name | Description
 &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 %}
+**`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 %}
diff --git a/translations/ja-JP/content/get-started/learning-about-github/about-github-advanced-security.md b/translations/ja-JP/content/get-started/learning-about-github/about-github-advanced-security.md
index d99e76f16a62..c8b27e59dfad 100644
--- a/translations/ja-JP/content/get-started/learning-about-github/about-github-advanced-security.md
+++ b/translations/ja-JP/content/get-started/learning-about-github/about-github-advanced-security.md
@@ -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 %}
-
-{% ifversion not ghae %}
-## Enabling {% data variables.product.prodname_advanced_security %} features on {% data variables.product.prodname_dotcom_the_website %}
+{%- elsif ghec %}
+For public repositories these features are permanently on and can only be disabled if you change the visibility of the project so that the code is no longer public. 
 
-For public repositories 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. 
 
-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 %}
+{%- 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)."
 
-{% 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/ja-JP/content/get-started/quickstart/github-flow.md b/translations/ja-JP/content/get-started/quickstart/github-flow.md
index 0ae27c41792d..e555ed5d9f21 100644
--- a/translations/ja-JP/content/get-started/quickstart/github-flow.md
+++ b/translations/ja-JP/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/ja-JP/content/get-started/quickstart/set-up-git.md b/translations/ja-JP/content/get-started/quickstart/set-up-git.md
index 2b916a6abb01..f8272f9fc359 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
@@ -40,6 +40,16 @@ If you don't need to work with files locally, {% data variables.product.product_
 ## Setting up Git
 
 1. [Download and install the latest version of 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. 
+
+{% 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).
 
diff --git a/translations/ja-JP/content/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository.md b/translations/ja-JP/content/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository.md
index c682319d40f1..e2b617a11c78 100644
--- a/translations/ja-JP/content/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository.md
+++ b/translations/ja-JP/content/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository.md
@@ -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/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 9143bc58ecc1..f9a01951007b 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: GitHub 上での執筆とフォーマットについて
-intro: GitHubは、GitHub Flavored Markdown と呼ばれるテキストフォーマットの構文を、いくつかのユニークな執筆用の機能と組み合わせています。
+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.
 redirect_from:
   - /articles/about-writing-and-formatting-on-github
   - /github/writing-on-github/about-writing-and-formatting-on-github
@@ -11,22 +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.
 
-[Markdown](http://daringfireball.net/projects/markdown/) は、プレーンテキストをフォーマットするための読みやすく書きやすい構文です。
+We've added some custom functionality to create {% data variables.product.prodname_dotcom %} Flavored Markdown, used to format prose and code across our site.
 
-サイトで文章とコードをフォーマットするのに使われる {% data variables.product.prodname_dotcom %}Flavored 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).
 
-また、[@メンション](/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 で他のユーザーとやりとりできます。
+## Text formatting toolbar
 
-## テキストフォーマット用のツールバー
+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 %}
 
-![Markdown ツールバー](/assets/images/help/writing/markdown-toolbar.gif)
+## 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 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/)
+{% 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 %}
+
+## 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/)"
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 5753951e64b4..f3c22ea38e68 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
@@ -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/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 2759091a2af7..71616f8e104e 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: コードブロックの作成と強調表示
-intro: コードのサンプルをコードブロックにし、構文を強調表示して共有しましょう。
+title: Creating and highlighting code blocks
+intro: Share samples of code with fenced code blocks and enabling syntax highlighting.
 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
 
-三連バッククォート <code>\`\`\`</code> をコードのブロック前後に入力すると、コードブロックを作成できます。 ソースコードを読みやすくするために、コードブロックの前後に空の行を入れることをお勧めします。
+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.
 
 <pre>
 ```
 function test() {
-  console.log("この関数の前に空白行があるのがわかりますか?");
+  console.log("notice the blank line before this function?");
 }
 ```
 </pre>
 
-![表示されたコードブロック](/assets/images/help/writing/fenced-code-block-rendered.png)
+![Rendered fenced code block](/assets/images/help/writing/fenced-code-block-rendered.png)
 
 {% tip %}
 
-**ヒント:** リスト内でフォーマットを保持するために、フェンスされていないコードのブロックをスペース 8 つでインデントしてください。
+**Tip:** To preserve your formatting within a list, make sure to indent non-fenced code blocks by eight spaces.
 
 {% endtip %}
 
@@ -45,14 +45,15 @@ Look! You can see my backticks.
 
 ![Rendered fenced code with backticks block](/assets/images/help/writing/fenced-code-show-backticks-rendered.png)
 
+{% 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.
 
-たとえば、Ruby コードの構文を強調表示するには:
+For example, to syntax highlight Ruby code:
 
     ```ruby
     require 'redcarpet'
@@ -60,11 +61,11 @@ Look! You can see my backticks.
     puts markdown.to_html
     ```
 
-![Ruby の構文を強調して表示されたコードブロック](/assets/images/help/writing/code-block-syntax-highlighting-rendered.png)
+![Rendered code block with Ruby syntax highlighting](/assets/images/help/writing/code-block-syntax-highlighting-rendered.png)
 
-構文強調表示のための言語検出の実行や[サードパーティの文法](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)でご覧いただけます。
+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).
 
-## 参考リンク
+## Further reading
 
-- [{% data variables.product.prodname_dotcom %} Flavored Markdown の仕様](https://github.github.com/gfm/)
-- [基本的な書き方とフォーマットの構文](/articles/basic-writing-and-formatting-syntax)
+- [{% data variables.product.prodname_dotcom %} Flavored Markdown Spec](https://github.github.com/gfm/)
+- "[Basic writing and formatting syntax](/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 0811727590d4..4c5738d5f522 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: 情報を表に編成する
-intro: 表を作成して、コメント、Issue、プルリクエスト、ウィキの情報を編成できます。
+title: Organizing information with tables
+intro: 'You can build tables to organize information in comments, issues, pull requests, and wikis.'
 redirect_from:
   - /articles/organizing-information-with-tables
   - /github/writing-on-github/organizing-information-with-tables
@@ -11,24 +11,23 @@ versions:
   ghec: '*'
 shortTitle: Organized data with tables
 ---
+## Creating a table
 
-## 表を作成する
-
-表は、パイプ文字 (`|`) とハイフン (`-`) を使って作成できます。 ハイフンでヘッダを作成し、パイプ文字で各列を分けます。 正しく表示されるように、表の前には空白行を 1 行追加してください。
+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.
 
 ```markdown
 
-| ヘッダ 1 | ヘッダ 2 |
+| First Header  | Second Header |
 | ------------- | ------------- |
-| 内容セル  | 内容セル  |
-| 内容セル  | 内容セル  |
+| Content Cell  | Content Cell  |
+| Content Cell  | Content Cell  |
 ```
 
-![レンダリングされた表](/assets/images/help/writing/table-basic-rendered.png)
+![Rendered table](/assets/images/help/writing/table-basic-rendered.png)
 
-表の両側のパイプ文字はオプションです。
+The pipes on either end of the table are optional.
 
-セルの幅は変わるので、列がぴったり一致する必要はありません。 各列のヘッダ行には、ハイフンを 3 つ以上使用してください。
+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.
 
 ```markdown
 | Command | Description |
@@ -37,11 +36,13 @@ shortTitle: Organized data with tables
 | git diff | Show file differences that haven't been staged |
 ```
 
-![異なるセル幅で表示された表](/assets/images/help/writing/table-varied-columns-rendered.png)
+![Rendered table with varied cell width](/assets/images/help/writing/table-varied-columns-rendered.png)
+
+{% data reusables.user_settings.enabling-fixed-width-fonts %}
 
-## 表の内容をフォーマットする
+## Formatting content within your table
 
-表では、リンク、インラインのコードブロック、テキストスタイルなどの[フォーマット](/articles/basic-writing-and-formatting-syntax)を使用できます。
+You can use [formatting](/articles/basic-writing-and-formatting-syntax) such as links, inline code blocks, and text styling within your table:
 
 ```markdown
 | Command | Description |
@@ -50,9 +51,9 @@ shortTitle: Organized data with tables
 | `git diff` | Show file differences that **haven't been** staged |
 ```
 
-![テキストをフォーマットして表示された表](/assets/images/help/writing/table-inline-formatting-rendered.png)
+![Rendered table with formatted text](/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 |
@@ -61,9 +62,9 @@ shortTitle: Organized data with tables
 | git diff     | git diff       | git diff      |
 ```
 
-![テキストを左寄せ、右寄せ、センタリングして表示された表](/assets/images/help/writing/table-aligned-text-rendered.png)
+![Rendered table with left, center, and right text alignment](/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 |
@@ -72,9 +73,9 @@ shortTitle: Organized data with tables
 | Pipe     | \|        |
 ```
 
-![パイプ文字をエスケープして表示された表](/assets/images/help/writing/table-escaped-character-rendered.png)
+![Rendered table with an escaped pipe](/assets/images/help/writing/table-escaped-character-rendered.png)
 
-## 参考リンク
+## Further reading
 
-- [{% data variables.product.prodname_dotcom %} Flavored Markdown の仕様](https://github.github.com/gfm/)
-- [基本的な書き方とフォーマットの構文](/articles/basic-writing-and-formatting-syntax)
+- [{% data variables.product.prodname_dotcom %} Flavored Markdown Spec](https://github.github.com/gfm/)
+- "[Basic writing and formatting syntax](/articles/basic-writing-and-formatting-syntax)"
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 868b241f5917..4dbbbda93125 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
@@ -20,7 +20,7 @@ When you close a project board, any configured workflow automation will pause by
 
 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)."
 
-1. Navigate to list of project boards in your repository or organization, or owned by your user account.
+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**.
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 129930c30f03..b290d300bc7d 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,6 +1,6 @@
 ---
-title: クローズされたプロジェクトボードを再びオープンする
-intro: クローズされたプロジェクトボードを再びオープンして、プロジェクトボードに設定されているワークフロー自動化を再開することができます。
+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.
 redirect_from:
   - /github/managing-your-work-on-github/managing-project-boards/reopening-a-closed-project-board
   - /articles/reopening-a-closed-project-board
@@ -12,21 +12,22 @@ versions:
   ghec: '*'
 topics:
   - Pull requests
-shortTitle: プロジェクトボードの再オープン
+shortTitle: Reopen project board
 ---
-
 {% data reusables.projects.project_boards_old %}
 
-プロジェクトボードをクローズすると、プロジェクトボードに設定されているワークフロー自動化はデフォルトで一時停止されます。 詳しい情報については[プロジェクトボードのクローズ](/articles/closing-a-project-board)を参照してください。
+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)."
 
-プロジェクトボードを再びオープンする際、自動化を*同期*するオプションがあります。これにより、ボードに設定されている自動化設定に従って、ボード上のカードの位置を更新します。
+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. 再びオープンするプロジェクトボードに移動します。
+1. Navigate to the project board you want to reopen.
 {% data reusables.project-management.click-menu %}
-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)
+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)
 
-## 参考リンク
+## Further reading
 
-- 「[プロジェクトボードの自動化を設定する](/articles/configuring-automation-for-project-boards)」
+- "[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/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 e0091d01e0d4..b7d8e6e244e6 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: プロジェクトボード上のカードのアーカイブ
-intro: プロジェクトボードのカードをアーカイブすることにより、プロジェクトの過去の経過を失うことなくワークフローを整理できます。
+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.
 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,20 +12,23 @@ versions:
   ghec: '*'
 topics:
   - Pull requests
-shortTitle: ボード上のカードのアーカイブ
+shortTitle: Archive cards on board
 ---
-
 {% data reusables.projects.project_boards_old %}
 
-プロジェクトボードの自動化は、アーカイブされたプロジェクトボードのカードには適用されません。 たとえばプロジェクトボードのアーカイブで Issue をクローズしたとしても、アーカイブされたカードは自動的に "Done" 列には移動しません。 プロジェクトボードアーカイブからカードをリストアすると、そのカードはアーカイブされたときに置かれていた列に戻ります。
+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.
 
-## プロジェクトボード上のカードのアーカイブ
+## Archiving cards on a project board
 
-1. プロジェクトボードで、アーカイブしたいカードを見つけて {% 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)
+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)
 
-## サイドバーからのプロジェクトボード上のカードのリストア
+## Restoring cards on a project board from the sidebar
 
 {% data reusables.project-management.click-menu %}
-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)
+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)
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 39f5423642d5..d4ad5f88aee8 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: Issue の作成
-intro: Issueは様々な方法で作成できるので、ワークフローで最も便利な方法を選択できます。
+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.'
 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,20 +27,23 @@ topics:
   - Pull requests
   - Issues
   - Project management
-shortTitle: Issueの作成
+shortTitle: Create an issue
 type: how_to
 ---
 
-Issue は、バグ、拡張、その他リクエストの追跡に使用できます。 詳細は「[Issue について](/issues/tracking-your-work-with-issues/about-issues)」を参照してください。
+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)."
 
 {% data reusables.repositories.administrators-can-disable-issues %}
 
-## リポジトリからのIssueの作成
+## Creating an issue from a repository
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-issues %}
 {% data reusables.repositories.new_issue %}
-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)
+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)
 {% data reusables.repositories.type-issue-title-and-description %}
 {% data reusables.repositories.assign-an-issue-as-project-maintainer %}
 {% data reusables.repositories.submit-new-issue %}
@@ -61,31 +64,37 @@ 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"
 ```
 
-## コメントからのIssueの作成
-
-IssueもしくはPull Requestのコメントから、新しいIssueをオープンできます。 コメントから開いたIssueには、コメントの元の投稿場所を示すスニペットが含まれています。
-
-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)
+## Creating an issue from a comment
+
+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.
+
+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)
 {% data reusables.repositories.assign-an-issue-as-project-maintainer %}
 {% data reusables.repositories.submit-new-issue %}
 
-## コードからのIssueの作成
+## Creating an issue from code
 
-コードの特定の行または複数の行から、ファイルまたはプルリクエストで Issue を開くことができます。 コードから Issue を開くと、Issue には選択した行またはコードの範囲を示すスニペットが含まれています。 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 で表示されるコードスニペット](/assets/images/help/repository/issue-opened-from-code.png)
+![Code snippet rendered in an issue opened from code](/assets/images/help/repository/issue-opened-from-code.png)
 
 {% data reusables.repositories.navigate-to-repo %}
-1. Issue で参照したいコードを探します。
-    - ファイルのコードに関する Issue を開くには、そのファイルに移動します。
-    - プルリクエストのコードに関する Issue を開くには、そのプルリクエストに移動し、{% octicon "diff" aria-label="The file diff icon" %}[**Files changed**] をクリックします。 次に、コメントに含めたいコードを持っているファイルを探し、[**View**] をクリックします。
+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**.
 {% data reusables.repositories.choose-line-or-range %}
-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)
+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)
 {% data reusables.repositories.type-issue-title-and-description %}
 {% data reusables.repositories.assign-an-issue-as-project-maintainer %}
 {% data reusables.repositories.submit-new-issue %}
@@ -100,48 +109,49 @@ 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 %}
 
-## プロジェクトボードのノートからのIssueの作成
+## Creating an issue from a project board note
 
-プロジェクトボードを使用して作業の追跡や優先順位付けをしている場合、プロジェクトボードの注釈を 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)」を参照してください。
+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)."
 
 {% ifversion fpt or ghec %}
 
-## タスクリストのアイテムからのIssueの作成
+## Creating an issue from a task list item
 
-Issue内で、タスクリストを使って作業を小さなタスクに分割し、作業全体を完了するまで追跡できます。 さらなる追跡あるいはディスカッションがタスクに必要な場合、そのタスクにマウスを移動させ、タスクの右上の{% octicon "issue-opened" aria-label="The issue opened icon" %}をクリックし、Issueに変換できます。 詳しい情報については[タスクリストについて](/issues/tracking-your-work-with-issues/creating-issues/about-task-lists)を参照してください。
+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)."
 
 {% endif %}
 
-## URLクエリからのIssueの作成
+## Creating an issue from a URL query
 
-Issueをオープンするのにクエリパラメータを利用できます。 クエリパラメータはカスタマイズ可能なURLのオプション部分で、{% data variables.product.prodname_dotcom %}上の検索フィルタの結果やIssueテンプレートといった特定のWebページビューを共有できます。 独自のクエリパラメータを作成するには、キーと値のペアをマッチさせなければなりません。
+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.
 
 {% tip %}
 
-**ヒント:** デフォルトのラベル、割り当て、Issue のタイトルを持ってオープンされる Issue テンプレートを作成することもできます。 詳しい情報については「[有益なIssueとPull Requestを促進するためのテンプレートの利用](/communities/using-templates-to-encourage-useful-issues-and-pull-requests)」を参照してください。
+**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)."
 
 {% endtip %}
 
-クエリパラメータを使うには、同等のアクションを行うための適切な権限を持っていなければなりません。 たとえばクエリパラメータの`labels`を使うには、Issueにラベルを追加する権限を持っていなければなりません。 For more information, see "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)."
+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)."
 
 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.
 
-| クエリパラメータ    | サンプル                                                                                                                                                                                                                                                                                                                                                           |
-| ----------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `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)」を参照してください。 |
+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)."
 
 {% ifversion fpt or ghes > 3.3 or ghae-issue-5036 %}
 ## Creating an issue from a {% data variables.product.prodname_code_scanning %} alert
@@ -152,6 +162,6 @@ If you're using issues to track and prioritize your work, you can use issues to
 
 {% endif %}
 
-## 参考リンク
+## Further reading
 
-- [GitHubでの執筆](/github/writing-on-github)
+- "[Writing on 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 6f847a592769..2b2ad52ec4ca 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
@@ -234,4 +234,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/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 85bc7e04622f..c3e5acb97476 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: プロジェクト（ベータ）の作成
-intro: プロジェクトを作成し、展開し、カスタムフィールドを追加する方法を学んでください。
+title: Creating a project (beta)
+intro: 'Learn how to make a project, populate it, and add custom fields.'
 allowTitleToDifferFromFilename: true
 miniTocMaxHeadingLevel: 3
 versions:
@@ -11,11 +11,11 @@ topics:
   - Projects
 ---
 
-プロジェクトは、{% data variables.product.company_short %}のデータと最新の状況を保つアイテムのカスタマイズ可能なコレクションです。 プロジェクトでは、Issue、Pull Request、メモ書きできるアイデアを追跡できます。 カスタムフィールドを追加して、特定の目的のためのビューを作成できます。
+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 reusables.projects.projects-beta %}
 
-## プロジェクトの作成
+## Creating a project
 
 ### Creating an organization project
 
@@ -25,41 +25,41 @@ topics:
 
 {% data reusables.projects.create-user-project %}
 
-## プロジェクトへのアイテムの追加
+## Adding items to your project
 
-プロジェクトは、ドラフトのIssue、Issue、Pull Requestを追跡できます。
+Your project can track draft issues, issues, and pull requests.
 
-### ドラフトIssueの作成
+### Creating draft issues
 
-ドラフトIssueは、素早くアイデアを捕捉するのに役立ちます。
+Draft issues are useful to quickly capture ideas.
 
-1. カーソルをプロジェクトの最下行、{% octicon "plus" aria-label="plus icon" %}の隣に持ってきてください。
-2. アイデアを入力し、**Enter**を押してください。
+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**.
 
 You can convert draft issues into issues. For more information, see [Converting draft issues to issues](#converting-draft-issues-to-issues).
 
-### Issue およびプルリクエスト
+### Issues and pull requests
 
-#### IssueあるいはPull RequestのURLの貼り付け
+#### Paste the URL of an issue or pull request
 
-1. カーソルをプロジェクトの最下行、{% octicon "plus" aria-label="plus icon" %}の隣に持ってきてください。
-1. 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.
 
-#### IssueあるいはPull Requestの検索
+#### Searching for an issue or pull request
 
-1. カーソルをプロジェクトの最下行、{% octicon "plus" aria-label="plus icon" %}の隣に持ってきてください。
-2. `#`を入力してください。
-3. Pull RequestあるいはIssueがあるリポジトリを選択してください。 リポジトリ名の一部を入力して、選択肢を狭めることができます。
-4. 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.
 
-#### IssueあるいはPull Requestの中からプロジェクトをアサインする
+#### Assigning a project from within an issue or pull request
 
-1. プロジェクトに追加したいIssueあるいはPull Requestにアクセスしてください。
-2. サイドバーで**Projects（プロジェクト）**をクリックしてください。
-3. IssueあるいはPull Requestを追加したいプロジェクトを選択してください。
-4. あるいは、カスタムフィールドに入力してください。
+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.
 
-   ![プロジェクトサイドバー](/assets/images/help/issues/project_side_bar.png)
+   ![Project sidebar](/assets/images/help/issues/project_side_bar.png)
 
 ## Converting draft issues to issues
 
@@ -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.
@@ -93,26 +93,27 @@ 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
 
-プロジェクトは、タイトル、アサインされた人、ラベル、マイルストーン、リポジトリへのあらゆる変更を含め、IssueやPull Requestに関する最新の情報を追跡します。 プロジェクトが初期化された時点では、"title（タイトル）"と"assignees（アサインされた人）"が表示されます。他のフィールドは非表示になります。 プロジェクト内でのそれらのフィールドの可視性は変更できます。
+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.
 
 1. {% data reusables.projects.open-command-palette %}
-2. "show"と入力を始めてください。
-3. 希望するコマンド（たとえば"Show: Repository"）を選択してください。
+2. Start typing "show".
+3. Select the desired command (for example: "Show: Repository").
 
-あるいは、これはUIから行うこともできます。
+Alternatively, you can do this in the UI:
 
-1. 右端のフィールドヘッダの{% octicon "plus" aria-label="the plus icon" %}をクリックしてください。 プロジェクトのフィールドのドロップダウンメニューが表示されます。 ![フィールドの表示もしくは非表示](/assets/images/help/issues/projects_fields_menu.png)
-2. 表示あるいは非表示にしたいフィールドを選択してください。 {% octicon "check" aria-label="check icon" %}は、表示されるフィールドを示します。
+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.
 
-### カスタムフィールドの追加
+### Adding custom fields
 
-プロジェクトにカスタムフィールドを追加できます。 カスタムフィールドは、プロジェクトのIssueあるいはPull Requestのサイドバー上に表示されます。
+You can add custom fields to your project. Custom fields will display on the side bar of issues and pull requests in the project.
 
 Custom fields can be text, number, date, single select, or iteration:
 
@@ -122,11 +123,12 @@ 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 %} "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. ドロップダウンメニューを選択し、目的の種類をクリックしてください。
+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.
 
@@ -139,7 +141,7 @@ You can later edit the drop down options for single select and iteration fields.
 
 ## Customizing your views
 
-プロジェクトは、テーブルあるいはボードとしてみることができ、フィールドでのアイテムのグループ化、アイテムのフィルタリングなどができます。 詳しい情報については「[プロジェクト（ベータ）のビューのカスタマイズ](/issues/trying-out-the-new-projects-experience/customizing-your-project-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)."
 
 ## Configuring built-in automation
 
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 6f49d506d908..4b00391366db 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: APIを使ったプロジェクト（ベータ）の管理
-intro: GraphQL APIを使って、プロジェクトに関する情報を見つけたり、プロジェクトを更新したりできます。
+title: Using the API to manage projects (beta)
+intro: You can use the GraphQL API to find information about projects and to update projects.
 versions:
   fpt: '*'
   ghec: '*'
@@ -11,17 +11,17 @@ topics:
   - Projects
 ---
 
-この記事では、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)."
+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)."
 
 {% data reusables.projects.projects-beta %}
 
-## 認証
+## Authentication
 
 {% include tool-switcher %}
 
 {% curl %}
 
-以下のすべての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)."
+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)."
 
 {% endcurl %}
 
@@ -29,15 +29,15 @@ topics:
 
 {% 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. コマンドラインの認証に関する詳しい情報については「[ gh authログイン](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. For more information on command line authentication, see "[gh auth login](https://cli.github.com/manual/gh_auth_login)."
 
 {% endcli %}
 
 {% cli %}
 
-## 変数の利用
+## Using variables
 
-以下のすべての例で、変数を使ってスクリプトをシンプルにできます。 数値、論理値あるいはヌルである変数を渡すには、`-F`を使ってください。 その他の変数には`-f`を使ってください。 例,
+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,
 
 ```shell
 my_org="octo-org"
@@ -52,19 +52,19 @@ 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 %}
 
-## プロジェクトに関する情報を見つける
+## Finding information about projects
 
-プロジェクトに関するデータを取得するには、クエリを使ってください。 詳しい情報については「[クエリについて]({% ifversion ghec%}/free-pro-team@latest{% endif %}/graphql/guides/forming-calls-with-graphql#about-queries)」を参照してください。
+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)."
 
 ### Finding the node ID of an organization project
 
-APIを通じてプロジェクトを更新するには、プロジェクトのノードIDを知る必要があります。
+To update your project through the API, you will need to know the node ID of the project.
 
-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です。
+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 %}
 
@@ -90,7 +90,7 @@ gh api graphql -f query='
 ```
 {% endcli %}
 
-Organization中のすべてのプロジェクトのノードIDを見つけることもできます。 以下の例は、Orgazation中の最初の20個のプロジェクトのノードIDとタイトルを返します。 `ORGANIZATION`をOrganization名で置き換えてください。 たとえば`octo-org`というようにします。
+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 %}
 
@@ -121,9 +121,9 @@ gh api graphql -f query='
 
 ### Finding the node ID of a user project
 
-APIを通じてプロジェクトを更新するには、プロジェクトのノードIDを知る必要があります。
+To update your project through the API, you will need to know the node ID of the project.
 
-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です。
+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 %}
 
@@ -149,7 +149,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. `octocat`などです。
+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 %}
 
@@ -178,11 +178,11 @@ gh api graphql -f query='
 ```
 {% endcli %}
 
-### フィールドのノードIDを見つける
+### Finding the node ID of a field
 
-フィールドの値を更新するには、フィールドのノード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.
+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.
 
-以下の例は、プロジェクト内の最初の20個のフィールドのID、名前、設定を返します。 `PROJECT_ID`をプロジェクトのノードIDで置き換えてください。
+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 %}
 
@@ -214,7 +214,7 @@ gh api graphql -f query='
 ```
 {% endcli %}
 
-レスポンスは以下の例のようになります。
+The response will look similar to the following example:
 
 ```json
 {
@@ -249,13 +249,13 @@ gh api graphql -f query='
 }
 ```
 
-各フィールドは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.
+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.
 
-### プロジェクト中のアイテムに関する情報を見つける
+### Finding information about items in a project
 
-APIでクエリを行い、プロジェクト中のアイテムに関する情報を見つけることができます。
+You can query the API to find information about items in your project.
 
-以下の例は、プロジェクト中の最初の20個のアイテムのタイトルとIDを返します。 それぞれのアイテムについては、プロジェクト中の最初の8個のフィールドの値と名前も返します。 アイテムがIssueあるいはPull Requestの場合、アサインされた最初の10人のログインも返します。 `PROJECT_ID`をプロジェクトのノードIDで置き換えてください。
+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 %}
 
@@ -310,7 +310,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.
 
 ```shell
 {
@@ -321,19 +321,19 @@ gh api graphql -f query='
 }
 ```
 
-## プロジェクトの更新
+## Updating projects
 
-プロジェクトを更新するには、ミューテーションを使ってください。 For more information, see "[About mutations]({% ifversion ghec %}/free-pro-team@latest{% endif %}/graphql/guides/forming-calls-with-graphql#about-mutations)."
+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)."
 
 {% note %}
 
-**ノート:** 同じ呼び出し中で、アイテムを追加して更新することはできません。 `addProjectNextItem`を使ってアイテムを追加し、それから`updateProjectNextItemField`を使ってそのアイテムを更新しなければなりません。
+**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.
 
 {% endnote %}
 
-### プロジェクトへのアイテムの追加
+### Adding an item to a project
 
-以下の例は、プロジェクトにIssueあるいはPull Requestを追加します。 `PROJECT_ID`をプロジェクトのノードIDで置き換えてください。 `CONTENT_ID`を、追加したいIssueあるいはPull RequestのノードIDで置き換えてください。
+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 %}
 
@@ -359,7 +359,7 @@ gh api graphql -f query='
 ```
 {% endcli %}
 
-レスポンスには、新しく作成されたアイテムのノードIDが含まれます。
+The response will contain the node ID of the newly created item.
 
 ```json
 {
@@ -373,11 +373,11 @@ 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で置き換えてください。
+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 %}
 
@@ -412,7 +412,7 @@ gh api graphql -f query='
 
 {% note %}
 
-**ノート:** `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.
+**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.
 
 {% endnote %}
 
@@ -420,8 +420,8 @@ gh api graphql -f query='
 
 The following example will update the value of a single select field for an item.
 
-- `PROJECT_ID` - プロジェクトのノードIDで置き換えてください。
-- `ITEM_ID` - 更新したいアイテムのノードIDで置き換えてください。
+- `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.
 
@@ -460,8 +460,8 @@ gh api graphql -f query='
 
 The following example will update the value of an iteration field for an item.
 
-- `PROJECT_ID` - プロジェクトのノードIDで置き換えてください。
-- `ITEM_ID` - 更新したいアイテムのノードIDで置き換えてください。
+- `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).
 
@@ -496,9 +496,9 @@ gh api graphql -f query='
 ```
 {% endcli %}
 
-### プロジェクトからのアイテムの削除
+### Deleting an item from a project
 
-以下の例は、プロジェクトからアイテムを削除します。 `PROJECT_ID`をプロジェクトのノードIDで置き換えてください。 `ITEM_ID`を、削除したいアイテムのノードIDで置き換えてください。
+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 %}
 
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 18e0211cc7fd..3053a0a101b5 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: Organization のセキュリティおよび分析設定を管理する
-intro: '{% data variables.product.prodname_dotcom %} 上の Organization のプロジェクトでコードを保護し分析する機能を管理できます。'
+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 %}.'
 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,146 +13,164 @@ versions:
 topics:
   - Organizations
   - Teams
-shortTitle: セキュリティと分析の管理
+shortTitle: Manage security & analysis
 ---
 
-## セキュリティおよび分析設定の管理について
+## About management of security and analysis settings
 
-{% data variables.product.prodname_dotcom %} を使用して、Organization のリポジトリを保護できます。 Organization でメンバーが作成する既存または新規のリポジトリすべてについて、セキュリティおよび分析機能を管理できます。 {% ifversion fpt or ghec %}{% data variables.product.prodname_GH_advanced_security %} のライセンスをお持ちの場合は、これらの機能へのアクセスを管理することもできます。 {% 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 %}
 
-## セキュリティと分析の設定を表示する
+## Displaying the security and analysis settings
 
 {% data reusables.profile.access_org %}
 {% data reusables.profile.org_settings %}
 {% data reusables.organizations.security-and-analysis %}
 
-表示されるページでは、Organization 内のリポジトリのすべてのセキュリティおよび分析機能を有効化または無効化にできます。
+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 %}Organization が {% data variables.product.prodname_GH_advanced_security %} のライセンスを持つ Enterprise に属している場合、ページには {% data variables.product.prodname_advanced_security %} 機能を有効化または無効化するオプションも含まれます。 {% data variables.product.prodname_GH_advanced_security %} を使用するリポジトリは、ページの下部に一覧表示されます。{% 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 %}{% 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 %}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 ghae %}このページには、{% 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 %}
 
-## すべての既存のリポジトリに対して機能を有効化または無効化する
+## Enabling or disabling a feature for all existing repositories
 
-すべてのリポジトリの機能を有効化または無効化できます。 {% ifversion fpt or ghec %}変更が Organization 内のリポジトリに与える影響は、リポジトリの可視性によって決まります。
+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:
 
-- **依存関係グラフ** - この機能はパブリックリポジトリに対して常に有効になっているため、変更はプライベートリポジトリにのみ影響します。
-- **{% data variables.product.prodname_dependabot_alerts %}** - 変更はすべてのリポジトリに影響します。
-- **{% data variables.product.prodname_dependabot_security_updates %}** - 変更はすべてのリポジトリに影響します。
-- **{% 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 %}
+- **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 %}
+
+{% endif %}
 
 {% data reusables.advanced-security.note-org-enable-uses-seats %}
 
-1. Organization のセキュリティと分析の設定に移動します。 詳しい情報については、「[セキュリティと分析の設定を表示する](#displaying-the-security-and-analysis-settings)」を参照してください。
-2. [Configure security and analysis features] で、機能の右側にある [**Disable all**] または [**Enable**] をクリックします。 {% 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)
+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 %}
+   {% 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 %}
-   ![[Configure security and analysis] 機能の [Enable all] または [Disable all] ボタン](/assets/images/enterprise/3.3/organizations/security-and-analysis-disable-or-enable-all-ghas.png)
+   !["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)
    {% endif %}
    {% ifversion ghes = 3.1 or ghes = 3.2 %}
-   ![[Configure security and analysis] 機能の [Enable all] または [Disable all] ボタン](/assets/images/enterprise/3.1/help/organizations/security-and-analysis-disable-or-enable-all-ghas.png)
+   !["Enable all" or "Disable all" button for "Configure security and analysis" features](/assets/images/enterprise/3.1/help/organizations/security-and-analysis-disable-or-enable-all-ghas.png)
    {% endif %}
    {% ifversion ghes = 3.0 %}
-   ![[Configure security and analysis] 機能の [Enable all] または [Disable all] ボタン](/assets/images/enterprise/3.0/organizations/security-and-analysis-disable-or-enable-all-ghas.png)
+   !["Enable all" or "Disable all" button for "Configure security and analysis" features](/assets/images/enterprise/3.0/organizations/security-and-analysis-disable-or-enable-all-ghas.png)
    {% endif %}
    {% ifversion ghae %}
-   ![[Configure security and analysis] 機能の [Enable all] または [Disable all] ボタン](/assets/images/enterprise/github-ae/organizations/security-and-analysis-disable-or-enable-all-ghae.png)
+   !["Enable all" or "Disable all" button for "Configure security and analysis" features](/assets/images/enterprise/github-ae/organizations/security-and-analysis-disable-or-enable-all-ghae.png)
    {% endif %}
    {% ifversion fpt or ghes = 3.0 or ghec %}
-3. オプションで、Organization の新しいリポジトリに対して機能をデフォルトで有効にすることもできます。
+3. Optionally, enable the feature by default for new repositories in your organization.
    {% ifversion fpt or ghec %}
-   ![新規のリポジトリの [Enable by default] オプション](/assets/images/help/organizations/security-and-analysis-enable-by-default-in-modal.png)
+   !["Enable by default" option for new repositories](/assets/images/help/organizations/security-and-analysis-enable-by-default-in-modal.png)
    {% endif %}
    {% ifversion ghes = 3.0 %}
-   ![新規のリポジトリの [Enable by default] オプション](/assets/images/enterprise/3.0/organizations/security-and-analysis-secret-scanning-enable-by-default.png)
+   !["Enable by default" option for new repositories](/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. Organization のすべてのリポジトリに対してこの機能を有効または無効にするには、[**Disable FEATURE**] または [**Enable FEATURE**] をクリックします。
+4. Click **Disable FEATURE** or **Enable FEATURE** to disable or enable the feature for all the repositories in your organization.
    {% ifversion fpt or ghec %}
-   ![機能 を無効または有効にするボタン](/assets/images/help/organizations/security-and-analysis-enable-dependency-graph.png)
+   ![Button to disable or enable feature](/assets/images/help/organizations/security-and-analysis-enable-dependency-graph.png)
    {% endif %}
    {% ifversion ghes = 3.0 %}
-   ![機能 を無効または有効にするボタン](/assets/images/enterprise/3.0/organizations/security-and-analysis-enable-secret-scanning.png)
+   ![Button to disable or enable feature](/assets/images/enterprise/3.0/organizations/security-and-analysis-enable-secret-scanning.png)
    {% endif %}
    {% endif %}
    {% ifversion ghae or ghes > 3.0 %}
-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)
+3. Click **Enable/Disable all** or **Enable/Disable for eligible repositories** to confirm the change.
+   ![Button to enable feature for all the eligible repositories in the organization](/assets/images/enterprise/github-ae/organizations/security-and-analysis-enable-secret-scanning-existing-repos-ghae.png)
    {% endif %}
 
    {% data reusables.security.displayed-information %}
 
-## 新しいリポジトリが追加されたときに機能を自動的に有効化または無効化する
+## Enabling or disabling a feature automatically when new repositories are added
 
-1. Organization のセキュリティと分析の設定に移動します。 詳しい情報については、「[セキュリティと分析の設定を表示する](#displaying-the-security-and-analysis-settings)」を参照してください。
-2. [Configure security and analysis features]の下で、機能の右から、Organizatin中の新しいリポジトリ{% ifversion fpt or ghec %}あるいはすべての新しいプライベートリポジトリ{% endif %}でデフォルトでその機能を有効または無効にします。
-   {% ifversion fpt or ghec %}
-   ![新規のリポジトリに対して機能を有効または無効にするチェックボックス](/assets/images/help/organizations/security-and-analysis-enable-or-disable-feature-checkbox-dotcom.png)
+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 %}
+   ![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 %}
-   ![新規のリポジトリに対して機能を有効または無効にするチェックボックス](/assets/images/enterprise/3.3/organizations/security-and-analysis-enable-or-disable-feature-checkbox.png)
+   {% 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 %}
-   ![新規のリポジトリに対して機能を有効または無効にするチェックボックス](/assets/images/enterprise/3.1/help/organizations/security-and-analysis-enable-or-disable-feature-checkbox.png)
+   ![Checkbox for enabling or disabling a feature for new repositories](/assets/images/enterprise/3.1/help/organizations/security-and-analysis-enable-or-disable-feature-checkbox.png)
    {% endif %}
    {% ifversion ghes = 3.0 %}
-   ![新規のリポジトリに対して機能を有効または無効にするチェックボックス](/assets/images/enterprise/3.0/organizations/security-and-analysis-enable-or-disable-secret-scanning-checkbox.png)
+   ![Checkbox for enabling or disabling a feature for new repositories](/assets/images/enterprise/3.0/organizations/security-and-analysis-enable-or-disable-secret-scanning-checkbox.png)
    {% endif %}
    {% ifversion ghae %}
-   ![新規のリポジトリに対して機能を有効または無効にするチェックボックス](/assets/images/enterprise/github-ae/organizations/security-and-analysis-enable-or-disable-secret-scanning-checkbox-ghae.png)
+   ![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 -->
 
-## {% data variables.product.prodname_dependabot %} のプライベート依存関係へのアクセスを許可する
+## Allowing {% data variables.product.prodname_dependabot %} to access private dependencies
 
-{% data variables.product.prodname_dependabot %} は、プロジェクト内の古い依存関係参照をチェックし、それらを更新するためのプルリクエストを自動的に生成できます。 これを行うには、{% data variables.product.prodname_dependabot %} がすべてのターゲット依存関係ファイルにアクセスできる必要があります。 通常、1 つ以上の依存関係にアクセスできない場合、バージョン更新は失敗します。 詳しい情報については、「[{% data variables.product.prodname_dependabot %} バージョン更新について](/github/administering-a-repository/about-dependabot-version-updates)」を参照してください。
+{% 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 %} はプライベートリポジトリまたはプライベートパッケージレジストリにある依存関係を更新できません。 ただし、依存関係が、その依存関係を使用するプロジェクトと同じ Organization 内のプライベート {% data variables.product.prodname_dotcom %} リポジトリにある場合は、ホストリポジトリへのアクセスを許可することで、{% data variables.product.prodname_dependabot %} がバージョンを正常に更新できるようにすることができます。
+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 %} がこれらの依存関係のバージョンを更新できるようにすることができます。 これを行うには、リポジトリの _dependabot.yml_ ファイルに認証の詳細を追加します。 詳しい情報については、「[依存関係の更新の設定オプション](/github/administering-a-repository/configuration-options-for-dependency-updates#configuration-options-for-private-registries) 」を参照してください。
+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 %} がプライベート {% data variables.product.prodname_dotcom %} リポジトリにアクセスできるようにするには：
+To allow {% data variables.product.prodname_dependabot %} to access a private {% data variables.product.prodname_dotcom %} repository:
 
-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. 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. あるいは、リストからリポジトリを差k除するには、リポジトリの右の{% octicon "x" aria-label="The X icon" %}をクリックします。 ![リポジトリを削除する [X] ボタン](/assets/images/help/organizations/dependabot-private-repository-list.png)
+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)
 {% endif %}
 
-{% ifversion fpt or ghes > 3.0 or ghec %}
+{% ifversion ghes > 3.0 or ghec %}
 
-## Organization 内の個々のリポジトリから {% data variables.product.prodname_GH_advanced_security %} へのアクセスを削除する
+## Removing access to {% data variables.product.prodname_GH_advanced_security %} from individual repositories in an 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 %} 機能を無効にすることもできます。
+You can manage access to {% data variables.product.prodname_GH_advanced_security %} features for a repository from its "Settings" tab. For more information, see "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)." However, you can also disable {% data variables.product.prodname_GH_advanced_security %} features for a repository from the "Settings" tab for the organization.
 
-1. 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 %} の機能へのアクセスを削除します。
+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 %}.
 
 {% note %}
 
-**注釈:** リポジトリの {% data variables.product.prodname_GH_advanced_security %} へのアクセスを削除する場合は、影響を受ける開発チームと連絡を取り、変更が意図されたものかを確認する必要があります。 これにより、失敗したコードスキャンの実行をデバッグすることに時間を費すことがなくなります。
+**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.
 
 {% endnote %}
 
 {% endif %}
 
-## 参考リンク
+## Further reading
 
-- 「[リポジトリをセキュアにする](/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 %}
-- [依存関係グラフについて](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)
-- 「[プロジェクトの依存関係にある脆弱性を管理する](/github/managing-security-vulnerabilities/managing-vulnerabilities-in-your-projects-dependencies)」{% endif %}
+- "[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 %}
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 08a2b3eb702e..c6eb09d51919 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
@@ -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 %}
@@ -662,15 +662,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 +697,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/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 7a0e4bbd0d08..0a64d782c971 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
@@ -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** |
@@ -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/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 1d9605802b7c..ad9f8d0d0002 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
@@ -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 %}
 
@@ -36,16 +40,18 @@ 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. 詳しい情報については「[OrganizationリポジトリへのTeamのアクセス管理](/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. 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)."
 
 {% 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/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 6c9b1b78368c..761cda09ece3 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,87 +1,85 @@
 ---
-title: GitHub Packagesの権限について
-intro: パッケージの権限の管理方法を学んでください。
+title: About permissions for GitHub Packages
+intro: Learn about how to manage permissions for your packages.
 product: '{% data reusables.gated-features.packages %}'
 versions:
   fpt: '*'
   ghes: '*'
   ghae: '*'
   ghec: '*'
-shortTitle: 権限について
+shortTitle: About permissions
 ---
 
 {% ifversion fpt or ghec %}
-パッケージの権限は、リポジトリスコープかユーザ/Organizationスコープです。
+The permissions for packages are either repository-scoped or user/organization-scoped.
 {% endif %}
 
-## リポジトリスコープのパッケージの権限
+## Permissions for repository-scoped packages
 
-リポジトリスコープのパッケージは、パッケージを所有するリポジトリの権限と可視性を継承します。 リポジトリをスコープとするパッケージは、リポジトリのメインページにアクセスし、ページ右にある**パッケージ**リンクをクリックすれば見つかります。 {% ifversion fpt or ghec %}詳しい情報については「[リポジトリのパッケージへの接続](/packages/learn-github-packages/connecting-a-repository-to-a-package)」を参照してください。{% endif %}
+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 %}
 
-以下の{% data variables.product.prodname_registry %}レジストリは、リポジトリスコープの権限を使います。
+The {% data variables.product.prodname_registry %} registries below use repository-scoped permissions:
 
-  {% ifversion not fpt or ghec %}-Dockerレジストリ（`docker.pkg.github.com`）{% endif %}
-  - npmレジストリ
-  - RubyGemsレジストリ
-  - Apache Mavenレジストリ
-  - NuGetレジストリ
+  {% ifversion not fpt or ghec %}- Docker registry (`docker.pkg.github.com`){% endif %}
+  - npm registry
+  - RubyGems registry
+  - Apache Maven registry
+  - NuGet registry
 
 {% ifversion fpt or ghec %}
-## ユーザ/Organizationスコープのパッケージの詳細な権限
+## 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.
 
-現在の処、{% data variables.product.prodname_container_registry %}だけがコンテナイメージパッケージに関する詳細な権限を提供しています。
+Currently, only the {% data variables.product.prodname_container_registry %} offers granular permissions for your container image packages.
 
-## コンテナイメージの可視性とアクセス権限
+## Visibility and access permissions for container images
 
 {% data reusables.package_registry.visibility-and-access-permissions %}
 
-詳しい情報については「[パッケージのアクセス制御と可視性](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility)」を参照してください。
+For more information, see "[Configuring a package's access control and visibility](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility)."
 
 {% endif %}
 
-## パッケージの管理
+## About scopes and permissions for package registries
 
-パッケージレジストリでホストされているパッケージを使用もしくは管理するためには、適切なスコープを持つトークンを使わなければならず、ユーザアカウントが適切な権限を持っていなければなりません。
+To use or manage a package hosted by a package registry, you must use a token with the appropriate scope, and your user account must have appropriate permissions.
 
-例:
--  リポジトリからパッケージをダウンロードしてインストールするには、トークンは`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 %}[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 %}."
+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`                                                                                                                                                                                                                                                                                                                                                | {% data variables.product.prodname_registry %}からのパッケージのダウンロードとインストール | 読み取り         |
-| `write:packages`                                                                                                                                                                                                                                                                                                                                               | {% data variables.product.prodname_registry %}へのパッケージのアップロードと公開      | 書き込み         |
-| `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 %} |                                                                      |              |
-| 管理                                                                                                                                                                                                                                                                                                                                                             |                                                                      |              |
-| `repo`                                                                                                                                                                                                                                                                                                                                                         | パッケージのアップロードと削除 (`write:packages`または`delete:packages`と併せて)           | 書き込みもしくは読み取り |
+| 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 |
 
-{% data variables.product.prodname_actions %}ワークフローを作成する際には、`GITHUB_TOKEN`を使って{% data variables.product.prodname_registry %}にパッケージを公開してインストールでき、個人アクセストークンを保存して管理する必要はありません。
+When you create a {% data variables.product.prodname_actions %} workflow, you can use the `GITHUB_TOKEN` to publish and install packages in {% data variables.product.prodname_registry %} without needing to store and manage a personal access token.
 
 For more information, see:{% 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キー、個人を識別する情報といったセンシティブなデータを含むパッケージを公開した時
+- "[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)"
 
-## {% data variables.product.prodname_actions %}ワークフローでのパッケージへのアクセスのメンテナンス
+## 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 %}に関する概念的な背景や、ワークフローでのパッケージの使用例については、「[GitHub Actionsワークフローを使用したGitHub Packagesの管理](/packages/managing-github-packages-using-github-actions-workflows)」を参照してください。
+For more conceptual background on {% data variables.product.prodname_actions %} or examples of using packages in workflows, see "[Managing GitHub Packages using GitHub Actions workflows](/packages/managing-github-packages-using-github-actions-workflows)."
 
-### アクセストークン
+### Access tokens  
 
-- ワークフローリポジトリに関連するパッケージを公開するには、`GITHUB_TOKEN`を使用してください。
-- `GITHUB_TOKEN`がアクセスできない他のプライベートリポジトリに関連するパッケージをインストールするには、個人アクセストークンを使用してください。
+- 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
 
-{% data variables.product.prodname_actions %}ワークフローで使われる`GITHUB_TOKEN`に関する詳しい情報については「[ワークフローでの認証](/actions/reference/authentication-in-a-workflow#using-the-github_token-in-a-workflow)」を参照してください。
+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)."
 
 {% ifversion fpt or ghec %}
-### コンテナイメージに対する{% data variables.product.prodname_actions %}アクセス
+### {% data variables.product.prodname_actions %} access for container images
 
-ワークフローがコンテナイメージに確実にアクセスできるようにするには、ワークフローが実行されるリポジトリへの{% data variables.product.prodname_actions %}アクセスを有効化しなければなりません。 この設定は、パッケージの設定ページにあります。 詳しい情報については「[パッケージへのワークフローアクセスの保証](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility#ensuring-workflow-access-to-your-package)」を参照してください。
+To ensure your workflows have access to your container image, you must enable {% data variables.product.prodname_actions %} access to the repositories where your workflow is run. You can find this setting on your package's settings page. For more information, see "[Ensuring workflow access to your package](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility#ensuring-workflow-access-to-your-package)."
 
 {% endif %}
diff --git a/translations/ja-JP/content/packages/learn-github-packages/deleting-a-package.md b/translations/ja-JP/content/packages/learn-github-packages/deleting-a-package.md
index 56a00d1b5b66..b1e3ac123094 100644
--- a/translations/ja-JP/content/packages/learn-github-packages/deleting-a-package.md
+++ b/translations/ja-JP/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/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 f4a16e4e0ef4..26d0725a9ba0 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: パッケージを削除および復元する
-intro: パッケージの削除と復元の方法を学びます。
+title: Deleting and restoring a package
+intro: Learn how to delete or restore a package.
 product: '{% data reusables.gated-features.packages %}'
 redirect_from:
   - /github/managing-packages-with-github-packages/deleting-a-package
@@ -11,84 +11,91 @@ versions:
   fpt: '*'
   ghes: '>=3.1'
   ghec: '*'
-shortTitle: パッケージの削除と復元
+  ghae: '*'
+shortTitle: Delete & restore a package
 ---
 
 {% data reusables.package_registry.packages-ghes-release-stage %}
 
-## {% data variables.product.prodname_dotcom %}におけるパッケージの削除および復元のサポート
+## Package deletion and restoration support on {% data variables.product.prodname_dotcom %}
 
-{% data variables.product.prodname_dotcom %}では、必要なアクセス権がある場合、以下を削除できます。
-- プライベートパッケージ全体
-- パッケージの全バージョンでダウンロード数が5000以下の場合、パブリックパッケージ全体
-- プライベートパッケージの特定のバージョン
-- パッケージバージョンのダウンロード数が5000以下の場合、パブリックパッケージの特定のバージョン
+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
 
 {% note %}
 
-**注釈:**
-- パッケージのいずれかのパージョンでダウンロード数が5000を超えている場合は、パブリックパッケージを削除できません。 この場合は、[GitHubサポート](https://support.github.com/contact?tags=docs-packages)までお問い合わせください。
-- パブリックパッケージを削除する場合、そのパッケージに依存するプロジェクトを破壊する可能性があることに注意してください。
+**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.
 
 {% endnote %}
 
-{% data variables.product.prodname_dotcom %}では、以下の場合にパッケージ全体またはパッケージバージョンを復元できます。
-- 削除後30日以内にパッケージを復元する。
-- 同一のパッケージ名前空間が使用可能であり、新しいパッケージで使用されていない。
+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.
 
-## パッケージAPIのサポート
+{% ifversion fpt or ghec or ghes %}
+## Packages API support
 
 {% ifversion fpt or ghec %}
 
-REST APIを使用してパッケージを管理できます。 詳しい情報については、「[{% data variables.product.prodname_registry %} API](/rest/reference/packages)」を参照してください。
+You can use the REST API to manage your packages. For more information, see the "[{% data variables.product.prodname_registry %} API](/rest/reference/packages)."
 
 {% 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 %}
 
-## パッケージの削除や復元に必要な権限
+## 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.
 
-{% data variables.product.prodname_registry %}上でリポジトリのスコープが付いたパッケージには、以下が挙げられます。
+Repository-scoped packages on {% data variables.product.prodname_registry %} include these packages:
 - npm
 - RubyGems
 - maven
 - Gradle
 - NuGet
-{% ifversion not fpt or ghec %}-`docker.pkg.github.com/OWNER/REPOSITORY/IMAGE-NAME`にあるDockerイメージ{% endif %}
+{% ifversion not fpt or ghec %}- Docker images at `docker.pkg.github.com/OWNER/REPOSITORY/IMAGE-NAME`{% endif %}
 
 {% 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.-->
+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)."
 
 {% endif %}
 
-## パッケージのバージョンを削除する
+## Deleting a package version
 
-### {% data variables.product.prodname_dotcom %}上でリポジトリのスコープが付いたバージョンを削除する
+### Deleting a version of a repository-scoped package on {% data variables.product.prodname_dotcom %}
 
-リポジトリのスコープが付いたパッケージのバージョンを削除するには、パッケージを所有するリポジトリの管理者権限が必要です。 詳しい情報については、「[必要な権限](#required-permissions-to-delete-or-restore-a-package)」を参照してください。
+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)."
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.package_registry.packages-from-code-tab %}
 {% data reusables.package_registry.package-settings-option %}
-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)
+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)
 
-### GraphQLでリポジトリのスコープが付いたパッケージのバージョンを削除する
+{% 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.
 
 {% ifversion fpt or ghec %}
-GraphQLは、`ghcr.io`にあるコンテナやDockerイメージではサポートされていません。
-{% 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. For more information, see the "[{% 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)."
 
-以下の例では、`MDIyOlJlZ2lzdHJ5UGFja2FnZVZlcnNpb243MTExNg`の`packageVersionId`を使用して、パッケージバージョンを削除する方法を示します。
+The following example demonstrates how to delete a package version, using a `packageVersionId` of `MDIyOlJlZ2lzdHJ5UGFja2FnZVZlcnNpb243MTExNg`.
 
 ```shell
 curl -X POST \
@@ -98,121 +105,148 @@ curl -X POST \
 HOSTNAME/graphql
 ```
 
-パッケージのバージョンIDと併せて{% data variables.product.prodname_registry %}に公開したすべてプライベートパッケージを見つけるには、`registryPackagesForQuery`コネクションが利用できます。 `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.
+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.
 
-`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 %}上に表示されなくなります。
+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 %}
-### {% data variables.product.prodname_dotcom %}上でユーザのスコープが付いたパッケージのバージョンを削除する
+### Deleting a version of a user-scoped package on {% data variables.product.prodname_dotcom %}
 
-`ghcr.io`にあるDockerイメージなどで、 {% data variables.product.prodname_dotcom %}上のユーザのスコープが付いたパッケージの、特定のバージョンを削除するには、以下のステップに従ってください。 パッケージ全体を削除するには、「[{% data variables.product.prodname_dotcom %}上でユーザのスコープが付いたパッケージ全体を削除する](#deleting-an-entire-user-scoped-package-on-github)」を参照してください。
+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)."
 
-パッケージのバージョンを削除できるユーザを確認するには、「[必要な権限](#required-permissions-to-delete-or-restore-a-package)」を参照してください。
+To review who can delete a package version, see "[Required permissions](#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. 左にある [**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)
+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)
 
-### GitHub上でOrganizationのスコープが付いたパッケージのバージョンを削除する
+### Deleting a version of an organization-scoped package on {% data variables.product.prodname_dotcom %}
 
-`ghcr.io`にあるDockerイメージなどで、{% data variables.product.prodname_dotcom %}上のOrganizationのスコープが付いたパッケージの、特定のバージョンを削除するには、以下のステップに従ってください。 パッケージ全体を削除するには、「[{% data variables.product.prodname_dotcom %}上でOrganizationのスコープが付いたパッケージ全体を削除する](#deleting-an-entire-organization-scoped-package-on-github)」を参照してください。
+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)."
 
-パッケージのバージョンを削除できるユーザを確認するには、「[必要な権限](#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 %}
-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)
+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)
 {% endif %}
 
-## パッケージ全体を削除する
+## Deleting an entire package
 
-### {% data variables.product.prodname_dotcom %}上でリポジトリのスコープが付いたパッケージ全体を削除する
+### Deleting an entire repository-scoped package on {% data variables.product.prodname_dotcom %}
 
-リポジトリのスコープが付いたパッケージ全体を削除するには、パッケージを所有するリポジトリの管理者権限が必要です。 詳しい情報については、「[必要な権限](#required-permissions-to-delete-or-restore-a-package)」を参照してください。
+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)."
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.package_registry.packages-from-code-tab %}
 {% data reusables.package_registry.package-settings-option %}
-4. [Danger Zone] の下にある [**Delete this package**] をクリックします。
-5. 確認メッセージを読み、パッケージ名を入力してから、[**I understand, delete this package.**] をクリックします。 ![パッケージの削除の確認ボタン](/assets/images/help/package-registry/package-version-deletion-confirmation.png)
+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)
 
 {% ifversion fpt or ghec %}
-### {% data variables.product.prodname_dotcom %}上でユーザのスコープが付いたパッケージ全体を削除する
+### Deleting an entire user-scoped package on {% data variables.product.prodname_dotcom %}
 
-パッケージを削除できるユーザを確認するには、「[必要な権限](#required-permissions-to-delete-or-restore-a-package)」を参照してください。
+To review who can delete a package, see "[Required permissions](#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. 左側にある [**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)
+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)
 
-### {% data variables.product.prodname_dotcom %}上でOrganizationのスコープが付いたパッケージ全体を削除する
+### Deleting an entire organization-scoped package on {% data variables.product.prodname_dotcom %}
 
-パッケージを削除できるユーザを確認するには、「[必要な権限](#required-permissions-to-delete-or-restore-a-package)」を参照してください。
+To review who can delete a package, see "[Required permissions](#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. 左側にある [**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)
+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)
 {% endif %}
 
-## パッケージを復元する
+## Restoring packages
 
-以下の場合、削除したパッケージまたはバージョンを復元できます。
-- 削除後30日以内にパッケージを復元する。
-- 同一のパッケージ名前空間がまだ使用可能であり、新しいパッケージで再使用されていない。
+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.
 
-たとえば、リポジトリ`octo-repo-owner/octo-repo`のスコープが付いていた、`octo-package`という名前のrubygemパッケージを削除した場合、パッケージ名前空間`rubygem.pkg.github.com/octo-repo-owner/octo-repo/octo-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.
 
-また、次の権限要件のいずれかを満たす必要もあります。
+{% 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 %}
 
-詳しい情報については、「[必要な権限](#required-permissions-to-delete-or-restore-a-package)」を参照してください。
+For more information, see "[Required permissions](#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.
 
-### Organization内のパッケージを復元する
+### 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 %}.
 
-Organizationでパッケージを復元できるユーザを確認するには、「[必要な権限](#required-permissions-to-delete-or-restore-a-package)」を参照してください。
+To review who can restore a package in an organization, see "[Required permissions](#required-permissions-to-delete-or-restore-a-package)."
 
 {% data reusables.organizations.navigate-to-org %}
 {% data reusables.organizations.org_settings %}
-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)
+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)
 
 {% ifversion fpt or ghec %}
 
-### ユーザアカウントのスコープが付いたパッケージを復元する
+### Restoring a user-account scoped package
 
-パッケージが所有するリポジトリにあったか、ユーザアカウントのスコープが付いていた場合、削除されたパッケージをユーザアカウント設定から復元できます。 詳しい情報については、「[必要な権限](#required-permissions-to-delete-or-restore-a-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)."
 
 {% data reusables.user_settings.access_settings %}
-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)
+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)
 
 {% endif %}
 
-### パッケージのバージョンを復元する
+### Restoring a package version
 
-パッケージのランディングページから、パッケージのバージョンを復元できます。 パッケージを復元できるユーザを確認するには、「[必要な権限](#required-permissions-to-delete-or-restore-a-package)」を参照してください。
+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)."
 
-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)
+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)
diff --git a/translations/ja-JP/content/packages/learn-github-packages/introduction-to-github-packages.md b/translations/ja-JP/content/packages/learn-github-packages/introduction-to-github-packages.md
index 63268fe2a232..aa1182e2f8cf 100644
--- a/translations/ja-JP/content/packages/learn-github-packages/introduction-to-github-packages.md
+++ b/translations/ja-JP/content/packages/learn-github-packages/introduction-to-github-packages.md
@@ -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/ja-JP/content/packages/working-with-a-github-packages-registry/working-with-the-apache-maven-registry.md b/translations/ja-JP/content/packages/working-with-a-github-packages-registry/working-with-the-apache-maven-registry.md
index a494c22c1126..74d94bffcfa9 100644
--- a/translations/ja-JP/content/packages/working-with-a-github-packages-registry/working-with-the-apache-maven-registry.md
+++ b/translations/ja-JP/content/packages/working-with-a-github-packages-registry/working-with-the-apache-maven-registry.md
@@ -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/ja-JP/content/packages/working-with-a-github-packages-registry/working-with-the-docker-registry.md b/translations/ja-JP/content/packages/working-with-a-github-packages-registry/working-with-the-docker-registry.md
index e27195ffd4db..4abbabae7099 100644
--- a/translations/ja-JP/content/packages/working-with-a-github-packages-registry/working-with-the-docker-registry.md
+++ b/translations/ja-JP/content/packages/working-with-a-github-packages-registry/working-with-the-docker-registry.md
@@ -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/ja-JP/content/packages/working-with-a-github-packages-registry/working-with-the-gradle-registry.md b/translations/ja-JP/content/packages/working-with-a-github-packages-registry/working-with-the-gradle-registry.md
index 92f12983f8e9..3db0070fdbc4 100644
--- a/translations/ja-JP/content/packages/working-with-a-github-packages-registry/working-with-the-gradle-registry.md
+++ b/translations/ja-JP/content/packages/working-with-a-github-packages-registry/working-with-the-gradle-registry.md
@@ -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/ja-JP/content/packages/working-with-a-github-packages-registry/working-with-the-npm-registry.md b/translations/ja-JP/content/packages/working-with-a-github-packages-registry/working-with-the-npm-registry.md
index 6f606db0cbb4..1163c54a5f6e 100644
--- a/translations/ja-JP/content/packages/working-with-a-github-packages-registry/working-with-the-npm-registry.md
+++ b/translations/ja-JP/content/packages/working-with-a-github-packages-registry/working-with-the-npm-registry.md
@@ -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/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 347a099de337..24357fc22311 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
@@ -233,4 +233,4 @@ Your NuGet package may fail to push if the `RepositoryUrl` in *.csproj* is not s
 
 ## 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/ja-JP/content/packages/working-with-a-github-packages-registry/working-with-the-rubygems-registry.md b/translations/ja-JP/content/packages/working-with-a-github-packages-registry/working-with-the-rubygems-registry.md
index 7afbca5c42b3..22d46ba47ad5 100644
--- a/translations/ja-JP/content/packages/working-with-a-github-packages-registry/working-with-the-rubygems-registry.md
+++ b/translations/ja-JP/content/packages/working-with-a-github-packages-registry/working-with-the-rubygems-registry.md
@@ -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/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 e80d8bbb5639..b0a0606bd748 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: HTTPS で GitHub Pages サイトを保護する
-intro: 'HTTPS は、他者によるあなたのサイトへのトラフィックの詮索や改ざんを防ぐ暗号化のレイヤーを追加します。 透過的に HTTP リクエストを HTTPS にリダイレクトするために、あなたの {% data variables.product.prodname_pages %} サイトに HTTPS を強制できます。'
+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.'
 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: HTTPSでのサイトの保護
+shortTitle: Secure site with HTTPS
 ---
 
-リポジトリの管理者権限があるユーザは、{% data variables.product.prodname_pages %} サイトに強制的に HTTPS を指定できます。
+People with admin permissions for a repository can enforce HTTPS for a {% data variables.product.prodname_pages %} site.
 
-## HTTPS と {% data variables.product.prodname_pages %} について
+## About HTTPS and {% data variables.product.prodname_pages %}
 
-カスタムドメインが正しく設定されたサイトを含めたすべての {% 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)」を参照してください。
+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 reusables.pages.no_sensitive_data_pages %}
 
@@ -29,35 +29,42 @@ shortTitle: HTTPSでのサイトの保護
 
 {% endnote %}
 
-## あなたの {% data variables.product.prodname_pages %} サイトに HTTPS を強制する
+## Enforcing HTTPS for your {% data variables.product.prodname_pages %} site
 
 {% data reusables.pages.navigate-site-repo %}
 {% data reusables.repositories.sidebar-settings %}
 {% data reusables.pages.sidebar-pages %}
-3. [{% data variables.product.prodname_pages %}] で、[**Enforce HTTPS**] を選択します。 ![[Enforce HTTPS] チェックボックス](/assets/images/help/pages/enforce-https-checkbox.png)
+3. Under "{% data variables.product.prodname_pages %}," select **Enforce HTTPS**.
+  ![Enforce HTTPS checkbox](/assets/images/help/pages/enforce-https-checkbox.png)
 
-## 混在したコンテンツの問題を解決する
+## Troubleshooting certificate provisioning ("Certificate not yet created" error")
 
-{% data variables.product.prodname_pages %} サイトの HTTPS を有効化したが、サイトの HTML がまだ HTTP 経由で画像、CSS、JavaScript を参照している場合、サイトは*混在したコンテンツ*を提供する場合があります。 混在したコンテンツを提供することで、サイトのセキュリティが下がり、アセットの読み込みに問題が生じる場合があります。
+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.
 
-サイトでコンテンツの混在を解消するには、サイトの HTML で `http://` を `https://` に変更して、すべてのアセットが HTTPS 経由で提供されるようにしてください。
+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.
 
-アセットは通常、以下の場所にあります。
-- サイトで Jekyll を使用している場合、HTML ファイルは *_layouts* フォルダにあります。
-- CSS は普通、HTML ファイルの `<head>` セクションにあります。
-- JavaScript は通常、`<head>` セクションまたは閉じタグ `</body>` の直前にあります。
-- 画像はたいてい、`<body>` セクションにあります。
+## 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.
+
+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.
+
+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.
 
 {% tip %}
 
-**ヒント:** サイトのソースファイルでアセットが見つからない場合は、テキストエディタまたは {% data variables.product.product_name %} 上で、サイトのソースファイルから `http`を検索してみましょう。
+**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 %}.
 
 {% endtip %}
 
-### HTML ファイルで参照されているアセットの例
+### Examples of assets referenced in an HTML file
 
-|  アセットのタイプ  |                                                       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>` |  
+| 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>`  
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 79d880a5c6e2..fc4cd43b04b6 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 %}. 独自のクエリパラメータを作成するには、キーと値のペアをマッチさせなければなりません。
+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.
 
 {% tip %}
 
-**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)」を参照してください。
+**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)."
 
 {% endtip %}
 
-クエリパラメータを使うには、同等のアクションを行うための適切な権限を持っていなければなりません。 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)."
+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)."
 
 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.
 
-| クエリパラメータ     | サンプル                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
-| ------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `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)」を参照してください。 |
+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)."
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 c43e0c7eb545..6de225c336f9 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: プルリクエスト内の依存関係の変更をレビューする
-intro: プルリクエストに依存関係への変更が含まれている場合は、変更内容の概要と、依存関係に既知の脆弱性があるかどうかを確認できます。
+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.'
 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 %}. 詳しい情報については、「[{% 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 %}. 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 %}
 
-依存関係のレビューでは、「左にシフト」することができます。 提供された予測情報を使用して、本番環境に至る前に脆弱性のある依存関係をキャッチできます。 For more information, see "[About dependency review](/code-security/supply-chain-security/about-dependency-review)."
+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)."
 
-## プルリクエスト内の依存関係を確認する
+## Reviewing dependencies in a pull request
 
 {% data reusables.repositories.sidebar-pr %}
 {% data reusables.repositories.choose-pr-review %}
 {% data reusables.repositories.changed-files %}
 
-1. プルリクエストに多数のファイルが含まれている場合は、[**File filter**] ドロップダウンメニューを使用して、依存関係を記録しないすべてのファイルを折りたたみます。 これにより、レビューを依存関係の変更に焦点を絞りやすくなります。
+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.
 
-   ![ファイルフィルタメニュー](/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.
+   ![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.
 
   {% note %}
 
@@ -49,31 +49,31 @@ shortTitle: Review dependency changes
 
    {% endnote %}
 
-1. マニフェストまたはロックファイルのヘッダの右側で、**リッチ{% octicon "file" aria-label="The rich diff icon" %}** diff ボタンをクリックして依存関係のレビューを表示します。
+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.
 
-   ![リッチ diff ボタン](/assets/images/help/pull_requests/dependency-review-rich-diff.png)
+   ![The rich diff button](/assets/images/help/pull_requests/dependency-review-rich-diff.png)
 
-2. 依存関係のレビューにリストされている依存関係を確認します。
+2. Check the dependencies listed in the dependency review.
 
-   ![依存関係のレビューにおける脆弱性の警告](/assets/images/help/pull_requests/dependency-review-vulnerability.png)
+   ![Vulnerability warnings in a dependency review](/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.
 
-   各依存関係の横にあるアイコンは、このプルリクエストで依存関係が追加された (<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>) ことを示しています。
+   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.
 
-   その他の情報は次のとおりです。
+   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:
 
-   * 脆弱性の簡単な説明。
-   * Common Vulnerabilities and Exposures (CVE) または {% data variables.product.prodname_security_advisories %} (GHSA) 識別番号。 この ID をクリックすると、脆弱性の詳細を確認できます。
-   * 脆弱性の重要度。
-   * 脆弱性が修正された依存関係のバージョン。 誰かのプルリクエストを確認している場合は、パッチを適用したバージョンまたはそれ以降のリリースに依存関係を更新するようにコントリビューターに依頼することができます。
+   * 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.
 
 {% data reusables.repositories.return-to-source-diff %}
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 6e91cda0c6f7..f9a5eda3a696 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
@@ -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/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 2d760fe6f2ca..08f567b7b363 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
@@ -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/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 fe9eb1dd68d4..e8587b730661 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
@@ -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/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 fd64a80a8175..04e3abaa6d43 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
@@ -111,8 +111,9 @@ Now the checks will always pass whenever someone sends a pull request that doesn
 
 {% 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/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 0181b7ae84e7..1619c037aa9e 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
@@ -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/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 60c27fc3591c..96c2ccfa4b27 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
@@ -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/ja-JP/data/features/enterprise-owners-visible-for-org-members.yml b/translations/ja-JP/data/features/enterprise-owners-visible-for-org-members.yml
new file mode 100644
index 000000000000..1b0a06a45fe2
--- /dev/null
+++ b/translations/ja-JP/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/ja-JP/data/features/fixed-width-font-gfm-fields.yml b/translations/ja-JP/data/features/fixed-width-font-gfm-fields.yml
new file mode 100644
index 000000000000..2c9ea31ac655
--- /dev/null
+++ b/translations/ja-JP/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/ja-JP/data/release-notes/github-ae/2021-06/2021-12-06.yml b/translations/ja-JP/data/release-notes/github-ae/2021-06/2021-12-06.yml
index 770966b82157..9205e8151dfa 100644
--- a/translations/ja-JP/data/release-notes/github-ae/2021-06/2021-12-06.yml
+++ b/translations/ja-JP/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/ja-JP/data/reusables/actions/actions-group-concurrency.md b/translations/ja-JP/data/reusables/actions/actions-group-concurrency.md
index 2c756b7b2ebb..aa880cb90f1b 100644
--- a/translations/ja-JP/data/reusables/actions/actions-group-concurrency.md
+++ b/translations/ja-JP/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/ja-JP/data/reusables/actions/cd-templates-actions.md b/translations/ja-JP/data/reusables/actions/cd-templates-actions.md
index 8bc2c822266d..7bc93daf9a4d 100644
--- a/translations/ja-JP/data/reusables/actions/cd-templates-actions.md
+++ b/translations/ja-JP/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/ja-JP/data/reusables/actions/workflow-organization-templates.md b/translations/ja-JP/data/reusables/actions/workflow-organization-templates.md
index a3ba7572e49a..0dc4dc05b0e2 100644
--- a/translations/ja-JP/data/reusables/actions/workflow-organization-templates.md
+++ b/translations/ja-JP/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/ja-JP/data/reusables/actions/workflow-template-overview.md b/translations/ja-JP/data/reusables/actions/workflow-template-overview.md
index 17513477e45e..ee0b46242061 100644
--- a/translations/ja-JP/data/reusables/actions/workflow-template-overview.md
+++ b/translations/ja-JP/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/ja-JP/data/reusables/advanced-security/ghas-availability.md b/translations/ja-JP/data/reusables/advanced-security/ghas-availability.md
new file mode 100644
index 000000000000..ad4315d7c13b
--- /dev/null
+++ b/translations/ja-JP/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/ja-JP/data/reusables/advanced-security/note-org-enable-uses-seats.md b/translations/ja-JP/data/reusables/advanced-security/note-org-enable-uses-seats.md
index 4f4f4e5a0d08..6f050b742bc9 100644
--- a/translations/ja-JP/data/reusables/advanced-security/note-org-enable-uses-seats.md
+++ b/translations/ja-JP/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/ja-JP/data/reusables/advanced-security/security-feature-availability.md b/translations/ja-JP/data/reusables/advanced-security/security-feature-availability.md
new file mode 100644
index 000000000000..ef965ceae37e
--- /dev/null
+++ b/translations/ja-JP/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/ja-JP/data/reusables/github-actions/example-github-runner.md b/translations/ja-JP/data/reusables/github-actions/example-github-runner.md
index bbc48c1e7f4b..85bbb9aa62c6 100644
--- a/translations/ja-JP/data/reusables/github-actions/example-github-runner.md
+++ b/translations/ja-JP/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/ja-JP/data/reusables/github-actions/java-jvm-architecture.md b/translations/ja-JP/data/reusables/github-actions/java-jvm-architecture.md
index 8bebbd6544da..73ae89060ef1 100644
--- a/translations/ja-JP/data/reusables/github-actions/java-jvm-architecture.md
+++ b/translations/ja-JP/data/reusables/github-actions/java-jvm-architecture.md
@@ -1,6 +1,6 @@
 ### JVMのバージョンとアーキテクチャの指定
 
-スターターワークフローテンプレートは、X64プラットフォーム用のOpenJDK 8を含む`PATH`をセットアップします。 異なるバージョンの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ランタイム環境を選択できます。
 
 たとえば、x64プラットフォーム上でAdoptiumが提供するJDKのバージョン11を使うには、`setup-java`アクションを使って`java-version`、`distribution`、`architecture` パラメータを`'11'`、`'adopt'`、`x64`に設定できます。
 
diff --git a/translations/ja-JP/data/reusables/organizations/people.md b/translations/ja-JP/data/reusables/organizations/people.md
index 29ba1ff3564c..56d2d6f9f23e 100644
--- a/translations/ja-JP/data/reusables/organizations/people.md
+++ b/translations/ja-JP/data/reusables/organizations/people.md
@@ -1,5 +1,5 @@
 1. Organization 名の下で、クリックします
-{% 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/ja-JP/data/reusables/pages/twenty-minutes-to-publish.md b/translations/ja-JP/data/reusables/pages/twenty-minutes-to-publish.md
index 52a088fdc813..40d004bbae9e 100644
--- a/translations/ja-JP/data/reusables/pages/twenty-minutes-to-publish.md
+++ b/translations/ja-JP/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/ja-JP/data/reusables/repositories/actions-tab.md b/translations/ja-JP/data/reusables/repositories/actions-tab.md
index 4627e75c2f99..487e60904333 100644
--- a/translations/ja-JP/data/reusables/repositories/actions-tab.md
+++ b/translations/ja-JP/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/ja-JP/data/reusables/repositories/private_forks_inherit_permissions.md b/translations/ja-JP/data/reusables/repositories/private_forks_inherit_permissions.md
index ded629ea27f6..f6fcfcb9f476 100644
--- a/translations/ja-JP/data/reusables/repositories/private_forks_inherit_permissions.md
+++ b/translations/ja-JP/data/reusables/repositories/private_forks_inherit_permissions.md
@@ -1 +1 @@
-プライベートフォークは、上流もしくは親リポジトリの権限構造を継承します。 たとえば、上流リポジトリがプライベートで読み取り/書き込みアクセスをあるTeamに与えているなら、そのチームはプライベートの上流リポジトリのすべてのフォークに読み取り/書き込みアクセスを持つことになります。 これは、プライベートリポジトリのオーナーがコードに対するコントロールを管理するための役に立ちます。
+プライベートフォークは、上流もしくは親リポジトリの権限構造を継承します。 これは、プライベートリポジトリのオーナーがコードに対するコントロールを管理するための役に立ちます。 たとえば、上流リポジトリがプライベートで読み取り/書き込みアクセスをあるTeamに与えているなら、そのチームはプライベートの上流リポジトリのすべてのフォークに読み取り/書き込みアクセスを持つことになります。 Only team permissions (not individual permissions) are inherited by private forks.
diff --git a/translations/ja-JP/data/reusables/secret-scanning/partner-secret-list-private-repo.md b/translations/ja-JP/data/reusables/secret-scanning/partner-secret-list-private-repo.md
index e3205af06b52..0f516b6bbba8 100644
--- a/translations/ja-JP/data/reusables/secret-scanning/partner-secret-list-private-repo.md
+++ b/translations/ja-JP/data/reusables/secret-scanning/partner-secret-list-private-repo.md
@@ -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/ja-JP/data/reusables/user_settings/appearance-settings.md b/translations/ja-JP/data/reusables/user_settings/appearance-settings.md
new file mode 100644
index 000000000000..d764df6b856e
--- /dev/null
+++ b/translations/ja-JP/data/reusables/user_settings/appearance-settings.md
@@ -0,0 +1,3 @@
+1. [User settings] サイドバーで、[**Appearance**] をクリックします。
+
+   ![[User settings] サイドバーの [Appearance] タブ](/assets/images/help/settings/appearance-tab.png)
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/user_settings/enabling-fixed-width-fonts.md b/translations/ja-JP/data/reusables/user_settings/enabling-fixed-width-fonts.md
new file mode 100644
index 000000000000..b40ae916b5d7
--- /dev/null
+++ b/translations/ja-JP/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/ja-JP/data/reusables/webhooks/issue_event_api_properties.md b/translations/ja-JP/data/reusables/webhooks/issue_event_api_properties.md
index 5c4bc227b245..81f27e518d0a 100644
--- a/translations/ja-JP/data/reusables/webhooks/issue_event_api_properties.md
+++ b/translations/ja-JP/data/reusables/webhooks/issue_event_api_properties.md
@@ -1,3 +1,3 @@
-| キー       | 種類       | 説明                                                                                           |
-| -------- | -------- | -------------------------------------------------------------------------------------------- |
-| `action` | `string` | 実行されたアクション. `opened`、`closed`、`reopened`、`assigned`、`unassigned`、`labeled`、`unlabeled`のいずれか。 |
+| キー       | 種類       | 説明                                                                                                                       |
+| -------- | -------- | ------------------------------------------------------------------------------------------------------------------------ |
+| `action` | `string` | 実行されたアクション. Can be one of `opened`, `edited`, `closed`, `reopened`, `assigned`, `unassigned`, `labeled`, or `unlabeled`. |
diff --git a/translations/ja-JP/data/reusables/webhooks/pull_request_event_api_properties.md b/translations/ja-JP/data/reusables/webhooks/pull_request_event_api_properties.md
index 4c5f0d3e08c9..ddc095beed2a 100644
--- a/translations/ja-JP/data/reusables/webhooks/pull_request_event_api_properties.md
+++ b/translations/ja-JP/data/reusables/webhooks/pull_request_event_api_properties.md
@@ -1,3 +1,3 @@
-| キー       | 種類       | 説明                                                                                                                                                     |
-| -------- | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| `action` | `string` | 実行されたアクション. `opened`、`closed`、`reopened`、`assigned`、`unassigned`、`review_requested`、`review_request_removed`、`labeled`、`unlabeled`、`synchronize`のいずれか。 |
+| キー       | 種類       | 説明                                                                                                                                                                                     |
+| -------- | -------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `action` | `string` | 実行されたアクション. Can be one of `opened`, `edited`, `closed`, `reopened`, `assigned`, `unassigned`, `review_requested`, `review_request_removed`, `labeled`, `unlabeled`, and `synchronize`. |
diff --git a/translations/ja-JP/data/ui.yml b/translations/ja-JP/data/ui.yml
index 33b23f1e1b8b..5f0b0c033509 100644
--- a/translations/ja-JP/data/ui.yml
+++ b/translations/ja-JP/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:
diff --git a/translations/ja-JP/data/variables/product.yml b/translations/ja-JP/data/variables/product.yml
index 42a521b2d500..272bd9d00620 100644
--- a/translations/ja-JP/data/variables/product.yml
+++ b/translations/ja-JP/data/variables/product.yml
@@ -97,8 +97,6 @@ prodname_matching_fund: 'GitHub Sponsors Matching Fund'
 #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'
diff --git a/translations/log/ja-resets.csv b/translations/log/ja-resets.csv
index 5f2dc19e6328..47087d76c3fb 100644
--- a/translations/log/ja-resets.csv
+++ b/translations/log/ja-resets.csv
@@ -36,6 +36,7 @@ translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-gith
 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
@@ -97,7 +98,7 @@ translations/ja-JP/content/actions/hosting-your-own-runners/using-self-hosted-ru
 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-workflow-templates.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
@@ -109,7 +110,7 @@ translations/ja-JP/content/actions/learn-github-actions/reusing-workflows.md,ren
 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-workflow-templates.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
@@ -276,6 +277,7 @@ 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
@@ -448,6 +450,7 @@ translations/ja-JP/content/code-security/supply-chain-security/keeping-your-depe
 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
@@ -466,6 +469,7 @@ translations/ja-JP/content/codespaces/customizing-your-codespace/setting-your-de
 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
@@ -484,6 +488,7 @@ translations/ja-JP/content/codespaces/setting-up-your-project-for-codespaces/set
 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
@@ -603,6 +608,7 @@ translations/ja-JP/content/get-started/getting-started-with-git/updating-credent
 translations/ja-JP/content/get-started/index.md,rendering error
 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
@@ -673,12 +679,15 @@ translations/ja-JP/content/github/working-with-github-support/submitting-a-ticke
 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
@@ -692,14 +701,19 @@ translations/ja-JP/content/issues/organizing-your-work-with-project-boards/manag
 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
@@ -716,6 +730,7 @@ translations/ja-JP/content/organizations/granting-access-to-your-organization-wi
 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
@@ -737,6 +752,7 @@ translations/ja-JP/content/organizations/managing-organization-settings/setting-
 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
@@ -768,8 +784,10 @@ translations/ja-JP/content/organizations/restricting-access-to-your-organization
 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
@@ -791,6 +809,7 @@ translations/ja-JP/content/pages/getting-started-with-github-pages/configuring-a
 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
@@ -819,9 +838,11 @@ translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/propos
 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

From d2b9b236c45a1fb948e14105f4f95954a9f1d57c Mon Sep 17 00:00:00 2001
From: Robert Sese <robert.sese@gmail.com>
Date: Thu, 6 Jan 2022 16:35:56 -0600
Subject: [PATCH 05/13] Add label for search input (#24130)

---
 components/Search.tsx      | 61 ++++++++++++++++++++------------------
 stylesheets/utilities.scss | 11 +++++++
 2 files changed, 43 insertions(+), 29 deletions(-)

diff --git a/components/Search.tsx b/components/Search.tsx
index 5bffca38715f..d99a60e4fe38 100644
--- a/components/Search.tsx
+++ b/components/Search.tsx
@@ -209,35 +209,38 @@ export function Search({
     <div data-testid="search" aria-hidden="true">
       <div className="position-relative z-2">
         <form role="search" className="width-full d-flex" noValidate onSubmit={onFormSubmit}>
-          <input
-            data-testid="site-search-input"
-            ref={inputRef}
-            className={cx(
-              styles.searchInput,
-              iconSize === 24 && 'form-control px-6 f4',
-              iconSize === 16 && 'form-control px-5 f4',
-              variant === 'compact' && 'py-2',
-              variant === 'expanded' && 'py-3',
-              isHeaderSearch && styles.searchInputHeader,
-              !isHeaderSearch && 'width-full',
-              isHeaderSearch && query && styles.searchInputExpanded,
-              isHeaderSearch && query && 'position-absolute top-0 right-0'
-            )}
-            style={{
-              background: `var(--color-canvas-default) url("/assets/images/octicons/search-${iconSize}.svg") no-repeat ${
-                iconSize === 24 ? '12px' : '6px'
-              }`,
-            }}
-            type="search"
-            placeholder={t`placeholder`}
-            autoComplete="off"
-            autoCorrect="off"
-            autoCapitalize="off"
-            spellCheck="false"
-            maxLength={512}
-            onChange={onSearch}
-            value={localQuery}
-          />
+          <label className="text-normal width-full">
+            <span className="visually-hidden">{t`placeholder`}</span>
+            <input
+              data-testid="site-search-input"
+              ref={inputRef}
+              className={cx(
+                styles.searchInput,
+                iconSize === 24 && 'form-control px-6 f4',
+                iconSize === 16 && 'form-control px-5 f4',
+                variant === 'compact' && 'py-2',
+                variant === 'expanded' && 'py-3',
+                isHeaderSearch && styles.searchInputHeader,
+                !isHeaderSearch && 'width-full',
+                isHeaderSearch && query && styles.searchInputExpanded,
+                isHeaderSearch && query && 'position-absolute top-0 right-0'
+              )}
+              style={{
+                background: `var(--color-canvas-default) url("/assets/images/octicons/search-${iconSize}.svg") no-repeat ${
+                  iconSize === 24 ? '12px' : '6px'
+                }`,
+              }}
+              type="search"
+              placeholder={t`placeholder`}
+              autoComplete="off"
+              autoCorrect="off"
+              autoCapitalize="off"
+              spellCheck="false"
+              maxLength={512}
+              onChange={onSearch}
+              value={localQuery}
+            />
+          </label>
           <button className="d-none" type="submit" title="Submit the search query." hidden />
         </form>
       </div>
diff --git a/stylesheets/utilities.scss b/stylesheets/utilities.scss
index cef0e6c9f70e..a949a2fec487 100644
--- a/stylesheets/utilities.scss
+++ b/stylesheets/utilities.scss
@@ -83,3 +83,14 @@
 .min-h-screen {
   min-height: 100vh;
 }
+
+.visually-hidden {
+  border: 0;
+  clip: rect(0 0 0 0);
+  height: 1px;
+  margin: -1px;
+  overflow: hidden;
+  padding: 0;
+  position: absolute !important;
+  width: 1px;
+}

From 4fbad6022fbb913c6c3a4f24d8b113838c1fc302 Mon Sep 17 00:00:00 2001
From: Avinash Sridhar <sridharavinash@users.noreply.github.com>
Date: Thu, 6 Jan 2022 19:26:21 -0500
Subject: [PATCH 06/13] update PR enforcement level documentation for protected
 branches (#24117)

* update PR enforcement level documentation for protected branches

Updates the documentation for protected_branches to add additional metadata for expected values for the enforcement level.

* update enterprise audited-actions page

Co-authored-by: Ethan Palm <56270045+ethanpalm@users.noreply.github.com>
---
 .../monitoring-activity-in-your-enterprise/audited-actions.md   | 2 +-
 .../reviewing-the-audit-log-for-your-organization.md            | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/content/admin/user-management/monitoring-activity-in-your-enterprise/audited-actions.md b/content/admin/user-management/monitoring-activity-in-your-enterprise/audited-actions.md
index 87a3c98508b3..03fa96599c39 100644
--- a/content/admin/user-management/monitoring-activity-in-your-enterprise/audited-actions.md
+++ b/content/admin/user-management/monitoring-activity-in-your-enterprise/audited-actions.md
@@ -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/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 c6eb09d51919..621972fd3cce 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
@@ -550,7 +550,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.

From ef5853794c6f01be918eaa735dc61b3460aa36be Mon Sep 17 00:00:00 2001
From: Evi Liu <evi-liu@github.com>
Date: Thu, 6 Jan 2022 16:30:55 -0800
Subject: [PATCH 07/13] Update repository-roles-for-an-organization.md (#24121)

Updated to properly reflect Triage permissions for `deleting a discussion`

Co-authored-by: Ethan Palm <56270045+ethanpalm@users.noreply.github.com>
---
 .../repository-roles-for-an-organization.md                     | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization.md b/content/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization.md
index 0a64d782c971..62a0509814db 100644
--- a/content/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization.md
+++ b/content/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization.md
@@ -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

From 7d75265b01039a324a0f29ca1b1e1ebd9644e4eb Mon Sep 17 00:00:00 2001
From: Peter Bengtsson <peterbe@github.com>
Date: Thu, 6 Jan 2022 21:25:16 -0500
Subject: [PATCH 08/13] hydration fails on CollapsibleSection with hash in URL
 (#24105)

---
 components/page-header/Breadcrumbs.tsx | 7 ++++---
 components/sidebar/SidebarProduct.tsx  | 4 +++-
 2 files changed, 7 insertions(+), 4 deletions(-)

diff --git a/components/page-header/Breadcrumbs.tsx b/components/page-header/Breadcrumbs.tsx
index 218d8953ea53..2eb74d9327e9 100644
--- a/components/page-header/Breadcrumbs.tsx
+++ b/components/page-header/Breadcrumbs.tsx
@@ -12,13 +12,14 @@ export type BreadcrumbT = {
 
 export const Breadcrumbs = () => {
   const router = useRouter()
-  const pathWithLocale = `/${router.locale}${router.asPath.split('?')[0]}` // remove query string
+  // remove query string and hash
+  const pathWithLocale = `/${router.locale}${router.asPath.split('?')[0].split('#')[0]}`
   const { breadcrumbs } = useMainContext()
 
   return (
     /*
-      NOTE: The breadcrumbs class and the nav tag are used by the 
-      LUNR search scripts. The a tag generated by the Link is also used.
+      NOTE: The breadcrumbs class and the nav tag are used by the
+      Lunr search scripts. The a tag generated by the Link is also used.
       If these change, please also change
       updating script/search/parse-page-sections-into-records.js.
     */
diff --git a/components/sidebar/SidebarProduct.tsx b/components/sidebar/SidebarProduct.tsx
index 09488cd96c0a..d3a1495edced 100644
--- a/components/sidebar/SidebarProduct.tsx
+++ b/components/sidebar/SidebarProduct.tsx
@@ -30,7 +30,9 @@ export const SidebarProduct = () => {
   }
 
   const productTitle = currentProductTree.renderedShortTitle || currentProductTree.renderedFullTitle
-  const routePath = `/${router.locale}${router.asPath.split('?')[0]}` // remove query string
+  // remove query string and hash
+  const routePath = `/${router.locale}${router.asPath.split('?')[0].split('#')[0]}`
+
   const hasExactCategory = !!currentProductTree.childPages.find(({ href }) =>
     routePath.includes(href)
   )

From dd470209551ec212bd6986751ad12d38469a4d72 Mon Sep 17 00:00:00 2001
From: GitHub Actions <action@github.com>
Date: Fri, 7 Jan 2022 02:25:49 +0000
Subject: [PATCH 09/13] update search indexes

---
 lib/search/indexes/github-docs-3.0-cn-records.json.br    | 4 ++--
 lib/search/indexes/github-docs-3.0-cn.json.br            | 4 ++--
 lib/search/indexes/github-docs-3.0-en-records.json.br    | 4 ++--
 lib/search/indexes/github-docs-3.0-en.json.br            | 4 ++--
 lib/search/indexes/github-docs-3.0-es-records.json.br    | 4 ++--
 lib/search/indexes/github-docs-3.0-es.json.br            | 4 ++--
 lib/search/indexes/github-docs-3.0-ja-records.json.br    | 4 ++--
 lib/search/indexes/github-docs-3.0-ja.json.br            | 4 ++--
 lib/search/indexes/github-docs-3.0-pt-records.json.br    | 4 ++--
 lib/search/indexes/github-docs-3.0-pt.json.br            | 4 ++--
 lib/search/indexes/github-docs-3.1-cn-records.json.br    | 4 ++--
 lib/search/indexes/github-docs-3.1-cn.json.br            | 4 ++--
 lib/search/indexes/github-docs-3.1-en-records.json.br    | 4 ++--
 lib/search/indexes/github-docs-3.1-en.json.br            | 4 ++--
 lib/search/indexes/github-docs-3.1-es-records.json.br    | 4 ++--
 lib/search/indexes/github-docs-3.1-es.json.br            | 4 ++--
 lib/search/indexes/github-docs-3.1-ja-records.json.br    | 4 ++--
 lib/search/indexes/github-docs-3.1-ja.json.br            | 4 ++--
 lib/search/indexes/github-docs-3.1-pt-records.json.br    | 4 ++--
 lib/search/indexes/github-docs-3.1-pt.json.br            | 4 ++--
 lib/search/indexes/github-docs-3.2-cn-records.json.br    | 4 ++--
 lib/search/indexes/github-docs-3.2-cn.json.br            | 4 ++--
 lib/search/indexes/github-docs-3.2-en-records.json.br    | 4 ++--
 lib/search/indexes/github-docs-3.2-en.json.br            | 4 ++--
 lib/search/indexes/github-docs-3.2-es-records.json.br    | 4 ++--
 lib/search/indexes/github-docs-3.2-es.json.br            | 4 ++--
 lib/search/indexes/github-docs-3.2-ja-records.json.br    | 4 ++--
 lib/search/indexes/github-docs-3.2-ja.json.br            | 4 ++--
 lib/search/indexes/github-docs-3.2-pt-records.json.br    | 4 ++--
 lib/search/indexes/github-docs-3.2-pt.json.br            | 4 ++--
 lib/search/indexes/github-docs-3.3-cn-records.json.br    | 4 ++--
 lib/search/indexes/github-docs-3.3-cn.json.br            | 4 ++--
 lib/search/indexes/github-docs-3.3-en-records.json.br    | 4 ++--
 lib/search/indexes/github-docs-3.3-en.json.br            | 4 ++--
 lib/search/indexes/github-docs-3.3-es-records.json.br    | 4 ++--
 lib/search/indexes/github-docs-3.3-es.json.br            | 4 ++--
 lib/search/indexes/github-docs-3.3-ja-records.json.br    | 4 ++--
 lib/search/indexes/github-docs-3.3-ja.json.br            | 4 ++--
 lib/search/indexes/github-docs-3.3-pt-records.json.br    | 4 ++--
 lib/search/indexes/github-docs-3.3-pt.json.br            | 4 ++--
 lib/search/indexes/github-docs-dotcom-cn-records.json.br | 4 ++--
 lib/search/indexes/github-docs-dotcom-cn.json.br         | 4 ++--
 lib/search/indexes/github-docs-dotcom-en-records.json.br | 4 ++--
 lib/search/indexes/github-docs-dotcom-en.json.br         | 4 ++--
 lib/search/indexes/github-docs-dotcom-es-records.json.br | 4 ++--
 lib/search/indexes/github-docs-dotcom-es.json.br         | 4 ++--
 lib/search/indexes/github-docs-dotcom-ja-records.json.br | 4 ++--
 lib/search/indexes/github-docs-dotcom-ja.json.br         | 4 ++--
 lib/search/indexes/github-docs-dotcom-pt-records.json.br | 4 ++--
 lib/search/indexes/github-docs-dotcom-pt.json.br         | 4 ++--
 lib/search/indexes/github-docs-ghae-cn-records.json.br   | 4 ++--
 lib/search/indexes/github-docs-ghae-cn.json.br           | 4 ++--
 lib/search/indexes/github-docs-ghae-en-records.json.br   | 4 ++--
 lib/search/indexes/github-docs-ghae-en.json.br           | 4 ++--
 lib/search/indexes/github-docs-ghae-es-records.json.br   | 4 ++--
 lib/search/indexes/github-docs-ghae-es.json.br           | 4 ++--
 lib/search/indexes/github-docs-ghae-ja-records.json.br   | 4 ++--
 lib/search/indexes/github-docs-ghae-ja.json.br           | 4 ++--
 lib/search/indexes/github-docs-ghae-pt-records.json.br   | 4 ++--
 lib/search/indexes/github-docs-ghae-pt.json.br           | 4 ++--
 lib/search/indexes/github-docs-ghec-cn-records.json.br   | 4 ++--
 lib/search/indexes/github-docs-ghec-cn.json.br           | 4 ++--
 lib/search/indexes/github-docs-ghec-en-records.json.br   | 4 ++--
 lib/search/indexes/github-docs-ghec-en.json.br           | 4 ++--
 lib/search/indexes/github-docs-ghec-es-records.json.br   | 4 ++--
 lib/search/indexes/github-docs-ghec-es.json.br           | 4 ++--
 lib/search/indexes/github-docs-ghec-ja-records.json.br   | 4 ++--
 lib/search/indexes/github-docs-ghec-ja.json.br           | 4 ++--
 lib/search/indexes/github-docs-ghec-pt-records.json.br   | 4 ++--
 lib/search/indexes/github-docs-ghec-pt.json.br           | 4 ++--
 70 files changed, 140 insertions(+), 140 deletions(-)

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 e90d3385f089..cbc151da924d 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:bf0d3266b1b5f9e382aed496eff6145ce7356f010107e9863e7e3d968bd1a729
-size 614354
+oid sha256:a8c129497dad312c79c7feecfc6822dab6b1afa690f7526b916224878928922c
+size 614104
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 17be058dc1b5..7e121e1ecd1c 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:e557f30cf77b9db893f1fef2056eda3b1a5c0328a089b8b4f5babc4b0e0a36a6
-size 1746261
+oid sha256:fd3c25979ba047f2efbdd1d849e25ffde4d06900b563eb603c82652cc464af83
+size 1746379
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 17d2f7e66a48..e9d31d0a85ad 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:41a61a693a4db1feb16c02b00d39832e21d0ab804c7787a070ddb9cc5beaa854
-size 952991
+oid sha256:06a281919304d6668358f5d750ee9c108ff9a5cd5b1ce617b002a59bb1c31491
+size 953481
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 b75fec79f700..1f3cfa165911 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:6fce889f2d54d3e2a941b75b9f4ee8650219ada2f317e8b4aa9e06dd84492d66
-size 3907727
+oid sha256:60ddeb263073c13d050ea4fbeeaffd3e9c7df89c4ef876808a7ff7dc39c22223
+size 3909467
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 e18cfe753f7e..69814559d2e6 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:72046310964c2a4f0a2881e29e30bf573d5792e8381d107101d461707627113d
-size 583112
+oid sha256:481f5263749fb0a795d9e77e33ba646db12110dbdc592068c64cb53bbe4a78c3
+size 583029
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 f0368fcf1e92..9daef8bfa759 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:341d3462086f1b0622846c70bbf5acb906885d0741dda9d94654e558d0b93e0d
-size 2697317
+oid sha256:b3ecbbde22aafe54f5baca62a67047c829d8ac04d1a8c5f457e8568031241bcc
+size 2696940
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 3bf362e175cd..6ef48bacde64 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:a9ae1b7cc8b305ba17fbade8872c2fcf9f77287efb96d7bd6850086d4d6b5325
-size 617679
+oid sha256:104d608ec74a99ccb507e228a996cbc80994c00c35ac962ca8297b473306a247
+size 617836
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 2d12c1423339..655f508146aa 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:ff9fcd1e83ee5691271b3e73ca9a10bcabb118e4f2204b37a8cc6887aba3430d
-size 3468065
+oid sha256:db04900e8d79cefc4cdd24aa51dd209c6d724d3b150141665cf31753b036df49
+size 3475588
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 9d997601b2df..13036236509e 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:fd4cb19c69c307fa0bb0200c59af02cf540e4688f20685d725001f80b910f6fb
-size 595514
+oid sha256:bdb63edd7fcb4c6cbdfc2823fdfae66d3888e61c4bea94a0d5c6bfcba9946461
+size 596000
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 6c98da818da5..1dc0edf32ecf 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:89f7c612f80646b38af93bee62a8f5346d213a2baf0623be950c6410d46ae024
-size 2805065
+oid sha256:ae8634d008fabb40ac5c354b9b306fb6bc52f19340fdb56e8e8947290ba661e2
+size 2818370
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 3b18c51847b5..0f06acfa0918 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:5bf779972fed511dc0518c185ebe467902d774dc0c052d60c930a45b5af50789
-size 627771
+oid sha256:c5ef5ac4ed1f8ba7f0be4144a14358d020a61f6b5acd13924d5adfe4e9bb1d3f
+size 627625
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 28230e319b24..2dcb18ecb3f2 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:2f88e707845e93125b2c512c8f301106bc13e8981d22cd916d0e5b83eb567052
-size 1787270
+oid sha256:788008c86f71cbd508fcfa17a6ace3d847d5223f24bbc5c9470e42ea77d4d528
+size 1787947
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 9fe8eb1dce60..9336eb78a621 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:21263ca5cc80884e5fec3748bb374a015fe0a682161af2d4449650dd829ba650
-size 978235
+oid sha256:865b2905736490e6eeb8abf64637af625cd189dd8b10a4d31e27ff0a8b543abb
+size 978626
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 984cc549f782..2e68ba73ce64 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:1f309d87992083ccdef62dcc6eb692be40e9e7cf7fdd0678861ae1b57991f68c
-size 3999791
+oid sha256:893589670a8828d67a0d609148c4dae7d9e5b302ffdc1bf683509c74fe5598af
+size 3999207
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 fd8e21fb5a92..2a95bcc6a4e9 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:3c30e3be98c6bfb39baeea3dc6f2e89e6f9dfc481b35c5caa34b8171b413f9e1
-size 595256
+oid sha256:c3691123c1fbdce1681f9ca794b8695717db8f5245bcb438f33b6804f2c0e916
+size 595361
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 1a425f05e8e8..67601ce760be 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:a4d9b5a5f130578890a93515a4ac5f1842b54161fa75ff6c6ae863b27ea85801
-size 2758952
+oid sha256:39d51db33870a887c36764a5f572ffdddcf121b09e2732dd5095cff9fe91f1d9
+size 2759447
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 0ec979c432a6..9ea80717d459 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:3556c729c3f4b7954ed641cf6c4968464cfd0243faa0df07b9282808506de365
-size 631042
+oid sha256:a3e339bd0038301ba6dbc75df7a3e0499c35393c2ecc2841afcb8ae7f30e098a
+size 630988
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 10d94ffeec55..157ffc3bfae6 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:ded7f1e71692ab47d661efcd665567580e66a5208dbf4e5d03b5395031406fae
-size 3547415
+oid sha256:d1d1de5713e614d89912f644851cf67b0caf14e625865988f4be11a9cc3cc742
+size 3555751
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 c0be5dd23782..2e5ccb5eba88 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:cc07a303624f396a92fae7859f2f86ccad8075d5d1b1e8e6401db9b3fa0e3af6
-size 607737
+oid sha256:8f900b2bd195c245642b6fe7566844e1a4cee00a5811ae024ea0192628ef2d8a
+size 608281
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 ee82e878ba59..aa8df7717b74 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:55811386b7c4c4ec3b454e4a38db48fb525cb9e91d7048be9239164ad189ef28
-size 2867718
+oid sha256:d8534c870feda1d5f701430a5bb7d4d1e9ad461ef934ef974ff9325447603b1e
+size 2882343
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 d1f2eaae1284..f4a9ed98fe33 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:c585e3a18210744cf976451ae7e6c65d68b0bfe68a35d9a7af0f7681a85b8da5
-size 639117
+oid sha256:f31a4c3776b44c1d6e59452725105b996c64bdfa9f6c1af2f0f98f5eb1551801
+size 639173
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 a1eade484cd6..bb7bbcbe8a5d 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:02a9d9ae6b11df799a3111b0d59a3f4cdbae576cd51dc93fa34e5910eafd7a80
-size 1814800
+oid sha256:ac5ea5b34725f30a455985282f206872223165b1a4df85ab12f6f875d2de9a54
+size 1814926
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 92c7a271765f..ff1b3ef225c8 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:531f7b4408d0b5d2e1d9be0eb253cf982a1dbe561d25f00ef491950d7dd00742
-size 1008981
+oid sha256:a6e7597d35a8843cd2ea5f0181b19becc8976255ab0b04619329b5ec3edc350f
+size 1009455
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 4069416fe5d9..0e0d58351920 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:7701343abeb0481ee1081b5f3ffa3004c1441ecefc9ddcb4b2b17959495d21d8
-size 4122899
+oid sha256:50e67b53d39541d65a79087bb285ea62807148119ebf280a9799d8e7d00c42e5
+size 4122739
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 995d38dffa65..18860230bc00 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:5ed6da46fb3da7f761a1bd131df60be58b5c8a83c862bd215549f21ac1e2a5fd
-size 605785
+oid sha256:d8c9787b7c0f5358dc678008e6d929feeae348310f2201fecbc34d0523ac452e
+size 605722
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 fb735a087fdc..a9eddec88143 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:0726d07ff907286aca1b49ceb33bebfff9f39bc881986b73335b85dd6127fd12
-size 2813979
+oid sha256:36faddc8512b1c3896cbe5bb0a39ac90eb2b3859191474f50281a72a76e4a520
+size 2813687
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 78f6346ffc77..106ac85f55ee 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:f1e5845c4c8ebff2fbb7cb7ae7d5759d4e204da49a7d34044b529d8ccb1237eb
-size 642395
+oid sha256:5a4fded95a1f88057c5bbef4b288c9257eddd32788a5d652a973c8f98546cf07
+size 642406
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 4b18c5a049af..9e23ac21a099 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:354a101158effaf2a0b2f6604cec2997fc88090814c60b235c387a8c1b096626
-size 3613930
+oid sha256:b3be33491a7106b737772df3e44b8b375ee04feee4f4020306fac5f65a37c189
+size 3621046
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 b17193635a54..621d1dd02c9a 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:23ab42266d74b1c5884f5e7f858003720258cd643a0c426f91a7b08c7eeccb9f
-size 619114
+oid sha256:426e866304ddfee0d09f6c23237e25a762f7602a8232e3f56643870e98b623df
+size 619713
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 be23ad25266d..f11a352093a6 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:253155527dd6c9bd284a9c41de0741a2ce32bfabc32c9250de899c07630fe293
-size 2918086
+oid sha256:33accf15baf72ba168fe5deb5117696116fd249c3c960313c04e74d363b1cddc
+size 2932297
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 7d0ae0b38e5d..462bab225a8f 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:0ea4aec2f2ac76d310e9038d64d2e37cf86427e69e07a5d2d0845836325b6581
-size 659526
+oid sha256:56e342502f1ebed6e2029f00aa402b795933fbf5c41c1a5f2087a41f150aa78a
+size 659595
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 b52bef7bbcc7..60d08b3a9876 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:34d89582c9d36e8e216de368d8c997dbfd2ac20e2dc0210d1e4ae3836f531863
-size 1871880
+oid sha256:3ed64e59c1adb3527f0085fbde5601992bd0abe205ef8c44e8fd99163eec94e7
+size 1872260
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 9410147060d0..98c488a9d012 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:5d0ce61b84936273911ecf902fd03aaadb240511945bf4d020a03be3caecad65
-size 1042787
+oid sha256:37fba52912d8dadeb491d6f380b8958a081290aebcb36e8fa9deb19d5f7426cd
+size 1043238
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 8da7ae9d1a87..76980db41481 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:89565d782f172c680c591d802da61cff8ae94a4b89de35a54ef11d3befaa57ab
-size 4222997
+oid sha256:23ff8183f5a605dac60604af590d665da408662a28b814e3bfa9ae0d4a67be74
+size 4224481
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 658591348728..10fdba696512 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:4e9b26912aea2bac012061144019d0011f5e217088f82138b89e1881dad59f4f
-size 623846
+oid sha256:6523d2c88dcaa9e0e2b5811cd2fa1fbe6a83f0f477310acffa61a1907ea1cf89
+size 624076
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 36fb6b92b5d9..387ac64f5530 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:c4aa783eb858577c2f84de6a09d176906a1526f795797e57027e2de5b1093881
-size 2911925
+oid sha256:00d6f0e435620925a01ec395e7647526b0846e0d84199ee41989afa01295e44b
+size 2911879
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 69e2b2e0fd2c..27873b4de17c 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:0f869ebd495db8b83e766fcd28f2d3a6cf90e0a7633c8b7c55b41bd841d82467
-size 663898
+oid sha256:b7e5303b09d84040582657d8368b731e2e694244303b0a10f4e00279523c3bee
+size 663865
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 d32fddd5dcdf..46f84b191863 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:c929eee1de45e248ee47839552b7ad540fdab9068b9f3ebf4b9bcda1293a2d73
-size 3732070
+oid sha256:625a52f6a476915e1d8060d415351d294013c48d73a94eb4f574441bf0aa0ff8
+size 3740689
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 e1e3284c034e..994c5ba493b1 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:0d028f2e510bddda74d3701a311e15b3a1f1844fb19cbae401c14a0f0f61fa19
-size 638406
+oid sha256:22d0040d15134aa49fbf88a9a54a7fbd842442ed60e486f37ff2659f9fde7d1e
+size 638942
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 9241b9e2b0b6..e445ad79f01a 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:81b8d2d286719dffacba9d54b1dc80668fa1731b4682aefefb68ad3c8eeea2b2
-size 3005699
+oid sha256:d2ca7a677233b5eea18405457f3e9169d8fd780799a5c0278a46034254f2a031
+size 3020011
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 4a55bf9a3a0a..e79222773087 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:2f344dddb8844e39e9693940284bd1cbf6850b02fd5f21efcfa52b10f687a342
-size 848373
+oid sha256:1f5427dc01465c70eda59623ef3476743998847740bbbab5f00d343080f69f7b
+size 848221
diff --git a/lib/search/indexes/github-docs-dotcom-cn.json.br b/lib/search/indexes/github-docs-dotcom-cn.json.br
index ad9a15b2acfd..670f5486bdd2 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:fbe11456e60f7e3a00fcbf7429302ea8d2afdecec65ea344aaa7b372fb611d40
-size 2092746
+oid sha256:c4bd837ad9ff848b1eb7387172c620696900a002ea014cd2f933f1498a1763fa
+size 2093072
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 ccff8df5caf6..7decc89e14b4 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:3e5f71cbb46ac354d07488c19c58c3c1820ff80c0d362b93f182dc9b4630d1a3
-size 1319724
+oid sha256:80bdc2cc0ce044bca5ffb44109ab196d4249010a8aee8df8841a58b0310f6c92
+size 1320194
diff --git a/lib/search/indexes/github-docs-dotcom-en.json.br b/lib/search/indexes/github-docs-dotcom-en.json.br
index 2408dd7e803c..7c6399606c40 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:c2bba002d78bb2ff67503fdd6e3a6cb040554220d2b0b64f4df9a268e1d035cd
-size 5068195
+oid sha256:eb0b64b87e593a226f1997a91adb074989f19c4fdfd8f84ce3593fb3aec41385
+size 5069169
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 be885cfb4972..9462d1b5ad4e 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:79efe5e112185951abab36b559f63a711a2f57f4f957729c7d7f9f8a6f8bc35a
-size 794751
+oid sha256:aad2c6ced5b3a3f0774f552430d4f1ea69d7a7303c3fc486c88845475bc2a891
+size 794752
diff --git a/lib/search/indexes/github-docs-dotcom-es.json.br b/lib/search/indexes/github-docs-dotcom-es.json.br
index 6e3ac987add6..e81162458d2d 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:21651c5235e5a4c0671bb3ffa22306fffcb4382069fb3a4f4cc09dfc2143887c
-size 3496873
+oid sha256:f7f6c34d89672f904b3e76df22e7b2ee9a7156cb8eda122748fb544e948f364f
+size 3497756
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 c13a3b8e253d..067d272480d1 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:471aece860918febeaf298219687df057ecb8d344aad8dff5c7a1d73bd8dd284
-size 856431
+oid sha256:1002084860127e3f192c7fc243fe677f716a40188650a55760c46861577285de
+size 856270
diff --git a/lib/search/indexes/github-docs-dotcom-ja.json.br b/lib/search/indexes/github-docs-dotcom-ja.json.br
index b4a933ac58e3..c5ccf2beb7c1 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:09ee85fbc868c82f4675796419dfbb8ba9fec368646bd72312eb00998c33b26f
-size 4549618
+oid sha256:0f08e42f1c0c919505164a331154cf3de732deadbdfd0e5a3928af2b45c52fff
+size 4557984
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 bd90b68e9826..28111043ed8b 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:382ea5c1df894fda5480e26f5a47579d0a8969fe355969b6c804a96f63908b88
-size 809522
+oid sha256:e6638fc6e78524e25054f16d3b07ed5b89b65505bdaf5da71a26b2e2c204316d
+size 810457
diff --git a/lib/search/indexes/github-docs-dotcom-pt.json.br b/lib/search/indexes/github-docs-dotcom-pt.json.br
index f78449ade3b5..b112aee1a134 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:1271df27d7e350fb841816656c644730f0a3755dd9a7cf4aa63bb944c050f9d7
-size 3591525
+oid sha256:00ec6e75e2f2ce7ab2d6d7bbad58c4f8937e9f2c560eb2b3a9b24075ae118c51
+size 3612122
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 aa977ef43cff..a84a46762e3f 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:4097cf43f83211ec0ba6d3174d9a29c4228df25fbbff9b847ba4a566534c6a7c
-size 512938
+oid sha256:f6194d918a4ea5392d759b7d2046ce73f67468db2f1d8201251744ea5da9763f
+size 513067
diff --git a/lib/search/indexes/github-docs-ghae-cn.json.br b/lib/search/indexes/github-docs-ghae-cn.json.br
index d803a4f7aee9..2f81bdb434b8 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:02e772c54ca4f5af98b608c3eeb7f7095c3ba5ae49eae4710fbf731b91395252
-size 1416228
+oid sha256:410e0d61a60de1c0b948c735731b56c430a6362b70fc3bebc4e366e6714c6cea
+size 1416127
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 ef4cff5831f8..4c43e472cafc 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:1e2f6f31eeff10e2b794ae5d726ea745b456cef001c47a4ce65a493eefe27aa9
-size 832616
+oid sha256:98831fc664bd14da82dfca5dad08bc1b5c540e4280189d74e847a66346334b02
+size 832625
diff --git a/lib/search/indexes/github-docs-ghae-en.json.br b/lib/search/indexes/github-docs-ghae-en.json.br
index 5772d2394567..e685c398ef5c 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:0c985c71ccdab129c526ce136cf61fc6eaffbb1e4e6657835cbd5c18749e7b3c
-size 3342798
+oid sha256:5f01208d08d795801a73a1ab37a783873f966bb4db622b3f5535ac297fae4a13
+size 3341448
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 95623f7ae6d1..57c7526f77d2 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:b6fc73541c8405c57ab9c4d2c3f0b6872312e4b691c6d89adc6315053b911a4f
-size 486834
+oid sha256:2e0feeac907110215fe58bc1dc138404d9fe35f8023106d92303f38357f43cb0
+size 486806
diff --git a/lib/search/indexes/github-docs-ghae-es.json.br b/lib/search/indexes/github-docs-ghae-es.json.br
index 22df908ff737..b3c8426eda30 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:d8f97b09483e8ee94a15072fa0358e5b6c6b23320bb46fa2dd39f08fa41a3fd1
-size 2189725
+oid sha256:f2aef7ac4eacd4c4cc7b1b2341b20ad8f863fcebcd3bcb9b2e04a70ab7fdfb0b
+size 2189614
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 4e4e77e7509a..7676bda254d2 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:079ebb6d7342612c49f95c70efce0a8f3a1312b289dd0f580426cf06f38202a4
-size 516141
+oid sha256:c04b7793b357dee2f35a042cf7d0c137c38a88038d201e057fa32a02e48a0c9b
+size 516994
diff --git a/lib/search/indexes/github-docs-ghae-ja.json.br b/lib/search/indexes/github-docs-ghae-ja.json.br
index 92cfabe8a232..2004605a5fa4 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:1f65c8654ad55bb5fa02508309dddd2f340538f293d425c2e779b978e29c5b0f
-size 2793959
+oid sha256:b3209d5bb167f70b3dad62ef33aa92d0a5f3b2edcabbf8678e72cfc846984c33
+size 2803490
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 7451caab7178..49d9820af46d 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:e781ad9debdc01f463b09703a8c519ec0e00d529f90c7d0a643fff5ad6989c6e
-size 499288
+oid sha256:1fe09b34b857806f30a6f05779a69a1d62d18f63162598f2c578b09630511c02
+size 500473
diff --git a/lib/search/indexes/github-docs-ghae-pt.json.br b/lib/search/indexes/github-docs-ghae-pt.json.br
index cb99239808d8..f447056900f0 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:4462c7f27a691314c7221b09b78c02eec8096405d0ab093d7b1eefad56194b71
-size 2273618
+oid sha256:bfd6b22f85d67287ecd949a5030bab8f24f9f2aed52753ac121c5fe50a2d5cb4
+size 2289466
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 ca5d11081f14..f1fdc4790a66 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:3017e59b8402dbc46a45d3990e8c785210399e4cf64d452b1c59ab3875fdf985
-size 772170
+oid sha256:6dbba82bd8b4d11b72434a0890c5f4aa783c051358d5d00f8dcea2d049a45cd8
+size 771926
diff --git a/lib/search/indexes/github-docs-ghec-cn.json.br b/lib/search/indexes/github-docs-ghec-cn.json.br
index 79b758a6f683..849a8c6674cc 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:2e56c1aa35f3b00801aa83667876a0694e69cedcbf23b965305cfb8420c4aa5a
-size 2110046
+oid sha256:4fef0015581524acc1048e5cd3c56b793f1c9d9de820858e551d223362a186fd
+size 2109874
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 24558e23e2eb..6d92d67c67fd 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:d992b7d6b439ab63408f5c9952c0ae59a241c967ef7dd2d83588c3d64aecaf35
-size 1189645
+oid sha256:18d8bf3b92c65938dde5e27027381c874aac2445d29a225acf294e7e332fac73
+size 1186212
diff --git a/lib/search/indexes/github-docs-ghec-en.json.br b/lib/search/indexes/github-docs-ghec-en.json.br
index 0ba576fa1742..9f2734ed1896 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:e22d721524181a3c40aec76543d65f9bd0d30c0eb2f35bf8a3b80e55d8f02207
-size 4803960
+oid sha256:a26dc3cb6cffdb9f093dcaf971a1452e3ac12069bb4f2a470cb9d96a418d7b68
+size 4803372
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 5abf4ba7033d..8f2ff5526e21 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:01056fe5a3c31365045d421f20706c9539fc11ccdee6879fc317d1dbfe669c49
-size 739392
+oid sha256:7fbf59cf13d696ddeda001b213d314fe51c85e4fc993554e6804d440d1dd4747
+size 739553
diff --git a/lib/search/indexes/github-docs-ghec-es.json.br b/lib/search/indexes/github-docs-ghec-es.json.br
index 4ca02779c73b..331897b53b45 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:6d7bcbcde58f36c0bb3f507138a387c2abe61dc60bb6412718d1e3d433596529
-size 3440568
+oid sha256:85d9e1aa7e997efe4a3a4f8b7b5d33d7c6603e4f5791169221d68c2e971b2e20
+size 3441260
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 4526d7cae75a..5ae1c3e4fdf7 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:ba36b7f36eaa54f42b7d99639cc558ed2a0ea28695a32ded8e2d3fe42cdcaccb
-size 782302
+oid sha256:5e8bacc68383676df6cb3d0ede86eae9827f38e4172dbccd91f6e673f9201e35
+size 782951
diff --git a/lib/search/indexes/github-docs-ghec-ja.json.br b/lib/search/indexes/github-docs-ghec-ja.json.br
index aabc732f8a89..1f131bef2103 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:541994252655ff92ad413376d2450bfaf6aad1edbd73d9907aded36d56edffc3
-size 4388816
+oid sha256:3d63cb9c8194204fc3178a01d08000f9ad063bbc3eefe7a4ba67e89967c64868
+size 4397424
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 f32344ec82ce..e8398d244b8b 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:4b75e48de78fbc2d62a3e1784a4d51730944c2df503d2acec4647274eb3c2d01
-size 754269
+oid sha256:d5f74ccedc1285ff7c8623d24e548d95cc15fc2095861c6c1942d37decc0a1a4
+size 755772
diff --git a/lib/search/indexes/github-docs-ghec-pt.json.br b/lib/search/indexes/github-docs-ghec-pt.json.br
index 8cb2ff801375..447a71aaf39d 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:b4ace355144e71c10afc664ca48a4406a06895559a74eda0706c40caf2ead8c6
-size 3530312
+oid sha256:33e01cfded40b04ebc91f9751a5b1404d96c632f0188d2a56c8308c737353a46
+size 3550370

From 03c9f5ea578e7bb46c81a2ef106645a41814715a Mon Sep 17 00:00:00 2001
From: Ramya Parimi <33761166+ramyaparimi@users.noreply.github.com>
Date: Thu, 6 Jan 2022 20:30:47 -0600
Subject: [PATCH 10/13] Merged notification workflow are failing  (#24081)

* Update triage-issue-comments.yml

* Update merged-notification.yml

* Update triage-issue-comments.yml
---
 .github/workflows/merged-notification.yml | 1 +
 1 file changed, 1 insertion(+)

diff --git a/.github/workflows/merged-notification.yml b/.github/workflows/merged-notification.yml
index 828a864c1df5..8604b4223b5d 100644
--- a/.github/workflows/merged-notification.yml
+++ b/.github/workflows/merged-notification.yml
@@ -11,6 +11,7 @@ on:
 
 permissions:
   issues: write
+  pull-requests: write
 
 jobs:
   comment:

From e136bb4df729c793abb3f727feb1eb9f64900510 Mon Sep 17 00:00:00 2001
From: GitHub Actions <action@github.com>
Date: Fri, 7 Jan 2022 10:11:15 +0000
Subject: [PATCH 11/13] update search indexes

---
 lib/search/indexes/github-docs-3.0-cn-records.json.br    | 4 ++--
 lib/search/indexes/github-docs-3.0-cn.json.br            | 4 ++--
 lib/search/indexes/github-docs-3.0-en-records.json.br    | 4 ++--
 lib/search/indexes/github-docs-3.0-en.json.br            | 4 ++--
 lib/search/indexes/github-docs-3.0-es-records.json.br    | 4 ++--
 lib/search/indexes/github-docs-3.0-es.json.br            | 4 ++--
 lib/search/indexes/github-docs-3.0-ja-records.json.br    | 4 ++--
 lib/search/indexes/github-docs-3.0-ja.json.br            | 4 ++--
 lib/search/indexes/github-docs-3.0-pt-records.json.br    | 4 ++--
 lib/search/indexes/github-docs-3.0-pt.json.br            | 4 ++--
 lib/search/indexes/github-docs-3.1-cn-records.json.br    | 4 ++--
 lib/search/indexes/github-docs-3.1-cn.json.br            | 4 ++--
 lib/search/indexes/github-docs-3.1-en-records.json.br    | 4 ++--
 lib/search/indexes/github-docs-3.1-en.json.br            | 4 ++--
 lib/search/indexes/github-docs-3.1-es-records.json.br    | 4 ++--
 lib/search/indexes/github-docs-3.1-es.json.br            | 4 ++--
 lib/search/indexes/github-docs-3.1-ja-records.json.br    | 4 ++--
 lib/search/indexes/github-docs-3.1-ja.json.br            | 4 ++--
 lib/search/indexes/github-docs-3.1-pt-records.json.br    | 4 ++--
 lib/search/indexes/github-docs-3.1-pt.json.br            | 4 ++--
 lib/search/indexes/github-docs-3.2-cn-records.json.br    | 4 ++--
 lib/search/indexes/github-docs-3.2-cn.json.br            | 4 ++--
 lib/search/indexes/github-docs-3.2-en-records.json.br    | 4 ++--
 lib/search/indexes/github-docs-3.2-en.json.br            | 4 ++--
 lib/search/indexes/github-docs-3.2-es-records.json.br    | 4 ++--
 lib/search/indexes/github-docs-3.2-es.json.br            | 4 ++--
 lib/search/indexes/github-docs-3.2-ja-records.json.br    | 4 ++--
 lib/search/indexes/github-docs-3.2-ja.json.br            | 4 ++--
 lib/search/indexes/github-docs-3.2-pt-records.json.br    | 4 ++--
 lib/search/indexes/github-docs-3.2-pt.json.br            | 4 ++--
 lib/search/indexes/github-docs-3.3-cn-records.json.br    | 4 ++--
 lib/search/indexes/github-docs-3.3-cn.json.br            | 4 ++--
 lib/search/indexes/github-docs-3.3-en-records.json.br    | 4 ++--
 lib/search/indexes/github-docs-3.3-en.json.br            | 4 ++--
 lib/search/indexes/github-docs-3.3-es-records.json.br    | 4 ++--
 lib/search/indexes/github-docs-3.3-es.json.br            | 4 ++--
 lib/search/indexes/github-docs-3.3-ja-records.json.br    | 4 ++--
 lib/search/indexes/github-docs-3.3-ja.json.br            | 4 ++--
 lib/search/indexes/github-docs-3.3-pt-records.json.br    | 4 ++--
 lib/search/indexes/github-docs-3.3-pt.json.br            | 4 ++--
 lib/search/indexes/github-docs-dotcom-cn-records.json.br | 4 ++--
 lib/search/indexes/github-docs-dotcom-cn.json.br         | 4 ++--
 lib/search/indexes/github-docs-dotcom-en-records.json.br | 4 ++--
 lib/search/indexes/github-docs-dotcom-en.json.br         | 4 ++--
 lib/search/indexes/github-docs-dotcom-es-records.json.br | 4 ++--
 lib/search/indexes/github-docs-dotcom-es.json.br         | 4 ++--
 lib/search/indexes/github-docs-dotcom-ja-records.json.br | 4 ++--
 lib/search/indexes/github-docs-dotcom-ja.json.br         | 4 ++--
 lib/search/indexes/github-docs-dotcom-pt-records.json.br | 4 ++--
 lib/search/indexes/github-docs-dotcom-pt.json.br         | 4 ++--
 lib/search/indexes/github-docs-ghae-cn-records.json.br   | 4 ++--
 lib/search/indexes/github-docs-ghae-cn.json.br           | 4 ++--
 lib/search/indexes/github-docs-ghae-en-records.json.br   | 4 ++--
 lib/search/indexes/github-docs-ghae-en.json.br           | 4 ++--
 lib/search/indexes/github-docs-ghae-es-records.json.br   | 4 ++--
 lib/search/indexes/github-docs-ghae-es.json.br           | 4 ++--
 lib/search/indexes/github-docs-ghae-ja-records.json.br   | 4 ++--
 lib/search/indexes/github-docs-ghae-ja.json.br           | 4 ++--
 lib/search/indexes/github-docs-ghae-pt-records.json.br   | 4 ++--
 lib/search/indexes/github-docs-ghae-pt.json.br           | 4 ++--
 lib/search/indexes/github-docs-ghec-cn-records.json.br   | 4 ++--
 lib/search/indexes/github-docs-ghec-cn.json.br           | 4 ++--
 lib/search/indexes/github-docs-ghec-en-records.json.br   | 4 ++--
 lib/search/indexes/github-docs-ghec-en.json.br           | 4 ++--
 lib/search/indexes/github-docs-ghec-es-records.json.br   | 4 ++--
 lib/search/indexes/github-docs-ghec-es.json.br           | 4 ++--
 lib/search/indexes/github-docs-ghec-ja-records.json.br   | 4 ++--
 lib/search/indexes/github-docs-ghec-ja.json.br           | 4 ++--
 lib/search/indexes/github-docs-ghec-pt-records.json.br   | 4 ++--
 lib/search/indexes/github-docs-ghec-pt.json.br           | 4 ++--
 70 files changed, 140 insertions(+), 140 deletions(-)

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 cbc151da924d..316c460bacc7 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:a8c129497dad312c79c7feecfc6822dab6b1afa690f7526b916224878928922c
-size 614104
+oid sha256:0cec2153858bad7f6ac4246c926eda3a6d3d623000f96b88a68fbb0e53fe766b
+size 614192
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 7e121e1ecd1c..d508a498fe6e 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:fd3c25979ba047f2efbdd1d849e25ffde4d06900b563eb603c82652cc464af83
-size 1746379
+oid sha256:9b6a72590a2103e6772604bae4f6cec1edb9540d5fe3014accd400f3656418b0
+size 1746050
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 e9d31d0a85ad..34c1e31283ba 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:06a281919304d6668358f5d750ee9c108ff9a5cd5b1ce617b002a59bb1c31491
-size 953481
+oid sha256:1cbddf388a4955d3feb874bdf172fb9b7afe6ca3c6f01ce4122aab58bb53f734
+size 953371
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 1f3cfa165911..7d10a2318ab4 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:60ddeb263073c13d050ea4fbeeaffd3e9c7df89c4ef876808a7ff7dc39c22223
-size 3909467
+oid sha256:02bfe0eef905f5f26b403b73ac0d5245381391d9828a4c0af7d0c4e1cf13330f
+size 3908037
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 69814559d2e6..bb34ab53ea12 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:481f5263749fb0a795d9e77e33ba646db12110dbdc592068c64cb53bbe4a78c3
-size 583029
+oid sha256:25751acbe9d61214ec573099a7a16c7fd572d8ee9bbc3dc4d024118aa491722c
+size 583242
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 9daef8bfa759..15829fa84284 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:b3ecbbde22aafe54f5baca62a67047c829d8ac04d1a8c5f457e8568031241bcc
-size 2696940
+oid sha256:dffc9c739447cb042f463d42916532bfc2f8a7018145547b902032cd2ecad9ec
+size 2696456
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 6ef48bacde64..41b531022aa3 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:104d608ec74a99ccb507e228a996cbc80994c00c35ac962ca8297b473306a247
-size 617836
+oid sha256:4d1217f17c19753f065a1ba01a068ee4089b9ed9cc12ef41a6f84d7d9ae00b77
+size 617760
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 655f508146aa..81c5c1376c54 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:db04900e8d79cefc4cdd24aa51dd209c6d724d3b150141665cf31753b036df49
-size 3475588
+oid sha256:d396cea609d4b95ba8d6bcb46a4860f10bc17d06a67e57c8548f2bb41f538964
+size 3475965
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 13036236509e..5cce5bef099d 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:bdb63edd7fcb4c6cbdfc2823fdfae66d3888e61c4bea94a0d5c6bfcba9946461
-size 596000
+oid sha256:42db78cbb45f319dce16ea08132d0f0061b6b3f22878780bc900e684925cc9be
+size 595954
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 1dc0edf32ecf..45d211f7be57 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:ae8634d008fabb40ac5c354b9b306fb6bc52f19340fdb56e8e8947290ba661e2
-size 2818370
+oid sha256:270ed8721b5a975859e27a25d86ed6fe097724f30dcff5ee398f3d350453e5cb
+size 2817446
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 0f06acfa0918..b14cd24123e0 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:c5ef5ac4ed1f8ba7f0be4144a14358d020a61f6b5acd13924d5adfe4e9bb1d3f
-size 627625
+oid sha256:0fa4927d721d6c7d4d75a7be716485aa565bf05c0d2bfd3efe8c2dfc7fc866ef
+size 627862
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 2dcb18ecb3f2..15b45215ebcb 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:788008c86f71cbd508fcfa17a6ace3d847d5223f24bbc5c9470e42ea77d4d528
-size 1787947
+oid sha256:87ba8ac9d78a99f70402071bbafa7dd9443d3c958ff0e773a530b48b2242f3a6
+size 1787816
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 9336eb78a621..aef2b303c36e 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:865b2905736490e6eeb8abf64637af625cd189dd8b10a4d31e27ff0a8b543abb
-size 978626
+oid sha256:5b76cb885a52a72378c9cf26a5c1da32d459670b4b7ac04088f4dcd28beffc4c
+size 978130
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 2e68ba73ce64..09847f7987d9 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:893589670a8828d67a0d609148c4dae7d9e5b302ffdc1bf683509c74fe5598af
-size 3999207
+oid sha256:732637981e723e21a79570cbe6fad80eda1a109ab5b3fc52304467b762f1161b
+size 3999134
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 2a95bcc6a4e9..191327637c96 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:c3691123c1fbdce1681f9ca794b8695717db8f5245bcb438f33b6804f2c0e916
-size 595361
+oid sha256:d0b0c2088d452fcd597ec79c6fa43466d7dd03aeca93906d619081c6406eff13
+size 595425
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 67601ce760be..03b033dc23ba 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:39d51db33870a887c36764a5f572ffdddcf121b09e2732dd5095cff9fe91f1d9
-size 2759447
+oid sha256:d812a1abcae1918776678f1ab5d41615697c125855b9c4981d69c406251c19e8
+size 2759139
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 9ea80717d459..ed2622a61fa9 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:a3e339bd0038301ba6dbc75df7a3e0499c35393c2ecc2841afcb8ae7f30e098a
-size 630988
+oid sha256:2b124d950dd096cd37a76b2ffa1b73543bd1c7800feac066935307b409864412
+size 630922
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 157ffc3bfae6..da043e4cd1b6 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:d1d1de5713e614d89912f644851cf67b0caf14e625865988f4be11a9cc3cc742
-size 3555751
+oid sha256:41cf2b3b8155a6a6306b7e72090f0e3838593294863aa39bbcee7df39cdd561c
+size 3555075
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 2e5ccb5eba88..7920f919400d 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:8f900b2bd195c245642b6fe7566844e1a4cee00a5811ae024ea0192628ef2d8a
-size 608281
+oid sha256:d89302e61319912655babb76073d86647d1e83adc4611e4581c80f82ac6adbdf
+size 608057
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 aa8df7717b74..ba9df1216484 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:d8534c870feda1d5f701430a5bb7d4d1e9ad461ef934ef974ff9325447603b1e
-size 2882343
+oid sha256:48a9664a479d4ac5b6f76434f81a3f30b65636866718d9f8c155997b5535eaf6
+size 2882371
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 f4a9ed98fe33..6d0bd9430080 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:f31a4c3776b44c1d6e59452725105b996c64bdfa9f6c1af2f0f98f5eb1551801
-size 639173
+oid sha256:2c49e83233bffb7896e74391f8e63d64a153c9c208f5e6cc5ea55db8803f4a25
+size 639101
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 bb7bbcbe8a5d..1725882e2fe4 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:ac5ea5b34725f30a455985282f206872223165b1a4df85ab12f6f875d2de9a54
-size 1814926
+oid sha256:6af4ae7b7662f8715ac98b188c4bdb1d79182ce9aeb5f8ee214cccc21ec2a546
+size 1814882
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 ff1b3ef225c8..4ce6b583da47 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:a6e7597d35a8843cd2ea5f0181b19becc8976255ab0b04619329b5ec3edc350f
-size 1009455
+oid sha256:d94680b23ed30beebbc30b26ea799c1c29df52b388f1de61875cba1c5927945c
+size 1009573
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 0e0d58351920..2ebf174b69bc 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:50e67b53d39541d65a79087bb285ea62807148119ebf280a9799d8e7d00c42e5
-size 4122739
+oid sha256:5d09c7f931d0a13a0a0e95fdbc9e0420b58bd2b9a37aaa080c1e28d81b220524
+size 4122308
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 18860230bc00..88805569877d 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:d8c9787b7c0f5358dc678008e6d929feeae348310f2201fecbc34d0523ac452e
-size 605722
+oid sha256:dd6ffcc105929de4fe485e6a14d0a3e23b47d2d13c7831f2b38289bea06a3af8
+size 605908
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 a9eddec88143..78101f3b840a 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:36faddc8512b1c3896cbe5bb0a39ac90eb2b3859191474f50281a72a76e4a520
-size 2813687
+oid sha256:757639374323f1df2d3e481b827f4134de85fbdb8412aaebcd5b8f0aef395c1d
+size 2813951
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 106ac85f55ee..f72fcf38140f 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:5a4fded95a1f88057c5bbef4b288c9257eddd32788a5d652a973c8f98546cf07
-size 642406
+oid sha256:3c0fd63313374abecfbd731d26d8929553b73c8302d058f1b2ed6841121c42f3
+size 642417
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 9e23ac21a099..be2e5ce944de 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:b3be33491a7106b737772df3e44b8b375ee04feee4f4020306fac5f65a37c189
-size 3621046
+oid sha256:ea728c3aef8229944493fe087b69d6f103e7801ab2832fe793910eb3b8adb1e8
+size 3621934
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 621d1dd02c9a..bc63ef1cb311 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:426e866304ddfee0d09f6c23237e25a762f7602a8232e3f56643870e98b623df
-size 619713
+oid sha256:17cff44d5e138e95ddfe1cd3e8a265b4df9b28e43a9969bdd0619051851891de
+size 619392
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 f11a352093a6..d0a790eeb664 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:33accf15baf72ba168fe5deb5117696116fd249c3c960313c04e74d363b1cddc
-size 2932297
+oid sha256:6cec1a1c5273b196d417ce9b9aa1b8ebe3cd383bf976ad240e747cb4580d11ad
+size 2932051
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 462bab225a8f..53197bb6f98b 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:56e342502f1ebed6e2029f00aa402b795933fbf5c41c1a5f2087a41f150aa78a
-size 659595
+oid sha256:209bc843fd76f6f01ffa3c9a8d8aafc37fed3339e1978918ff32084b6d08059b
+size 659311
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 60d08b3a9876..6857e0cb8a02 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:3ed64e59c1adb3527f0085fbde5601992bd0abe205ef8c44e8fd99163eec94e7
-size 1872260
+oid sha256:c2e90e6c0a835433333848900167fd9c8f1f2e6da95dfaa00297cef04c3c4978
+size 1871667
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 98c488a9d012..d3de24a5a505 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:37fba52912d8dadeb491d6f380b8958a081290aebcb36e8fa9deb19d5f7426cd
-size 1043238
+oid sha256:3719725e273b6d56f2ee23ae332b6a338ba559e6faab29dec3f6aa222fb2b1ab
+size 1042669
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 76980db41481..c777db12bc3c 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:23ff8183f5a605dac60604af590d665da408662a28b814e3bfa9ae0d4a67be74
-size 4224481
+oid sha256:0e02d7e823c19497a5a688c8984ac100e49c91272ce146efb04f82598edf5f8f
+size 4223345
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 10fdba696512..76832b40d758 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:6523d2c88dcaa9e0e2b5811cd2fa1fbe6a83f0f477310acffa61a1907ea1cf89
-size 624076
+oid sha256:f0536330a1a6b36c5a429158d568642964e75be2223dc3dbf0a8739fd9cddb87
+size 623819
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 387ac64f5530..ebf73458d1b8 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:00d6f0e435620925a01ec395e7647526b0846e0d84199ee41989afa01295e44b
-size 2911879
+oid sha256:02cf5e9d441bc8ad52d11824c842a5bee0b2ac36dce49df5257ef0254595b477
+size 2911998
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 27873b4de17c..ba1ba83bc2d4 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:b7e5303b09d84040582657d8368b731e2e694244303b0a10f4e00279523c3bee
-size 663865
+oid sha256:608e04fab101c2ee2f81085f56da7752dfb81d46122a7a61f9d4dcfe09e83ff6
+size 663744
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 46f84b191863..ceeb0e3e5502 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:625a52f6a476915e1d8060d415351d294013c48d73a94eb4f574441bf0aa0ff8
-size 3740689
+oid sha256:fcd24ee6a264ffb8cb4e2310d27ef5cc5c69229c36120eb3823b9bf53c62fcd4
+size 3740834
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 994c5ba493b1..e1f70d7b74ad 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:22d0040d15134aa49fbf88a9a54a7fbd842442ed60e486f37ff2659f9fde7d1e
-size 638942
+oid sha256:b8f494e59fee68ad6792428dd6305e527effb5a56e7e0af602769d59d2f35529
+size 638701
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 e445ad79f01a..ce4a1eda1f8a 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:d2ca7a677233b5eea18405457f3e9169d8fd780799a5c0278a46034254f2a031
-size 3020011
+oid sha256:6b132e372cfd042fc6468b7cd2dda20aecec3fa14989a31e1a7312ab6c6bc99c
+size 3020351
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 e79222773087..8f8c35238b21 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:1f5427dc01465c70eda59623ef3476743998847740bbbab5f00d343080f69f7b
-size 848221
+oid sha256:f5aad425f26d377204067e0e74bd66f8b0ecfd1d0d61800d5000d311f58c4735
+size 848344
diff --git a/lib/search/indexes/github-docs-dotcom-cn.json.br b/lib/search/indexes/github-docs-dotcom-cn.json.br
index 670f5486bdd2..59f92717cf4e 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:c4bd837ad9ff848b1eb7387172c620696900a002ea014cd2f933f1498a1763fa
-size 2093072
+oid sha256:e1764b5df0d0cfcda01bfd36b1d9fc68e5798e6bb6dbdaf55c4c923223117946
+size 2091647
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 7decc89e14b4..c8d0347e26df 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:80bdc2cc0ce044bca5ffb44109ab196d4249010a8aee8df8841a58b0310f6c92
-size 1320194
+oid sha256:d82df8e3c717aee07cbf1cae420aa10d01793cfa579afbe91a30e523eac583cc
+size 1326610
diff --git a/lib/search/indexes/github-docs-dotcom-en.json.br b/lib/search/indexes/github-docs-dotcom-en.json.br
index 7c6399606c40..ac0b58e54305 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:eb0b64b87e593a226f1997a91adb074989f19c4fdfd8f84ce3593fb3aec41385
-size 5069169
+oid sha256:956a4248a382cd62ad4eb1b24942f1a5eb5319fb96e4036d9e1ca439fc101362
+size 5067291
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 9462d1b5ad4e..036d05d2b651 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:aad2c6ced5b3a3f0774f552430d4f1ea69d7a7303c3fc486c88845475bc2a891
-size 794752
+oid sha256:2437a8ff253785ed964f22de57151c7208ac5568bb5ebf1f6ed449fce3c63949
+size 794673
diff --git a/lib/search/indexes/github-docs-dotcom-es.json.br b/lib/search/indexes/github-docs-dotcom-es.json.br
index e81162458d2d..a67ca59ac4a1 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:f7f6c34d89672f904b3e76df22e7b2ee9a7156cb8eda122748fb544e948f364f
-size 3497756
+oid sha256:74774a66ae548cea5ed39de5aaee46c82d2c82e9b51e3c4cb2f6f908b250e5d4
+size 3497052
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 067d272480d1..91162fd46c76 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:1002084860127e3f192c7fc243fe677f716a40188650a55760c46861577285de
-size 856270
+oid sha256:799c0915c8e18146ea4b8a76fa87e9fafc478b271ddad2f2c87c0a56cf114aba
+size 855925
diff --git a/lib/search/indexes/github-docs-dotcom-ja.json.br b/lib/search/indexes/github-docs-dotcom-ja.json.br
index c5ccf2beb7c1..2b9a6a107572 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:0f08e42f1c0c919505164a331154cf3de732deadbdfd0e5a3928af2b45c52fff
-size 4557984
+oid sha256:72a0e297c5437ba526a637c1f1e85f266cb486361a6c47964db6521ad67e6ee6
+size 4557536
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 28111043ed8b..d164a323490c 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:e6638fc6e78524e25054f16d3b07ed5b89b65505bdaf5da71a26b2e2c204316d
-size 810457
+oid sha256:5eae8653c7c4c6804d4afda50a37b0896cc25aaca959c587613263ec58e563b7
+size 810193
diff --git a/lib/search/indexes/github-docs-dotcom-pt.json.br b/lib/search/indexes/github-docs-dotcom-pt.json.br
index b112aee1a134..0b26b2f4a7a9 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:00ec6e75e2f2ce7ab2d6d7bbad58c4f8937e9f2c560eb2b3a9b24075ae118c51
-size 3612122
+oid sha256:0545c767ddc7de6012ead4bc2be66d9d30d18d5d217f63c12f1e8d0acb365bc0
+size 3612825
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 a84a46762e3f..05fc4368254e 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:f6194d918a4ea5392d759b7d2046ce73f67468db2f1d8201251744ea5da9763f
-size 513067
+oid sha256:be4c170b5a6af0b7a592009553aade6e2c79b612ce65e014837637c5a8706792
+size 512992
diff --git a/lib/search/indexes/github-docs-ghae-cn.json.br b/lib/search/indexes/github-docs-ghae-cn.json.br
index 2f81bdb434b8..df04d3fdc8ff 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:410e0d61a60de1c0b948c735731b56c430a6362b70fc3bebc4e366e6714c6cea
-size 1416127
+oid sha256:7b541df104ae9b0f7d2ee08fa1212bbce783fa57e878e1b561fa3936f1a8ec03
+size 1415896
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 4c43e472cafc..4a2324465326 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:98831fc664bd14da82dfca5dad08bc1b5c540e4280189d74e847a66346334b02
-size 832625
+oid sha256:b047be7232f2e0f9497f83a7cbe3ee64ad8a1cdd89da3ab88f575bba0b24d51a
+size 832771
diff --git a/lib/search/indexes/github-docs-ghae-en.json.br b/lib/search/indexes/github-docs-ghae-en.json.br
index e685c398ef5c..c1c5acfb1d95 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:5f01208d08d795801a73a1ab37a783873f966bb4db622b3f5535ac297fae4a13
-size 3341448
+oid sha256:27802a6e4483d260f7b0b17d82f3e28dda5696bc0c76ad4689d258cab6e3c388
+size 3342188
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 57c7526f77d2..431a45ac1c29 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:2e0feeac907110215fe58bc1dc138404d9fe35f8023106d92303f38357f43cb0
-size 486806
+oid sha256:6c881b94556fff7f76f993eb5e87f82a1975a4ee441dfcb8e4a128c8d46222a6
+size 486858
diff --git a/lib/search/indexes/github-docs-ghae-es.json.br b/lib/search/indexes/github-docs-ghae-es.json.br
index b3c8426eda30..0f5df2a5b081 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:f2aef7ac4eacd4c4cc7b1b2341b20ad8f863fcebcd3bcb9b2e04a70ab7fdfb0b
-size 2189614
+oid sha256:e8d191b409a4b526e9a340812d94c2760ee5f6533981924da7d7a76595404839
+size 2189618
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 7676bda254d2..c744a1112527 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:c04b7793b357dee2f35a042cf7d0c137c38a88038d201e057fa32a02e48a0c9b
-size 516994
+oid sha256:27133b203cac6c9f0c2603e1510a9e3973bb08c0f92aea0719af40977751b577
+size 516912
diff --git a/lib/search/indexes/github-docs-ghae-ja.json.br b/lib/search/indexes/github-docs-ghae-ja.json.br
index 2004605a5fa4..0824335f86f4 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:b3209d5bb167f70b3dad62ef33aa92d0a5f3b2edcabbf8678e72cfc846984c33
-size 2803490
+oid sha256:0f7ffe6e22241efb4c42970bc592737eb93c13e00347d9c514e38c621fdb4383
+size 2803070
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 49d9820af46d..d00265618e5e 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:1fe09b34b857806f30a6f05779a69a1d62d18f63162598f2c578b09630511c02
-size 500473
+oid sha256:4bb35efb41d1ed3031787a34a71043c20952de479486f9db56280938285da47e
+size 500334
diff --git a/lib/search/indexes/github-docs-ghae-pt.json.br b/lib/search/indexes/github-docs-ghae-pt.json.br
index f447056900f0..bec38af272e7 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:bfd6b22f85d67287ecd949a5030bab8f24f9f2aed52753ac121c5fe50a2d5cb4
-size 2289466
+oid sha256:201b44e4b08dc6b50201b01b86e18ee1e372526571be76b69a5f8335ef06e215
+size 2289882
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 f1fdc4790a66..bc1fa23ffbf9 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:6dbba82bd8b4d11b72434a0890c5f4aa783c051358d5d00f8dcea2d049a45cd8
-size 771926
+oid sha256:9f543ae89dc7e518c4eab94afb98ae9b1f255a0f91ec65f05c144afed3039401
+size 772123
diff --git a/lib/search/indexes/github-docs-ghec-cn.json.br b/lib/search/indexes/github-docs-ghec-cn.json.br
index 849a8c6674cc..f0e890762dc9 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:4fef0015581524acc1048e5cd3c56b793f1c9d9de820858e551d223362a186fd
-size 2109874
+oid sha256:a0b2dd2cce8aec8897f2e83dbfcab8589f25f90138e5abf260efd71da099a31a
+size 2109848
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 6d92d67c67fd..7886ab8690f5 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:18d8bf3b92c65938dde5e27027381c874aac2445d29a225acf294e7e332fac73
-size 1186212
+oid sha256:206979b7dd19b72899bbe6facc1e8526c8bc36ce1665abc4e6deb832cd8d0487
+size 1190150
diff --git a/lib/search/indexes/github-docs-ghec-en.json.br b/lib/search/indexes/github-docs-ghec-en.json.br
index 9f2734ed1896..e6a93911c199 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:a26dc3cb6cffdb9f093dcaf971a1452e3ac12069bb4f2a470cb9d96a418d7b68
-size 4803372
+oid sha256:3f105adb6e7e510e4b2d65daa02d313d0e4f520e04a65008a8d75bd35f1f4703
+size 4804756
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 8f2ff5526e21..347256ea380a 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:7fbf59cf13d696ddeda001b213d314fe51c85e4fc993554e6804d440d1dd4747
-size 739553
+oid sha256:9bf3a8dcb74256489a090cdf09af86c1497c5240fcf0acdffb8ce54f5fdb1b11
+size 739530
diff --git a/lib/search/indexes/github-docs-ghec-es.json.br b/lib/search/indexes/github-docs-ghec-es.json.br
index 331897b53b45..08ce61b7b28c 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:85d9e1aa7e997efe4a3a4f8b7b5d33d7c6603e4f5791169221d68c2e971b2e20
-size 3441260
+oid sha256:cb4ee2c689ef5912330f1e5946d7cae091a81b4971b619d7ca73d0246b22d691
+size 3441309
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 5ae1c3e4fdf7..fb86bbe1081c 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:5e8bacc68383676df6cb3d0ede86eae9827f38e4172dbccd91f6e673f9201e35
-size 782951
+oid sha256:93d3784d9097109935cdc898b0c5029a0f4620110b5f5350e84cf646b2bde50a
+size 782643
diff --git a/lib/search/indexes/github-docs-ghec-ja.json.br b/lib/search/indexes/github-docs-ghec-ja.json.br
index 1f131bef2103..e97886c5e4ad 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:3d63cb9c8194204fc3178a01d08000f9ad063bbc3eefe7a4ba67e89967c64868
-size 4397424
+oid sha256:4ac417ed51018c052402a069028caed421161885c16b5ed4625bd8b44f02ef62
+size 4396075
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 e8398d244b8b..0b32d5c7308b 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:d5f74ccedc1285ff7c8623d24e548d95cc15fc2095861c6c1942d37decc0a1a4
-size 755772
+oid sha256:a666f59df1239968a312569aea214edecfbf7bd6bdf687fbc1b673a070b56263
+size 755905
diff --git a/lib/search/indexes/github-docs-ghec-pt.json.br b/lib/search/indexes/github-docs-ghec-pt.json.br
index 447a71aaf39d..53640b0e9ad2 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:33e01cfded40b04ebc91f9751a5b1404d96c632f0188d2a56c8308c737353a46
-size 3550370
+oid sha256:c589a660781677249029b61c3fb9bd70748a83220529e149258450447c5a6876
+size 3550430

From c670ed14ef6c7d2f7020a58bf700d75f491d76f7 Mon Sep 17 00:00:00 2001
From: Allison Weins <3174849+2percentsilk@users.noreply.github.com>
Date: Fri, 7 Jan 2022 08:40:49 -0800
Subject: [PATCH 12/13] Add instructions to download usage report (#13722)

---
 .../help/codespaces/usage-report-download.png   | Bin 0 -> 12277 bytes
 .../viewing-your-codespaces-usage.md            |   3 ++-
 .../codespaces-report-download.md               |   2 ++
 3 files changed, 4 insertions(+), 1 deletion(-)
 create mode 100644 assets/images/help/codespaces/usage-report-download.png
 create mode 100644 data/reusables/dotcom_billing/codespaces-report-download.md

diff --git a/assets/images/help/codespaces/usage-report-download.png b/assets/images/help/codespaces/usage-report-download.png
new file mode 100644
index 0000000000000000000000000000000000000000..3d4460a10c62e249162b08927e4c9fcccba574a2
GIT binary patch
literal 12277
zcmY*<1yqzl_xGYGup$l8u&{K4(z(>Gpumz+N{J{S-4eQVElVn?EJz4QODo+-cY|~z
z9pA3{zW?{zbKpGZnVCDk`@3`Roq6VlYCcxI3#0`C0D!wNs1h6ixJ`w5j>Er!`M*nt
zxBvhIYGFzWIvzNi6SwS}1t|diGuL@m&+Y4+YEPfwKiT(gqweWg5yy5HBAqMMQw4)D
z&q$;^1S`T5-;$kx008hOmbXD6F)v7>{SC>;Fb@m;=Su#=5EKFz(@K4ahu|Q{Wx~9_
zb3aq;8Ot3CHteux0-Z5rLquhtZ4Cc(%wVd!Wf~AxcS}VVjBS^fqvcmEdSmL(y+s~>
zL<qx5mJcV2RBigPN|Q6-pd)!7T%LxV_b@YcnKMsWBS7_;qeegu&z3DrLHQ4&!%SvI
z84fKDF90|BaMmZbI(AlWIL}|{+>8BcsKm^zXD+j@csg_SucWw_`PSG7AOo8J87$05
z*|W-D)iVX4{MIwYrmV#c83+j*f@0PG8NJ|9<{7nb8#nrCV<~UL$??1Hs4L1nOPa&3
z9?c29tB=km$3XV?rD(}yp<7N}Ws%r%7Nwi3?NdgLX0dSG0@>IqpPBE-IxM!w0|;lY
z4LYCDes+sGNFm<c-=;E1x-qQ6!#k(+W|rY)BXJ2Q2nPVTXtf`UUf<Pf&E!?3j6SoC
zE6>^gIT|UD_~r`aKfXE){e{reUw4KFqBTLeQLKEr=ol;pfY_$$^~*e_o&~M=%$F*Z
zp|W;9QzyGkI1l_EpeU2_ICa%N1fuI%0ylX6m_qP~6#eSFA1>YLG-RFmP<dyz;kvE0
z`d~X4Fp^5!O5OcXtu%#Vv6cc=SOE1iW(P$Q0{{+zTkF0<>C$-~I?J4;TCSfeU(eQ$
zd%PLX-?^O>X%uM|VL6=D2^&TUgMV|N3Ui>Nrq;2@+jszg_*<Rx(!?_@Q=_iGV?{H$
zl?0OS^&Iq;?hty+bkO*W>saJ{qG&SW<5Gm1+8O0R-y_e$z*tHm)`IlM&V1t%M=`vl
zNuTY`E2c^0ImP|pWbGgP1v~imp5GhS2XD|y;*G|Klukl*n)p1n<tjAwx^#?ATg*P(
z=xL0-Q|cqEO{uT(;n!D&epfl7Ow03`(w=d9oW%6H5?)i5V6QRh7u&C=Zq}F5R;JVk
zKf0Zr^7AFk^L{P_9^uBQnzseLe1g7;tawGt0)t{GzbV^1^3*K<c=SKmru;fQD6DBp
z=&eLMpT(uVC^s~@ztZ!>xq1`#Th^eJb&scWe>3#CNoNklO^lwmB@{7&8C1h!(sj{Z
znRafeTi0}0ANYPkeCp>NSa8I&d|6)4)N+~l2j^okO9{gQz3~Wc0tO}~rU$`vc(XK`
zi*7^B)Ot=~d)+B<d|W|ditsdOSpPN;oY1%7UT$IOv_sL+3#>nUCq@5cQplr(jz{lb
zO?+W$=?LV|NK+rAxP}~bV^$5J3LYNb`T4nbk9}!r@#Qq&!Hb$6Q}QNi*7sVuhVV4C
zFw!W6D95OeX}W0Yi#%vKMXp@P;p{Jdc5KKnLayV(P0YG3RfnUaf^X|6ch*5&Q@7ah
zVy?c~c4NZ?GiaC!E%`Q%2Wj46pDHKGNULcbW4`Om1!qvoi-fuhU~O%HuJggoE&N(A
zx?xbBd^{SJEEjx}Ud%I-Pet~2Lt&|jH_6&HU4tXmmUFM^6*~3D_JKyyCk(`*EsfI{
zeIimZu`5g{+AKOI`bXb}?WyEsIbMv42G(F?aJ~Uk*|!vZzHOzC2Jc7yU)P2OW;ow4
zqZ}3j6nbq}U)Lf!`8G}!xnQp*eZ>$h_CJ05-a$(vp|dkq=dVSKu{e;(gjw@^Bir93
zMs^Be+62*zGGQFw+a5!iK`lvbU)$P8RnT4^3bsr5>bj1+Ik0Tmm*eL)v?LH0x0uIC
zzb!K?X#LxJMFB&t&xeABF1J`$DA_<erY}J*6{y8EzUXPg2w#Oyh~0<m^W&ZL^mH|-
zh2lR=`#z7a^Bei_HU}#fD58+JF>E_DnM`0NnK92-o*-tDH7?Nm{P{E4z!(x~-fb~v
zvGgj}t*%RN1Nkzu0^y?nhnxnr8Y<ARk?kd4MR<64Y%Do}jV%-^^h;>-(xk#Gv0w!B
zo35M<?TG2jE8V6?U{n8ZfM@vD>M9gMOGgHe@SL&AcOQ3R7#L95Qim!)Xvwjb?@6=B
z$Kv54hZ{eCpUuT+6Slz@931>VfGl<`E<`}XlIV#X8Sl795Zb#K3oBoLJ)}3{?JPi0
zOlmkKy2-9I7#1veb^Z7efVeLTMpGY9A5ourO~}at7jAwegZpUm%5>@x<U*nEZUO*c
z^i<a6{&E*)Su~qZ8zagZ8U#R*cL}&!rAI+6b8RPW!SeP)3D^V!MqepkpE}#dBcr0D
zkB^SP=l~FCI7uJ!L9TP8VdKx*ghDrdOOnH7+Y)NZ*w8fq0xq$aE19<Mkqb8!AP+G@
zoXOyIt4|4R+}-v6k->)c8hr|>-oP{xaLwrCAt?G>ts&S5#)h`}u;95<T3YJy83w7o
zgRu+7Dp(SDKrL+$cJxU`4uXP-`A<AZL6nu2vSOjH2^?+Tcrd_Bcw_Z4x_o;Z)@rgS
zeEYmba(l5>)#Rgp;Zw<%_K<2iOjaVu?SG+@KWtv?;R`uC*;_=gqfHxT*WA?NAF?N&
zS5|YgjIsmC9)y-CS!D}?l$ZN7pe^Rbh6SRucgY7HU=XWAd3bmngD#G?CflN!W@|k~
zW(aaecl0-02mRX>$y-9t)a@Z*C92DrCtBC>@s!v+^xcXb?N*b@j<yx`wt;wEU7UVn
zM@RPbxG?hTau>K+JHI;57-b?<WpU!tisXcrPKTDD7nDNTg+R(Z0*|2MwxW-qTW*us
zc;SG7fm!sevLM&$>A}~|`%*RDw{OIpTYI|;y!lO|`(YJ9@mmb*vE4xgTy=gr`J?CW
z=KFI!#+X9dr)daTGfn+Se$yP(K>q}&uKujc7eVCkqFK4|Xxh7rG40wxXwH7e<WG9e
z!k{e54#XkWGuhEE>wGURC+3C5sCIKg&}a01{Z!?`*lBq0lEb}j+1OdT_xXbN4=HWD
zt;K-xrb>SsrODxE;cg!d_AfuQf2)7dbx&=rVFEj|KaB|J&B^Zk8aX`III7e>bDVbc
z^oi1XkKPb>=YtsnF7DUZD3XLx*HF~kCt&CsQ6GzwPm5Vx7s5rMK<~P5MrK!!su_p=
zvXRa{C9<@_ZnENCx!q{Jz=zZ&_E_3JagOWiHy@;0ioDLZ-^en_Q8{lk=kHxL1-r0Z
zUzOilZyha~9T>PcJr|4P<v+$GZNKYN@)zok!P$xn2P*<N0RP(>&{Mx?+HT<T*}^!r
zh<Mzxlp2I~zBzX=f8>iAxxka8k5>T!^Pe5o_Tx3h#%f)?4L^uj_XQ7>m6vCcPt{z{
zX(rsFeKhs4NzC>IW;;p-53EP}o-DP5l^Z?pNfSBkep>yjGg7KYha@5f2?i77f)k63
z>FP%`(q)M6+hFv^1ntWgogVjn+_t4YNl_EPASfglZT30g@$S^Ad@PnoFxpdXq*)Nn
z@?M1j)6T-E7#z(g<**8s6)>&OGlWz-9vtnK`<|}5X2=@X_=+%)?Ku+Ux?s@&6=mu!
zwd<q8EZ6NZvxoBX5H|eSnW=eNju;vquDhO_zZiO)CP_}bs>uZ1Amfnb#~3^=262CR
zV`&+xEKG(%fI%=Q>!DIz9S$a$%45(4)nUY8gkg~)F);**%=SnX)<YjN$uY>fnGb*X
z9iCVy?Rhpe>CO~X@;1i|t2PZ3^TQxQA#}Wyz0T9?N*z#iu%lhMgQWMEpC{&Tw5yx&
zIipCEAYCit^Iv<A@AU!@cbf7i1!cVM$G?C75)kI!gy-sH90k>@iBBHLB^vM5$(>jf
z+fCK}Hct?d5t$t65AEsh)y0`}prfXLOhi#@(1YJWN~ZBXHI;#pW^HYafsyfvv7z~$
z{hsvH)TETnwXF>%>ZFtu^O}Rmrt$9XUSX);HGsxXJlXtfTHojF?DMlTp{wsYJV4N%
z%HzInLL#DK?+Z{{|BBoySx5|xpNmU`_1?o>ZK>DRBfa5GeXdqkY{wh=Q>@R;)zrEc
z7s=^6fBqEQah4z@yO!?h>El>=AS?8P4wBim>{MmUpV&nTKZ=_aQl2Qih8}S+<`-Ot
zrk^UCsT5B;Un_R;tnBlx#13!N2Y#xs&A;Kl;MUYr$%ZF+UwQ#QSCW)WwZ>x9zPhEt
zt4DJ8QEPBiWOQur>9YQ8NZaXLQ}o6<oiGHaH>0K|Sha0Y^S7<T3(hrBxrXnh&Do!=
zdB5zQuJrH~yskSim1d7L{-jv{@<qqsqFGZ_WMpLeJ<wf3LU?q;+(>y@#hzhyPe2_o
z{njg<-wJJ#rbZm(bEF-hG-=QEI%3(d#GB(<mG7Vi-nEe%qPCW<G%JARd4@a3dJ(PF
zXDW1;yTmu9Eh#hlaK-oSYY%4d_U89lmzm-`QVK<^tw<K*=hXYck<Xt$kG;q1YhmM_
zu=JOjWqhulZLeLJB=u2y-aTPidly^CNq^t<{%h&__4kXeckhpkh|Tzp)<I&@{MK|;
zq4rV8JbKWNM=#yBKfSZt5VKu)HR3UKadA=cfuR+DpWw~<kd61RpNJ$W&YLy7e0=lI
z$V7qJp~|6e)}9;akG{V%y|VQ{sx*R-QJ92mMXkl%8}}J-t>jK`0QZ%d#+WJ>(S)A3
zUv_8o%Yy{F)^|sn(|vvXphpf&-g-61o2Ao<Cq0ZZrpe39@+LNdM0h!0IZWj)yh)o_
zts)=wbV?K!)UhtA+aiX>JsTNukO*=b857J3z%GO+WSm{@xFX&pe;hslRqcH?H2j-R
z?2d_{#PJg!sd<}J4h?cVRn5T`R`Bf~{D%WeL+Z|IMz62sr4@zV7OJSU8BIv8wx&l)
z@bdGOGFCutlt-uze)fBolU4r4&0gVYPi=SF%vCS>XC33Qg?(UdZpb~U<MEXvW??%g
zeIc3$k8Ka`gcGV=^A2XxrD9eKJxEs$V!qrt*e00Mw!i=I!*Q@+4DZNH|9eq8BA5@q
zZPR-zOP9l1{7`LhHt+e=uI_w-Fe{k1i+MBRo8vfst`c4<DX74t5{Du_=Ht-F@Z>bE
z1PurwR9JGFd9p)|&&5j67)38*>ViN-qt?^+h9UoDf*wTLa9i2yq~o3wD;TB&_Eo7l
z-WC{Jk-Iuap_>xy9&o=IxHk1-+iFZIY*-s<{iV0IyZ8B(O|+c@C#8%aK7;Qu@s&=w
z+|kltN8KEu&BbQ8K)Ux{{L|CO*}HgtbMtKmIvxV}zalGV9;r|ns4RT`7^C$&uIjYK
zXy=<0z1^@#Uy~-80H3|q<?vU(gX8ONpI$Wwd~qaL`*p*4KzBpsYk88s>0?>WCidv;
z(nk3XHtCkJKAxf~kaWng+y$DM*88mL-h1@nMX=wMdrB9DyPBk6etp1?>$BM|R9fYf
zZ{l}WEBXXhG`9k@_QNgKmZNPcd0zOY-w!r7j#hHit}+cPdXIUav-#kOgggJX0MWf$
zO>b=xmL$O2>du0o3+{8-ccLXeE3t%7RxtU3QaB~5L;w%c>HbrK1clQu@XXxpkUY2n
z<eMc_h+=I8nzBrx=<E;_$q`hOo0};S&g(9TWs}=#w4nENNk_d7KKncG{skmfuqw2r
zj-ikF2b0a4)>aPM4~AcnRdWfS#v*^x_@Gd-J8w=Lr*PgqLd)<3JZLzr@ynTDdb5zb
zWI7dsU?P}=w;FzD8`#Qw^;(kww_N@QL@Y~<zd>@F-Q{)~+2ggq#HW1Xo2kcBuXj%C
zZw8~%<}Yr6aB6X<IGb2`(Izlfis-EpDUK%Kj`r=7JJTgs`>(HsB--RoVjG~6_z+Y9
ze&pzPQuqUAuyOEE<?7W<ye0?Gh~Ka7C%^alR)i95)9*A!HI^w!ug-xY1s!HWS88AN
z&5RANc8}ZtpgEZv8d=NWxCwgn=uyk;qz8Sc|Cf7LpGMlBIyP}>NZLIRt4QSPFn^z1
zrG67cd7a_R4A!JzJ>X`~Ar-a$mgHEnH1N>Z_fB|tt#aPYLX~~-#ow$zRL4PVg7MJB
z1ENT9g%B%bp^D@?u7r?`a141VjY#f7_8`@(m-c2i*@h*nS}m4T(~GciALI28nN^`t
zNC!2TJiuPy$=RKTlSR4fjiuJf?b^gIFaSGebjJI=j$E|My|hOQng?^N(FgjrHm6gV
zAh4i@qC%>^^5#fWRgE6LI(>R+GVsl&>j*vBzv$XnG4f?Lgq(a^+G7?RNyroJadeu9
z8!o*+mS^I9RCm-m`BsYpVpwTb%9|iZ9#m2Aoa0Iyw%Aov=V^)nyA2k&FWf)e#$zhZ
zH>MQhWbZI_bxFI}T^t^GU!aE%lP4Sejv(iX=1W7}FR2vQDArep8|N^39TEg0$rj^0
z74?ctqDOBeQX{!8r{yk<oZ?B8uR1j`p&17h@Vt>IIEtQ6oGAT^n>1+>^QQdv{M*Hp
z?SVoXFgKBuyvl;c@mm@PXaE?$^%+k}x>IyxIBpslafn(RE$}!+m<9ZP5<V51s4LL`
zcqPn?W?^z6LMW}$%N1~1kK9N!U;G`?)~uoGs*Uqv(;&iWA((}>3N3ku^F9d~tp1kx
zg!AGXeo4qf;kIyu_x_;f?p{7w`+pKKiWLmde0x*&WOeW>!wSR0uUxSt1zQhlfL>F`
zFrzFPVJFbC3N-BGyBC^{AYwH%Kol3m#s^jd*03GFO=(o+xj;l}s5d?_M}W&X4=q?S
z)PJRuf*2&7)Fpg6n(=kDE8By35H92KqYi?_0>f{JWj_V!l0O&8N*z)If)p~*#b<*y
zQjnMS_IIV`04Pz400?MJFb$$%@o>H79vOwHZrZ~WCYpSzW0spBtt(^Y;2#15x4|DH
zoRk*UtQ4VcG!IZdgB;!W;|M^M^BD)M;0zVRz?zYYqlm}%=>zr|KfF(Uknp@g1e5B=
z8VU-gRiL&Z9wIHuH;1R#**U_)k(~2IXVl=wzt;ZdUtJ{$h!X<*5r#=_#FOdX^H#L+
zCf-ea9m5=YGRb8~H_6)Y!@h+U?U#td^^MnTeBv$88`%-;gduGNm!z}l;vc_3pq9OQ
zbYzQ^wVwzP;0SiUM+2(qU-*;QfR!24AU4^j=FN1Sy*V6(US|>}6FX^mD78m?1wc@T
zp1vG*Zc_PHystT*E2DEhH4`z&(wdr|xA(H@2L}a3a?NK@$O`d-`b>H9%!vbcvx`Yl
z-2H(fy|=6$tTRz_(m~c&rOmEaNHWOxv(@o)@$pibK&0^rBjki=q9`UyL+gru4<6Zz
z6K!3^o;2_^BJfh~N!^GF)J*z0@8d@e&sr3raeY#=8`T1v0<MSud^U^|>$Bj_h&gr}
z3MMA2QDb*)r{7PnE*oyaImt;dR3JEFI@=ZN8Cj};C3H7>LMSYX#Wybo8!i)-<_RE;
zuV5vP`QETCGznS1rBjVz{WoEnd6OG1re4dgHae&AV>k~=obKHK(d33$(t5=1={r5=
z!Q&CC?L(>I4ss!y>t>k|OZd4ppY^i}V(>G_LS5SD$-TY22W!K2cfJOrh<$H@a!&+^
zCh0Y-6>e+A-vkjH3YA-JxYbdSgW@kU9za-l`3pGY1SKt9+*vHN41X6_oq8_6jk8Lt
zH4HPQc^#LkO`k^TX8*#Lp9n%m%%z=YY4rN_)Be7p|8bN(Q5OBjW4`N$H0wodD)B;V
z<X+9xD#378@R$0JT#oGUqi$yb;1%-@{D;c~5Cq#3zhZjxdo?uICJ-rWQkvE<p>maR
zzyfyS%lb*v^~@Rsxv|m`jVyV^nz=atbu($b%KciQr56{Jo2DCuqzCo%^|h^e_><bI
zg;L$p3n4|FG$0Zkn1xjbW><tD3!0Q-#lc}QxC9MdK}cJj03yHX<*<myq7d$Lg;$7X
zd+OBEnn`&TI0-6B27Q<&^!Roqdn8iScEX&vrS)Z7J_`ukqbRaTXw%j3Z|lijK@XCE
zu=w)*z*&k+@R969f2G}f1-la^4ZG7T)oj}0R$KV-8-8e+tWCe}l85i|Z!s?KK3$=(
zWe$BNk5#RY%HOyY+zf>6mBe?zk&w*B0gI20Fc5g32gaPt`-Fya!-*Ljk|xfX6`3-7
z2gVd|1UbuQ1q-Y<Tz?0xW%zgPO-Qm-fm0u;6uURWNavciYHOt2w?NmVne!l)pGvIY
zE!$55R?$|A`IAs8#h-(okL(~cB&a3PlHs3YadaRnxm6Yxu&(e^*zitQF!FJ#WP#e1
zwPxSwo04iotrC7{YH_fkgnOY2KG$P#(S2dbb^MP17#N=W`twQMvqa41y673xN0A|6
zZCQmlNNL+W1h{gN{pwL(DwIDEX`cK(HM1ls3>}N(?RDM+JeE%&0rhnEsNvE?sI(k%
zA(Xxt4?q@PTJT|ZCC!6%r@h{-_>%Vqnk`$6p*L_MjiKYDWR%BwKn&C7dtu2GXhMo~
zcsC1`RE?`qq)c1@a-EL0No`28uS8`)@D&2RQL`*Y21&#N6~AUvgq{*t?~{_1mJcH6
zmXz<24B^A@vg4URR)!(0;J>?SepP5zgUQ!BL4J=sLibIZ#X5!qTe8rptD+rIO6h`j
zBz(A0b>~;A10jnVh95vT^%?RD5>-}j^EoPuI?>Ii;@*l)JGnyOhmtutv34t0$B;pd
zV;5LnRnEE=iCbz36+F}OgAP{y8l2#doC>5P?P}Zi1a(}z?;biN<U@T=p712h=Pn`W
zKxxkrTdwI*j;pl24YRebwlc^Yf=Nv#k%Fc@x)@-=3^hkS)+8uaG=0Y_19SjV>B~iX
z|KbxQa6J3YS>D&DC+rU^eeen9K82TCX?m+#(?VGEkCj=#oEntO=qWstQ~Xedk(LSJ
z5Ph{OS_z2of6q^tvv12{Y))bG)gtBtATT0>yyOOsIr@!JPw&rJyjIfN&Y08=RwUt<
za}-{C7aR>N0?CFq@E4_oe<uCBSN}Vz#!Oe9#y)~{;9aydziW@AM%wL?-3ExpjOR`h
znr=$<#l2|z7cb4^<L|(3eKF(3HC42FW21#18fGJW!;jrWELon!82>9~sYhI@7ru2e
zxC+(&Jnre(XzoV=K~=@{62$&Crw=1kW8`rx{glMOg*5d!eIOwq$nr**1+CjBE$|~+
zy11~upA_CvUhrJ?<PG#g+8qX*&k+u|^}CV1ckYDy2<EFd8Kfu%M`|CFO?|l4CMbU0
zj0S<z7)@zuXv+2P&1R91u{Jw@V{YR4{DB01^{!A8fj+kM@nPwbc64wSKu7#@c_&O<
zg@x_iA>)2gbF`^lc}Psy0xQ3DiI5>U2hxy?hzTZ%k`HW9&{OT8zp*3}<`W*Wx^BB~
z&lm|#ih-3$P)<qk3b#x4KqLiBt2L?l7_(d0eZb}MIRfH@JB9Iv%n2b%QO;uT#?d$v
zzrlhNek)bzS5e(NeHiVsN-m%SvzwBW(+pAHkKGb#p6ODsHxVm$zURsxFBb6)6JGzJ
zJ(p5v`s9h3bt!sKj|5>>+D#Re9E5ysz0#<L+qo<kv95r1iW{T@9Ysa74W+yXO9gj!
z*4HH$|LfXF?DqbK7vt04>V#GRAg(h^Ot(DpTOOh%#OUGb7mC~Jfd;r2mShOV6nn^2
z>6<otr<-hkY@QW|2=e(-@?M%0g*5i%<z{y_@;lRC9=oRo;&CCsmSKd0h@k$vv-DTo
zUsXWh#*tmuPe%CB`1@pDl*!#3YuBwtJ5-whjs@PaQwQ>#aJ<`L&LEu8F`+B5&5QZA
z{5!wuyf8<mraCshvpWI})lS=`Z-=KM*uH-rgR4TVVhhLa##Q|!g<3I00R(=^2y5O(
z-Q^ku*?K)!Im@|FwG8@IBYC+|rvXBjd0pcXGxTa@$S6S(=7EX$<<5w>>kJ+;P|Pjq
zS{;1>+%~e9SG2v7kpHndS8@!DR^{DF?^$Fr!TI_YUAxoh+)sQ3%eX$VGkp4h9m{kA
z*6?=`W@wVeJv`v^L(sroYo3mfxM^l90-hLYrQ%r<?f4~C<@<Wg?TEX1Zh=SyiIDEp
zHx#$6+bYYR<6%Sl+8*;Sl}0XAC|e?g+h-<RDw^+>CWUDS=m=_M-rB@j)$E%KE6E!F
zmIQ%L*x-*+$0~p;yJ=r7x&6w#?ShEg$>1Re<+=xTSik3J!D*_=nOgb(t!m$Se%p<z
z)enYK@*%Z`$GU<Rq#J+<2F*Im%vB6AC-k~4EkhhKJhDDZs~=w{KOr%x@rJ6?JH9kK
z&+akWdh({kt3U-hk=6d|-b7DltEKnR_MIZ4=!mhK`;3?ae0a?L&p;Bm7E!e@De9Mk
zo0h1_XAKbsRp`HS`>d-IqU@{34`0kt^CqY&R|%?b>U@*b6ik5Pl(_P5i^Q(H<wSmQ
zwvqTPp5lT!#p$uBDcYJ8>Ihiw@dm#Zt_&>q<m+^=+#_(RRt#U1;EfV$*B|l(hsC61
z-<0lt`}*}+H_`-nUK%-0%rkR$fKc}agu7EgpBM6WpA+0%Bxc9S-><MTz|RJOk5TB0
z{}<Uk0ad8G%nABg#?;Yntbp-P#c3$PVY@~Cz`pYa#T<5f5&r}+)*OeZ-s~3Mq8cF`
zRc%U!?UU1($_4oWnNDq1RjVG(S6OKD$wbj4sk|VIdR$Q&5r7oefkxioBzz%~JEglz
zLGwdFMeyM%DZHN;LlK#}rZvuNRsI|?LWK;G->askmZbvaev&j)<&5|jpW}_9kQGCl
zRUU|DW(meEm0vs7Y2GnmSC*yhen;f_Y13s^HR!u}^sG2q7S22>{C28P-DqUlO4NS#
z4>RkRFT>ioI((WZLiFMCZ7R3J9zH9u+gk6sKIoIvH^8x2L^q9WJpk&H`nTSG7`z-$
z$<EGT3voR3u<LGEU#I)1mO}Em#roig_U?@c9}O9qx;$b_JZ{pnJbw%GV1cwxL7g$y
z!OMbMJK}$6W`{t&J<PRPJb5P-UyHa1Xc(Y=eM4U@5{cQCe|jsEn5a(=`tw0^*=aeJ
z6-=OV6R>=wywJKM>$~*p7e1Hw^x0IabwSJ-2QCfStDF7bM?+T%XTK7>wIGHn@X#(Q
zh`t`LFdL+TOvaHTBaum{bqhM;5>m28KDPQ8*8<bhC>m~JhN`?eWm}t!>=>q-Z(Td1
zkzpP`DZ`N`RZelYh+~>sEN${!G6b_xEa-}gqqojYl9C$Y|KsStFhFu&n2Vy_dfTF*
z+ZKKu(HiPG#I}?EM4K@`hzQ@At84U8<HKYZTN2wUFlXhk!~~3)pHZq?(n*_}nF-CB
z#S}}~89d}jU;<GdXYi1K2s&{Hte#F+-=)iPd6r8`#`xAo>Z$(h+<$yCUzikbVX-KN
z2db))fGlu4y^9aKFD#rVZExFjYHsc%+|_RTP{mRa_N|Op#F0>E^H4#McG8X&e7ZhU
z;#woaJg+8w?2;IWRHDy8w2!MOC4Ui0hknxzz~{PF(3ggw5(Qa1r~KxSUkVBF3Ci7F
zd@V>(|M`@I?rVoFreE6ID+~K#4&cI}9WeuJ>=d0RB+DYn4~&tS+SV(f_vMIuIHCPA
zG9nhlkXE*ZkHAJ=U<aFgK%J<A|G?1DeFudA5#b4dczcnK;6wbUbQbb(0VXNa<X>bE
z!il*#O|7dzWq-1RGEz8oQKiM`_5so4z{GP)F7x1~{GZii3}v8RHYpqejR2@*CPy$C
z(H$`%$x?@Gvkakfk%wr*%2>9RFCv?>V{u_AA;(kSJi`N!6z?qjgul;rINUdw)Q|ta
z-Q09tozE&iFaN1^L$Xn^t*>KfI;9+Dm-j^Z*W%t@Xxfad=B+4VpOD5|8EU-IEymsL
zws=v}KH-=T)p_|Fgim)6X=`yp*-%P#!FxocBy2$}^X^(>;};jwKdkoDIa7+>I1BHV
z1hy!1w+X=#I;6+NX8b=fky{9Fy?;MmRpmLQOBSL>Doj+(9ak&Z)WkY1Q#U;=gK>tJ
zeVHX{Gj-S2JB0~!9X~ju8m_&04|)b%lO%++&C9E#f?Nc=`V#VV_$6%bx?VM$xdpe$
zINZ<DF1}9>lYXym*O!dFiq?Vl=&5;6&pd0dNH>E#Dw5OuLc!0Cu6$e`_4thwIY&n<
zozsq>?a>mZFTeyf%km}zm^-;)Q{-*IQgKO0{?dLzr5OHAHVD}9Ta_sT@^&Wvmx-UO
zU)+pX*~z8r`6NAN-1oKspp9_q%OayZo#*ar>r&Q1W)y6<9%2UOAZH{~b(a{ZGBZ6H
zy{@&g3=is^bB*6)u9N`=IFtj+%T_r+n1I)`{i_<ISNC1fqUU}=Ppl|dlwkqzFBFCD
zS|F~gba)`{jxB2>Kk1;Wg-t@0qEAF<f(HA@+K_<c=4~u;$^i#)7fN`Y=`lCDyu4hO
z8!Y2*+A_mP>FTWmAS~@vN-ca8Yo6s0n1`frE`kie=eWUqq&iS00bOP8cZ}5n>IXl?
z?gnR`V(Y&EnxObDt1Xa*hDLe%)Xa=&F@&tnykWNT+?3q)!~h)R*<$H;k$W;m&!u@p
zTkKDXYAkH$ISKQtGR}sa#jW-!x}VM(QOXQ4t+gJWc44kN0U40>-(Iar8yg!fz_qzK
zW@sSV`e&DGwMor+!N~ezN1TekS(;p!dX`=#0X&X^vxVCu5Zx}I2Q?&#5Hh6CLCW4;
zemLyg-M@IyRn*Y;ywvjr7HAG~WOP*j3sOm-K;MNa9G&}smVG^90o-$y!Tc;~xk^ps
zmXc8JFde@*Fy@n`h62z4#P!QF2Pv4^8x^Hdf4%p4`Pb@!K*P+W9ChS^1XiSU4WzTA
zTNesLjRCpBSoA?ACMK!a%Pz+4%}v}~q;WV}zwGlX5yFE{S`HLUqfEDokQ8ppra$yA
zOajqXKQNFvjRVoQmdJCECt}P!B^{P|a-!$is#xLpMxY0@kq@&<3_y0aw%>qU&~VFe
z^yA7&+j8!5+F?MG^nGB6`KPaA`|ZC~fAD}?e2O6hEE!q;KupmM0I;nZ=;G{b!Gnf;
zbnx}{b#X!0S$zj~$R;t)5q-bIB|dYiYQ_V;d>W&_OX+6>vQY@h!4@O{{DC&2$&c7$
z!7!Cft%lhh7s(1po?d<-WMXo1a%zgu094gB*t9CNnX3-i&hqDE2Zrl2V)b$koYsXJ
z;@V;qQwV>TfX_!^$Y1tC6MKUV_<o&({Lu5f+>nnd{NBBLZEbB6y7qQ<RX_sy-Z2-R
zU%(ocqB))`L)<co+R(rFcRd2*vU3ZN_OD-?1P<9(8Wrdj=nXQ$D}_^2QZ{#XHqx?v
z^q~MslzHJ-o_%2bLXon(S^yQUKFH?dS4#MY>}Y-HnS|WwUuii=+wdh_s3Se`?RWN-
zuOf;mF;|%bG1b*GlW94rJ3xXANQt%0A33jiz!nh+xA=%0>AfjYThaSZ{-}VN$%Ash
zMe;W{c*oSwn;u@z1NH}YFd~+wS9dUq^Vb5`UUxVK;$lhEfqIcY{E)p3uMm$)6tLo<
z3YRp{x6Z`CUa5iH$ib3jf+0S!$Rd1k%%m+LJC_Ps3I8|GfZygcUfzZQ31a?IU}JhS
zC6GFp;6_;}ti{H@-=Km$*!{xKn=|-RP2aAGU%Fyg_=Mqen-A=6<2gwGY992Mx%Lv}
z#kZ_2MQGE#%iKRkotx)I=Z8<o2FJONk8HS3Q<BLCqLWtmM42Gf)mbKHe^H-E(C9&r
z`ClHtnRQJaF}NtZeqNgU53k%x(TTgs=<#Kp(L@t)%{n&|TRZ>&aHB6cjS7*4y&%uT
zo}CgK(U03$GU45qRLPZNg+!obAeUU5-oF`ipiTc!R2Lp-ZDrf67a{@N;FhW2GRo`P
z7OG&RioK1#=|3XivcXFxq77YC@1Sjq#ded`SjJ&O`ePQj9j}W$!}*vXpZ=imKjQ&c
zc@o)Jl5nLx#{k1fT>w?YkfM`=k-lWym^*xo`{zQ=F5f{<S>Vz=ZnEj00eRU;ZHl(1
zz=0hmh5w2{&oiUapAX8al|i)uy5U#Qm}5oTCQ`KOm%q+oQZcW!B^|QlDq0CG?jNbJ
z8@yjLZC^V6WprcNNg}<^x^&!9`1It&!_Uvp+uNJZG;Bpf<C+>kWVpmHoFmAM0%kAd
zBDwQ`U(EA&xf_8c3-sr&wxeqs6I78w!DVfgV}HFcBMoTdL(;*AI(kxQh+f>wu}(fb
zIi7bI!xX7(xz(8#>G8P3K7|Is_V(5ozRPtxCR2pXe+l^o1?lQg8no!m>mn#ETTb)j
z;7ij?k<rXDdVft!KYYZD5@1<&tq>1eqJn*P6G#kCyBt}9P{1AyZXTbnqRjbiba}&-
zg&JNT;o&6B-U~IN%4c~V^+^J*LpjD7O<{KHiKAYQvmd&Bg;MmX!ahDKBAQw2kHzFK
z@5R*iCK#c|UTmD3s=Cz_4!)b!0=FokYS1~c_ou%KxV0P&{$jfQ-Eorg91;^T(cYt_
z&Zz8(7UvlXtGK~<{;EoDA2@kJ3I1oZHfZ2|W9tJg^otmudmW2Vew2Cnqf)|c6q?VN
z+bY-(;Lq-8HbfPMPG(hpFfwAy=y}q99Q{ddp8!1%oP-7*hX0K}^3(62Vn%46dt3<<
z=Jc>@2@4k3xxhAxzokl?vTZ5ZkJ{hDiMzKY%fT5v*18n)mcB`~xHe&jX?iodRTcTq
zCXGOwrNW~+Dhv=Uu#N2x6L>e<rKVCQMLpl<el(5)Wo3JY6l>^vRx#Buhd5P6+3HcI
zNaKFrZ+~MDwG!>?n6lvo7T6$=ALW#|B+2E{L3|Aan2^C-?BbGH6IH`XyE31SSLGiB
z1u%y-UXH#ncut~LBoyA5a+0=FWbXbvFVE}ha&?&$o&E;$vSwZzyRtFG%Y#SSu7eCZ
zuHKq@JqlVQRXId(ehY3$w=8%i)AffzQRLtRw-tH-@{*ro5hbMXo;i+blR#=>aQfEx
zR{PN{Z-57@aF+i2S4R_v<EuYC?Y45;GV6EJ{p7r^fMkCvp)o~qevRY<XOwGmM`0A&
zrqW=VjWWlFM!DSqNJD5#OMvACf<SU1&gll=Y3rl?gT`_X?o_WAJF-Z6yZ}Jh%=MSp
zcclnXP0bgirM(GVI}D48?rlywZJB;&{lAK2&a`+y(|j0JAX%niI<H5g+OF>TE%#T5
zPbc6_eHvY|>O5!x2xyzeR&rWp8bo!bt4c8Ho|jHua>imEQwOaF4dcu0hV`G1O%CJi
zSTMnQRf_4$7y8#O|I}1__=gP<!HU`Vt_{Jn9s2XmxBZJ6-AkYeel1QzQL5g@tba<k
zmGczgW$IKGvmyZA)`Sl3yoG)Oi~z6un7kOK6Nu&vM!zsIpiB_C`31Pq$lkG>6Qz3o
z`#)nL@G=@Bu`h*024c3Y6<Q3@M;oeS12-`V5MTT3i#;sR&Pqh>dqqiCo|6txJLnHE
z%@{)v*W{z|Ub3&r16EreI&{K+k#wFt9Q~Rsl<{hn=cC<NEVeQ&gT-ok`o`JB)nA>M
zFLLC9x7Gcx=o_Ph{uHqT%wAtI+-RH$y8ct6j-S|{PC&wMAs&YvE$>17-2sRd?hgo2
x#n$%$9+JOM{PQ48-mZ9nEfB)gOa>qh@BA>HQ{=Wtsl~hiz?2^=6+)i9{eRSQqZa@G

literal 0
HcmV?d00001

diff --git a/content/billing/managing-billing-for-github-codespaces/viewing-your-codespaces-usage.md b/content/billing/managing-billing-for-github-codespaces/viewing-your-codespaces-usage.md
index 9a8de62e3c6e..fefb537a338b 100644
--- a/content/billing/managing-billing-for-github-codespaces/viewing-your-codespaces-usage.md
+++ b/content/billing/managing-billing-for-github-codespaces/viewing-your-codespaces-usage.md
@@ -19,6 +19,7 @@ Organization owners and billing managers can view {% data variables.product.prod
 
 {% data reusables.organizations.billing-settings %}
 {% data reusables.dotcom_billing.codespaces-minutes %}
+{% data reusables.dotcom_billing.codespaces-report-download %}
 
 ## Viewing {% data variables.product.prodname_codespaces %} usage for your enterprise account
 
@@ -27,4 +28,4 @@ Enterprise owners and billing managers can view {% data variables.product.prodna
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.settings-tab %}
 {% data reusables.enterprise-accounts.billing-tab %}
-1. Under "{% data variables.product.prodname_codespaces %}", view the usage details of each organization in your enterprise account.
+1. Under "{% data variables.product.prodname_codespaces %}", view the usage details of each organization in your enterprise account.
\ No newline at end of file
diff --git a/data/reusables/dotcom_billing/codespaces-report-download.md b/data/reusables/dotcom_billing/codespaces-report-download.md
new file mode 100644
index 000000000000..e58138c80c8a
--- /dev/null
+++ b/data/reusables/dotcom_billing/codespaces-report-download.md
@@ -0,0 +1,2 @@
+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.
+  ![Download CSV report](/assets/images/help/codespaces/usage-report-download.png)
\ No newline at end of file

From 41e31e4a18c8e934adfc3402797e93f4a95c5f47 Mon Sep 17 00:00:00 2001
From: GitHub Actions <action@github.com>
Date: Fri, 7 Jan 2022 18:10:19 +0000
Subject: [PATCH 13/13] update search indexes

---
 lib/search/indexes/github-docs-3.0-cn-records.json.br    | 4 ++--
 lib/search/indexes/github-docs-3.0-cn.json.br            | 4 ++--
 lib/search/indexes/github-docs-3.0-en-records.json.br    | 4 ++--
 lib/search/indexes/github-docs-3.0-en.json.br            | 4 ++--
 lib/search/indexes/github-docs-3.0-es-records.json.br    | 4 ++--
 lib/search/indexes/github-docs-3.0-es.json.br            | 4 ++--
 lib/search/indexes/github-docs-3.0-ja-records.json.br    | 4 ++--
 lib/search/indexes/github-docs-3.0-ja.json.br            | 4 ++--
 lib/search/indexes/github-docs-3.0-pt-records.json.br    | 4 ++--
 lib/search/indexes/github-docs-3.0-pt.json.br            | 4 ++--
 lib/search/indexes/github-docs-3.1-cn-records.json.br    | 4 ++--
 lib/search/indexes/github-docs-3.1-cn.json.br            | 4 ++--
 lib/search/indexes/github-docs-3.1-en-records.json.br    | 4 ++--
 lib/search/indexes/github-docs-3.1-en.json.br            | 4 ++--
 lib/search/indexes/github-docs-3.1-es-records.json.br    | 4 ++--
 lib/search/indexes/github-docs-3.1-es.json.br            | 4 ++--
 lib/search/indexes/github-docs-3.1-ja-records.json.br    | 4 ++--
 lib/search/indexes/github-docs-3.1-ja.json.br            | 4 ++--
 lib/search/indexes/github-docs-3.1-pt-records.json.br    | 4 ++--
 lib/search/indexes/github-docs-3.1-pt.json.br            | 4 ++--
 lib/search/indexes/github-docs-3.2-cn-records.json.br    | 4 ++--
 lib/search/indexes/github-docs-3.2-cn.json.br            | 4 ++--
 lib/search/indexes/github-docs-3.2-en-records.json.br    | 4 ++--
 lib/search/indexes/github-docs-3.2-en.json.br            | 4 ++--
 lib/search/indexes/github-docs-3.2-es-records.json.br    | 4 ++--
 lib/search/indexes/github-docs-3.2-es.json.br            | 4 ++--
 lib/search/indexes/github-docs-3.2-ja-records.json.br    | 4 ++--
 lib/search/indexes/github-docs-3.2-ja.json.br            | 4 ++--
 lib/search/indexes/github-docs-3.2-pt-records.json.br    | 4 ++--
 lib/search/indexes/github-docs-3.2-pt.json.br            | 4 ++--
 lib/search/indexes/github-docs-3.3-cn-records.json.br    | 4 ++--
 lib/search/indexes/github-docs-3.3-cn.json.br            | 4 ++--
 lib/search/indexes/github-docs-3.3-en-records.json.br    | 4 ++--
 lib/search/indexes/github-docs-3.3-en.json.br            | 4 ++--
 lib/search/indexes/github-docs-3.3-es-records.json.br    | 4 ++--
 lib/search/indexes/github-docs-3.3-es.json.br            | 4 ++--
 lib/search/indexes/github-docs-3.3-ja-records.json.br    | 4 ++--
 lib/search/indexes/github-docs-3.3-ja.json.br            | 4 ++--
 lib/search/indexes/github-docs-3.3-pt-records.json.br    | 4 ++--
 lib/search/indexes/github-docs-3.3-pt.json.br            | 4 ++--
 lib/search/indexes/github-docs-dotcom-cn-records.json.br | 4 ++--
 lib/search/indexes/github-docs-dotcom-cn.json.br         | 4 ++--
 lib/search/indexes/github-docs-dotcom-en-records.json.br | 4 ++--
 lib/search/indexes/github-docs-dotcom-en.json.br         | 4 ++--
 lib/search/indexes/github-docs-dotcom-es-records.json.br | 4 ++--
 lib/search/indexes/github-docs-dotcom-es.json.br         | 4 ++--
 lib/search/indexes/github-docs-dotcom-ja-records.json.br | 4 ++--
 lib/search/indexes/github-docs-dotcom-ja.json.br         | 4 ++--
 lib/search/indexes/github-docs-dotcom-pt-records.json.br | 4 ++--
 lib/search/indexes/github-docs-dotcom-pt.json.br         | 4 ++--
 lib/search/indexes/github-docs-ghae-cn-records.json.br   | 4 ++--
 lib/search/indexes/github-docs-ghae-cn.json.br           | 4 ++--
 lib/search/indexes/github-docs-ghae-en-records.json.br   | 4 ++--
 lib/search/indexes/github-docs-ghae-en.json.br           | 4 ++--
 lib/search/indexes/github-docs-ghae-es-records.json.br   | 4 ++--
 lib/search/indexes/github-docs-ghae-es.json.br           | 4 ++--
 lib/search/indexes/github-docs-ghae-ja-records.json.br   | 4 ++--
 lib/search/indexes/github-docs-ghae-ja.json.br           | 4 ++--
 lib/search/indexes/github-docs-ghae-pt-records.json.br   | 4 ++--
 lib/search/indexes/github-docs-ghae-pt.json.br           | 4 ++--
 lib/search/indexes/github-docs-ghec-cn-records.json.br   | 4 ++--
 lib/search/indexes/github-docs-ghec-cn.json.br           | 4 ++--
 lib/search/indexes/github-docs-ghec-en-records.json.br   | 4 ++--
 lib/search/indexes/github-docs-ghec-en.json.br           | 4 ++--
 lib/search/indexes/github-docs-ghec-es-records.json.br   | 4 ++--
 lib/search/indexes/github-docs-ghec-es.json.br           | 4 ++--
 lib/search/indexes/github-docs-ghec-ja-records.json.br   | 4 ++--
 lib/search/indexes/github-docs-ghec-ja.json.br           | 4 ++--
 lib/search/indexes/github-docs-ghec-pt-records.json.br   | 4 ++--
 lib/search/indexes/github-docs-ghec-pt.json.br           | 4 ++--
 70 files changed, 140 insertions(+), 140 deletions(-)

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 316c460bacc7..49660b3fecbf 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:0cec2153858bad7f6ac4246c926eda3a6d3d623000f96b88a68fbb0e53fe766b
-size 614192
+oid sha256:7e6e14672daa356488457ab305eb75154202459b93e047457f824d1bfc23f9dc
+size 614232
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 d508a498fe6e..cbf90644d551 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:9b6a72590a2103e6772604bae4f6cec1edb9540d5fe3014accd400f3656418b0
-size 1746050
+oid sha256:b3590a60e2ede21e943b7ac6d2eb08557db45b89649280b890134f733c9b01b2
+size 1746093
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 34c1e31283ba..916a44d3ab22 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:1cbddf388a4955d3feb874bdf172fb9b7afe6ca3c6f01ce4122aab58bb53f734
-size 953371
+oid sha256:7f013b8c5d26ef0efbb153b29233bdc741430d2d64d9ea4a70daeadc73bd650e
+size 953503
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 7d10a2318ab4..7bfc493cd1c3 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:02bfe0eef905f5f26b403b73ac0d5245381391d9828a4c0af7d0c4e1cf13330f
-size 3908037
+oid sha256:a33b95ecb3f8dcf38981699c51bc527aa2793d68bb3f4d9fce7402602a84ebe2
+size 3908720
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 bb34ab53ea12..4bac84f43893 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:25751acbe9d61214ec573099a7a16c7fd572d8ee9bbc3dc4d024118aa491722c
-size 583242
+oid sha256:9258a3bbb825046afbfbc1b236b41bb6dc4a59a8b0ef5efe3c15fa34a7495eb7
+size 583218
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 15829fa84284..23787699dab6 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:dffc9c739447cb042f463d42916532bfc2f8a7018145547b902032cd2ecad9ec
-size 2696456
+oid sha256:51d209eb88668dcff6dac091fe684e490b853ca7dca7c582593f86058d3c4653
+size 2697374
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 41b531022aa3..290eff35bfac 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:4d1217f17c19753f065a1ba01a068ee4089b9ed9cc12ef41a6f84d7d9ae00b77
-size 617760
+oid sha256:f7c30e6382bc4f8adc59f208f95f35e068efef1193c0e710b023d46ff25ab94b
+size 617864
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 81c5c1376c54..1a3c431c4bdb 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:d396cea609d4b95ba8d6bcb46a4860f10bc17d06a67e57c8548f2bb41f538964
-size 3475965
+oid sha256:6e43e124333207dedb4b571ef8ced1e040a8f9d8a0c93f4a29be285abef7057a
+size 3476083
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 5cce5bef099d..df387335c603 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:42db78cbb45f319dce16ea08132d0f0061b6b3f22878780bc900e684925cc9be
-size 595954
+oid sha256:8c1497c28bc73439d6b4576ee6baa9a5353a59a0ce9e17701fe2cd56b176b50d
+size 595908
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 45d211f7be57..2f57f4aa0616 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:270ed8721b5a975859e27a25d86ed6fe097724f30dcff5ee398f3d350453e5cb
-size 2817446
+oid sha256:c4413ffabe60e3f0ec56b5f5d626a51d20ee5a987a64a05af54d168358620307
+size 2817510
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 b14cd24123e0..be8ed2bbc46e 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:0fa4927d721d6c7d4d75a7be716485aa565bf05c0d2bfd3efe8c2dfc7fc866ef
-size 627862
+oid sha256:dddba8b0e85a1ab4d5de2bce34cb26674b2a0d651b0f6afc4269ccdabf2bc38b
+size 627736
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 15b45215ebcb..da844e59814c 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:87ba8ac9d78a99f70402071bbafa7dd9443d3c958ff0e773a530b48b2242f3a6
-size 1787816
+oid sha256:41d8d8dae29f29f2f261097c00b5a0eabac7143e068daa9dd99550e5c5ae8df2
+size 1787720
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 aef2b303c36e..08b8f2e90909 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:5b76cb885a52a72378c9cf26a5c1da32d459670b4b7ac04088f4dcd28beffc4c
-size 978130
+oid sha256:aabe9f6e6eb75cc23846a668f16f65ad6781af598430419ed3ea79ea273d307b
+size 978561
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 09847f7987d9..20ec296e5443 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:732637981e723e21a79570cbe6fad80eda1a109ab5b3fc52304467b762f1161b
-size 3999134
+oid sha256:06a862d69f7cf20042e98856f9b63695a319b65f03dddb1ea9ce62cf04c98cb0
+size 3999358
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 191327637c96..d20f1790181d 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:d0b0c2088d452fcd597ec79c6fa43466d7dd03aeca93906d619081c6406eff13
-size 595425
+oid sha256:baf3cb7ee29549ac009c551760db099075bcbe065ca887fe2e11fd310675ed91
+size 595427
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 03b033dc23ba..11c33ee02a4e 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:d812a1abcae1918776678f1ab5d41615697c125855b9c4981d69c406251c19e8
-size 2759139
+oid sha256:459d45c3c9859fca6d6ec2fe8958b987f7d70a9f3e82fe46ee4c42ff5d2fb46c
+size 2758694
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 ed2622a61fa9..3de22114e13b 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:2b124d950dd096cd37a76b2ffa1b73543bd1c7800feac066935307b409864412
-size 630922
+oid sha256:f2b851b6059c105ec7e16e50c728f9ca5050147bb2ee5a6dba972ccf9973fe81
+size 630936
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 da043e4cd1b6..ecc8e9f73e6a 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:41cf2b3b8155a6a6306b7e72090f0e3838593294863aa39bbcee7df39cdd561c
-size 3555075
+oid sha256:dba25b874f4387de4008053ccc7145735685600c22f41b5e224861c206f9957e
+size 3555891
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 7920f919400d..c6b6ab82ec97 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:d89302e61319912655babb76073d86647d1e83adc4611e4581c80f82ac6adbdf
-size 608057
+oid sha256:0867a67a26f2b84806ada78dc564b9dd604a6b3f326005e91f7378fcf0785305
+size 608330
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 ba9df1216484..608be35800ec 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:48a9664a479d4ac5b6f76434f81a3f30b65636866718d9f8c155997b5535eaf6
-size 2882371
+oid sha256:54b243eeade0dbecabda058858ff292dddd82bce1586f31edd78a4242d0368f4
+size 2882526
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 6d0bd9430080..7e68a08844bc 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:2c49e83233bffb7896e74391f8e63d64a153c9c208f5e6cc5ea55db8803f4a25
-size 639101
+oid sha256:a71575ebf0b664e953106b96fbebb24b51688010a8de54a685b76b3e09520953
+size 639225
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 1725882e2fe4..ea0081a388be 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:6af4ae7b7662f8715ac98b188c4bdb1d79182ce9aeb5f8ee214cccc21ec2a546
-size 1814882
+oid sha256:738f2563ef61d88e6415cd87cd0ae540fe7d9999d840eda629163bf2a5d8c4b7
+size 1814295
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 4ce6b583da47..1358fbea3dfd 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:d94680b23ed30beebbc30b26ea799c1c29df52b388f1de61875cba1c5927945c
-size 1009573
+oid sha256:f3a1342f8953055ab2915aba803f4315ba198d56e489fe985375d67f3fa8d692
+size 1009424
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 2ebf174b69bc..dcd0e428964d 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:5d09c7f931d0a13a0a0e95fdbc9e0420b58bd2b9a37aaa080c1e28d81b220524
-size 4122308
+oid sha256:8cacec8a65df8ecac63b6cbf34f81b0b3628fb8fc8b2bc6b9d8da899d3388922
+size 4123027
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 88805569877d..702792f79aab 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:dd6ffcc105929de4fe485e6a14d0a3e23b47d2d13c7831f2b38289bea06a3af8
-size 605908
+oid sha256:0b47dfbbe995dae3467bf2591a70c4c9aeb5fe089050ad77f4e7748b70245763
+size 605963
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 78101f3b840a..c688f33a5b30 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:757639374323f1df2d3e481b827f4134de85fbdb8412aaebcd5b8f0aef395c1d
-size 2813951
+oid sha256:a067d4ff26303f8e23480c61da2391604e4f762cedca986de045d1c14a7015cf
+size 2813305
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 f72fcf38140f..7d9c6dde5bb9 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:3c0fd63313374abecfbd731d26d8929553b73c8302d058f1b2ed6841121c42f3
-size 642417
+oid sha256:713fdac44ec779b1d3096a3ac1de647e04ac896c2b9286abfc068d942b82f6c0
+size 642438
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 be2e5ce944de..417ac7292125 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:ea728c3aef8229944493fe087b69d6f103e7801ab2832fe793910eb3b8adb1e8
-size 3621934
+oid sha256:52556a267e7a96a5458dc71db39e8c648e6d8bab3866924a9131d1817921c972
+size 3622350
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 bc63ef1cb311..2208ac3bb61f 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:17cff44d5e138e95ddfe1cd3e8a265b4df9b28e43a9969bdd0619051851891de
-size 619392
+oid sha256:9b46a1b25ebbb6c24a8b413e5934aff58a60bd06f6cd22d915bd11eb2be4001e
+size 619597
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 d0a790eeb664..6bddb2d97341 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:6cec1a1c5273b196d417ce9b9aa1b8ebe3cd383bf976ad240e747cb4580d11ad
-size 2932051
+oid sha256:318d6a0c137d3dfc0f2c2a6aedd6a221803dc585c9fb081c2139f68bb54cdb1d
+size 2932186
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 53197bb6f98b..3cab6a026489 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:209bc843fd76f6f01ffa3c9a8d8aafc37fed3339e1978918ff32084b6d08059b
-size 659311
+oid sha256:7b48ba9c991d13e292097bd67a63f41e910fdfa4d757948281ef43d56f2223ed
+size 659631
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 6857e0cb8a02..57477204877b 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:c2e90e6c0a835433333848900167fd9c8f1f2e6da95dfaa00297cef04c3c4978
-size 1871667
+oid sha256:3c4feeefe5393edfd46c77a1d774f9ee8f25460019da8b6f8c803198f9b5c8d3
+size 1872542
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 d3de24a5a505..1aa56bbd51fc 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:3719725e273b6d56f2ee23ae332b6a338ba559e6faab29dec3f6aa222fb2b1ab
-size 1042669
+oid sha256:b58624f91cb3dc27c31c5ad9d94616afc0f0b3c2bd276f077dfe042a83aba6b9
+size 1043394
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 c777db12bc3c..1784ae2e1cb0 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:0e02d7e823c19497a5a688c8984ac100e49c91272ce146efb04f82598edf5f8f
-size 4223345
+oid sha256:45439f30b363c2586d23ba69790b84d48acd21f84375ae6ecbad2a29d5e4efae
+size 4223447
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 76832b40d758..3a51fba5d33a 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:f0536330a1a6b36c5a429158d568642964e75be2223dc3dbf0a8739fd9cddb87
-size 623819
+oid sha256:1d4fe5958a5b3f57d577ab9f84ace0a6fa22ff6c313d495430c02aced988ddf4
+size 624145
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 ebf73458d1b8..aa440578be26 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:02cf5e9d441bc8ad52d11824c842a5bee0b2ac36dce49df5257ef0254595b477
-size 2911998
+oid sha256:993d6ac41032f50bfc4779534da574600ee659d284678ae68a80385e4f7f0686
+size 2912046
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 ba1ba83bc2d4..5e9635fc3f3e 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:608e04fab101c2ee2f81085f56da7752dfb81d46122a7a61f9d4dcfe09e83ff6
-size 663744
+oid sha256:4baea3f2c5efe95a45a4beaeabc072213ac307b409112682f497e6d5c3de7786
+size 663828
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 ceeb0e3e5502..665c66767fdc 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:fcd24ee6a264ffb8cb4e2310d27ef5cc5c69229c36120eb3823b9bf53c62fcd4
-size 3740834
+oid sha256:dd9b2ca18ddf82a57e8de938e15e5e41d20d2a25c0d6cbae9b6d499188c49834
+size 3740590
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 e1f70d7b74ad..abc0c4dfc75a 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:b8f494e59fee68ad6792428dd6305e527effb5a56e7e0af602769d59d2f35529
-size 638701
+oid sha256:7303f5d145eb9a2345f588d53b74810511a8b806a144b60ab76896ac7973de55
+size 638726
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 ce4a1eda1f8a..729c5a25efde 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:6b132e372cfd042fc6468b7cd2dda20aecec3fa14989a31e1a7312ab6c6bc99c
-size 3020351
+oid sha256:36e4819862dffc6e86dd581c30faa75d862d35a6e918d9810265c2cf91e2c948
+size 3020254
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 8f8c35238b21..c77c5cf87791 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:f5aad425f26d377204067e0e74bd66f8b0ecfd1d0d61800d5000d311f58c4735
-size 848344
+oid sha256:d9e7475dfb81a579d97338a67e4640862127ec35fa1a019bf0f8e9f34d0bceb3
+size 848253
diff --git a/lib/search/indexes/github-docs-dotcom-cn.json.br b/lib/search/indexes/github-docs-dotcom-cn.json.br
index 59f92717cf4e..8b249cf295c5 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:e1764b5df0d0cfcda01bfd36b1d9fc68e5798e6bb6dbdaf55c4c923223117946
-size 2091647
+oid sha256:06dbbcf4a5c3dec786e9041081792c84b2172c02878c824eca170f852cbdd4f6
+size 2092844
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 c8d0347e26df..3bf307793983 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:d82df8e3c717aee07cbf1cae420aa10d01793cfa579afbe91a30e523eac583cc
-size 1326610
+oid sha256:8dc367f5434049367d97bcb0cfbf213b9db514e239c57793c314a36980bffd6f
+size 1326748
diff --git a/lib/search/indexes/github-docs-dotcom-en.json.br b/lib/search/indexes/github-docs-dotcom-en.json.br
index ac0b58e54305..88f21752c94b 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:956a4248a382cd62ad4eb1b24942f1a5eb5319fb96e4036d9e1ca439fc101362
-size 5067291
+oid sha256:9d812fb255b0362510b62107795545c2dde5e84c7e5eb052a0c836af61c10174
+size 5068641
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 036d05d2b651..d3fad9ae09a0 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:2437a8ff253785ed964f22de57151c7208ac5568bb5ebf1f6ed449fce3c63949
-size 794673
+oid sha256:352df21845169e570a4984f1c7a0382fcde9e693404ba200582a12683fbec734
+size 794943
diff --git a/lib/search/indexes/github-docs-dotcom-es.json.br b/lib/search/indexes/github-docs-dotcom-es.json.br
index a67ca59ac4a1..309778ced570 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:74774a66ae548cea5ed39de5aaee46c82d2c82e9b51e3c4cb2f6f908b250e5d4
-size 3497052
+oid sha256:4a0338dba5177e7a58e08ba7b71aa3735d6736436a848f627c03de4b25b74e95
+size 3497791
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 91162fd46c76..59c0080dfd51 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:799c0915c8e18146ea4b8a76fa87e9fafc478b271ddad2f2c87c0a56cf114aba
-size 855925
+oid sha256:82020f873e8976b3aae3c8eb1b505a49c7ea13b9d7cf5e0e64e7ef2bc6abb7af
+size 856227
diff --git a/lib/search/indexes/github-docs-dotcom-ja.json.br b/lib/search/indexes/github-docs-dotcom-ja.json.br
index 2b9a6a107572..a83c210797eb 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:72a0e297c5437ba526a637c1f1e85f266cb486361a6c47964db6521ad67e6ee6
-size 4557536
+oid sha256:ebd12b18b97fa2f7a958a586a855982b9e73a8468822c680362073cdd89cf9ca
+size 4558863
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 d164a323490c..2006332c53a7 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:5eae8653c7c4c6804d4afda50a37b0896cc25aaca959c587613263ec58e563b7
-size 810193
+oid sha256:1f1c72236d1273dd9b346f5338e268f7899a669039fd415417110d1a8d22a7a8
+size 810484
diff --git a/lib/search/indexes/github-docs-dotcom-pt.json.br b/lib/search/indexes/github-docs-dotcom-pt.json.br
index 0b26b2f4a7a9..6cec67159f53 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:0545c767ddc7de6012ead4bc2be66d9d30d18d5d217f63c12f1e8d0acb365bc0
-size 3612825
+oid sha256:1ff0de8298232bd014dbeee4bdbbeb6af2799ab8f5bf468580ad3f65898960ab
+size 3612380
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 05fc4368254e..3c1400e2f9ff 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:be4c170b5a6af0b7a592009553aade6e2c79b612ce65e014837637c5a8706792
-size 512992
+oid sha256:935e7fe5dd5a832b08f7b958e605b46c8e6bf8ab94080837bcd359ed712dcda4
+size 512959
diff --git a/lib/search/indexes/github-docs-ghae-cn.json.br b/lib/search/indexes/github-docs-ghae-cn.json.br
index df04d3fdc8ff..7ce53f10afd3 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:7b541df104ae9b0f7d2ee08fa1212bbce783fa57e878e1b561fa3936f1a8ec03
-size 1415896
+oid sha256:a889f8edd9516368260143d00a6612815992639ceb77f941a1e6d0a3902904d3
+size 1415967
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 4a2324465326..26f1fbe03fe5 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:b047be7232f2e0f9497f83a7cbe3ee64ad8a1cdd89da3ab88f575bba0b24d51a
-size 832771
+oid sha256:2e74b26f66295a82254881d32fdb93aef6a49600b40b650953f64776236e083d
+size 832393
diff --git a/lib/search/indexes/github-docs-ghae-en.json.br b/lib/search/indexes/github-docs-ghae-en.json.br
index c1c5acfb1d95..43890f89f6ee 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:27802a6e4483d260f7b0b17d82f3e28dda5696bc0c76ad4689d258cab6e3c388
-size 3342188
+oid sha256:1e5d72abd22e1faa11d64ea863e593416d8d5cca43c6a01faca75eccf7b59b07
+size 3342331
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 431a45ac1c29..dce1b54e77e2 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:6c881b94556fff7f76f993eb5e87f82a1975a4ee441dfcb8e4a128c8d46222a6
-size 486858
+oid sha256:06ed387367a34bf0ac6732a053a90ba1b4dd65a318f3bc514d1dc07105eae0f6
+size 486868
diff --git a/lib/search/indexes/github-docs-ghae-es.json.br b/lib/search/indexes/github-docs-ghae-es.json.br
index 0f5df2a5b081..32444811b436 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:e8d191b409a4b526e9a340812d94c2760ee5f6533981924da7d7a76595404839
-size 2189618
+oid sha256:be693ad02a3e6055b96f4716a4876c448566d42e39dc391cb8f6c49af6a2f0db
+size 2189320
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 c744a1112527..2813a8fdc262 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:27133b203cac6c9f0c2603e1510a9e3973bb08c0f92aea0719af40977751b577
-size 516912
+oid sha256:60ecc11b3dff7542a5b59209caad7da94786d3fcf29cd884007a3014f56fdd33
+size 517000
diff --git a/lib/search/indexes/github-docs-ghae-ja.json.br b/lib/search/indexes/github-docs-ghae-ja.json.br
index 0824335f86f4..0d501f76fc53 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:0f7ffe6e22241efb4c42970bc592737eb93c13e00347d9c514e38c621fdb4383
-size 2803070
+oid sha256:40b6921dfc60a5d1814d6b22791b4e8534ed09833f21559cdd9c772b813b3239
+size 2803053
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 d00265618e5e..08600ab43cf8 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:4bb35efb41d1ed3031787a34a71043c20952de479486f9db56280938285da47e
-size 500334
+oid sha256:d7d45f1970f8dfbc7e754f9fb275ed709e1ec33340e73facb1982fbc5ef714ab
+size 500587
diff --git a/lib/search/indexes/github-docs-ghae-pt.json.br b/lib/search/indexes/github-docs-ghae-pt.json.br
index bec38af272e7..7da208d33b76 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:201b44e4b08dc6b50201b01b86e18ee1e372526571be76b69a5f8335ef06e215
-size 2289882
+oid sha256:4cb6292eb502eda6ea5129bb6c500d8395db9943973f372bc37a39318975ba90
+size 2289406
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 bc1fa23ffbf9..89a7fc991083 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:9f543ae89dc7e518c4eab94afb98ae9b1f255a0f91ec65f05c144afed3039401
-size 772123
+oid sha256:c8fbb7c18528c8c48a3839d7e5ef6a0f58465d38315c09ab37a383bc258095ba
+size 772083
diff --git a/lib/search/indexes/github-docs-ghec-cn.json.br b/lib/search/indexes/github-docs-ghec-cn.json.br
index f0e890762dc9..2dd59f4bd449 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:a0b2dd2cce8aec8897f2e83dbfcab8589f25f90138e5abf260efd71da099a31a
-size 2109848
+oid sha256:d6dc7c1f9dfb5ab444ee7b5a6bcd02a67d387ea94c056126b0453495dd72eed7
+size 2110242
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 7886ab8690f5..9570eb852c8e 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:206979b7dd19b72899bbe6facc1e8526c8bc36ce1665abc4e6deb832cd8d0487
-size 1190150
+oid sha256:215b20836338b0188f9a8391fc63f521f34751986a64d625b105f3d1a119b637
+size 1185520
diff --git a/lib/search/indexes/github-docs-ghec-en.json.br b/lib/search/indexes/github-docs-ghec-en.json.br
index e6a93911c199..ceafda27f180 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:3f105adb6e7e510e4b2d65daa02d313d0e4f520e04a65008a8d75bd35f1f4703
-size 4804756
+oid sha256:2716fc97fa306eda3a9c71cc3a8b1b8b4038f1e41042f3c39295a8c7667e6c07
+size 4805586
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 347256ea380a..5a3ac742b323 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:9bf3a8dcb74256489a090cdf09af86c1497c5240fcf0acdffb8ce54f5fdb1b11
-size 739530
+oid sha256:de70beddfe25424e82c8e765b3658c6af33082da83e04e210dbd0d7bd2e329a1
+size 739613
diff --git a/lib/search/indexes/github-docs-ghec-es.json.br b/lib/search/indexes/github-docs-ghec-es.json.br
index 08ce61b7b28c..51ebb1ac94e3 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:cb4ee2c689ef5912330f1e5946d7cae091a81b4971b619d7ca73d0246b22d691
-size 3441309
+oid sha256:812e2c920c3c5ed6c657eee841dfb79acc32d980cd39a70abe659ccb423b2376
+size 3440814
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 fb86bbe1081c..45cf2c78a01f 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:93d3784d9097109935cdc898b0c5029a0f4620110b5f5350e84cf646b2bde50a
-size 782643
+oid sha256:2c73145ce9a5874b0c8c9653e211771958d1dc9be753971940dfb6da77cdec83
+size 782756
diff --git a/lib/search/indexes/github-docs-ghec-ja.json.br b/lib/search/indexes/github-docs-ghec-ja.json.br
index e97886c5e4ad..88a118b74678 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:4ac417ed51018c052402a069028caed421161885c16b5ed4625bd8b44f02ef62
-size 4396075
+oid sha256:c55feeadca1dd358775b5ba1a060de709cb897e7cec78de966616c172e1fbbb9
+size 4396759
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 0b32d5c7308b..0112378da6ff 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:a666f59df1239968a312569aea214edecfbf7bd6bdf687fbc1b673a070b56263
-size 755905
+oid sha256:b3d0de3fc6d9addd5633852b8211913f82764037a761f9b375cc0126e0df84c5
+size 755754
diff --git a/lib/search/indexes/github-docs-ghec-pt.json.br b/lib/search/indexes/github-docs-ghec-pt.json.br
index 53640b0e9ad2..40360b529c47 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:c589a660781677249029b61c3fb9bd70748a83220529e149258450447c5a6876
-size 3550430
+oid sha256:24a124e9357f9b2e715c24dd70b3057b267761ffccd365ad1fc8491e102e4861
+size 3550257