diff --git a/assets/images/help/security/suggest-improvements-to-advisory-on-github-com.png b/assets/images/help/security/suggest-improvements-to-advisory-on-github-com.png
index 300b105b7f..0f224af62c 100644
Binary files a/assets/images/help/security/suggest-improvements-to-advisory-on-github-com.png and b/assets/images/help/security/suggest-improvements-to-advisory-on-github-com.png differ
diff --git a/components/context/MainContext.tsx b/components/context/MainContext.tsx
index f14b0ac877..51a62d5560 100644
--- a/components/context/MainContext.tsx
+++ b/components/context/MainContext.tsx
@@ -3,7 +3,6 @@ import pick from 'lodash/pick'
 
 import type { BreadcrumbT } from 'components/page-header/Breadcrumbs'
 import type { FeatureFlags } from 'components/hooks/useFeatureFlags'
-import { ExcludesNull } from 'components/lib/ExcludesNull'
 
 export type ProductT = {
   external: boolean
@@ -27,14 +26,9 @@ type VersionItem = {
 }
 
 export type ProductTreeNode = {
-  page: {
-    hidden?: boolean
-    documentType: 'article' | 'mapTopic'
-    title: string
-    shortTitle: string
-  }
-  renderedShortTitle?: string
-  renderedFullTitle: string
+  documentType: 'article' | 'mapTopic'
+  title: string
+  shortTitle: string
   href: string
   childPages: Array<ProductTreeNode>
 }
@@ -178,9 +172,10 @@ export const getMainContext = async (req: any, res: any): Promise<MainContextT>
     enterpriseServerVersions: req.context.enterpriseServerVersions,
     allVersions: req.context.allVersions,
     currentVersion: req.context.currentVersion,
-    currentProductTree: req.context.currentProductTree
-      ? getCurrentProductTree(req.context.currentProductTree)
-      : null,
+    // This is a slimmed down version of `req.context.currentProductTree`
+    // that only has the minimal titles stuff needed for sidebars and
+    // any page that is hidden is omitted.
+    currentProductTree: req.context.currentProductTreeTitlesExcludeHidden || null,
     featureFlags: {},
     searchVersions: req.context.searchVersions,
     nonEnterpriseDefaultVersion: req.context.nonEnterpriseDefaultVersion,
@@ -189,26 +184,6 @@ export const getMainContext = async (req: any, res: any): Promise<MainContextT>
   }
 }
 
-// only pull things we need from the product tree, and make sure there are default values instead of `undefined`
-const getCurrentProductTree = (input: any): ProductTreeNode | null => {
-  if (input.page.hidden) {
-    return null
-  }
-
-  return {
-    href: input.href,
-    renderedShortTitle: input.renderedShortTitle || '',
-    renderedFullTitle: input.renderedFullTitle || '',
-    page: {
-      hidden: input.page.hidden || false,
-      documentType: input.page.documentType,
-      title: input.page.title,
-      shortTitle: input.page.shortTitle || '',
-    },
-    childPages: (input.childPages || []).map(getCurrentProductTree).filter(ExcludesNull),
-  }
-}
-
 export const MainContext = createContext<MainContextT | null>(null)
 
 export const useMainContext = (): MainContextT => {
diff --git a/components/context/ProductLandingContext.tsx b/components/context/ProductLandingContext.tsx
index 72b045f7a5..9e1108fbf8 100644
--- a/components/context/ProductLandingContext.tsx
+++ b/components/context/ProductLandingContext.tsx
@@ -110,7 +110,7 @@ export const getProductLandingContextFromRequest = async (
     hasGuidesPage,
     product: {
       href: productTree.href,
-      title: productTree.renderedShortTitle || productTree.renderedFullTitle,
+      title: productTree.page.shortTitle || productTree.page.title,
     },
     whatsNewChangelog: req.context.whatsNewChangelog || [],
     changelogUrl: req.context.changelogUrl || [],
diff --git a/components/landing/ProductArticlesList.tsx b/components/landing/ProductArticlesList.tsx
index f1bb878ac9..98856e798a 100644
--- a/components/landing/ProductArticlesList.tsx
+++ b/components/landing/ProductArticlesList.tsx
@@ -19,7 +19,7 @@ export const ProductArticlesList = () => {
   return (
     <div className="d-flex gutter flex-wrap" data-testid="product-articles-list">
       {currentProductTree.childPages.map((treeNode, i) => {
-        if (treeNode.page.documentType === 'article') {
+        if (treeNode.documentType === 'article') {
           return null
         }
 
@@ -36,7 +36,7 @@ const ProductTreeNodeList = ({ treeNode }: { treeNode: ProductTreeNode }) => {
     <div className="col-12 col-lg-4 mb-6 height-full">
       <h3 className="mb-3 f4">
         <Link className="color-unset text-underline" href={treeNode.href}>
-          {treeNode.renderedFullTitle}
+          {treeNode.title}
         </Link>
       </h3>
 
@@ -58,8 +58,8 @@ const ProductTreeNodeList = ({ treeNode }: { treeNode: ProductTreeNode }) => {
               }}
             >
               <Link className="d-block width-full" href={childNode.href}>
-                {childNode.renderedFullTitle}
-                {childNode.page.documentType === 'mapTopic' ? (
+                {childNode.title}
+                {childNode.documentType === 'mapTopic' ? (
                   <small className="color-fg-muted d-inline-block">
                     &nbsp;&bull; {childNode.childPages.length} articles
                   </small>
diff --git a/components/sidebar/ProductCollapsibleSection.tsx b/components/sidebar/ProductCollapsibleSection.tsx
index 3dcd36f068..0f6dad548f 100644
--- a/components/sidebar/ProductCollapsibleSection.tsx
+++ b/components/sidebar/ProductCollapsibleSection.tsx
@@ -29,7 +29,7 @@ export const ProductCollapsibleSection = (props: SectionProps) => {
 
   // The lowest level page link displayed in the tree
   const renderTerminalPageLink = (page: ProductTreeNode) => {
-    const title = page.renderedShortTitle || page.renderedFullTitle
+    const title = page.shortTitle || page.title
 
     const isCurrent = routePath === page.href
     return (
@@ -78,10 +78,10 @@ export const ProductCollapsibleSection = (props: SectionProps) => {
       {
         <>
           {/* <!-- some pages have nested child pages (formerly known as a mapTopic) --> */}
-          {page.childPages[0]?.page.documentType === 'mapTopic' ? (
+          {page.childPages[0]?.documentType === 'mapTopic' ? (
             <ul className="list-style-none position-relative">
               {page.childPages.map((childPage, i) => {
-                const childTitle = childPage.renderedShortTitle || childPage.renderedFullTitle
+                const childTitle = childPage.shortTitle || childPage.title
 
                 const isActive = routePath.includes(childPage.href)
                 const isCurrent = routePath === childPage.href
@@ -108,7 +108,7 @@ export const ProductCollapsibleSection = (props: SectionProps) => {
                 )
               })}
             </ul>
-          ) : page.childPages[0]?.page.documentType === 'article' ? (
+          ) : page.childPages[0]?.documentType === 'article' ? (
             <div data-testid="sidebar-article-group" className="pb-0">
               <ActionList variant="full" className="my-2">
                 {page.childPages.map(renderTerminalPageLink)}
diff --git a/components/sidebar/RestCollapsibleSection.tsx b/components/sidebar/RestCollapsibleSection.tsx
index db9d62ab5d..40dc522b7d 100644
--- a/components/sidebar/RestCollapsibleSection.tsx
+++ b/components/sidebar/RestCollapsibleSection.tsx
@@ -181,7 +181,7 @@ export const RestCollapsibleSection = (props: SectionProps) => {
               </div>
             ) : (
               page.childPages.map((childPage, i) => {
-                const childTitle = childPage.renderedShortTitle || childPage.renderedFullTitle
+                const childTitle = childPage.shortTitle || childPage.title
                 const isActive = routePath.includes(childPage.href)
                 const isCurrent = routePath === childPage.href
 
diff --git a/components/sidebar/SidebarProduct.tsx b/components/sidebar/SidebarProduct.tsx
index 1c2eadeedb..0d82ee76c8 100644
--- a/components/sidebar/SidebarProduct.tsx
+++ b/components/sidebar/SidebarProduct.tsx
@@ -36,16 +36,16 @@ export const SidebarProduct = () => {
     routePath.includes(href)
   )
 
-  const productTitle = currentProductTree.renderedShortTitle || currentProductTree.renderedFullTitle
+  const productTitle = currentProductTree.shortTitle || currentProductTree.title
 
   const productSection = () => (
     <li className="my-3" data-testid="product-sidebar-items">
       <ul className="list-style-none">
         {currentProductTree &&
           currentProductTree.childPages.map((childPage, i) => {
-            const isStandaloneCategory = childPage.page.documentType === 'article'
+            const isStandaloneCategory = childPage.documentType === 'article'
 
-            const childTitle = childPage.renderedShortTitle || childPage.renderedFullTitle
+            const childTitle = childPage.shortTitle || childPage.title
             const isActive =
               routePath.includes(childPage.href + '/') || routePath === childPage.href
             const defaultOpen = hasExactCategory ? isActive : false
@@ -96,8 +96,8 @@ export const SidebarProduct = () => {
         <li className="my-3">
           <ul className="list-style-none">
             {conceptualPages.map((childPage, i) => {
-              const isStandaloneCategory = childPage.page.documentType === 'article'
-              const childTitle = childPage.renderedShortTitle || childPage.renderedFullTitle
+              const isStandaloneCategory = childPage.documentType === 'article'
+              const childTitle = childPage.shortTitle || childPage.title
               const isActive =
                 routePath.includes(childPage.href + '/') || routePath === childPage.href
               const defaultOpen = hasExactCategory ? isActive : false
@@ -145,9 +145,8 @@ export const SidebarProduct = () => {
         <li className="my-3">
           <ul className="list-style-none">
             {restPages.map((childPage, i) => {
-              const isStandaloneCategory = childPage.page.documentType === 'article'
-
-              const childTitle = childPage.renderedShortTitle || childPage.renderedFullTitle
+              const isStandaloneCategory = childPage.documentType === 'article'
+              const childTitle = childPage.shortTitle || childPage.title
               const isActive =
                 routePath.includes(childPage.href + '/') || routePath === childPage.href
               const defaultOpen = hasExactCategory ? isActive : false
@@ -178,19 +177,15 @@ export const SidebarProduct = () => {
     <ul data-testid="sidebar" className={styles.container}>
       <AllProductsLink />
 
-      {!currentProductTree.page.hidden && (
-        <>
-          <li data-testid="sidebar-product" title={productTitle} className="my-2">
-            <Link
-              href={currentProductTree.href}
-              className="pl-4 pr-5 pb-1 f4 color-fg-default no-underline"
-            >
-              {productTitle}
-            </Link>
-          </li>
-          {currentProduct && currentProduct.id === 'rest' ? restSection() : productSection()}
-        </>
-      )}
+      <li data-testid="sidebar-product" title={productTitle} className="my-2">
+        <Link
+          href={currentProductTree.href}
+          className="pl-4 pr-5 pb-1 f4 color-fg-default no-underline"
+        >
+          {productTitle}
+        </Link>
+      </li>
+      {currentProduct && currentProduct.id === 'rest' ? restSection() : productSection()}
     </ul>
   )
 }
diff --git a/content/README.md b/content/README.md
index 139e1802d4..dbd5c95100 100644
--- a/content/README.md
+++ b/content/README.md
@@ -326,14 +326,36 @@ When adding a new article, make sure the filename is a [kebab-cased](https://en.
 
 ## Whitespace control
 
-When using Liquid conditionals in lists or tables, you can use [whitespace control](https://shopify.github.io/liquid/basics/whitespace/) characters to prevent the addition of newlines that would break the list or table rendering.
+When using Liquid conditionals in lists or tables, you can use [whitespace control](https://shopify.github.io/liquid/basics/whitespace/) characters to prevent the addition of newlines and other whitespace that would break the list or table rendering.
 
-Just add a hyphen on either the left, right, or both sides to indicate that there should be no newline on that side. For example, this statement removes a newline on the left side:
+You can add a hyphen (`-`) on either the left, right, or both sides to indicate that there should be no newline or other whitespace on that side.
 
 ```
 {%- ifversion fpt %}
 ```
 
+For example, to version a table row, instead of adding liquid versioning for the row starting at the end of the previous row, like this:
+
+```
+Column A | Column B | Column C
+---------|----------|---------
+This row is for all versions | B1 | C1{% ifversion ghes %}
+This row is for GHES only | B2 | C2{% endif %}
+This row is for all versions | B3 | C3
+```
+
+You can include the liquid versioning on its own line and use whitespace control to strip the newline to the left of the liquid tag. This makes reading the source much easier, without breaking the rendering of the table:
+
+```
+Column A | Column B | Column C
+---------|----------|---------
+This row is for all versions | B1 | C1
+{%- ifversion ghes %}
+This row is for GHES only | B2 | C2
+{%- endif %}
+This row is for all versions | B3 | C3
+```
+
 ## Links
 
 Links to docs in the `docs-internal` repository must start with a product ID (like `/actions` or `/admin`) and contain the entire filepath, but not the file extension. For example, `/actions/creating-actions/about-custom-actions`.
diff --git a/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/permission-levels-for-a-personal-account-repository.md b/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/permission-levels-for-a-personal-account-repository.md
index 55099932d7..e113259b91 100644
--- a/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/permission-levels-for-a-personal-account-repository.md
+++ b/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/permission-levels-for-a-personal-account-repository.md
@@ -50,7 +50,7 @@ The repository owner has full control of the repository. In addition to the acti
 | Manage data use for a private repository | "[Managing data use settings for your private repository](/get-started/privacy-on-github/managing-data-use-settings-for-your-private-repository)"|{% endif %}
 | Define code owners for the repository | "[About code owners](/github/creating-cloning-and-archiving-repositories/about-code-owners)" |
 | Archive the repository | "[Archiving repositories](/repositories/archiving-a-github-repository/archiving-repositories)" |{% ifversion fpt or ghec %}
-| Create security advisories | "[About {% data variables.product.prodname_security_advisories %}](/github/managing-security-vulnerabilities/about-github-security-advisories)" |
+| Create security advisories | "[About repository security advisories](/github/managing-security-vulnerabilities/about-github-security-advisories)" |
 | Display a sponsor button | "[Displaying a sponsor button in your repository](/github/administering-a-repository/displaying-a-sponsor-button-in-your-repository)" |{% endif %}
 | Allow or disallow auto-merge for pull requests | "[Managing auto-merge for pull requests in your repository](/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository)" | 
 | Manage webhooks and deploy keys	| "[Managing deploy keys](/developers/overview/managing-deploy-keys#deploy-keys)" |
diff --git a/content/actions/creating-actions/setting-exit-codes-for-actions.md b/content/actions/creating-actions/setting-exit-codes-for-actions.md
index 0d23be239a..853617610f 100644
--- a/content/actions/creating-actions/setting-exit-codes-for-actions.md
+++ b/content/actions/creating-actions/setting-exit-codes-for-actions.md
@@ -21,7 +21,7 @@ type: how_to
 
 Exit status | Check run status | Description
 ------------|------------------|------------
-`0` | `success` | The action completed successfully and other tasks that depends on it can begin.
+`0` | `success` | The action completed successfully and other tasks that depend on it can begin.
 Nonzero value (any integer but 0)| `failure` | Any other exit code indicates the action failed. When an action fails, all concurrent actions are canceled and future actions are skipped. The check run and check suite both get a `failure` status.
 
 ## Setting a failure exit code in a JavaScript action
diff --git a/content/actions/security-guides/security-hardening-for-github-actions.md b/content/actions/security-guides/security-hardening-for-github-actions.md
index 5a18705739..fed4af9a0b 100644
--- a/content/actions/security-guides/security-hardening-for-github-actions.md
+++ b/content/actions/security-guides/security-hardening-for-github-actions.md
@@ -215,6 +215,12 @@ For more information on how to configure this setting, see {% ifversion allow-ac
 
 These sections consider some of the steps an attacker can take if they're able to run malicious commands on a {% data variables.product.prodname_actions %} runner.
 
+{% note %}
+
+**Note:** {% data variables.product.prodname_dotcom %}-hosted runners do not scan for malicious code downloaded by a user during their job, such as a compromised third party library.
+
+{% endnote %}
+
 ### Accessing secrets
 
 Workflows triggered using the `pull_request` event have read-only permissions and have no access to secrets. However, these permissions differ for various event triggers such as `issue_comment`, `issues` and `push`, where the attacker could attempt to steal repository secrets or use the write permission of the job's [`GITHUB_TOKEN`](/actions/reference/authentication-in-a-workflow#permissions-for-the-github_token).
diff --git a/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server.md b/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server.md
index 5b79fefc07..fd0656617f 100644
--- a/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server.md
+++ b/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server.md
@@ -77,9 +77,15 @@ Maximum concurrency was measured using multiple repositories, job duration of ap
 
 {%- endif %}
 
-{%- ifversion ghes = 3.6 %}
+{%- ifversion ghes > 3.5 %}
 
-{% data reusables.actions.hardware-requirements-3.6 %}
+
+| vCPUs | Memory | Maximum Connected Runners |
+| :---| :--- | :--- |
+| 8   | 64 GB  | 740  runners |
+| 32  | 160 GB | 2700 runners |
+| 96  | 384 GB | 7000 runners |
+| 128 | 512 GB | 7000 runners |
 
 {% data variables.product.company_short %} measured maximum connected runners using multiple repositories, job duration of approximately 10 minutes, and 10 MB artifact uploads. You may experience different performance depending on the overall levels of activity on your instance.
 
diff --git a/content/code-security/dependabot/dependabot-alerts/editing-security-advisories-in-the-github-advisory-database.md b/content/code-security/dependabot/dependabot-alerts/editing-security-advisories-in-the-github-advisory-database.md
deleted file mode 100644
index bc319ee063..0000000000
--- a/content/code-security/dependabot/dependabot-alerts/editing-security-advisories-in-the-github-advisory-database.md
+++ /dev/null
@@ -1,55 +0,0 @@
----
-title: Editing security advisories in the GitHub Advisory Database
-intro: 'You can submit improvements to any advisory published in the {% data variables.product.prodname_advisory_database %}.'
-redirect_from:
-  - /code-security/security-advisories/editing-security-advisories-in-the-github-advisory-database
-  - /code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/editing-security-advisories-in-the-github-advisory-database
-versions:
-  fpt: '*'
-  ghec: '*'
-  ghes: '*'
-  ghae: '*'
-type: how_to
-topics:
-  - Security advisories
-  - Alerts
-  - Dependabot
-  - Vulnerabilities
-  - CVEs
-shortTitle: Edit Advisory Database
----
-
-## About editing advisories in the {% data variables.product.prodname_advisory_database %}
-Security advisories in the {% data variables.product.prodname_advisory_database %} at [github.com/advisories](https://github.com/advisories) are considered global advisories. Anyone can suggest improvements on any global security advisory in the {% data variables.product.prodname_advisory_database %}. You can edit or add any detail, including additionally affected ecosystems, severity level or description of who is impacted. The {% data variables.product.prodname_security %} curation team will review the submitted improvements and publish them onto the {% data variables.product.prodname_advisory_database %} if accepted.
-{% ifversion fpt or ghec %}
-Only repository owners and administrators can edit repository-level security advisories. For more information, see "[Editing a repository security advisory](/code-security/security-advisories/editing-a-security-advisory)."{% endif %}
-
-## Editing advisories in the GitHub Advisory Database
-
-1. Navigate to https://github.com/advisories.
-1. Select the security advisory you would like to contribute to.
-1. On the right-hand side of the page, click the **Suggest improvements for this vulnerability** link.
-   
-   ![Screenshot of the suggest improvements link](/assets/images/help/security/suggest-improvements-to-advisory.png)
-
-1. In the "Improve security advisory" form, make the desired improvements. You can edit or add any detail.{% ifversion fpt or ghec %} For information about correctly specifying information on the form, including affected versions, see "[Best practices for writing repository security advisories](/code-security/repository-security-advisories/best-practices-for-writing-repository-security-advisories)."{% endif %}{% ifversion security-advisories-reason-for-change %}
-1. Under **Reason for change**, explain why you want to make this improvement. If you include links to supporting material this will help our reviewers.
-   
-   ![Screenshot of the reason for change field](/assets/images/help/security/security-advisories-suggest-improvement-reason.png){% endif %}
-
-1. When you finish editing the advisory, click **Submit improvements**.
-1. Once you submit your improvements, a pull request containing your changes will be created for review in [github/advisory-database](https://github.com/github/advisory-database) by the {% data variables.product.prodname_security %} curation team. If the advisory originated from a {% data variables.product.prodname_dotcom %} repository, we will also tag the original publisher for optional commentary. You can view the pull request and get notifications when it is updated or closed.
-
-You can also open a pull request directly on an advisory file in the [github/advisory-database](https://github.com/github/advisory-database) repository. For more information, see the [contribution guidelines](https://github.com/github/advisory-database/blob/main/CONTRIBUTING.md). 
-
-{% ifversion security-advisories-ghes-ghae %}
-## Editing advisories from {% data variables.location.product_location %}
-
-If you have {% data variables.product.prodname_github_connect %} enabled for {% data variables.location.product_location %}, you will be able to see advisories by adding `/advisories` to the instance url. 
-
-1. Navigate to `https://HOSTNAME/advisories`.
-2. Select the security advisory you would like to contribute to.
-3. On the right-hand side of the page, click the **Suggest improvements for this vulnerability on {% data variables.product.prodname_dotcom_the_website %}.** link. A new tab opens with the same security advisory on {% data variables.product.prodname_dotcom_the_website %}.
-![Suggest improvements link](/assets/images/help/security/suggest-improvements-to-advisory-on-github-com.png)
-4. Edit the advisory, following steps four through six in "[Editing advisories in the GitHub Advisory Database](#editing-advisories-in-the-github-advisory-database)" above.
-{% endif %}
diff --git a/content/code-security/dependabot/dependabot-alerts/index.md b/content/code-security/dependabot/dependabot-alerts/index.md
index cf21c428cc..d91deda0d1 100644
--- a/content/code-security/dependabot/dependabot-alerts/index.md
+++ b/content/code-security/dependabot/dependabot-alerts/index.md
@@ -15,8 +15,6 @@ topics:
   - Repositories
   - Dependencies
 children:
-  - /browsing-security-advisories-in-the-github-advisory-database
-  - /editing-security-advisories-in-the-github-advisory-database
   - /about-dependabot-alerts
   - /configuring-dependabot-alerts
   - /viewing-and-updating-dependabot-alerts
diff --git a/content/code-security/getting-started/adding-a-security-policy-to-your-repository.md b/content/code-security/getting-started/adding-a-security-policy-to-your-repository.md
index 5fa2c487be..9c14fe91d4 100644
--- a/content/code-security/getting-started/adding-a-security-policy-to-your-repository.md
+++ b/content/code-security/getting-started/adding-a-security-policy-to-your-repository.md
@@ -35,7 +35,7 @@ You can create a default security policy for your organization or personal accou
 {% endtip %}
 
 {% ifversion fpt or ghec %}
-After someone reports a security vulnerability in your project, you can use {% data variables.product.prodname_security_advisories %} to disclose, fix, and publish information about the vulnerability. For more information about the process of reporting and disclosing vulnerabilities in {% data variables.product.prodname_dotcom %}, see "[About coordinated disclosure of security vulnerabilities](/code-security/security-advisories/about-coordinated-disclosure-of-security-vulnerabilities#about-reporting-and-disclosing-vulnerabilities-in-projects-on-github)." For more information about {% data variables.product.prodname_security_advisories %}, see "[About {% data variables.product.prodname_security_advisories %}](/github/managing-security-vulnerabilities/about-github-security-advisories)."
+After someone reports a security vulnerability in your project, you can use {% data variables.product.prodname_security_advisories %} to disclose, fix, and publish information about the vulnerability. For more information about the process of reporting and disclosing vulnerabilities in {% data variables.product.prodname_dotcom %}, see "[About coordinated disclosure of security vulnerabilities](/code-security/security-advisories/about-coordinated-disclosure-of-security-vulnerabilities#about-reporting-and-disclosing-vulnerabilities-in-projects-on-github)." For more information about repository security advisories, see "[About repository security advisories](/github/managing-security-vulnerabilities/about-github-security-advisories)."
 
 {% data reusables.repositories.github-security-lab %}
 {% endif %}
diff --git a/content/code-security/getting-started/github-security-features.md b/content/code-security/getting-started/github-security-features.md
index fe09160461..081272149c 100644
--- a/content/code-security/getting-started/github-security-features.md
+++ b/content/code-security/getting-started/github-security-features.md
@@ -28,7 +28,7 @@ Make it easy for your users to confidentially report security vulnerabilities th
 {% ifversion fpt or ghec %}
 ### Security advisories
 
-Privately discuss and fix security vulnerabilities in your repository's code. You can then publish a security advisory to alert your community to the vulnerability and encourage community members to upgrade. For more information, see "[About {% data variables.product.prodname_security_advisories %}](/github/managing-security-vulnerabilities/about-github-security-advisories)."
+Privately discuss and fix security vulnerabilities in your repository's code. You can then publish a security advisory to alert your community to the vulnerability and encourage community members to upgrade. For more information, see "[About repository security advisories](/github/managing-security-vulnerabilities/about-github-security-advisories)."
 
 {% endif %}
 {% ifversion fpt or ghec or ghes %}
diff --git a/content/code-security/getting-started/securing-your-organization.md b/content/code-security/getting-started/securing-your-organization.md
index f30c86cc01..63cff8ac9b 100644
--- a/content/code-security/getting-started/securing-your-organization.md
+++ b/content/code-security/getting-started/securing-your-organization.md
@@ -125,7 +125,7 @@ For more information, see "[Managing security and analysis settings for your org
 ## 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 {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts),"{% endif %} {% ifversion fpt or ghec or ghes %}"[Managing pull requests for dependency updates](/code-security/supply-chain-security/managing-pull-requests-for-dependency-updates)," {% endif %}"[Managing {% data variables.product.prodname_code_scanning %} for your repository](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository)," and "[Managing alerts from {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/managing-alerts-from-secret-scanning)."
 
-{% ifversion fpt or ghec %}If you have a security vulnerability, you can create a security advisory to privately discuss and fix the vulnerability. For more information, see "[About {% data variables.product.prodname_security_advisories %}](/code-security/security-advisories/about-github-security-advisories)" and "[Creating a security advisory](/code-security/security-advisories/creating-a-security-advisory)."
+{% 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 repository security advisories](/code-security/security-advisories/about-github-security-advisories)" and "[Creating a security advisory](/code-security/security-advisories/creating-a-security-advisory)."
 {% endif %}
 
 {% ifversion ghes or ghec or ghae %}You{% elsif fpt %}Organizations that use {% data variables.product.prodname_ghe_cloud %}{% endif %} can view, filter, and sort security alerts for repositories owned by {% ifversion ghes or ghec or ghae %}your{% elsif fpt %}their{% endif %} organization in the security overview. For more information, see{% ifversion ghes or ghec or ghae %} "[About the security overview](/code-security/security-overview/about-the-security-overview)."{% elsif fpt %} "[About the security overview](/enterprise-cloud@latest/code-security/security-overview/about-the-security-overview)" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% endif %}
diff --git a/content/code-security/getting-started/securing-your-repository.md b/content/code-security/getting-started/securing-your-repository.md
index 59b241eefe..3e84f7c163 100644
--- a/content/code-security/getting-started/securing-your-repository.md
+++ b/content/code-security/getting-started/securing-your-repository.md
@@ -133,5 +133,5 @@ You can set up {% data variables.product.prodname_code_scanning %} to automatica
 ## 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 {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts),"{% endif %} {% ifversion fpt or ghec or ghes %}"[Managing pull requests for dependency updates](/code-security/supply-chain-security/managing-pull-requests-for-dependency-updates)," {% endif %}"[Managing {% data variables.product.prodname_code_scanning %} for your repository](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository)," and "[Managing alerts from {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/managing-alerts-from-secret-scanning)."
 
-{% ifversion fpt or ghec %}If you have a security vulnerability, you can create a security advisory to privately discuss and fix the vulnerability. For more information, see "[About {% data variables.product.prodname_security_advisories %}](/code-security/security-advisories/about-github-security-advisories)" and "[Creating a security advisory](/code-security/security-advisories/creating-a-security-advisory)."
+{% 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 repository 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/content/code-security/index.md b/content/code-security/index.md
index 14748f9224..e9d02c2953 100644
--- a/content/code-security/index.md
+++ b/content/code-security/index.md
@@ -53,7 +53,7 @@ children:
   - /adopting-github-advanced-security-at-scale
   - /secret-scanning
   - /code-scanning
-  - /repository-security-advisories
+  - /security-advisories
   - /supply-chain-security
   - /dependabot
   - /security-overview
diff --git a/content/code-security/repository-security-advisories/about-coordinated-disclosure-of-security-vulnerabilities.md b/content/code-security/repository-security-advisories/about-coordinated-disclosure-of-security-vulnerabilities.md
deleted file mode 100644
index c3510d002a..0000000000
--- a/content/code-security/repository-security-advisories/about-coordinated-disclosure-of-security-vulnerabilities.md
+++ /dev/null
@@ -1,71 +0,0 @@
----
-title: About coordinated disclosure of security vulnerabilities
-intro: Vulnerability disclosure is a coordinated effort between security reporters and repository maintainers.
-redirect_from:
-  - /code-security/security-advisories/about-coordinated-disclosure-of-security-vulnerabilities
-miniTocMaxHeadingLevel: 3
-versions:
-  fpt: '*'
-  ghec: '*'
-type: overview
-topics:
-  - Security advisories
-  - Vulnerabilities
-shortTitle: Coordinated disclosure
----
-
-## About disclosing vulnerabilities in the industry
-
-{% data reusables.security-advisory.disclosing-vulnerabilities %}
-
-The initial report of a vulnerability is made privately, and the full details are only published once the maintainer has acknowledged the issue, and ideally made remediations or a patch available, sometimes with a delay to allow more time for the patches to be installed. For more information, see the "[OWASP Cheat Sheet Series about vulnerability disclosure](https://cheatsheetseries.owasp.org/cheatsheets/Vulnerability_Disclosure_Cheat_Sheet.html#commercial-and-open-source-software)" on the OWASP Cheat Sheet Series website.
-
-### Best practices for vulnerability reporters
-
-It's good practice to report vulnerabilities privately to maintainers. When possible, as a vulnerability reporter, we recommend you avoid:
-- Disclosing the vulnerability publicly without giving maintainers a chance to remediate.
-- Bypassing the maintainers.
-- Disclosing the vulnerability before a fixed version of the code is available.
-- Expecting to be compensated for reporting an issue, where no public bounty program exists.
-
-It's acceptable for vulnerability reporters to disclose a vulnerability publicly after a period of time, if they have tried to contact the maintainers and not received a response, or contacted them and been asked to wait too long to disclose it. 
-
-We recommend vulnerability reporters clearly state the terms of their disclosure policy as part of their reporting process. Even if the vulnerability reporter does not adhere to a strict policy, it's a good idea to set clear expectations for maintainers in terms of timelines on intended vulnerability disclosures. For an example of disclosure policy, see the "[Security Lab's disclosure policy](https://securitylab.github.com/advisories#policy)" on the GitHub Security Lab website.
-
-### Best practices for maintainers
-
-As a maintainer, it's good practice to clearly indicate how and where you want to receive reports for vulnerabilities. If this information is not clearly available, vulnerability reporters don't know how to contact you, and may resort to extracting developer email addresses from git commit histories to try to find an appropriate security contact. This can lead to friction, lost reports, or the publication of unresolved reports.
-
-Maintainers should disclose vulnerabilities in a timely manner. If there is a security vulnerability in your repository, we recommend you:
-- Treat the vulnerability as a security issue rather than a simple bug, both in your response and your disclosure. For example, you'll need to explicitly mention that the issue is a security vulnerability in the release notes.
-- Acknowledge receipt of the vulnerability report as quickly as possible, even if no immediate resources are available for investigation. This sends the message that you are quick to respond and act, and it sets a positive tone for the rest of the interaction between you and the vulnerability reporter.
-- Involve the vulnerability reporter when you verify the impact and veracity of the report. It's likely the vulnerability reporter has already spent time considering the vulnerability in a variety of scenarios, some of which you may have not considered yourself.
-- Remediate the issue in a way that you see fit, taking any concerns and advice provided by the vulnerability reporter into careful consideration. Often the vulnerability reporter will have knowledge of certain corner cases and remediation bypasses that are easy to miss without a security research background.
-- Always acknowledge the vulnerability reporter when you credit the discovery.
-- Aim to publish a fix as soon as you can.
-- Ensure that you make the wider ecosystem aware of the issue and its remediation when you disclose the vulnerability. It is not uncommon to see cases where a recognized security issue is fixed in the current development branch of a project, but the commit or subsequent release is not explicitly marked as a security fix or release. This can cause problems with downstream consumers.
-
-Publishing the details of a security vulnerability doesn't make maintainers look bad. Security vulnerabilities are present everywhere in software, and users will trust maintainers who have a clear and established process for disclosing security vulnerabilities in their code.
-
-## About reporting and disclosing vulnerabilities in projects on {% data variables.product.prodname_dotcom %}
-
-The process for reporting and disclosing vulnerabilities for projects on {% data variables.product.prodname_dotcom_the_website %} is as follows:
-
- If you are a vulnerability reporter (for example, a security researcher) who would like report a vulnerability, first check if there is a security policy for the related repository. For more information, see "[About security policies](/code-security/getting-started/adding-a-security-policy-to-your-repository#about-security-policies)." If there is one, follow it to understand the process before contacting the security team for that repository. 
- 
- If there isn't a security policy in place, the most efficient way to establish a private means of communication with maintainers is to create an issue asking for a preferred security contact. It's worth noting that the issue will be immediately publicly visible, so it should not include any information about the bug. Once communication is established, you can suggest the maintainers define a security policy for future use.
-
-{% note %}
-
-**Note**: _For npm only_ - If we receive a report of malware in an npm package, we try to contact you privately. If you don't address the issue in a timely manner, we will disclose it. For more information, see "[Reporting malware in an npm package](https://docs.npmjs.com/reporting-malware-in-an-npm-package)" on the npm Docs website.
-
-{% endnote %}
-
- If you've found a security vulnerability in {% data variables.product.prodname_dotcom_the_website %}, please report the vulnerability through our coordinated disclosure process. For more information, see the [{% data variables.product.prodname_dotcom %} Security Bug Bounty](https://bounty.github.com/) website.
-
- If you are a maintainer, you can take ownership of the process at the very beginning of the pipeline by setting up a security policy for your repository, or otherwise making security reporting instructions clearly available, for example in your project’s README file. For information about adding a security policy, see "[About security policies](/code-security/getting-started/adding-a-security-policy-to-your-repository#about-security-policies)." If there is no security policy, it's likely that a vulnerability reporter will try to email you or otherwise privately contact you. Alternatively, someone may open a (public) issue with details of a security issue.
-
- As a maintainer, to disclose a vulnerability in your code, you first create a draft security advisory in the package's repository in {% data variables.product.prodname_dotcom %}. {% data reusables.security-advisory.security-advisory-overview %} For more information, see "[About {% data variables.product.prodname_security_advisories %} for repositories](/code-security/repository-security-advisories/about-github-security-advisories-for-repositories)."
-
-
- To get started, see "[Creating a repository security advisory](/code-security/repository-security-advisories/creating-a-repository-security-advisory)."
diff --git a/content/code-security/security-advisories/global-security-advisories/about-global-security-advisories.md b/content/code-security/security-advisories/global-security-advisories/about-global-security-advisories.md
new file mode 100644
index 0000000000..cca585473b
--- /dev/null
+++ b/content/code-security/security-advisories/global-security-advisories/about-global-security-advisories.md
@@ -0,0 +1,33 @@
+---
+title: About global security advisories
+intro: 'Global security database live in the {% data variables.product.prodname_advisory_database %}, which contains CVEs and {% data variables.product.company_short %}-originated security advisories affecting the open source world. You can contribute to improving global advisories.'
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '*'
+  ghae: '*'
+type: overview
+topics:
+  - Security advisories
+  - Alerts
+  - Vulnerabilities
+  - CVEs
+---
+
+## About global security advisories
+
+{% ifversion fpt or ghec %}There are two types of advisories: global security advisories and repository security advisories. For more information about repository security advisories, see "[About repository security advisories](/code-security/security-advisories/repository-security-advisories/about-repository-security-advisories)."{% endif %}
+
+Global security advisories are grouped into two categories: {% data variables.product.company_short %}-reviewed advisories and unreviewed advisories.
+- {% data variables.product.company_short %}-reviewed advisories are security vulnerabilities{% ifversion GH-advisory-db-supports-malware %} or malware{% endif %} that have been mapped to packages in ecosystems we support.
+- Unreviewed advisories are security vulnerabilites that we publish automatically into the {% data variables.product.prodname_advisory_database %}, directly from the National Vulnerability Database feed. 
+
+For more information about the {% data variables.product.prodname_advisory_database %}, see "[About the {% data variables.product.prodname_advisory_database %}](/code-security/security-advisories/global-security-advisories/about-the-github-advisory-database)."
+
+{% data reusables.security-advisory.global-advisories %}
+
+Every repository advisory is reviewed by the {% data variables.product.prodname_security %} curation team for consideration as a global advisory. We publish security advisories for any of the ecosystems supported by the dependency graph to the {% data variables.product.prodname_advisory_database %} on [github.com/advisories](https://github.com/advisories).
+
+You can access any advisory in the {% data variables.product.prodname_advisory_database %}. For more information, see "[Browsing security advisories in the GitHub Advisory Database](/code-security/security-advisories/global-security-advisories/browsing-security-advisories-in-the-github-advisory-database)."
+
+You can suggest improvements to any advisory in the {% data variables.product.prodname_advisory_database %}. For more information, see "[Editing security advisories in the {% data variables.product.prodname_advisory_database %}](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/editing-security-advisories-in-the-github-advisory-database)."
\ No newline at end of file
diff --git a/content/code-security/security-advisories/global-security-advisories/about-the-github-advisory-database.md b/content/code-security/security-advisories/global-security-advisories/about-the-github-advisory-database.md
new file mode 100644
index 0000000000..0425ed2dec
--- /dev/null
+++ b/content/code-security/security-advisories/global-security-advisories/about-the-github-advisory-database.md
@@ -0,0 +1,82 @@
+---
+title: About the GitHub Advisory database
+intro: 'The {% data variables.product.prodname_advisory_database %} contains a list of known security vulnerabilities {% ifversion GH-advisory-db-supports-malware %}and malware, {% endif %}grouped in two categories: {% data variables.product.company_short %}-reviewed advisories and unreviewed advisories.'
+miniTocMaxHeadingLevel: 3
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '*'
+  ghae: '*'
+type: overview
+topics:
+  - Security advisories
+  - Alerts
+  - Vulnerabilities
+  - CVEs
+---
+
+## About the {% data variables.product.prodname_advisory_database %}
+
+{% data reusables.repositories.tracks-vulnerabilities %}
+
+## About types of security advisories
+
+{% data reusables.advisory-database.beta-malware-advisories %}
+
+Each advisory in the {% data variables.product.prodname_advisory_database %} is for a vulnerability in open source projects{% ifversion GH-advisory-db-supports-malware %} or for malicious open source software{% endif %}. 
+
+{% data reusables.repositories.a-vulnerability-is %} Vulnerabilities in code are usually introduced by accident and fixed soon after they are discovered. You should update your code to use the fixed version of the dependency as soon as it is available.
+
+{% ifversion GH-advisory-db-supports-malware %}
+
+In contrast, malicious software, or malware, is code that is intentionally designed to perform unwanted or harmful functions. The malware may target hardware, software, confidential data, or users of any application that uses the malware. You need to remove the malware from your project and find an alternative, more secure replacement for the dependency.
+
+{% endif %}
+
+### {% data variables.product.company_short %}-reviewed advisories
+
+{% data variables.product.company_short %}-reviewed advisories are security vulnerabilities{% ifversion GH-advisory-db-supports-malware %} or malware{% endif %} that have been mapped to packages in ecosystems we support. We carefully review each advisory for validity and ensure that they have a full description, and contain both ecosystem and package information.
+
+Generally, we name our supported ecosystems after the software programming language's associated package registry. We review advisories if they are for a vulnerability in a package that comes from a supported registry.
+
+- Composer (registry: https://packagist.org/){% ifversion GH-advisory-db-erlang-support %}
+- Erlang (registry: https://hex.pm/){% endif %}
+- Go (registry: https://pkg.go.dev/)
+{%- ifversion fpt or ghec or ghes > 3.6 or ghae > 3.6 %}
+- GitHub Actions (https://github.com/marketplace?type=actions/) {% endif %}
+- Maven (registry: https://repo.maven.apache.org/maven2)
+- npm (registry: https://www.npmjs.com/)
+- NuGet (registry: https://www.nuget.org/)
+- pip (registry: https://pypi.org/){% ifversion dependency-graph-dart-support %}
+- pub (registry: https://pub.dev/packages/registry){% endif %}
+- RubyGems (registry: https://rubygems.org/)
+- Rust (registry: https://crates.io/)
+
+If you have a suggestion for a new ecosystem we should support, please open an [issue](https://github.com/github/advisory-database/issues) for discussion.
+
+If you enable {% data variables.product.prodname_dependabot_alerts %} for your repositories, you are automatically notified when a new {% data variables.product.company_short %}-reviewed advisory reports a vulnerability {% ifversion GH-advisory-db-supports-malware %}or malware{% endif %} for a package you depend on. For more information, see "[About {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)."
+
+### Unreviewed advisories
+
+Unreviewed advisories are security vulnerabilites that we publish automatically into the {% data variables.product.prodname_advisory_database %}, directly from the National Vulnerability Database feed. 
+
+{% data variables.product.prodname_dependabot %} doesn't create {% data variables.product.prodname_dependabot_alerts %} for unreviewed advisories as this type of advisory isn't checked for validity or completion.
+
+## About information in security advisories
+
+Each security advisory contains information about the vulnerability{% ifversion GH-advisory-db-supports-malware %} or malware,{% endif %} which may include the description, severity, affected package, package ecosystem, affected versions and patched versions, impact, and optional information such as references, workarounds, and credits. In addition, advisories from the National Vulnerability Database list contain a link to the CVE record, where you can read more details about the vulnerability, its CVSS scores, and its qualitative severity level. For more information, see the "[National Vulnerability Database](https://nvd.nist.gov/)" from the National Institute of Standards and Technology.
+
+The severity level is one of four possible levels defined in the "[Common Vulnerability Scoring System (CVSS), Section 5](https://www.first.org/cvss/specification-document)."
+- Low
+- Medium/Moderate
+- High
+- Critical
+
+The {% data variables.product.prodname_advisory_database %} uses the CVSS levels described above. If {% data variables.product.company_short %} obtains a CVE, the {% data variables.product.prodname_advisory_database %} uses CVSS version 3.1. If the CVE is imported, the {% data variables.product.prodname_advisory_database %} supports both CVSS versions 3.0 and 3.1.
+
+{% data reusables.repositories.github-security-lab %}
+
+## Further reading
+
+- "[About {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)"
+- MITRE's [definition of "vulnerability"](https://www.cve.org/ResourcesSupport/Glossary#vulnerability)
\ No newline at end of file
diff --git a/content/code-security/dependabot/dependabot-alerts/browsing-security-advisories-in-the-github-advisory-database.md b/content/code-security/security-advisories/global-security-advisories/browsing-security-advisories-in-the-github-advisory-database.md
similarity index 66%
rename from content/code-security/dependabot/dependabot-alerts/browsing-security-advisories-in-the-github-advisory-database.md
rename to content/code-security/security-advisories/global-security-advisories/browsing-security-advisories-in-the-github-advisory-database.md
index 663dc63e1b..cd3211d934 100644
--- a/content/code-security/dependabot/dependabot-alerts/browsing-security-advisories-in-the-github-advisory-database.md
+++ b/content/code-security/security-advisories/global-security-advisories/browsing-security-advisories-in-the-github-advisory-database.md
@@ -8,6 +8,7 @@ redirect_from:
   - /code-security/supply-chain-security/browsing-security-vulnerabilities-in-the-github-advisory-database
   - /code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/browsing-security-vulnerabilities-in-the-github-advisory-database
   - /code-security/dependabot/dependabot-alerts/browsing-security-vulnerabilities-in-the-github-advisory-database
+  - /code-security/dependabot/dependabot-alerts/browsing-security-advisories-in-the-github-advisory-database
 versions:
   fpt: '*'
   ghec: '*'
@@ -23,71 +24,10 @@ topics:
 ---
 <!--Marketing-LINK: From /features/security/software-supply-chain page "Browsing security vulnerabilities in the GitHub Advisory Database".-->
 
-## About the {% data variables.product.prodname_advisory_database %}
-
-The {% data variables.product.prodname_advisory_database %} contains a list of known security vulnerabilities {% ifversion GH-advisory-db-supports-malware %}and malware, {% endif %}grouped in two categories: {% data variables.product.company_short %}-reviewed advisories and unreviewed advisories.
-
-{% data reusables.repositories.tracks-vulnerabilities %}
-
-## About types of security advisories
-
-{% data reusables.advisory-database.beta-malware-advisories %}
-
-Each advisory in the {% data variables.product.prodname_advisory_database %} is for a vulnerability in open source projects{% ifversion GH-advisory-db-supports-malware %} or for malicious open source software{% endif %}. 
-
-{% data reusables.repositories.a-vulnerability-is %} Vulnerabilities in code are usually introduced by accident and fixed soon after they are discovered. You should update your code to use the fixed version of the dependency as soon as it is available.
-
-{% ifversion GH-advisory-db-supports-malware %}
-
-In contrast, malicious software, or malware, is code that is intentionally designed to perform unwanted or harmful functions. The malware may target hardware, software, confidential data, or users of any application that uses the malware. You need to remove the malware from your project and find an alternative, more secure replacement for the dependency.
-
-{% endif %}
-
-### {% data variables.product.company_short %}-reviewed advisories
-
-{% data variables.product.company_short %}-reviewed advisories are security vulnerabilities{% ifversion GH-advisory-db-supports-malware %} or malware{% endif %} that have been mapped to packages in ecosystems we support. We carefully review each advisory for validity and ensure that they have a full description, and contain both ecosystem and package information.
-
-Generally, we name our supported ecosystems after the software programming language's associated package registry. We review advisories if they are for a vulnerability in a package that comes from a supported registry.
-
-- Composer (registry: https://packagist.org/){% ifversion GH-advisory-db-erlang-support %}
-- Erlang (registry: https://hex.pm/){% endif %}
-- Go (registry: https://pkg.go.dev/)
-{%- ifversion fpt or ghec or ghes > 3.6 or ghae > 3.6 %}
-- GitHub Actions (https://github.com/marketplace?type=actions/) {% endif %}
-- Maven (registry: https://repo.maven.apache.org/maven2)
-- npm (registry: https://www.npmjs.com/)
-- NuGet (registry: https://www.nuget.org/)
-- pip (registry: https://pypi.org/){% ifversion dependency-graph-dart-support %}
-- pub (registry: https://pub.dev/packages/registry){% endif %}
-- RubyGems (registry: https://rubygems.org/)
-- Rust (registry: https://crates.io/)
-
-If you have a suggestion for a new ecosystem we should support, please open an [issue](https://github.com/github/advisory-database/issues) for discussion.
-
-If you enable {% data variables.product.prodname_dependabot_alerts %} for your repositories, you are automatically notified when a new {% data variables.product.company_short %}-reviewed advisory reports a vulnerability {% ifversion GH-advisory-db-supports-malware %}or malware{% endif %} for a package you depend on. For more information, see "[About {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)."
-
-### Unreviewed advisories
-
-Unreviewed advisories are security vulnerabilites that we publish automatically into the {% data variables.product.prodname_advisory_database %}, directly from the National Vulnerability Database feed. 
-
-{% data variables.product.prodname_dependabot %} doesn't create {% data variables.product.prodname_dependabot_alerts %} for unreviewed advisories as this type of advisory isn't checked for validity or completion.
-
-## About information in security advisories
-
-Each security advisory contains information about the vulnerability{% ifversion GH-advisory-db-supports-malware %} or malware,{% endif %} which may include the description, severity, affected package, package ecosystem, affected versions and patched versions, impact, and optional information such as references, workarounds, and credits. In addition, advisories from the National Vulnerability Database list contain a link to the CVE record, where you can read more details about the vulnerability, its CVSS scores, and its qualitative severity level. For more information, see the "[National Vulnerability Database](https://nvd.nist.gov/)" from the National Institute of Standards and Technology.
-
-The severity level is one of four possible levels defined in the "[Common Vulnerability Scoring System (CVSS), Section 5](https://www.first.org/cvss/specification-document)."
-- Low
-- Medium/Moderate
-- High
-- Critical
-
-The {% data variables.product.prodname_advisory_database %} uses the CVSS levels described above. If {% data variables.product.company_short %} obtains a CVE, the {% data variables.product.prodname_advisory_database %} uses CVSS version 3.1. If the CVE is imported, the {% data variables.product.prodname_advisory_database %} supports both CVSS versions 3.0 and 3.1.
-
-{% data reusables.repositories.github-security-lab %}
-
 ## Accessing an advisory in the {% data variables.product.prodname_advisory_database %}
 
+You can access any advisory in the {% data variables.product.prodname_advisory_database %}.
+
 1. Navigate to https://github.com/advisories.
 2. Optionally, to filter the list, use any of the drop-down menus.
   ![Dropdown filters](/assets/images/help/security/advisory-database-dropdown-filters.png)
@@ -182,7 +122,3 @@ In the local advisory database, you can see which repositories are affected by e
 5. For more details about the advisory, and for advice on how to fix the vulnerable repository, click the repository name.
 
 {% endif %}
-
-## Further reading
-
-- MITRE's [definition of "vulnerability"](https://www.cve.org/ResourcesSupport/Glossary#vulnerability)
diff --git a/translations/pt-BR/content/code-security/dependabot/dependabot-alerts/editing-security-advisories-in-the-github-advisory-database.md b/content/code-security/security-advisories/global-security-advisories/editing-security-advisories-in-the-github-advisory-database.md
similarity index 80%
rename from translations/pt-BR/content/code-security/dependabot/dependabot-alerts/editing-security-advisories-in-the-github-advisory-database.md
rename to content/code-security/security-advisories/global-security-advisories/editing-security-advisories-in-the-github-advisory-database.md
index bc319ee063..158a22500c 100644
--- a/translations/pt-BR/content/code-security/dependabot/dependabot-alerts/editing-security-advisories-in-the-github-advisory-database.md
+++ b/content/code-security/security-advisories/global-security-advisories/editing-security-advisories-in-the-github-advisory-database.md
@@ -4,6 +4,7 @@ intro: 'You can submit improvements to any advisory published in the {% data var
 redirect_from:
   - /code-security/security-advisories/editing-security-advisories-in-the-github-advisory-database
   - /code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/editing-security-advisories-in-the-github-advisory-database
+  - /code-security/dependabot/dependabot-alerts/editing-security-advisories-in-the-github-advisory-database
 versions:
   fpt: '*'
   ghec: '*'
@@ -19,12 +20,14 @@ topics:
 shortTitle: Edit Advisory Database
 ---
 
-## About editing advisories in the {% data variables.product.prodname_advisory_database %}
-Security advisories in the {% data variables.product.prodname_advisory_database %} at [github.com/advisories](https://github.com/advisories) are considered global advisories. Anyone can suggest improvements on any global security advisory in the {% data variables.product.prodname_advisory_database %}. You can edit or add any detail, including additionally affected ecosystems, severity level or description of who is impacted. The {% data variables.product.prodname_security %} curation team will review the submitted improvements and publish them onto the {% data variables.product.prodname_advisory_database %} if accepted.
+## Editing advisories in the {% data variables.product.prodname_advisory_database %}
+
+The advisories in the {% data variables.product.prodname_advisory_database %} are global security advisories. For more information about global security advisories, see "[About global security advisories](/code-security/security-advisories/global-security-advisories/about-global-security-advisories)."
+
+Anyone can suggest improvements on any global security advisory in the {% data variables.product.prodname_advisory_database %}. You can edit or add any detail, including additionally affected ecosystems, severity level or description of who is impacted. The {% data variables.product.prodname_security %} curation team will review the submitted improvements and publish them onto the {% data variables.product.prodname_advisory_database %} if accepted.
 {% ifversion fpt or ghec %}
 Only repository owners and administrators can edit repository-level security advisories. For more information, see "[Editing a repository security advisory](/code-security/security-advisories/editing-a-security-advisory)."{% endif %}
 
-## Editing advisories in the GitHub Advisory Database
 
 1. Navigate to https://github.com/advisories.
 1. Select the security advisory you would like to contribute to.
diff --git a/content/code-security/security-advisories/global-security-advisories/index.md b/content/code-security/security-advisories/global-security-advisories/index.md
new file mode 100644
index 0000000000..ee3276091e
--- /dev/null
+++ b/content/code-security/security-advisories/global-security-advisories/index.md
@@ -0,0 +1,21 @@
+---
+title: Working with global security advisories from the GitHub Advisory Database
+shortTitle: Global security advisories
+intro: 'Browse the {% data variables.product.prodname_advisory_database %} and submit improvements to any global security advisory.'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Security advisories
+  - Vulnerabilities
+  - Repositories
+  - CVEs
+children:
+  - /about-the-github-advisory-database
+  - /about-global-security-advisories
+  - /browsing-security-advisories-in-the-github-advisory-database
+  - /editing-security-advisories-in-the-github-advisory-database
+---
+
diff --git a/content/code-security/repository-security-advisories/best-practices-for-writing-repository-security-advisories.md b/content/code-security/security-advisories/guidance-on-reporting-and-writing/best-practices-for-writing-repository-security-advisories.md
similarity index 95%
rename from content/code-security/repository-security-advisories/best-practices-for-writing-repository-security-advisories.md
rename to content/code-security/security-advisories/guidance-on-reporting-and-writing/best-practices-for-writing-repository-security-advisories.md
index b4f1b2e1a2..696dd213c3 100644
--- a/content/code-security/repository-security-advisories/best-practices-for-writing-repository-security-advisories.md
+++ b/content/code-security/security-advisories/guidance-on-reporting-and-writing/best-practices-for-writing-repository-security-advisories.md
@@ -10,6 +10,8 @@ topics:
   - Security advisories
   - Vulnerabilities
 shortTitle: Best practices
+redirect_from:
+  - /code-security/repository-security-advisories/best-practices-for-writing-repository-security-advisories
 ---
 
 Anyone with admin permissions to a repository can create and edit a security advisory.
@@ -18,7 +20,7 @@ Anyone with admin permissions to a repository can create and edit a security adv
 
 ## About security advisories for repositories
 
-{% data reusables.security-advisory.security-advisory-overview %} For more information, see "[About GitHub Security Advisories for repositories](/code-security/repository-security-advisories/about-github-security-advisories-for-repositories)."
+{% data reusables.security-advisory.security-advisory-overview %} For more information, see "[About repository security advisories](/code-security/repository-security-advisories/about-github-security-advisories-for-repositories)."
 
 ## Best practices
 
diff --git a/content/code-security/security-advisories/guidance-on-reporting-and-writing/index.md b/content/code-security/security-advisories/guidance-on-reporting-and-writing/index.md
new file mode 100644
index 0000000000..d2bdf74639
--- /dev/null
+++ b/content/code-security/security-advisories/guidance-on-reporting-and-writing/index.md
@@ -0,0 +1,16 @@
+---
+title: Guidance on reporting and writing information about vulnerabilities
+shortTitle: Guidance on reporting and writing
+intro: Best practices for writing security advisories and managing privately reported security vulnerabilities.
+versions:
+  fpt: '*'
+  ghec: '*'
+topics:
+  - Security advisories
+  - Vulnerabilities
+  - Repositories
+  - CVEs
+children:
+  - /best-practices-for-writing-repository-security-advisories
+---
+
diff --git a/content/code-security/security-advisories/index.md b/content/code-security/security-advisories/index.md
new file mode 100644
index 0000000000..c0bfc4deb6
--- /dev/null
+++ b/content/code-security/security-advisories/index.md
@@ -0,0 +1,19 @@
+---
+title: Working with security advisories
+shortTitle: Security advisories
+intro: 'Learn how to work with security advisories on {% data variables.product.prodname_dotcom %},{% ifversion fpt or ghec %} whether you want to contribute to an existing global advisory, or create a security advisory for a repository,{% endif %} improving collaboration between repository maintainers and security researchers.'
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '*'
+  ghae: '*'
+topics:
+  - Security advisories
+  - Vulnerabilities
+  - Repositories
+  - CVEs
+children:
+- /global-security-advisories
+- /repository-security-advisories
+- /guidance-on-reporting-and-writing
+---
\ No newline at end of file
diff --git a/translations/es-ES/content/code-security/repository-security-advisories/about-coordinated-disclosure-of-security-vulnerabilities.md b/content/code-security/security-advisories/repository-security-advisories/about-coordinated-disclosure-of-security-vulnerabilities.md
similarity index 96%
rename from translations/es-ES/content/code-security/repository-security-advisories/about-coordinated-disclosure-of-security-vulnerabilities.md
rename to content/code-security/security-advisories/repository-security-advisories/about-coordinated-disclosure-of-security-vulnerabilities.md
index c3510d002a..232bba53f6 100644
--- a/translations/es-ES/content/code-security/repository-security-advisories/about-coordinated-disclosure-of-security-vulnerabilities.md
+++ b/content/code-security/security-advisories/repository-security-advisories/about-coordinated-disclosure-of-security-vulnerabilities.md
@@ -3,6 +3,7 @@ title: About coordinated disclosure of security vulnerabilities
 intro: Vulnerability disclosure is a coordinated effort between security reporters and repository maintainers.
 redirect_from:
   - /code-security/security-advisories/about-coordinated-disclosure-of-security-vulnerabilities
+  - /code-security/repository-security-advisories/about-coordinated-disclosure-of-security-vulnerabilities
 miniTocMaxHeadingLevel: 3
 versions:
   fpt: '*'
@@ -65,7 +66,7 @@ The process for reporting and disclosing vulnerabilities for projects on {% data
 
  If you are a maintainer, you can take ownership of the process at the very beginning of the pipeline by setting up a security policy for your repository, or otherwise making security reporting instructions clearly available, for example in your project’s README file. For information about adding a security policy, see "[About security policies](/code-security/getting-started/adding-a-security-policy-to-your-repository#about-security-policies)." If there is no security policy, it's likely that a vulnerability reporter will try to email you or otherwise privately contact you. Alternatively, someone may open a (public) issue with details of a security issue.
 
- As a maintainer, to disclose a vulnerability in your code, you first create a draft security advisory in the package's repository in {% data variables.product.prodname_dotcom %}. {% data reusables.security-advisory.security-advisory-overview %} For more information, see "[About {% data variables.product.prodname_security_advisories %} for repositories](/code-security/repository-security-advisories/about-github-security-advisories-for-repositories)."
+ As a maintainer, to disclose a vulnerability in your code, you first create a draft security advisory in the package's repository in {% data variables.product.prodname_dotcom %}. {% data reusables.security-advisory.security-advisory-overview %} For more information, see "[About repository security advisories](/code-security/repository-security-advisories/about-github-security-advisories-for-repositories)."
 
 
  To get started, see "[Creating a repository security advisory](/code-security/repository-security-advisories/creating-a-repository-security-advisory)."
diff --git a/content/code-security/repository-security-advisories/about-github-security-advisories-for-repositories.md b/content/code-security/security-advisories/repository-security-advisories/about-repository-security-advisories.md
similarity index 90%
rename from content/code-security/repository-security-advisories/about-github-security-advisories-for-repositories.md
rename to content/code-security/security-advisories/repository-security-advisories/about-repository-security-advisories.md
index 87ca60fd0a..9fcdbeb87c 100644
--- a/content/code-security/repository-security-advisories/about-github-security-advisories-for-repositories.md
+++ b/content/code-security/security-advisories/repository-security-advisories/about-repository-security-advisories.md
@@ -1,11 +1,13 @@
 ---
-title: About GitHub Security Advisories for repositories
-intro: 'You can use {% data variables.product.prodname_security_advisories %} to privately discuss, fix, and publish information about security vulnerabilities in your repository.'
+title: About repository security advisories
+intro: 'You can use repository security advisories to privately discuss, fix, and publish information about security vulnerabilities in your repository.'
+shortTitle: About repository security advisories
 redirect_from:
   - /articles/about-maintainer-security-advisories
   - /github/managing-security-vulnerabilities/about-maintainer-security-advisories
   - /github/managing-security-vulnerabilities/about-github-security-advisories
   - /code-security/security-advisories/about-github-security-advisories
+  - /code-security/repository-security-advisories/about-github-security-advisories-for-repositories
 versions:
   fpt: '*'
   ghec: '*'
@@ -14,20 +16,19 @@ topics:
   - Security advisories
   - Vulnerabilities
   - CVEs
-shortTitle: Repository security advisories
 ---
 
 {% data reusables.repositories.security-advisory-admin-permissions %}
 
 {% data reusables.security-advisory.security-researcher-cannot-create-advisory %}
 
-## About {% data variables.product.prodname_security_advisories %}
+## About repository security advisories
 
 {% data reusables.security-advisory.disclosing-vulnerabilities %} For more information, see "[About coordinated disclosure of security vulnerabilities](/code-security/repository-security-advisories/about-coordinated-disclosure-of-security-vulnerabilities)."
 
 {% data reusables.security-advisory.security-advisory-overview %}
 
-With {% data variables.product.prodname_security_advisories %}, you can:
+With repository security advisories, you can:
 
 1. Create a draft security advisory, and use the draft to privately discuss the impact of the vulnerability on your project. For more information, see "[Creating a repository security advisory](/code-security/repository-security-advisories/creating-a-repository-security-advisory)."
 2. Privately collaborate to fix the vulnerability in a temporary private fork.
diff --git a/content/code-security/repository-security-advisories/adding-a-collaborator-to-a-repository-security-advisory.md b/content/code-security/security-advisories/repository-security-advisories/adding-a-collaborator-to-a-repository-security-advisory.md
similarity index 96%
rename from content/code-security/repository-security-advisories/adding-a-collaborator-to-a-repository-security-advisory.md
rename to content/code-security/security-advisories/repository-security-advisories/adding-a-collaborator-to-a-repository-security-advisory.md
index 44d712e625..258050a6cf 100644
--- a/content/code-security/repository-security-advisories/adding-a-collaborator-to-a-repository-security-advisory.md
+++ b/content/code-security/security-advisories/repository-security-advisories/adding-a-collaborator-to-a-repository-security-advisory.md
@@ -6,6 +6,7 @@ redirect_from:
   - /github/managing-security-vulnerabilities/adding-a-collaborator-to-a-maintainer-security-advisory
   - /github/managing-security-vulnerabilities/adding-a-collaborator-to-a-security-advisory
   - /code-security/security-advisories/adding-a-collaborator-to-a-security-advisory
+  - /code-security/repository-security-advisories/adding-a-collaborator-to-a-repository-security-advisory
 versions:
   fpt: '*'
   ghec: '*'
diff --git a/content/code-security/repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability.md b/content/code-security/security-advisories/repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability.md
similarity index 97%
rename from content/code-security/repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability.md
rename to content/code-security/security-advisories/repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability.md
index c2aed44197..fffd348b80 100644
--- a/content/code-security/repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability.md
+++ b/content/code-security/security-advisories/repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability.md
@@ -5,6 +5,7 @@ redirect_from:
   - /articles/collaborating-in-a-temporary-private-fork-to-resolve-a-security-vulnerability
   - /github/managing-security-vulnerabilities/collaborating-in-a-temporary-private-fork-to-resolve-a-security-vulnerability
   - /code-security/security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-security-vulnerability
+  - /code-security/repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability
 versions:
   fpt: '*'
   ghec: '*'
diff --git a/content/code-security/repository-security-advisories/creating-a-repository-security-advisory.md b/content/code-security/security-advisories/repository-security-advisories/creating-a-repository-security-advisory.md
similarity index 96%
rename from content/code-security/repository-security-advisories/creating-a-repository-security-advisory.md
rename to content/code-security/security-advisories/repository-security-advisories/creating-a-repository-security-advisory.md
index b2ab287eb2..cdb1a2ceae 100644
--- a/content/code-security/repository-security-advisories/creating-a-repository-security-advisory.md
+++ b/content/code-security/security-advisories/repository-security-advisories/creating-a-repository-security-advisory.md
@@ -6,6 +6,7 @@ redirect_from:
   - /github/managing-security-vulnerabilities/creating-a-maintainer-security-advisory
   - /github/managing-security-vulnerabilities/creating-a-security-advisory
   - /code-security/security-advisories/creating-a-security-advisory
+  - /code-security/repository-security-advisories/creating-a-repository-security-advisory
 versions:
   fpt: '*'
   ghec: '*'
diff --git a/content/code-security/repository-security-advisories/editing-a-repository-security-advisory.md b/content/code-security/security-advisories/repository-security-advisories/editing-a-repository-security-advisory.md
similarity index 96%
rename from content/code-security/repository-security-advisories/editing-a-repository-security-advisory.md
rename to content/code-security/security-advisories/repository-security-advisories/editing-a-repository-security-advisory.md
index eb5163d8af..985a0b7fda 100644
--- a/content/code-security/repository-security-advisories/editing-a-repository-security-advisory.md
+++ b/content/code-security/security-advisories/repository-security-advisories/editing-a-repository-security-advisory.md
@@ -4,6 +4,7 @@ intro: You can edit the metadata and description for a repository security advis
 redirect_from:
   - /github/managing-security-vulnerabilities/editing-a-security-advisory
   - /code-security/security-advisories/editing-a-security-advisory
+  - /code-security/repository-security-advisories/editing-a-repository-security-advisory
 versions:
   fpt: '*'
   ghec: '*'
diff --git a/content/code-security/repository-security-advisories/index.md b/content/code-security/security-advisories/repository-security-advisories/index.md
similarity index 80%
rename from content/code-security/repository-security-advisories/index.md
rename to content/code-security/security-advisories/repository-security-advisories/index.md
index f6aaae5cc2..94adf80c24 100644
--- a/content/code-security/repository-security-advisories/index.md
+++ b/content/code-security/security-advisories/repository-security-advisories/index.md
@@ -1,11 +1,11 @@
 ---
-title: Managing repository security advisories for vulnerabilities in your project
+title: Working with repository security advisories
 shortTitle: Repository security advisories
 intro: 'Discuss, fix, and disclose security vulnerabilities in your repositories using repository security advisories.'
 redirect_from:
   - /articles/managing-security-vulnerabilities-in-your-project
   - /github/managing-security-vulnerabilities/managing-security-vulnerabilities-in-your-project
-  - /code-security/security-advisories
+  - /code-security/repository-security-advisories
 versions:
   fpt: '*'
   ghec: '*'
@@ -16,15 +16,14 @@ topics:
   - CVEs
 children:
   - /about-coordinated-disclosure-of-security-vulnerabilities
-  - /about-github-security-advisories-for-repositories
+  - /about-repository-security-advisories
   - /permission-levels-for-repository-security-advisories
   - /creating-a-repository-security-advisory
-  - /adding-a-collaborator-to-a-repository-security-advisory
-  - /removing-a-collaborator-from-a-repository-security-advisory
+  - /editing-a-repository-security-advisory
   - /collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability
   - /publishing-a-repository-security-advisory
-  - /editing-a-repository-security-advisory
+  - /adding-a-collaborator-to-a-repository-security-advisory
+  - /removing-a-collaborator-from-a-repository-security-advisory
   - /withdrawing-a-repository-security-advisory
-  - /best-practices-for-writing-repository-security-advisories
 ---
 
diff --git a/content/code-security/repository-security-advisories/permission-levels-for-repository-security-advisories.md b/content/code-security/security-advisories/repository-security-advisories/permission-levels-for-repository-security-advisories.md
similarity index 97%
rename from content/code-security/repository-security-advisories/permission-levels-for-repository-security-advisories.md
rename to content/code-security/security-advisories/repository-security-advisories/permission-levels-for-repository-security-advisories.md
index 110e83d07b..c3c1f27fbc 100644
--- a/content/code-security/repository-security-advisories/permission-levels-for-repository-security-advisories.md
+++ b/content/code-security/security-advisories/repository-security-advisories/permission-levels-for-repository-security-advisories.md
@@ -6,6 +6,7 @@ redirect_from:
   - /github/managing-security-vulnerabilities/permission-levels-for-maintainer-security-advisories
   - /github/managing-security-vulnerabilities/permission-levels-for-security-advisories
   - /code-security/security-advisories/permission-levels-for-security-advisories
+  - /code-security/repository-security-advisories/permission-levels-for-repository-security-advisories
 versions:
   fpt: '*'
   ghec: '*'
diff --git a/content/code-security/repository-security-advisories/publishing-a-repository-security-advisory.md b/content/code-security/security-advisories/repository-security-advisories/publishing-a-repository-security-advisory.md
similarity index 95%
rename from content/code-security/repository-security-advisories/publishing-a-repository-security-advisory.md
rename to content/code-security/security-advisories/repository-security-advisories/publishing-a-repository-security-advisory.md
index ca1864d977..c60c374416 100644
--- a/content/code-security/repository-security-advisories/publishing-a-repository-security-advisory.md
+++ b/content/code-security/security-advisories/repository-security-advisories/publishing-a-repository-security-advisory.md
@@ -6,6 +6,7 @@ redirect_from:
   - /github/managing-security-vulnerabilities/publishing-a-maintainer-security-advisory
   - /github/managing-security-vulnerabilities/publishing-a-security-advisory
   - /code-security/security-advisories/publishing-a-security-advisory
+  - /code-security/repository-security-advisories/publishing-a-repository-security-advisory
 versions:
   fpt: '*'
   ghec: '*'
@@ -82,7 +83,7 @@ Publishing a security advisory deletes the temporary private fork for the securi
 
 ## Requesting a CVE identification number (Optional)
 
-{% data reusables.repositories.request-security-advisory-cve-id %} For more information, see "[About {% data variables.product.prodname_security_advisories %} for repositories](/code-security/repository-security-advisories/about-github-security-advisories-for-repositories#cve-identification-numbers)."
+{% data reusables.repositories.request-security-advisory-cve-id %} For more information, see "[About repository security advisories](/code-security/repository-security-advisories/about-github-security-advisories-for-repositories#cve-identification-numbers)."
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-security %}
diff --git a/content/code-security/repository-security-advisories/removing-a-collaborator-from-a-repository-security-advisory.md b/content/code-security/security-advisories/repository-security-advisories/removing-a-collaborator-from-a-repository-security-advisory.md
similarity index 94%
rename from content/code-security/repository-security-advisories/removing-a-collaborator-from-a-repository-security-advisory.md
rename to content/code-security/security-advisories/repository-security-advisories/removing-a-collaborator-from-a-repository-security-advisory.md
index 12ff241bc1..d9df04352d 100644
--- a/content/code-security/repository-security-advisories/removing-a-collaborator-from-a-repository-security-advisory.md
+++ b/content/code-security/security-advisories/repository-security-advisories/removing-a-collaborator-from-a-repository-security-advisory.md
@@ -4,6 +4,7 @@ intro: 'When you remove a collaborator from a repository security advisory, they
 redirect_from:
   - /github/managing-security-vulnerabilities/removing-a-collaborator-from-a-security-advisory
   - /code-security/security-advisories/removing-a-collaborator-from-a-security-advisory
+  - /code-security/repository-security-advisories/removing-a-collaborator-from-a-repository-security-advisory
 versions:
   fpt: '*'
   ghec: '*'
diff --git a/content/code-security/repository-security-advisories/withdrawing-a-repository-security-advisory.md b/content/code-security/security-advisories/repository-security-advisories/withdrawing-a-repository-security-advisory.md
similarity index 89%
rename from content/code-security/repository-security-advisories/withdrawing-a-repository-security-advisory.md
rename to content/code-security/security-advisories/repository-security-advisories/withdrawing-a-repository-security-advisory.md
index 8c96507692..a338e9c9d0 100644
--- a/content/code-security/repository-security-advisories/withdrawing-a-repository-security-advisory.md
+++ b/content/code-security/security-advisories/repository-security-advisories/withdrawing-a-repository-security-advisory.md
@@ -4,6 +4,7 @@ intro: You can withdraw a repository security advisory that you've published.
 redirect_from:
   - /github/managing-security-vulnerabilities/withdrawing-a-security-advisory
   - /code-security/security-advisories/withdrawing-a-security-advisory
+  - /code-security/repository-security-advisories/withdrawing-a-repository-security-advisory
 versions:
   fpt: '*'
   ghec: '*'
diff --git a/content/code-security/security-overview/about-the-security-overview.md b/content/code-security/security-overview/about-the-security-overview.md
index 69e55a8adc..c763b80753 100644
--- a/content/code-security/security-overview/about-the-security-overview.md
+++ b/content/code-security/security-overview/about-the-security-overview.md
@@ -67,17 +67,23 @@ The security overview displays active alerts raised by security features. If the
 
 At the organization-level, the security overview displays aggregate and repository-specific security information for repositories owned by your organization. You can filter information by security features at the organization-level.
 
+Organization owners and security managers for organizations have access to the organization-level security overview. {% ifversion ghec or ghes > 3.6 or ghae > 3.6 %}Organization members can access the organization-level security overview to view results for repositories where they have admin privileges or have been granted access to security alerts. For more information on managing security alert access, see "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)".{% endif %}
+
 {% ifversion ghec or ghes > 3.4 or ghae > 3.4 %}
 ### About the enterprise-level security overview
 At the enterprise-level, the security overview displays aggregate and repository-specific security information for your enterprise. You can view repositories owned by your enterprise that have security alerts, view all security alerts, or security feature-specific alerts from across your enterprise.
 
-Organization owners and security managers for organizations in your enterprise also have limited access to the enterprise-level security overview. They can only view repositories and alerts for the organizations that they have full access to.
+Organization owners and security managers for organizations in your enterprise have access to the enterprise-level security overview. They can view repositories and alerts for the organizations that they have full access to.
+
+Enterprise owners can only see alerts for organizations that they are an owner or a security manager of.{% ifversion ghec or ghes > 3.5 or ghae > 3.5 %} Enterprise owners can join an organization as an organization owner to see all of its alerts in the enterprise-level security overview. For more information, see "[Managing your role in an organization owned by your enterprise](/admin/user-management/managing-organizations-in-your-enterprise/managing-your-role-in-an-organization-owned-by-your-enterprise)."{% endif %}
 
 {% elsif fpt %}
 ### About the enterprise-level security overview
 At the enterprise-level, the security overview displays aggregate and repository-specific information for an enterprise. For more information, see "[About the enterprise-level security overview](/enterprise-cloud@latest/code-security/security-overview/about-the-security-overview#about-the-enterprise-level-security-overview)" in the {% data variables.product.prodname_ghe_cloud %} documentation.
 {% endif %}
 
+{% ifversion ghes < 3.7 or ghae < 3.7 %}
 ### About the team-level security overview
 At the team-level, the security overview displays repository-specific security information for repositories that the team has admin privileges for. For more information, see "[Managing team access to an organization repository](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository)."
 {% endif %}
+{% endif %}
diff --git a/content/codespaces/codespaces-reference/allowing-your-codespace-to-access-a-private-image-registry.md b/content/codespaces/codespaces-reference/allowing-your-codespace-to-access-a-private-image-registry.md
index 4735372c6b..6cc391c202 100644
--- a/content/codespaces/codespaces-reference/allowing-your-codespace-to-access-a-private-image-registry.md
+++ b/content/codespaces/codespaces-reference/allowing-your-codespace-to-access-a-private-image-registry.md
@@ -29,7 +29,7 @@ If you publish a container image to {% data variables.packages.prodname_ghcr_or_
 
 By default, when you publish a container image to {% data variables.packages.prodname_ghcr_or_npm_registry %}, the image inherits the access setting of the repository from which the image was published. For example, if the repository is public, the image is also public. If the repository is private, the image is also private, but is accessible from the repository.
 
-This behavior is controlled by the **Inherit access from repo** option. **Inherit access from repo** is selected by default when publishing via {% data variables.product.prodname_actions %}, but not when publishing directly to {% data variables.packages.prodname_ghcr_or_npm_registry %} using a % data variables.product.pat_generic %}.
+This behavior is controlled by the **Inherit access from repo** option. **Inherit access from repo** is selected by default when publishing via {% data variables.product.prodname_actions %}, but not when publishing directly to {% data variables.packages.prodname_ghcr_or_npm_registry %} using a {% data variables.product.pat_generic %}.
 
 If the **Inherit access from repo** option was not selected when the image was published, you can manually add the repository to the published container image's access controls. For more information, see "[Configuring a package's access control and visibility](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility#inheriting-access-for-a-container-image-from-a-repository)."
 
diff --git a/content/codespaces/guides.md b/content/codespaces/guides.md
index 615cd5f8e8..7434924668 100644
--- a/content/codespaces/guides.md
+++ b/content/codespaces/guides.md
@@ -14,6 +14,8 @@ includeGuides:
   - /codespaces/setting-up-your-project-for-codespaces/setting-up-your-python-project-for-codespaces
   - /codespaces/setting-up-your-project-for-codespaces/setting-up-your-dotnet-project-for-codespaces
   - /codespaces/setting-up-your-project-for-codespaces/setting-up-your-java-project-for-codespaces
+  - /codespaces/setting-up-your-project-for-codespaces/setting-a-minimum-specification-for-codespace-machines
+  - /codespaces/setting-up-your-project-for-codespaces/automatically-opening-files-in-the-codespaces-for-a-repository
   - /codespaces/setting-up-your-project-for-codespaces/adding-a-codespaces-badge
   - /codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project
   - /codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account
diff --git a/content/codespaces/setting-up-your-project-for-codespaces/automatically-opening-files-in-the-codespaces-for-a-repository.md b/content/codespaces/setting-up-your-project-for-codespaces/automatically-opening-files-in-the-codespaces-for-a-repository.md
new file mode 100644
index 0000000000..e77e284122
--- /dev/null
+++ b/content/codespaces/setting-up-your-project-for-codespaces/automatically-opening-files-in-the-codespaces-for-a-repository.md
@@ -0,0 +1,50 @@
+---
+title: Automatically opening files in the codespaces for a repository
+shortTitle: Automatically opening files
+intro: 'You can set particular files to be opened automatically whenever someone creates a codespace for your repository and opens the codespace in the {% data variables.product.prodname_vscode %} web client.'
+permissions: People with write permissions to a repository can create or edit the codespace configuration.
+versions:
+  fpt: '*'
+  ghec: '*'
+type: how_to
+topics:
+  - Codespaces
+  - Set up
+---
+
+## Overview
+
+If there's a particular file that's useful for people to see when they create a codespace for your repository, you can set this file to be opened automatically in the {% data variables.product.prodname_vscode_shortname %} web client. You set this up in the dev container configuration file for your repository. 
+
+The file, or files, you specify are only opened the first time a codespace is opened in the web client. If the person closes the specified files, those files are not automatically reopened the next time that person opens or restarts the codespace.
+
+{% note %}
+
+**Note**: This automation only applies to the {% data variables.product.prodname_vscode_shortname %} web client, not to the {% data variables.product.prodname_vscode_shortname %} desktop application, or other supported editors.
+
+{% endnote %}
+
+## Setting files to be opened automatically
+
+{% data reusables.codespaces.edit-devcontainer-json %}
+1. Edit the `devcontainer.json` file, adding a `customizations.codespaces.openFiles` property. The `customizations` property resides at the top level of the file, within the enclosing JSON object. For example:
+
+   ```json{:copy}
+   "customizations": {
+     "codespaces": {
+       "openFiles": [
+         "README.md",
+         "scripts/tsconfig.json",
+         "docs/main/CODING_STANDARDS.md"
+       ]
+     }
+   }
+   ```
+
+   The value of the `openFiles` property is an array of one or more files in your repository. The paths are relative to the root of the repository (absolute paths are not supported). The files are opened in the web client in the order specified, with the first file in the array displayed in the editor.
+   
+1. Save the file and commit your changes to the required branch of the repository.
+
+## Further reading
+
+- "[Introduction to dev containers](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers)"
diff --git a/content/codespaces/setting-up-your-project-for-codespaces/index.md b/content/codespaces/setting-up-your-project-for-codespaces/index.md
index 4212348bb3..3bb880b2ea 100644
--- a/content/codespaces/setting-up-your-project-for-codespaces/index.md
+++ b/content/codespaces/setting-up-your-project-for-codespaces/index.md
@@ -16,6 +16,7 @@ children:
   - /setting-up-your-java-project-for-codespaces
   - /setting-up-your-python-project-for-codespaces
   - /setting-a-minimum-specification-for-codespace-machines
+  - /automatically-opening-files-in-the-codespaces-for-a-repository
   - /adding-a-codespaces-badge
 ---
 
diff --git a/content/codespaces/setting-up-your-project-for-codespaces/setting-a-minimum-specification-for-codespace-machines.md b/content/codespaces/setting-up-your-project-for-codespaces/setting-a-minimum-specification-for-codespace-machines.md
index 462c27c0db..3064fe0bb6 100644
--- a/content/codespaces/setting-up-your-project-for-codespaces/setting-a-minimum-specification-for-codespace-machines.md
+++ b/content/codespaces/setting-up-your-project-for-codespaces/setting-a-minimum-specification-for-codespace-machines.md
@@ -26,8 +26,8 @@ If your project needs a certain level of compute power, you can configure {% dat
 
 ## Setting a minimum machine specification
 
-1. {% data variables.product.prodname_github_codespaces %} for your repository are configured in a `devcontainer.json` file. If your repository does not already contain a `devcontainer.json` file, add one now. See "[Add a dev container configuration to your repository](/free-pro-team@latest/codespaces/setting-up-your-project-for-codespaces/setting-up-your-project-for-codespaces)."
-1. Edit the `devcontainer.json` file, adding a `hostRequirements` property such as this:
+{% data reusables.codespaces.edit-devcontainer-json %}
+1. Edit the `devcontainer.json` file, adding the `hostRequirements` property at the top level of the file, within the enclosing JSON object. For example:
 
    ```json{:copy}
    "hostRequirements": {
diff --git a/content/packages/working-with-a-github-packages-registry/working-with-the-npm-registry.md b/content/packages/working-with-a-github-packages-registry/working-with-the-npm-registry.md
index f17d1a1b94..e687fd7b2b 100644
--- a/content/packages/working-with-a-github-packages-registry/working-with-the-npm-registry.md
+++ b/content/packages/working-with-a-github-packages-registry/working-with-the-npm-registry.md
@@ -142,14 +142,14 @@ You can use `publishConfig` element in the *package.json* file to specify the re
   {% endif %}
   ```shell
   "publishConfig": {
-    "registry":"https://{% ifversion fpt or ghec %}npm.pkg.github.com{% else %}npm.HOSTNAME/{% endif %}"
+    "registry": "https://{% ifversion fpt or ghec %}npm.pkg.github.com{% else %}npm.HOSTNAME/{% endif %}"
   },
   ```
   {% ifversion ghes %}
   If your instance has subdomain isolation disabled:
    ```shell
    "publishConfig": {
-     "registry":"https://HOSTNAME/_registry/npm/"
+     "registry": "https://HOSTNAME/_registry/npm/"
    },
   ```
   {% endif %}
diff --git a/content/repositories/creating-and-managing-repositories/renaming-a-repository.md b/content/repositories/creating-and-managing-repositories/renaming-a-repository.md
index 0d3f8b8abf..ab4047e4f1 100644
--- a/content/repositories/creating-and-managing-repositories/renaming-a-repository.md
+++ b/content/repositories/creating-and-managing-repositories/renaming-a-repository.md
@@ -22,7 +22,7 @@ When you rename a repository, all existing information, with the exception of pr
 
 For more information on project sites, see "[About {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages#types-of-github-pages-sites)."
 
-In addition to redirecting web traffic, all `git clone`, `git fetch`, or `git push` operations targeting the previous location will continue to function as if made on the new location. However, to reduce confusion, we strongly recommend updating any existing local clones to point to the new repository URL. You can do this by using  `git remote` on the command line:
+In addition to redirecting web traffic, all `git clone`, `git fetch`, or `git push` operations targeting the previous location will continue to function as if made on the new location. However, to reduce confusion, we strongly recommend updating any existing local clones to point to the new repository URL. You can do this by using `git remote` on the command line:
 
 ```shell
 $ git remote set-url origin NEW_URL
@@ -44,7 +44,7 @@ If you plan to rename a repository that has a {% data variables.product.prodname
 
 {% warning %}
 
-**Warning**: If you create a new repository under your account in the future, do not reuse the original name of the renamed repository. If you do, redirects to the renamed repository will break.
+**Warning**: If you create a new repository under your account in the future, do not reuse the original name of the renamed repository. If you do, redirects to the renamed repository will no longer work.
 
 {% endwarning %}
 
diff --git a/content/repositories/creating-and-managing-repositories/transferring-a-repository.md b/content/repositories/creating-and-managing-repositories/transferring-a-repository.md
index dff4c98d4d..ca7dd28f84 100644
--- a/content/repositories/creating-and-managing-repositories/transferring-a-repository.md
+++ b/content/repositories/creating-and-managing-repositories/transferring-a-repository.md
@@ -51,6 +51,12 @@ When you transfer a repository, its issues, pull requests, wiki, stars, and watc
   $ git remote set-url origin NEW_URL
   ```
 
+  {% warning %}
+
+  **Warning**: If you create a new repository under your account in the future, do not reuse the original name of the transferred repository. If you do, redirects to the transferred repository will no longer work.
+
+  {% endwarning %}
+
 - When you transfer a repository from an organization to a personal account, the repository's read-only collaborators will not be transferred. This is because collaborators can't have read-only access to repositories owned by a personal account. For more information about repository permission levels, see "[Permission levels for a personal account repository](/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository)" and "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)."{% ifversion fpt or ghec %}
 - Sponsors who have access to the repository through a sponsorship tier may be affected. For more information, see "[Adding a repository to a sponsorship tier](/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers#adding-a-repository-to-a-sponsorship-tier)".{% endif %}
 
diff --git a/content/rest/guides/traversing-with-pagination.md b/content/rest/guides/traversing-with-pagination.md
index ed7f9b1189..f47cd8dbbf 100644
--- a/content/rest/guides/traversing-with-pagination.md
+++ b/content/rest/guides/traversing-with-pagination.md
@@ -12,6 +12,7 @@ versions:
 topics:
   - API
 shortTitle: Traverse with pagination
+miniTocMaxHeadingLevel: 3
 ---
 
 The {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API provides a vast wealth of information for developers to consume.
@@ -24,10 +25,13 @@ in the [platform-samples][platform samples] repository.
 
 {% data reusables.rest-api.dotcom-only-guide-note %}
 
+
+
 ## Basics of Pagination
 
 To start with, it's important to know a few facts about receiving paginated items:
 
+
 1. Different API calls respond with different defaults. For example, a call to
 [List public repositories](/rest/reference/repos#list-public-repositories)
 provides paginated items in sets of 30, whereas a call to the GitHub Search API
@@ -37,55 +41,127 @@ provides items in sets of 100
 [events](/rest/reference/activity#events) won't let you set a maximum for items to receive.
 Be sure to read the documentation on how to handle paginated results for specific endpoints.
 
-Information about pagination is provided in [the Link header](https://datatracker.ietf.org/doc/html/rfc5988)
-of an API call. For example, let's make a curl request to the search API, to find
-out how many times Mozilla projects use the phrase `addClass`:
+{% note %}
+
+**Note**: You should always rely on URLs included in the link header. Don't try to guess or construct your own URLs.
+
+{% endnote %}
+
+
+### Link header
+
+The response header includes information about pagination. For more information about headers, see "[Getting started with the REST API](/rest/guides/getting-started-with-the-rest-api#about-the-response-code-and-headers)." To get the response header, include the `-I` flag in your request. For example:
+
+```shell 
+$ curl -I -H "Accept: application/vnd.github+json" -H "Authorization: Bearer YOUR_TOKEN"   https://api.github.com/enterprises/advacado-corp/audit-log
 
-```shell
-$ curl -I "https://api.github.com/search/code?q=addClass+user:mozilla"
 ```
 
-The `-I` parameter indicates that we only care about the headers, not the actual
-content. In examining the result, you'll notice some information in the Link header
-that looks like this:
+The `-I` flag returns only the response header. If the response is paginated, the response header will include a `link` header. The header will look something like this:
 
-    Link: <https://api.github.com/search/code?q=addClass+user%3Amozilla&page=2>; rel="next",
-      <https://api.github.com/search/code?q=addClass+user%3Amozilla&page=34>; rel="last"
+```
+link: <https://api.github.com/enterprises/13827/audit-log?after=MS42NjQzODM5MTkzNDdlKzEyfDM0MkI6NDdBNDo4RTFGMEM6NUIyQkZCMzo2MzM0N0JBRg%3D%3D&before=>; rel="next"
+```
 
-Let's break that down. `rel="next"` says that the next page is `page=2`. This makes
-sense, since by default, all paginated queries start at page `1.` `rel="last"`
-provides some more information, stating that the last page of results is on page `34`.
-Thus, we have 33 more pages of information about `addClass` that we can consume.
-Nice!
+or
 
-**Always** rely on these link relations provided to you. Don't try to guess or construct your own URL.
+```
+link: <https://api.github.com/repositories/1300192/issues?page=2>; rel="next", <https://api.github.com/repositories/1300192/issues?page=511>; rel="last"
+```
+### Types of pagination
 
-### Navigating through the pages
+{% data variables.product.company_short %}'s API uses two pagination methods: page-based pagination and cursor-based pagination. If the `link` header includes `page`, then the operation uses page-based pagination. If the `link` header includes `before` and `after`, then the operation uses cursor-based pagination.
 
-Now that you know how many pages there are to receive, you can start navigating
-through the pages to consume the results. You do this by passing in a `page`
-parameter. By default, `page` always starts at `1`. Let's jump ahead to page 14
-and see what happens:
+
+#### Page based pagination
+
+The link header for page-based pagination will tell you information about the previous, next, first, and last pages. If you did not request a specific page, then the response will default to the first page and information about the first and previous pages will be omitted.
+
+For example, for a request that did not specify a page, this header states that the next page is `2` and the last page is `511`.
+
+```
+link: <https://api.github.com/repositories/1300192/issues?page=2>; rel="next", <https://api.github.com/repositories/1300192/issues?page=511>; rel="last"
+```
+
+For example, for a request that specified page 5, this header states that the previous page is `4`, the next page is `6`, the last page is `511`, and the first page is `1`.
+
+```
+link: <https://api.github.com/repositories/1300192/issues?page=4>; rel="prev", <https://api.github.com/repositories/1300192/issues?page=6>; rel="next", <https://api.github.com/repositories/1300192/issues?page=511>; rel="last", <https://api.github.com/repositories/1300192/issues?page=1>; rel="first"
+```
+
+#### Cursor based pagination
+
+Cursor pagination uses terms `before` and `after` in order to navigate through pages. `rel="next"` and `rel="prev"` this mark the cursor point in the data set and provides a reference for traveling to the page `before` and `after` the current page.  
+
+```
+link: <https://api.github.com/enterprises/13827/audit-log?after=MS42NjQzODMzMzk2MzZlKzEyfFdxSzIxdGU0MlBWNUp5UzhBWDF6LWc%3D&before=>; rel="next",
+<https://api.github.com/enterprises/13827/audit-log?after=&before=>; rel="first", 
+<https://api.github.com/enterprises/13827/audit-log?after=&before=MS42NjQzODM5MTcyMjllKzEyfDI4NDE6NEVFNDoxODBDRkM5OjY5REE0MzI6NjMzNDdCQUQ%3D>; rel="prev"
+```
+
+In this example, `rel=next` says that the next page is located at:
+
+```
+after=MS42NjQzODM5MTkzNDdlKzEyfDM0MkI6NDdBNDo4RTFGMEM6NUIyQkZCMzo2MzM0N0JBRg%3D%3D&before=>
+```
+
+
+
+
+### Using pagination
+
+#### Cursor based pagination
+
+Using cursor based pagination requires you to use the terms `before` and `after`. To navigate using `before` and `after`, copy the link header generated above into your curl request:
+
+```shell
+$ curl -I -H "Accept: application/vnd.github+json" -H "Authorization: Bearer YOUR_TOKEN"  https://api.github.com/enterprises/13827/audit-log?after=MS42NjQzODM5MTkzNDdlKzEyfDM0MkI6NDdBNDo4RTFGMEM6NUIyQkZCMzo2MzM0N0JBRg%3D%3D&before=>
+```
+
+The above example will generate a page of results and new header information that you can use to make the next request. `rel="next"` provides the next page of results. `rel="prev"` provides the previous page of results. The important part of the output here is the link header needs to be generated rather than manually imputed. Copy the entire link from the following output.
+
+```
+link: <https://api.github.com/enterprises/13827/audit-log?after=MS42NjQzODMzMzk2MzZlKzEyfFdxSzIxdGU0MlBWNUp5UzhBWDF6LWc%3D&before=>; rel="next", 
+<https://api.github.com/enterprises/13827/audit-log?after=&before=>; rel="first", 
+<https://api.github.com/enterprises/13827/audit-log?after=&before=MS42NjQzODM5MTcyMjllKzEyfDI4NDE6NEVFNDoxODBDRkM5OjY5REE0MzI6NjMzNDdCQUQ%3D>; rel="prev"
+```
+
+Unlike page-based pagination, the results will not return the last page number in the response.
+
+    link: <https://api.github.com/enterprises/13827/audit-log?after=MS42NjQzODMzMzk2MzZlKzEyfFdxSzIxdGU0MlBWNUp5UzhBWDF6LWc%3D&before=>; rel="next", 
+    <https://api.github.com/enterprises/13827/audit-log?after=&before=>; rel="first", 
+    <https://api.github.com/enterprises/13827/audit-log?after=&before=MS42NjQzODM5MTcyMjllKzEyfDI4NDE6NEVFNDoxODBDRkM5OjY5REE0MzI6NjMzNDdCQUQ%3D>; rel="prev"
+    
+Because cursor based pagination creates a reference point in the data set, it cannot calculate the total number of results.
+
+
+#### Page based pagination
+
+To navigate using page based pagination pass in a `page`
+parameter. By default, `page` always starts at `1`. In the following example, we have made a curl request to the search API Mozilla projects use the phrase `addClass`. Instead of starting at 1, lets jump to page 14. 
 
 ```shell
 $ curl -I "https://api.github.com/search/code?q=addClass+user:mozilla&page=14"
 ```
 
-Here's the link header once more:
+Here's an except of the link header in the HTTP request:
 
     Link: <https://api.github.com/search/code?q=addClass+user%3Amozilla&page=15>; rel="next",
       <https://api.github.com/search/code?q=addClass+user%3Amozilla&page=34>; rel="last",
       <https://api.github.com/search/code?q=addClass+user%3Amozilla&page=1>; rel="first",
       <https://api.github.com/search/code?q=addClass+user%3Amozilla&page=13>; rel="prev"
 
-As expected, `rel="next"` is at 15, and `rel="last"` is still 34. But now we've
+In this example, `rel="next"` is at 15, and `rel="last"` is 34. But now we've
 got some more information: `rel="first"` indicates the URL for the _first_ page,
 and more importantly, `rel="prev"` lets you know the page number of the previous
 page. Using this information, you could construct some UI that lets users jump
 between the first, previous, next, or last list of results in an API call.
 
+
 ### Changing the number of items received
 
+#### Page based pagination
+
 By passing the `per_page` parameter, you can specify how many items you want
 each page to return, up to 100 items. Let's try asking for 50 items about `addClass`:
 
@@ -102,6 +178,14 @@ As you might have guessed, the `rel="last"` information says that the last page
 is now 20. This is because we are asking for more information per page about
 our results.
 
+#### Cursor based pagination
+
+You can also pass the `per_page` parameter for cursor-based pagination. 
+
+```shell
+$ curl -I -H "Accept: application/vnd.github+json" -H "Authorization: Bearer YOUR_TOKEN"  https://api.github.com/enterprises/13827/audit-log?after=MS42NjQzODM5MTkzNDdlKzEyfDM0MkI6NDdBNDo4RTFGMEM6NUIyQkZCMzo2MzM0N0JBRg%3D%3D&before=>&per_page=50
+```
+
 ## Consuming the information
 
 You don't want to be making low-level curl calls just to be able to work with
diff --git a/data/learning-tracks/code-security.yml b/data/learning-tracks/code-security.yml
index a614b6945c..3b35eb0a73 100644
--- a/data/learning-tracks/code-security.yml
+++ b/data/learning-tracks/code-security.yml
@@ -4,15 +4,18 @@ security_advisories:
   description: 'Using repository security advisories to privately fix a reported vulnerability and get a CVE.'
   featured_track: '{% ifversion fpt or ghec %}true{% else %}false{% endif %}'
   guides:
-    - /code-security/repository-security-advisories/about-coordinated-disclosure-of-security-vulnerabilities
-    - /code-security/repository-security-advisories/creating-a-repository-security-advisory
-    - /code-security/repository-security-advisories/adding-a-collaborator-to-a-repository-security-advisory
-    - /code-security/repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability
-    - /code-security/repository-security-advisories/publishing-a-repository-security-advisory
-    - /code-security/repository-security-advisories/editing-a-repository-security-advisory
-    - /code-security/repository-security-advisories/withdrawing-a-repository-security-advisory
-    - /code-security/repository-security-advisories/removing-a-collaborator-from-a-repository-security-advisory
-    - /code-security/repository-security-advisories/best-practices-for-writing-repository-security-advisories
+    - /code-security/security-advisories/repository-security-advisories/about-coordinated-disclosure-of-security-vulnerabilities
+    - /code-security/security-advisories/global-security-advisories/about-the-github-advisory-database
+    - /code-security/security-advisories/global-security-advisories/about-global-security-advisories
+    - /code-security/security-advisories/repository-security-advisories/about-repository-security-advisories
+    - /code-security/security-advisories/repository-security-advisories/creating-a-repository-security-advisory
+    - /code-security/security-advisories/repository-security-advisories/adding-a-collaborator-to-a-repository-security-advisory
+    - /code-security/security-advisories/repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability
+    - /code-security/security-advisories/repository-security-advisories/publishing-a-repository-security-advisory
+    - /code-security/security-advisories/repository-security-advisories/editing-a-repository-security-advisory
+    - /code-security/security-advisories/repository-security-advisories/withdrawing-a-repository-security-advisory
+    - /code-security/security-advisories/repository-security-advisories/removing-a-collaborator-from-a-repository-security-advisory
+    - /code-security/security-advisories/guidance-on-reporting-and-writing/best-practices-for-writing-repository-security-advisories
 
 # Feature available on dotcom and GHES 3.3+, so articles available on GHAE and earlier GHES hidden to hide the learning track
 dependabot_alerts:
diff --git a/data/reusables/actions/hardware-requirements-3.6.md b/data/reusables/actions/hardware-requirements-3.6.md
deleted file mode 100644
index 5028ea1976..0000000000
--- a/data/reusables/actions/hardware-requirements-3.6.md
+++ /dev/null
@@ -1,6 +0,0 @@
-| vCPUs | Memory | Maximum Connected Runners |
-| :---| :--- | :--- |
-| 8   | 64 GB  | 740  runners |
-| 32  | 160 GB | 2700 runners |
-| 96  | 384 GB | 7000 runners |
-| 128 | 512 GB | 7000 runners |
diff --git a/data/reusables/codespaces/edit-devcontainer-json.md b/data/reusables/codespaces/edit-devcontainer-json.md
new file mode 100644
index 0000000000..55c57eee95
--- /dev/null
+++ b/data/reusables/codespaces/edit-devcontainer-json.md
@@ -0,0 +1 @@
+1. {% data variables.product.prodname_github_codespaces %} for your repository are configured in a `devcontainer.json` file. If your repository does not already contain a `devcontainer.json` file, add one now. See "[Add a dev container configuration to your repository](/free-pro-team@latest/codespaces/setting-up-your-project-for-codespaces/setting-up-your-project-for-codespaces)."
\ No newline at end of file
diff --git a/data/reusables/package_registry/authenticate_with_pat_for_v2_registry.md b/data/reusables/package_registry/authenticate_with_pat_for_v2_registry.md
index db1256da20..9bda52c077 100644
--- a/data/reusables/package_registry/authenticate_with_pat_for_v2_registry.md
+++ b/data/reusables/package_registry/authenticate_with_pat_for_v2_registry.md
@@ -1,6 +1,6 @@
 If your workflow is using a {% data variables.product.pat_generic %} to authenticate to a registry, then we highly recommend you update your workflow to use the `GITHUB_TOKEN`.
 
-{% ifversion fpt or ghec %}For guidance on updating your workflows that authenticate to a registry with a {% data variables.product.pat_generic %}, see "[Upgrading a workflow that accesses a registry using a {% data variables.product.pat_generic %}](/packages/managing-github-packages-using-github-actions-workflows/publishing-and-installing-a-package-with-github-actions#upgrading-a-workflow-that-accesses-a-registry-using-a-pat)."{% endif %}
+{% ifversion fpt or ghec %}For guidance on updating your workflows that authenticate to a registry with a {% data variables.product.pat_generic %}, see "[Upgrading a workflow that accesses a registry using a {% data variables.product.pat_generic %}](/packages/managing-github-packages-using-github-actions-workflows/publishing-and-installing-a-package-with-github-actions#upgrading-a-workflow-that-accesses-a-registry-using-a-personal-access-token)."{% endif %}
 
 For more information about the `GITHUB_TOKEN`, see "[Authentication in a workflow](/actions/reference/authentication-in-a-workflow#using-the-github_token-in-a-workflow)."
 
diff --git a/data/reusables/repositories/security-advisories-republishing.md b/data/reusables/repositories/security-advisories-republishing.md
index a461140c25..c2f7cd1471 100644
--- a/data/reusables/repositories/security-advisories-republishing.md
+++ b/data/reusables/repositories/security-advisories-republishing.md
@@ -1 +1 @@
-You can also use {% data variables.product.prodname_security_advisories %} to republish the details of a security vulnerability that you have already disclosed elsewhere by copying and pasting the details of the vulnerability into a new security advisory.
+You can also use repository security advisories to republish the details of a security vulnerability that you have already disclosed elsewhere by copying and pasting the details of the vulnerability into a new security advisory.
diff --git a/data/reusables/security-advisory/global-advisories.md b/data/reusables/security-advisory/global-advisories.md
new file mode 100644
index 0000000000..74822a646b
--- /dev/null
+++ b/data/reusables/security-advisory/global-advisories.md
@@ -0,0 +1 @@
+Security advisories in the {% data variables.product.prodname_advisory_database %} at [github.com/advisories](https://github.com/advisories) are considered global advisories. Anyone can suggest improvements on any global security advisory in the {% data variables.product.prodname_advisory_database %}. You can edit or add any detail, including additionally affected ecosystems, severity level or description of who is impacted. The {% data variables.product.prodname_security %} curation team will review the submitted improvements and publish them onto the {% data variables.product.prodname_advisory_database %} if accepted.
\ No newline at end of file
diff --git a/data/reusables/security-advisory/security-advisory-overview.md b/data/reusables/security-advisory/security-advisory-overview.md
index 3cf3379b92..3c4c6a964f 100644
--- a/data/reusables/security-advisory/security-advisory-overview.md
+++ b/data/reusables/security-advisory/security-advisory-overview.md
@@ -1 +1 @@
-{% data variables.product.prodname_security_advisories %} allow repository maintainers to privately discuss and fix a security vulnerability in a project. After collaborating on a fix, repository maintainers can publish the security advisory to publicly disclose the security vulnerability to the project's community. By publishing security advisories, repository maintainers make it easier for their community to update package dependencies and research the impact of the security vulnerabilities.
+Repository security advisories allow repository maintainers to privately discuss and fix a security vulnerability in a project. After collaborating on a fix, repository maintainers can publish the security advisory to publicly disclose the security vulnerability to the project's community. By publishing security advisories, repository maintainers make it easier for their community to update package dependencies and research the impact of the security vulnerabilities.
diff --git a/data/reusables/security-overview/permissions.md b/data/reusables/security-overview/permissions.md
index 2cf85d19c5..43dd55172d 100644
--- a/data/reusables/security-overview/permissions.md
+++ b/data/reusables/security-overview/permissions.md
@@ -1 +1 @@
-Organization owners and security managers can access the security overview for organizations{% ifversion ghec or ghes > 3.4 or ghae > 3.4 %} and view their organization's repositories via the enterprise-level security overview. Enterprise owners can use the enterprise-level security overview to view all repositories in their enterprise's organizations{% endif %}. Members of a team can see the security overview for repositories that the team has admin privileges for.
+{% ifversion not fpt %}Organization owners and security managers can access the organization-level security overview{% ifversion ghec or ghes > 3.4 or ghae > 3.4 %} and view alerts across multiple organizations via the enterprise-level security overview. Enterprise owners can only view repositories and alerts for organizations where they are added as an organization owner or security manager{% endif %}. {% ifversion ghec or ghes > 3.6 or ghae > 3.6 %}Organization members can access the organization-level security overview to view results for repositories where they have admin privileges or have been granted access to security alerts.{% else %}Members of a team can see the security overview for repositories that the team has admin privileges for.{% endif %}{% endif %}
diff --git a/lib/page-data.js b/lib/page-data.js
index e6b141c873..3af85714ec 100644
--- a/lib/page-data.js
+++ b/lib/page-data.js
@@ -3,16 +3,12 @@ import path from 'path'
 import languages from './languages.js'
 import { allVersions } from './all-versions.js'
 import createTree, { getBasePath } from './create-tree.js'
-import renderContent from './render-content/index.js'
 import loadSiteData from './site-data.js'
 import nonEnterpriseDefaultVersion from './non-enterprise-default-version.js'
 import Page from './page.js'
-import shortVersionsMiddleware from '../middleware/contextualizers/short-versions.js'
 
 const __dirname = path.dirname(fileURLToPath(import.meta.url))
 const versions = Object.keys(allVersions)
-const enterpriseServerVersions = versions.filter((v) => v.startsWith('enterprise-server@'))
-const renderOpts = { textOnly: true, encodeEntities: true }
 
 // These are the exceptions to the rule.
 // If a URI starts with one of these prefixes, it basically means we don't
@@ -103,31 +99,6 @@ export async function versionPages(obj, version, langCode, site) {
       (pl.pageVersion === 'homepage' && version === nonEnterpriseDefaultVersion)
   ).href
 
-  const req = {}
-
-  req.context = {
-    allVersions,
-    enterpriseServerVersions,
-    currentLanguage: langCode,
-    currentVersion: version,
-    site: site[langCode].site,
-  }
-
-  // The Liquid parseAndRender method is MUCH faster than renderContent or renderProp.
-  // This only works for titles and short titles, which have no other Markdown that needs
-  // to be converted to HTML, so we can get away with _only_ parsing Liquid.
-  await shortVersionsMiddleware(req, null, () => {})
-
-  obj.renderedFullTitle = obj.page.title.includes('{')
-    ? await renderContent.liquid.parseAndRender(obj.page.title, req.context, renderOpts)
-    : obj.page.title
-
-  if (obj.page.shortTitle) {
-    obj.renderedShortTitle = obj.page.shortTitle.includes('{')
-      ? await renderContent.liquid.parseAndRender(obj.page.shortTitle, req.context, renderOpts)
-      : obj.page.shortTitle
-  }
-
   if (!obj.childPages) return obj
   const versionedChildPages = await Promise.all(
     obj.childPages
diff --git a/lib/rest/static/dereferenced/api.github.com.deref.json b/lib/rest/static/dereferenced/api.github.com.deref.json
index 4677440fa1..c7a6179db0 100644
--- a/lib/rest/static/dereferenced/api.github.com.deref.json
+++ b/lib/rest/static/dereferenced/api.github.com.deref.json
@@ -634841,7 +634841,7 @@
     },
     "fork": {
       "post": {
-        "summary": "Fork",
+        "summary": "This event occurs when someone forks a repository. For more information, see \"[Fork a repo](https://docs.github.com/get-started/quickstart/fork-a-repo).\" For information about the API, see \"[Forks](https://docs.github.com/rest/repos/forks)\" in the REST API documentation.\n\nTo subscribe to this event, a GitHub App must have at least read-level access for the \"Contents\" repository permission.",
         "operationId": "fork",
         "externalDocs": {
           "url": "https://docs.github.com/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#fork"
@@ -989809,7 +989809,7 @@
     },
     "push": {
       "post": {
-        "summary": "Push",
+        "summary": "This event occurs when a commit or tag is pushed.\n\nTo subscribe to this event, a GitHub App must have at least read-level access for the \"Contents\" repository permission.\n\n**Note**: An event will not be created when more than three tags are pushed at once.",
         "operationId": "push",
         "externalDocs": {
           "url": "https://docs.github.com/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#push"
diff --git a/lib/rest/static/dereferenced/ghec.deref.json b/lib/rest/static/dereferenced/ghec.deref.json
index 64f58ef262..8081987c4e 100644
--- a/lib/rest/static/dereferenced/ghec.deref.json
+++ b/lib/rest/static/dereferenced/ghec.deref.json
@@ -642513,7 +642513,7 @@
     },
     "fork": {
       "post": {
-        "summary": "Fork",
+        "summary": "This event occurs when someone forks a repository. For more information, see \"[Fork a repo](https://docs.github.com/enterprise-cloud@latest//get-started/quickstart/fork-a-repo).\" For information about the API, see \"[Forks](https://docs.github.com/enterprise-cloud@latest//rest/repos/forks)\" in the REST API documentation.\n\nTo subscribe to this event, a GitHub App must have at least read-level access for the \"Contents\" repository permission.",
         "operationId": "fork",
         "externalDocs": {
           "url": "https://docs.github.com/enterprise-cloud@latest//developers/webhooks-and-events/webhooks/webhook-events-and-payloads#fork"
@@ -997481,7 +997481,7 @@
     },
     "push": {
       "post": {
-        "summary": "Push",
+        "summary": "This event occurs when a commit or tag is pushed.\n\nTo subscribe to this event, a GitHub App must have at least read-level access for the \"Contents\" repository permission.\n\n**Note**: An event will not be created when more than three tags are pushed at once.",
         "operationId": "push",
         "externalDocs": {
           "url": "https://docs.github.com/enterprise-cloud@latest//developers/webhooks-and-events/webhooks/webhook-events-and-payloads#push"
diff --git a/lib/rest/static/dereferenced/ghes-3.7.deref.json b/lib/rest/static/dereferenced/ghes-3.7.deref.json
index a1fd6f54f4..c9ba7c126c 100644
--- a/lib/rest/static/dereferenced/ghes-3.7.deref.json
+++ b/lib/rest/static/dereferenced/ghes-3.7.deref.json
@@ -597170,7 +597170,7 @@
     },
     "fork": {
       "post": {
-        "summary": "Fork",
+        "summary": "This event occurs when someone forks a repository. For more information, see \"[Fork a repo](https://docs.github.com/enterprise-server@3.7/get-started/quickstart/fork-a-repo).\" For information about the API, see \"[Forks](https://docs.github.com/enterprise-server@3.7/rest/repos/forks)\" in the REST API documentation.\n\nTo subscribe to this event, a GitHub App must have at least read-level access for the \"Contents\" repository permission.",
         "operationId": "fork",
         "externalDocs": {
           "url": "https://docs.github.com/enterprise-server@3.7/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#fork"
@@ -938287,7 +938287,7 @@
     },
     "push": {
       "post": {
-        "summary": "Push",
+        "summary": "This event occurs when a commit or tag is pushed.\n\nTo subscribe to this event, a GitHub App must have at least read-level access for the \"Contents\" repository permission.\n\n**Note**: An event will not be created when more than three tags are pushed at once.",
         "operationId": "push",
         "externalDocs": {
           "url": "https://docs.github.com/enterprise-server@3.7/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#push"
diff --git a/lib/rest/static/dereferenced/github.ae.deref.json b/lib/rest/static/dereferenced/github.ae.deref.json
index c3f2d4ef60..ca6d0ce744 100644
--- a/lib/rest/static/dereferenced/github.ae.deref.json
+++ b/lib/rest/static/dereferenced/github.ae.deref.json
@@ -513395,7 +513395,7 @@
     },
     "fork": {
       "post": {
-        "summary": "Fork",
+        "summary": "This event occurs when someone forks a repository. For more information, see \"[Fork a repo](https://docs.github.com/github-ae@latest/get-started/quickstart/fork-a-repo).\" For information about the API, see \"[Forks](https://docs.github.com/github-ae@latest/rest/repos/forks)\" in the REST API documentation.\n\nTo subscribe to this event, a GitHub App must have at least read-level access for the \"Contents\" repository permission.",
         "operationId": "fork",
         "externalDocs": {
           "url": "https://docs.github.com/github-ae@latest/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#fork"
@@ -840786,7 +840786,7 @@
     },
     "push": {
       "post": {
-        "summary": "Push",
+        "summary": "This event occurs when a commit or tag is pushed.\n\nTo subscribe to this event, a GitHub App must have at least read-level access for the \"Contents\" repository permission.\n\n**Note**: An event will not be created when more than three tags are pushed at once.",
         "operationId": "push",
         "externalDocs": {
           "url": "https://docs.github.com/github-ae@latest/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#push"
diff --git a/middleware/contextualizers/breadcrumbs.js b/middleware/contextualizers/breadcrumbs.js
index ef4195c4c9..3330614ccf 100644
--- a/middleware/contextualizers/breadcrumbs.js
+++ b/middleware/contextualizers/breadcrumbs.js
@@ -1,6 +1,4 @@
-import liquid from '../../lib/render-content/liquid.js'
-
-export default async function breadcrumbs(req, res, next) {
+export default function breadcrumbs(req, res, next) {
   if (!req.context.page) return next()
   const isEarlyAccess = req.context.page.relativePath.startsWith('early-access')
   if (req.context.page.hidden && !isEarlyAccess) return next()
@@ -12,76 +10,81 @@ export default async function breadcrumbs(req, res, next) {
     return next()
   }
 
-  req.context.breadcrumbs = await getBreadcrumbs(req, isEarlyAccess)
+  req.context.breadcrumbs = getBreadcrumbs(req, isEarlyAccess)
 
   return next()
 }
 
 const earlyAccessExceptions = ['insights', 'enterprise-importer']
 
-async function getBreadcrumbs(req, isEarlyAccess = false) {
-  const crumbs = []
-  const { currentPath, currentVersion } = req.context
-  const split = currentPath.split('/')
-  let cutoff = 2
+function getBreadcrumbs(req, isEarlyAccess) {
+  let cutoff = 0
+  // When in Early access docs consider the "root" be much higher.
+  // E.g. /en/early-access/github/migrating/understanding/about
+  // we only want it start at /migrating/understanding/about
+  // Essentially, we're skipping "/early-access" and its first
+  // top-level like "/github"
   if (isEarlyAccess) {
-    // When in Early access docs consider the "root" be much higher.
-    // E.g. /en/early-access/github/migrating/understanding/about
-    // we only want it start at /migrating/understanding/about
-    // Essentially, we're skipping "/early-access" and its first
-    // top-level like "/github"
-    cutoff++
-
+    const split = req.context.currentPath.split('/')
     // There are a few exceptions to this rule for the
     // /{version}/early-access/<product-name>/... URLs because they're a
     // bit different.
     // If there are more known exceptions, add them to the array above.
-    if (!earlyAccessExceptions.some((product) => split.includes(product))) {
-      cutoff++
-    }
-
-    // If the URL is early access AND has a version in it, go even further
-    // E.g. /en/enterprise-server@3.3/early-access/admin/hosting/mysql
-    // should start at /hosting/mysql.
-    if (currentVersion !== 'free-pro-team@latest') {
-      cutoff++
-    }
-  }
-  while (split.length > cutoff && split[split.length - 1] !== currentVersion) {
-    const href = split.join('/')
-    const page = req.context.pages[href]
-    if (page) {
-      crumbs.push({
-        href,
-        title: await getShortTitle(page, req.context),
-      })
+    if (earlyAccessExceptions.some((product) => split.includes(product))) {
+      cutoff = 1
     } else {
-      console.warn(`No page found with for '${href}'`)
+      cutoff = 2
     }
-    split.pop()
   }
-  crumbs.reverse()
 
+  const breadcrumbs = traverseTreeTitles(
+    req.context.currentPath,
+    req.context.currentProductTreeTitles
+  )
+  ;[...Array(cutoff)].forEach(() => breadcrumbs.shift())
+
+  return breadcrumbs
+}
+
+// Return an array as if you'd traverse down a tree. Imagine a tree like
+//
+//            (root /)
+//           /       \
+//        (/foo)     (/bar)
+//       /      \
+//    (/foo/bar)  (/foo/buzz)
+//
+// If the "currentPath" is `/foo/buzz` what you want to return is:
+//
+//  [
+//    {href: /, title: TITLE},
+//    {href: /foo, title: TITLE}
+//    {href: /foo/buzz, title: TITLE}
+//  ]
+//
+function traverseTreeTitles(currentPath, tree) {
+  const { href, title, shortTitle } = tree
+  const crumbs = [
+    {
+      href,
+      title: shortTitle || title,
+    },
+  ]
+  const currentPathSplit = Array.isArray(currentPath) ? currentPath : currentPath.split('/')
+  for (const child of tree.childPages) {
+    if (isParentOrEqualArray(child.href.split('/'), currentPathSplit)) {
+      crumbs.push(...traverseTreeTitles(currentPathSplit, child))
+      // Only ever going down 1 of the children
+      break
+    }
+  }
   return crumbs
 }
 
-async function getShortTitle(page, context) {
-  // Note! Don't use `page.title` or `page.shortTitle` because if they get
-  // set during rendering, they become the HTML entities encoded string.
-  // E.g. "Delete &amp; restore a package"
-
-  if (page.rawShortTitle) {
-    if (page.rawShortTitle.includes('{')) {
-      // Can't easily cache this because the `page` is reused for multiple
-      // permalinks. We could do what the `Page.render()` method does which
-      // specifically caches based on the `context.currentPath` but at
-      // this point it's probably not worth it.
-      return await liquid.parseAndRender(page.rawShortTitle, context)
-    }
-    return page.rawShortTitle
-  }
-  if (page.rawTitle.includes('{')) {
-    return await liquid.parseAndRender(page.rawTitle, context)
-  }
-  return page.rawTitle
+// Return true if an array is part of another array or equal.
+// Like `/foo/bar` is part of `/foo/bar/buzz`.
+// But also include `/foo/bar/buzz`.
+// Don't include `/foo/ba` if the final path is `/foo/baring`.
+function isParentOrEqualArray(base, final) {
+  return base.every((part, i) => part === final[i])
 }
diff --git a/middleware/contextualizers/current-product-tree.js b/middleware/contextualizers/current-product-tree.js
index 3bef4d0d55..4301d19451 100644
--- a/middleware/contextualizers/current-product-tree.js
+++ b/middleware/contextualizers/current-product-tree.js
@@ -1,9 +1,10 @@
 import path from 'path'
+import liquid from '../../lib/render-content/liquid.js'
 import findPageInSiteTree from '../../lib/find-page-in-site-tree.js'
 import removeFPTFromPath from '../../lib/remove-fpt-from-path.js'
 
 // This module adds currentProductTree to the context object for use in layouts.
-export default function currentProductTree(req, res, next) {
+export default async function currentProductTree(req, res, next) {
   if (!req.context.page) return next()
   if (req.context.page.documentType === 'homepage') return next()
 
@@ -20,13 +21,68 @@ export default function currentProductTree(req, res, next) {
       req.context.currentProduct
     )
   )
-  const currentProductTree = findPageInSiteTree(
+  req.context.currentProductTree = findPageInSiteTree(
     currentRootTree,
     req.context.currentEnglishTree,
     currentProductPath
   )
 
-  req.context.currentProductTree = currentProductTree
+  // First make a slim tree of just the 'href', 'title', 'shortTitle'
+  // 'documentType' and 'childPages' (which is recursive).
+  // This gets used for map topic and category pages.
+  req.context.currentProductTreeTitles = await getCurrentProductTreeTitles(
+    req.context.currentProductTree,
+    req.context
+  )
+  // Now make an even slimmer version that excludes all hidden pages.
+  // This is i used for sidebars.
+  req.context.currentProductTreeTitlesExcludeHidden = excludeHidden(
+    req.context.currentProductTreeTitles
+  )
 
   return next()
 }
+
+// Return a nested object that contains the bits and pieces we need
+// for the tree which is used for sidebars and listing
+async function getCurrentProductTreeTitles(input, context) {
+  const { page } = input
+  const childPages = await Promise.all(
+    (input.childPages || []).map((child) => getCurrentProductTreeTitles(child, context))
+  )
+
+  const renderedFullTitle = page.rawTitle.includes('{')
+    ? await liquid.parseAndRender(page.rawTitle, context)
+    : page.rawTitle
+  let renderedShortTitle = ''
+  if (page.rawShortTitle) {
+    renderedShortTitle = page.rawShortTitle.includes('{')
+      ? await liquid.parseAndRender(page.rawShortTitle, context)
+      : page.rawShortTitle
+  }
+
+  const node = {
+    href: input.href,
+    title: renderedFullTitle,
+    shortTitle:
+      renderedShortTitle && (renderedShortTitle || '') !== renderedFullTitle
+        ? renderedShortTitle
+        : '',
+    documentType: page.documentType,
+    childPages: childPages.filter(Boolean),
+  }
+  if (page.hidden) node.hidden = true
+  return node
+}
+
+function excludeHidden(tree) {
+  if (tree.hidden) return null
+  const newTree = {
+    href: tree.href,
+    title: tree.title,
+    shortTitle: tree.shortTitle,
+    documentType: tree.documentType,
+    childPages: tree.childPages.map(excludeHidden).filter(Boolean),
+  }
+  return newTree
+}
diff --git a/middleware/contextualizers/generic-toc.js b/middleware/contextualizers/generic-toc.js
index fb64cbfd26..569ed661d3 100644
--- a/middleware/contextualizers/generic-toc.js
+++ b/middleware/contextualizers/generic-toc.js
@@ -1,4 +1,5 @@
 import findPageInSiteTree from '../../lib/find-page-in-site-tree.js'
+import { liquid } from '../../lib/render-content/index.js'
 
 // This module adds either flatTocItems or nestedTocItems to the context object for
 // product, categorie, and map topic TOCs that don't have other layouts specified.
@@ -47,7 +48,7 @@ export default async function genericToc(req, res, next) {
   const isEarlyAccess = req.context.currentPath.includes('/early-access/')
   const isArticlesCategory = req.context.currentPath.endsWith('/articles')
 
-  req.context.showHiddenTocItems =
+  const includeHidden =
     earlyAccessToc || (isCategoryOrMapTopic && isEarlyAccess && !isArticlesCategory)
 
   // Conditionally run getTocItems() recursively.
@@ -59,49 +60,67 @@ export default async function genericToc(req, res, next) {
   if (currentTocType === 'flat' && !isOneOffProductToc) {
     isRecursive = false
     renderIntros = true
-    req.context.genericTocFlat = await getTocItems(
-      treePage.childPages,
-      req.context,
-      isRecursive,
-      renderIntros
-    )
+    req.context.genericTocFlat = []
+    req.context.genericTocFlat = await getTocItems(treePage, req.context, {
+      recurse: isRecursive,
+      renderIntros,
+      includeHidden,
+    })
   }
 
   // Get an array of child map topics and their child articles and add it to the context object.
   if (currentTocType === 'nested' || isOneOffProductToc) {
     isRecursive = !isOneOffProductToc
     renderIntros = false
-    req.context.genericTocNested = await getTocItems(
-      treePage.childPages,
-      req.context,
-      isRecursive,
-      renderIntros
-    )
+    req.context.genericTocNested = await getTocItems(treePage, req.context, {
+      recurse: isRecursive,
+      renderIntros,
+      includeHidden,
+    })
   }
 
   return next()
 }
 
-async function getTocItems(pagesArray, context, isRecursive, renderIntros) {
-  return (
-    await Promise.all(
-      pagesArray.map(async (child) => {
-        // only include a hidden page if showHiddenTocItems is true
-        if (child.page.hidden && !context.showHiddenTocItems) return
+// Return a nested object that contains the bits and pieces we need
+// for the tree which is used for sidebars and listing
+async function getTocItems(node, context, opts) {
+  // Cleaner than trying to be too terse inside the `.filter()` inline callback.
+  function filterHidden(child) {
+    return opts.includeHidden || !child.page.hidden
+  }
 
-        return {
-          title: child.renderedFullTitle,
-          fullPath: child.href,
-          // renderProp is the most expensive part of this function.
-          intro: renderIntros
-            ? await child.page.renderProp('intro', context, { unwrap: true })
-            : null,
-          childTocItems:
-            isRecursive && child.childPages
-              ? await getTocItems(child.childPages, context, isRecursive, renderIntros)
-              : null,
+  return await Promise.all(
+    node.childPages.filter(filterHidden).map(async (child) => {
+      const { page } = child
+      const title = page.rawTitle.includes('{')
+        ? await liquid.parseAndRender(page.rawTitle, context)
+        : page.rawTitle
+      let intro = null
+      if (opts.renderIntros) {
+        intro = ''
+        if (page.rawIntro) {
+          intro = page.rawIntro.includes('{')
+            ? await liquid.parseAndRender(page.rawIntro, context)
+            : page.rawIntro
         }
-      })
-    )
-  ).filter(Boolean)
+      }
+
+      let childTocItems = null
+      if (opts.recurse) {
+        childTocItems = []
+        if (child.childPages) {
+          childTocItems.push(...(await getTocItems(child, context, opts)))
+        }
+      }
+
+      const fullPath = child.href
+      return {
+        title,
+        fullPath,
+        intro,
+        childTocItems,
+      }
+    })
+  )
 }
diff --git a/middleware/index.js b/middleware/index.js
index dff852abe9..3a18593264 100644
--- a/middleware/index.js
+++ b/middleware/index.js
@@ -263,9 +263,9 @@ export default function (app) {
   app.use(instrument(webhooks, './contextualizers/webhooks'))
   app.use(asyncMiddleware(instrument(whatsNewChangelog, './contextualizers/whats-new-changelog')))
   app.use(instrument(layout, './contextualizers/layout'))
-  app.use(instrument(currentProductTree, './contextualizers/current-product-tree'))
+  app.use(asyncMiddleware(instrument(currentProductTree, './contextualizers/current-product-tree')))
   app.use(asyncMiddleware(instrument(genericToc, './contextualizers/generic-toc')))
-  app.use(asyncMiddleware(instrument(breadcrumbs, './contextualizers/breadcrumbs')))
+  app.use(instrument(breadcrumbs, './contextualizers/breadcrumbs'))
   app.use(instrument(features, './contextualizers/features'))
   app.use(asyncMiddleware(instrument(productExamples, './contextualizers/product-examples')))
   app.use(asyncMiddleware(instrument(productGroups, './contextualizers/product-groups')))
diff --git a/tests/content/site-tree.js b/tests/content/site-tree.js
index 8d930eb235..b12fb358c9 100644
--- a/tests/content/site-tree.js
+++ b/tests/content/site-tree.js
@@ -41,9 +41,6 @@ describe('siteTree', () => {
       expect(pageWithDynamicTitle.page.title).toEqual(
         'Installing {% data variables.product.prodname_enterprise %}'
       )
-
-      // Confirm a new property contains the rendered title
-      expect(pageWithDynamicTitle.renderedFullTitle).toEqual('Installing GitHub Enterprise')
     })
   })
 
diff --git a/tests/rendering/sidebar.js b/tests/rendering/sidebar.js
index d8bca619a0..9d4f05454e 100644
--- a/tests/rendering/sidebar.js
+++ b/tests/rendering/sidebar.js
@@ -173,4 +173,16 @@ describe('sidebar', () => {
       }
     }
   })
+  test("test a page where there's known sidebar short titles that use Liquid and ampersands", async () => {
+    const url =
+      '/en/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards'
+    const $ = await getDOM(url)
+    const linkTexts = []
+    $('[data-testid=sidebar]  a').each((i, element) => {
+      linkTexts.push($(element).text())
+    })
+    // This makes sure that none of the texts in there has their final HTML
+    // to be HTML entity encoded.
+    expect(linkTexts.filter((text) => text.includes('&amp;')).length).toBe(0)
+  })
 })
diff --git a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/permission-levels-for-a-personal-account-repository.md b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/permission-levels-for-a-personal-account-repository.md
index b02fa0533c..e113259b91 100644
--- a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/permission-levels-for-a-personal-account-repository.md
+++ b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/permission-levels-for-a-personal-account-repository.md
@@ -1,6 +1,6 @@
 ---
-title: Niveles de permisos para un repositorio de una cuenta personal
-intro: 'Un repositorio que pertenece a una cuenta personal tiene dos niveles de permiso: propietario del repositorio y colaboradores.'
+title: Permission levels for a personal account repository
+intro: 'A repository owned by a personal account has two permission levels: the repository owner and collaborators.'
 redirect_from:
   - /articles/permission-levels-for-a-user-account-repository
   - /github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository
@@ -14,84 +14,79 @@ versions:
 topics:
   - Accounts
 shortTitle: Repository permissions
-ms.openlocfilehash: e7c7a542204c7b1ce69bc19ac326fb248bbbff12
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
-ms.translationtype: HT
-ms.contentlocale: es-ES
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147066310'
 ---
-## Acerca de los niveles de permisos para un repositorio de una cuenta personal
+## About permissions levels for a personal account repository
 
-Los repositorios propiedad de las cuentas personales tienen un propietario. Los permisos de propiedad no se pueden compartir con otra cuenta personal.
+Repositories owned by personal accounts have one owner. Ownership permissions can't be shared with another personal account.
 
-También puede {% ifversion fpt or ghec %}invitar{% else %}agregar{% endif %} usuarios de {% data variables.product.product_name %} al repositorio como colaboradores. Para más información, vea "[Invitación de colaboradores a un repositorio personal](/github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository)".
+You can also {% ifversion fpt or ghec %}invite{% else %}add{% endif %} users on {% data variables.product.product_name %} to your repository as collaborators. For more information, see "[Inviting collaborators to a personal repository](/github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository)."
 
 {% tip %}
 
-**Sugerencia:** si necesitas un acceso más pormenorizado a un repositorio propiedad de tu cuenta personal, considera la posibilidad de transferir el repositorio a una organización. Para más información, vea "[Transferencia de un repositorio](/github/administering-a-repository/transferring-a-repository#transferring-a-repository-owned-by-your-personal-account)".
+**Tip:** If you require more granular access to a repository owned by your personal account, consider transferring the repository to an organization. For more information, see "[Transferring a repository](/github/administering-a-repository/transferring-a-repository#transferring-a-repository-owned-by-your-personal-account)."
 
 {% endtip %}
 
-## Acceso de propietarios a un repositorio propiedad de una cuenta personal
+## Owner access for a repository owned by a personal account
 
-El propietario del repositorio tiene control completo del repositorio. Adicionalmente a las acciones que pudiera realizar cualquier colaborador, el propietario del repositorio puede realizar las siguientes.
+The repository owner has full control of the repository. In addition to the actions that any collaborator can perform, the repository owner can perform the following actions.
 
-| Acción | Más información |
+| Action | More information |
 | :- | :- |
-| {% ifversion fpt or ghec %}Invitación a colaboradores{% else %}Adición de colaboradores{% endif %} | "[Invitación a colaboradores a un repositorio personal](/github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository)" |
-| Cambiar la visibilidad del repositorio | "[Configuración de la visibilidad de un repositorio](/github/administering-a-repository/setting-repository-visibility)" |{% ifversion fpt or ghec %}
-| Limitar las interacciones con el repositorio | "[Limitación de las interacciones en el repositorio](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository)" |{% endif %}
-| Renombrar una rama, incluyendo la rama predeterminada | "[Cambio del nombre de una rama](/github/administering-a-repository/renaming-a-branch)" |
-| Fusionar una solicitud de extracción sobre una rama protegida, incluso si no hay revisiones de aprobación | "[Acerca de las ramas protegidas](/github/administering-a-repository/about-protected-branches)" |
-| Eliminar el repositorio | "[Eliminación de un repositorio](/repositories/creating-and-managing-repositories/deleting-a-repository)" |
-| Administrar los temas del repositorio | "[Clasificación del repositorio con temas](/github/administering-a-repository/classifying-your-repository-with-topics)" |{% ifversion fpt or ghec %}
-| Administrar la seguridad y la configuración de análisis del repositorio | "[Administración de la configuración de seguridad y análisis para el repositorio](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)" |{% endif %}{% ifversion fpt or ghec %}
-| Habilitar la gráfica de dependencias para un repositorio privado | "[Exploración de las dependencias de un repositorio](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository#enabling-and-disabling-the-dependency-graph-for-a-private-repository)" |{% endif %}
-| Borrar y restaurar paquetes | "[Eliminación y restauración de un paquete](/packages/learn-github-packages/deleting-and-restoring-a-package)" |
-| Personalizar la vista previa de las redes sociales de un repositorio | "[Personalización de la vista previa de las redes sociales del repositorio ](/github/administering-a-repository/customizing-your-repositorys-social-media-preview)" |
-| Crear una plantilla del repositorio | "[Creación de un repositorio de plantillas](/github/creating-cloning-and-archiving-repositories/creating-a-template-repository)" |
-| Controlar el acceso a las {% data variables.product.prodname_dependabot_alerts %}| "[Administración de la configuración de seguridad y análisis para el repositorio](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts)" |{% ifversion fpt or ghec %}
-| Descartar las {% data variables.product.prodname_dependabot_alerts %} en el repositorio | "[Visualización y actualización de {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts)" |
-| Administrar el uso de datos para un repositorio privado | "[Administración de la configuración de uso de datos para el repositorio privado](/get-started/privacy-on-github/managing-data-use-settings-for-your-private-repository)"|{% endif %}
-| Definir propietarios del código para un repositorio | "[Acerca de los propietarios de código](/github/creating-cloning-and-archiving-repositories/about-code-owners)" |
-| Archivar el repositorio | "[Archivado de repositorios](/repositories/archiving-a-github-repository/archiving-repositories)" |{% ifversion fpt or ghec %}
-| Creación de avisos de seguridad | "[Acerca de {% data variables.product.prodname_security_advisories %}](/github/managing-security-vulnerabilities/about-github-security-advisories)" |
-| Representación de un botón de patrocinador | "[Representación de un botón de patrocinador en el repositorio](/github/administering-a-repository/displaying-a-sponsor-button-in-your-repository)" |{% endif %}
-| Permitir o dejar de permitir la fusión automática para las solicitudes de cambios | "[Administración de la combinación automática para las solicitudes de incorporación de cambios en el repositorio](/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository)" | 
+| {% ifversion fpt or ghec %}Invite collaborators{% else %}Add collaborators{% endif %} | "[Inviting collaborators to a personal repository](/github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository)" |
+| Change the visibility of the repository | "[Setting repository visibility](/github/administering-a-repository/setting-repository-visibility)" |{% ifversion fpt or ghec %}
+| Limit interactions with the repository | "[Limiting interactions in your repository](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository)" |{% endif %}
+| Rename a branch, including the default branch | "[Renaming a branch](/github/administering-a-repository/renaming-a-branch)" |
+| Merge a pull request on a protected branch, even if there are no approving reviews | "[About protected branches](/github/administering-a-repository/about-protected-branches)" |
+| Delete the repository | "[Deleting a repository](/repositories/creating-and-managing-repositories/deleting-a-repository)" |
+| Manage the repository's topics | "[Classifying your repository with topics](/github/administering-a-repository/classifying-your-repository-with-topics)" |{% ifversion fpt or ghec %}
+| Manage security and analysis settings for the repository | "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)" |{% endif %}{% ifversion fpt or ghec %}
+| Enable the dependency graph for a private repository | "[Exploring the dependencies of a repository](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository#enabling-and-disabling-the-dependency-graph-for-a-private-repository)" |{% endif %}
+| Delete and restore packages | "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)" |
+| 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)" |
+| Control access to {% data variables.product.prodname_dependabot_alerts %}| "[Managing security and analysis settings for your repository](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts)" |{% ifversion fpt or ghec %}
+| Dismiss {% data variables.product.prodname_dependabot_alerts %} in the repository | "[Viewing and updating {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts)" |
+| Manage data use for a private repository | "[Managing data use settings for your private repository](/get-started/privacy-on-github/managing-data-use-settings-for-your-private-repository)"|{% endif %}
+| Define code owners for the repository | "[About code owners](/github/creating-cloning-and-archiving-repositories/about-code-owners)" |
+| Archive the repository | "[Archiving repositories](/repositories/archiving-a-github-repository/archiving-repositories)" |{% ifversion fpt or ghec %}
+| Create security advisories | "[About repository security advisories](/github/managing-security-vulnerabilities/about-github-security-advisories)" |
+| Display a sponsor button | "[Displaying a sponsor button in your repository](/github/administering-a-repository/displaying-a-sponsor-button-in-your-repository)" |{% endif %}
+| Allow or disallow auto-merge for pull requests | "[Managing auto-merge for pull requests in your repository](/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository)" | 
+| Manage webhooks and deploy keys	| "[Managing deploy keys](/developers/overview/managing-deploy-keys#deploy-keys)" |
 
-## Acceso de colaboradores a un repositorio propiedad de una cuenta personal
+## Collaborator access for a repository owned by a personal account
 
-Los colaboradores de un repositorio personal pueden extraer (leer) el contienido del mismo y subir (escribir) los cambios al repositorio.
+Collaborators on a personal repository can pull (read) the contents of the repository and push (write) changes to the repository.
 
 {% note %}
 
-**Nota:** En un repositorio privado, los propietarios del repositorio solo pueden conceder acceso de escritura a los colaboradores. Los colaboradores no pueden tener acceso de solo lectura a los repositorios propiedad de una cuenta personal.
+**Note:** In a private repository, repository owners can only grant write access to collaborators. Collaborators can't have read-only access to repositories owned by a personal account.
 
 {% endnote %}
 
-Los colaboradores también pueden realizar las siguientes acciones.
+Collaborators can also perform the following actions.
 
-| Acción | Más información |
+| Action | More information |
 | :- | :- |
-| Bifurcar el repositorio | "[Acerca de las bifurcaciones](/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks)" |
-| Renombrar una rama diferente a la predeterminada | "[Cambio del nombre de una rama](/github/administering-a-repository/renaming-a-branch)" |
-| Crear, editar, y borrar comentarios en las confirmaciones, solicitudes de cambios y propuestas del repositorio | <ul><li>"[Acerca de las incidencias](/github/managing-your-work-on-github/about-issues)"</li><li>"[Comentario de una solicitud de incorporación de cambios](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request)"</li><li>"[Administración de comentarios negativos](/communities/moderating-comments-and-conversations/managing-disruptive-comments)"</li></ul> |
-| Crear, asignar, cerrar y volver a abrir las propuestas en el repositorio | "[Administración del trabajo con incidencias](/github/managing-your-work-on-github/managing-your-work-with-issues)" |
-| Administrar las etiquetas para las propuestas y solicitudes de cambios en el repositorio | "[Etiquetado de incidencias y solicitudes de incorporación de cambios](/github/managing-your-work-on-github/labeling-issues-and-pull-requests)" |
-| Administrar hitos para las propuestas y solicitudes de cambios en el repositorio | "[Creación y edición de hitos para incidencias y solicitudes de incorporación de cambios](/github/managing-your-work-on-github/creating-and-editing-milestones-for-issues-and-pull-requests)" |
-| Marcar una propuesta o solicitud de cambios en el repositorio como duplicada | "[Acerca de incidencias duplicadas y solicitudes de incorporación de cambios](/github/managing-your-work-on-github/about-duplicate-issues-and-pull-requests)" |
-| Crear, fusionar y cerrar las solicitudes de cambios en el repositorio | "[Propuesta de cambios en el trabajo con solicitudes de incorporación de cambios](/github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests)" |
-| Habilitar e inhabilitar la fusión automática para una solicitud de cambios | "[Combinación automática de una solicitud de incorporación de cambios](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request)"
-| Aplicar los cambios sugeridos a las solicitudes de cambios en el repositorio |"[Incorporación de comentarios en la solicitud de incorporación de cambios](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/incorporating-feedback-in-your-pull-request)" |
-| Crear una solicitud de cambios desde una bifurcación del repositorio | "[Creación de una solicitud de incorporación de cambios desde una bifurcación](/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request-from-a-fork)" |
-| Emitir una revisión de una solicitud de cambios que afecte la capacidad de fusión de una solicitud de cambios | "[Revisión de los cambios propuestos en una solicitud de incorporación de cambios](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request)" |
-| Crear y editar un wiki para el repositorio | "[Acerca de las wikis](/communities/documenting-your-project-with-wikis/about-wikis)" |
-| Crear y editar los lanzamientos del repositorio | "[Administración de versiones en un repositorio](/github/administering-a-repository/managing-releases-in-a-repository)" |
-| Actuar como propietario del código del repositorio | "[Acerca de los propietarios de código](/articles/about-code-owners)" |{% ifversion fpt or ghae or ghec %}
-| Publicar, ver o instalar paquetes | "[Publicación y administración de paquetes](/github/managing-packages-with-github-packages/publishing-and-managing-packages)" |{% endif %}
-| Eliminarse como colaboradores del repositorio | "[Eliminarse del repositorio de un colaborador](/github/setting-up-and-managing-your-github-user-account/removing-yourself-from-a-collaborators-repository)" |
+| Fork the repository | "[About forks](/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks)" |
+| Rename a branch other than the default branch | "[Renaming a branch](/github/administering-a-repository/renaming-a-branch)" |
+| Create, edit, and delete comments on commits, pull requests, and issues in the repository | <ul><li>"[About issues](/github/managing-your-work-on-github/about-issues)"</li><li>"[Commenting on a pull request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request)"</li><li>"[Managing disruptive comments](/communities/moderating-comments-and-conversations/managing-disruptive-comments)"</li></ul> |
+| Create, assign, close, and re-open issues in the repository | "[Managing your work with issues](/github/managing-your-work-on-github/managing-your-work-with-issues)" |
+| Manage labels for issues and pull requests in the repository | "[Labeling issues and pull requests](/github/managing-your-work-on-github/labeling-issues-and-pull-requests)" |
+| Manage milestones for issues and pull requests in the repository | "[Creating and editing milestones for issues and pull requests](/github/managing-your-work-on-github/creating-and-editing-milestones-for-issues-and-pull-requests)" |
+| Mark an issue or pull request in the repository as a duplicate | "[About duplicate issues and pull requests](/github/managing-your-work-on-github/about-duplicate-issues-and-pull-requests)" |
+| Create, merge, and close pull requests in the repository | "[Proposing changes to your work with pull requests](/github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests)" |
+| Enable and disable auto-merge for a pull request | "[Automatically merging a pull request](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request)"
+| Apply suggested changes to pull requests in the repository |"[Incorporating feedback in your pull request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/incorporating-feedback-in-your-pull-request)" |
+| Create a pull request from a fork of the repository | "[Creating a pull request from a fork](/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request-from-a-fork)" |
+| Submit a review on a pull request that affects the mergeability of the pull request | "[Reviewing proposed changes in a pull request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request)" |
+| Create and edit a wiki for the repository | "[About wikis](/communities/documenting-your-project-with-wikis/about-wikis)" |
+| Create and edit releases for the repository | "[Managing releases in a repository](/github/administering-a-repository/managing-releases-in-a-repository)" |
+| Act as a code owner for the repository | "[About code owners](/articles/about-code-owners)" |{% ifversion fpt or ghae or ghec %}
+| Publish, view, or install packages | "[Publishing and managing packages](/github/managing-packages-with-github-packages/publishing-and-managing-packages)" |{% endif %}
+| Remove themselves as collaborators on the repository | "[Removing yourself from a collaborator's repository](/github/setting-up-and-managing-your-github-user-account/removing-yourself-from-a-collaborators-repository)" |
 
-## Información adicional
+## Further reading
 
-- "[Roles de repositorio para una organización](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)"
+- "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)"
diff --git a/translations/es-ES/content/actions/examples/using-the-github-cli-on-a-runner.md b/translations/es-ES/content/actions/examples/using-the-github-cli-on-a-runner.md
index 351014a933..93a362c44b 100644
--- a/translations/es-ES/content/actions/examples/using-the-github-cli-on-a-runner.md
+++ b/translations/es-ES/content/actions/examples/using-the-github-cli-on-a-runner.md
@@ -1,7 +1,7 @@
 ---
-title: Using the GitHub CLI on a runner
+title: Uso de la CLI de GitHub en un ejecutor
 shortTitle: Use the GitHub CLI on a runner
-intro: 'How to use advanced {% data variables.product.prodname_actions %} features for continuous integration (CI).'
+intro: 'Cómo usar características avanzadas de {% data variables.product.prodname_actions %} para la integración continua (CI).'
 versions:
   fpt: '*'
   ghes: '> 3.1'
@@ -10,40 +10,34 @@ versions:
 type: how_to
 topics:
   - Workflows
+ms.openlocfilehash: e0787d09cd194de0038d259c1aff777cc91a4a6a
+ms.sourcegitcommit: bf11c3e08cbb5eab6320e0de35b32ade6d863c03
+ms.translationtype: HT
+ms.contentlocale: es-ES
+ms.lasthandoff: 10/27/2022
+ms.locfileid: '148111589'
 ---
-
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Example overview
+## Información general de ejemplo
 
-{% data reusables.actions.example-workflow-intro-ci %} When this workflow is triggered, it automatically runs a script that checks whether the {% data variables.product.prodname_dotcom %} Docs site has any broken links. If any broken links are found, the workflow uses the {% data variables.product.prodname_dotcom %} CLI to create a {% data variables.product.prodname_dotcom %} issue with the details.
+{% data reusables.actions.example-workflow-intro-ci %} Cuando se desencadena este flujo de trabajo, ejecuta automáticamente un script que comprueba si el sitio de {% data variables.product.prodname_dotcom %} Docs tienen vínculos rotos. Si se encuentran vínculos rotos, el flujo de trabajo usa la CLI de {% data variables.product.prodname_dotcom %} para crear una incidencia de {% data variables.product.prodname_dotcom %} con los detalles.
 
 {% data reusables.actions.example-diagram-intro %}
 
-![Overview diagram of workflow steps](/assets/images/help/images/overview-actions-using-cli-ci-example.png)
+![Diagrama general de los pasos del flujo de trabajo](/assets/images/help/images/overview-actions-using-cli-ci-example.png)
 
-## Features used in this example
+## Características que se usan en este ejemplo
 
 {% data reusables.actions.example-table-intro %}
 
-| **Feature**  | **Implementation** |
+| **Característica**  | **Implementación** |
 | --- | --- |
-{% data reusables.actions.cron-table-entry %}
-{% data reusables.actions.permissions-table-entry %}
-{% data reusables.actions.if-conditions-table-entry %}
-{% data reusables.actions.secrets-table-entry %}
-{% data reusables.actions.checkout-action-table-entry %}
-{% data reusables.actions.setup-node-table-entry %}
-| Using a third-party action: | [`peter-evans/create-issue-from-file`](https://github.com/peter-evans/create-issue-from-file)|
-| Running shell commands on the runner: | [`run`](/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idstepsrun) |
-| Running a script on the runner: | Using `script/check-english-links.js` |
-| Generating an output file: | Piping the output using the `>` operator |
-| Checking for existing issues using {% data variables.product.prodname_cli %}: | [`gh issue list`](https://cli.github.com/manual/gh_issue_list) |
-| Commenting on an issue using {% data variables.product.prodname_cli %}: | [`gh issue comment`](https://cli.github.com/manual/gh_issue_comment) |
+{% data reusables.actions.cron-table-entry %} {% data reusables.actions.permissions-table-entry %} {% data reusables.actions.if-conditions-table-entry %} {% data reusables.actions.secrets-table-entry %} {% data reusables.actions.checkout-action-table-entry %} {% data reusables.actions.setup-node-table-entry %} | Uso de una acción de terceros: | [`peter-evans/create-issue-from-file`](https://github.com/peter-evans/create-issue-from-file)| | Ejecución de comandos de shell en el ejecutor: | [`run`](/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idstepsrun) | | Ejecución de un script en el ejecutor: | Uso de `script/check-english-links.js` | | Generación de un archivo de salida: | Canalización de la salida mediante el operador `>` | | Comprobación de incidencias existentes mediante la {% data variables.product.prodname_cli %}: | [`gh issue list`](https://cli.github.com/manual/gh_issue_list) | | Realización de comentarios sobre una incidencia mediante la {% data variables.product.prodname_cli %}: | [`gh issue comment`](https://cli.github.com/manual/gh_issue_comment) |
 
-## Example workflow
+## Flujo de trabajo de ejemplo
 
-{% data reusables.actions.example-docs-engineering-intro %} [`check-all-english-links.yml`](https://github.com/github/docs/blob/main/.github/workflows/check-all-english-links.yml).
+{% data reusables.actions.example-docs-engineering-intro %} [`check-all-english-links.yml`](https://github.com/github/docs/blob/6e01c0653836c10d7e092a17566a2c88b10504ce/.github/workflows/check-all-english-links.yml).
 
 {% data reusables.actions.note-understanding-example %}
 
@@ -178,15 +172,15 @@ jobs:
 </tbody>
 </table>
 
-## Understanding the example
+## Descripción del ejemplo
 
 {% data reusables.actions.example-explanation-table-intro %}
 
 <table style="table-layout: fixed;">
 <thead>
   <tr>
-    <th style="width:60%"><b>Code</b></th>
-    <th style="width:40%"><b>Explanation</b></th>
+    <th style="width:60%"><b>Código</b></th>
+    <th style="width:40%"><b>Explicación</b></th>
   </tr>
 </thead>
 <tbody>
@@ -214,10 +208,10 @@ on:
 </td>
 <td>
 
-Defines the `workflow_dispatch` and `scheduled` as triggers for the workflow:
+Define `workflow_dispatch` y `scheduled` como desencadenadores para el flujo de trabajo:
 
-* The `workflow_dispatch` lets you manually run this workflow from the UI. For more information, see [`workflow_dispatch`](/actions/using-workflows/events-that-trigger-workflows#workflow_dispatch).
-* The `schedule` event lets you use `cron` syntax to define a regular interval for automatically triggering the workflow. For more information, see [`schedule`](/actions/reference/events-that-trigger-workflows#schedule).
+* `workflow_dispatch` permite ejecutar manualmente este flujo de trabajo desde la interfaz de usuario. Para más información, vea [`workflow_dispatch`](/actions/using-workflows/events-that-trigger-workflows#workflow_dispatch).
+* El evento `schedule` permite usar la sintaxis `cron` para definir un intervalo regular para desencadenar automáticamente el flujo de trabajo. Para más información, vea [`schedule`](/actions/reference/events-that-trigger-workflows#schedule).
 </td>
 </tr>
 <tr>
@@ -231,7 +225,7 @@ permissions:
 </td>
 <td>
 
-Modifies the default permissions granted to `GITHUB_TOKEN`. This will vary depending on the needs of your workflow. For more information, see "[Assigning permissions to jobs](/actions/using-jobs/assigning-permissions-to-jobs)."
+Modifica los permisos predeterminados concedidos a `GITHUB_TOKEN`. Esto variará en función de las necesidades del flujo de trabajo. Para obtener más información, consulta "[Asignación de permisos a trabajos](/actions/using-jobs/assigning-permissions-to-jobs)".
 </td>
 </tr>
 <tr>
@@ -243,7 +237,7 @@ jobs:
 </td>
 <td>
 
-Groups together all the jobs that run in the workflow file.
+Agrupa todos los trabajos que se ejecutan en el archivo de flujo de trabajo.
 </td>
 </tr>
 <tr>
@@ -256,7 +250,7 @@ Groups together all the jobs that run in the workflow file.
 </td>
 <td>
 
-Defines a job with the ID `check_all_english_links`, and the name `Check all links`, that is stored within the `jobs` key.
+Define un trabajo con el identificador `check_all_english_links` y el nombre `Check all links`, que se almacena en la clave `jobs`.
 </td>
 </tr>
 <tr>
@@ -268,7 +262,7 @@ if: github.repository == 'github/docs-internal'
 </td>
 <td>
 
-Only run the `check_all_english_links` job if the repository is named `docs-internal` and is within the `github` organization. Otherwise, the job is marked as _skipped_.
+El trabajo `check_all_english_links` solo se ejecuta si el repositorio se denomina `docs-internal` y está dentro de la organización `github`. De lo contrario, el trabajo se marca como _omitido_.
 </td>
 </tr>
 <tr>
@@ -280,7 +274,7 @@ runs-on: ubuntu-latest
 </td>
 <td>
 
-Configures the job to run on an Ubuntu Linux runner. This means that the job will execute on a fresh virtual machine hosted by {% data variables.product.prodname_dotcom %}. For syntax examples using other runners, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idruns-on)."
+Configura el job para ejecutarse en un ejecutor Ubuntu Linux. Esto significa que el trabajo se ejecutará en una máquina virtual nueva que se hospede en {% data variables.product.prodname_dotcom %}. Para obtener ejemplos de sintaxis con otros ejecutores, consulta «[Sintaxis de flujo de trabajo para {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idruns-on)».
 </td>
 </tr>
 <tr>
@@ -296,7 +290,7 @@ Configures the job to run on an Ubuntu Linux runner. This means that the job wil
 </td>
 <td>
 
-Creates custom environment variables, and redefines the built-in `GITHUB_TOKEN` variable to use a custom [secret](/actions/security-guides/encrypted-secrets). These variables will be referenced later in the workflow.
+Crea variables de entorno personalizadas y vuelve a definir la variable `GITHUB_TOKEN` integrada para usar un [secreto](/actions/security-guides/encrypted-secrets) personalizado. Se hará referencia a estas variables más adelante en el flujo de trabajo.
 </td>
 </tr>
 <tr>
@@ -308,7 +302,7 @@ Creates custom environment variables, and redefines the built-in `GITHUB_TOKEN`
 </td>
 <td>
 
-Groups together all the steps that will run as part of the `check_all_english_links` job. Each job in the workflow has its own `steps` section.
+Agrupa todos los pasos que se ejecutarán como parte del trabajo `check_all_english_links`. Cada trabajo del flujo de trabajo tiene su propia sección `steps`.
 </td>
 </tr>
 <tr>
@@ -321,7 +315,7 @@ Groups together all the steps that will run as part of the `check_all_english_li
 </td>
 <td>
 
-The `uses` keyword tells the job to retrieve the action named `actions/checkout`. This is an action that checks out your repository and downloads it to the runner, allowing you to run actions against your code (such as testing tools). You must use the checkout action any time your workflow will run against the repository's code or you are using an action defined in the repository.
+La palabra clave `uses` le indica al trabajo que recupere la acción denominada `actions/checkout`. Esta es una acción que revisa tu repositorio y lo descarga al ejecutor, lo que te permite ejecutar acciones contra tu código (tales como las herramientas de prueba). Debes utilizar la acción de verificación cada que tu flujo de trabajo se ejecute contra el código del repositorio o cada que estés utilizando una acción definida en el repositorio.
 </td>
 </tr>
 <tr>
@@ -337,7 +331,7 @@ The `uses` keyword tells the job to retrieve the action named `actions/checkout`
 </td>
 <td>
 
-This step uses the `actions/setup-node` action to install the specified version of the `node` software package on the runner, which gives you access to the `npm` command.
+En este paso, se usa la acción `actions/setup-node` para instalar la versión especificada del paquete de software `node` en el ejecutor, lo que te da acceso al comando `npm`.
 </td>
 </tr>
 <tr>
@@ -352,7 +346,7 @@ This step uses the `actions/setup-node` action to install the specified version
 </td>
 <td>
 
-The `run` keyword tells the job to execute a command on the runner. In this case, the `npm ci` and `npm run build` commands are run as separate steps to install and build the Node.js application in the repository.
+La palabra clave `run` indica al trabajo que ejecute un comando en el ejecutor. En este caso, los comandos `npm ci` y `npm run build` se ejecutan como pasos independientes para instalar y compilar la aplicación Node.js en el repositorio.
 </td>
 </tr>
 <tr>
@@ -366,7 +360,7 @@ The `run` keyword tells the job to execute a command on the runner. In this case
 </td>
 <td>
 
-This `run` command executes a script that is stored in the repository at `script/check-english-links.js`, and pipes the output to a file called `broken_links.md`.
+Este comando `run` ejecuta un script que se almacena en el repositorio en `script/check-english-links.js` y canaliza la salida a un archivo denominado `broken_links.md`.
 </td>
 </tr>
 <tr>
@@ -385,7 +379,7 @@ This `run` command executes a script that is stored in the repository at `script
 </td>
 <td>
 
-If the `check-english-links.js` script detects broken links and returns a non-zero (failure) exit status, then use a [workflow command](/actions/using-workflows/workflow-commands-for-github-actions#setting-an-output-parameter) to set an output that has the value of the first line of the `broken_links.md` file (this is used the next step).
+Si el script `check-english-links.js` detecta vínculos rotos y devuelve un estado de salida distinto de cero (error), usa un [comando de flujo de trabajo](/actions/using-workflows/workflow-commands-for-github-actions#setting-an-output-parameter) para establecer una salida que tenga el valor de la primera línea del archivo `broken_links.md` (se usa el paso siguiente).
 </td>
 </tr>
 <tr>
@@ -407,7 +401,7 @@ If the `check-english-links.js` script detects broken links and returns a non-ze
 </td>
 <td>
 
-Uses the `peter-evans/create-issue-from-file` action to create a new {% data variables.product.prodname_dotcom %} issue. This example is pinned to a specific version of the action, using the `b4f9ee0a9d4abbfc6986601d9b1a4f8f8e74c77e` SHA.
+Usa la acción `peter-evans/create-issue-from-file` para crear una incidencia de {% data variables.product.prodname_dotcom %}. Este ejemplo se ancla a una versión específica de la acción mediante el SHA `b4f9ee0a9d4abbfc6986601d9b1a4f8f8e74c77e`.
 </td>
 </tr>
 <tr>
@@ -435,9 +429,9 @@ Uses the `peter-evans/create-issue-from-file` action to create a new {% data var
 </td>
 <td>
 
-Uses [`gh issue list`](https://cli.github.com/manual/gh_issue_list) to locate the previously created issue from earlier runs. This is [aliased](https://cli.github.com/manual/gh_alias_set) to `gh list-reports` for simpler processing in later steps. To get the issue URL, the `jq` expression processes the resulting JSON output.
+Usa [`gh issue list`](https://cli.github.com/manual/gh_issue_list) para buscar la incidencia creada previamente a partir de ejecuciones anteriores. Se le asigna el [alias](https://cli.github.com/manual/gh_alias_set) `gh list-reports` para facilitar el procesamiento en pasos posteriores. Para obtener la dirección URL de la incidencia, la expresión `jq` procesa la salida JSON resultante.
 
-[`gh issue comment`](https://cli.github.com/manual/gh_issue_comment) is then used to add a comment to the new issue that links to the previous one.
+Después, se usa [`gh issue comment`](https://cli.github.com/manual/gh_issue_comment) para agregar un comentario a la nueva incidencia que vincula a la anterior.
 </td>
 </tr>
 <tr>
@@ -455,7 +449,7 @@ Uses [`gh issue list`](https://cli.github.com/manual/gh_issue_list) to locate th
 </td>
 <td>
 
-If an issue from a previous run is open and assigned to someone, then use [`gh issue comment`](https://cli.github.com/manual/gh_issue_comment) to add a comment with a link to the new issue.
+Si una incidencia de una ejecución anterior está abierta y asignada a alguien, usa [`gh issue comment`](https://cli.github.com/manual/gh_issue_comment) para agregar un comentario con un vínculo a la nueva incidencia.
 </td>
 </tr>
 <tr>
@@ -476,16 +470,16 @@ If an issue from a previous run is open and assigned to someone, then use [`gh i
 </td>
 <td>
 
-If an issue from a previous run is open and is not assigned to anyone, then:
+Si una incidencia de una ejecución anterior está abierta y no está asignada a nadie, haz lo siguiente:
 
-* Use [`gh issue comment`](https://cli.github.com/manual/gh_issue_comment) to add a comment with a link to the new issue.
-* Use [`gh issue close`](https://cli.github.com/manual/gh_issue_close) to close the old issue.
-* Use [`gh issue edit`](https://cli.github.com/manual/gh_issue_edit) to edit the old issue to remove it from a specific {% data variables.product.prodname_dotcom %} project board.
+* Usa [`gh issue comment`](https://cli.github.com/manual/gh_issue_comment) para agregar un comentario con un vínculo a la nueva incidencia.
+* Usa [`gh issue close`](https://cli.github.com/manual/gh_issue_close) para cerrar la incidencia antigua.
+* Usa [`gh issue edit`](https://cli.github.com/manual/gh_issue_edit) para editar la incidencia antigua y quitarla de un panel de proyecto específico de {% data variables.product.prodname_dotcom %}.
 </td>
 </tr>
 </tbody>
 </table>
 
-## Next steps
+## Pasos siguientes
 
 {% data reusables.actions.learning-actions %}
diff --git a/translations/es-ES/content/actions/using-workflows/workflow-commands-for-github-actions.md b/translations/es-ES/content/actions/using-workflows/workflow-commands-for-github-actions.md
index 61b705ee40..710052edb7 100644
--- a/translations/es-ES/content/actions/using-workflows/workflow-commands-for-github-actions.md
+++ b/translations/es-ES/content/actions/using-workflows/workflow-commands-for-github-actions.md
@@ -581,6 +581,8 @@ console.log("The running PID from the main action is: " +  process.env.STATE_pro
 
 During the execution of a workflow, the runner generates temporary files that can be used to perform certain actions. The path to these files are exposed via environment variables. You will need to use UTF-8 encoding when writing to these files to ensure proper processing of the commands. Multiple commands can be written to the same file, separated by newlines.
 
+Most commands in the following examples use double quotes for echoing strings, which will attempt to interpolate characters like `$` for shell variable names. To always use literal values in quoted strings, you can use single quotes instead.
+
 {% powershell %}
 
 {% note %}
diff --git a/translations/es-ES/content/admin/index.md b/translations/es-ES/content/admin/index.md
index 5fc77c32b6..916f323282 100644
--- a/translations/es-ES/content/admin/index.md
+++ b/translations/es-ES/content/admin/index.md
@@ -125,11 +125,11 @@ children:
   - /guides
   - /release-notes
   - /all-releases
-ms.openlocfilehash: ebd1473538d42928ff3d9abb3c0e2bd9f12767f5
-ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.openlocfilehash: 3980ad01e56bf1e38dd6473c5e5246c6d45350eb
+ms.sourcegitcommit: 3268914369fb29540e4d88ee5e56bc7a41f2a60e
 ms.translationtype: HT
 ms.contentlocale: es-ES
-ms.lasthandoff: 09/11/2022
-ms.locfileid: '147881159'
+ms.lasthandoff: 10/26/2022
+ms.locfileid: '148111316'
 ---
 
diff --git a/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-the-codeql-workflow-for-compiled-languages.md b/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-the-codeql-workflow-for-compiled-languages.md
index 242ee8f56a..1220575d5d 100644
--- a/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-the-codeql-workflow-for-compiled-languages.md
+++ b/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-the-codeql-workflow-for-compiled-languages.md
@@ -125,8 +125,8 @@ After removing the `autobuild` step, uncomment the `run` step and add build comm
 
 ``` yaml
 - run: |
-  make bootstrap
-  make release
+    make bootstrap
+    make release
 ```
 
 For more information about the `run` keyword, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepsrun)."
diff --git a/translations/es-ES/content/code-security/dependabot/dependabot-alerts/browsing-security-advisories-in-the-github-advisory-database.md b/translations/es-ES/content/code-security/dependabot/dependabot-alerts/browsing-security-advisories-in-the-github-advisory-database.md
deleted file mode 100644
index 663dc63e1b..0000000000
--- a/translations/es-ES/content/code-security/dependabot/dependabot-alerts/browsing-security-advisories-in-the-github-advisory-database.md
+++ /dev/null
@@ -1,188 +0,0 @@
----
-title: Browsing security advisories in the GitHub Advisory Database
-intro: 'You can browse the {% data variables.product.prodname_advisory_database %} to find advisories for security risks in open source projects that are hosted on {% data variables.product.company_short %}.'
-shortTitle: Browse Advisory Database
-miniTocMaxHeadingLevel: 3
-redirect_from:
-  - /github/managing-security-vulnerabilities/browsing-security-vulnerabilities-in-the-github-advisory-database
-  - /code-security/supply-chain-security/browsing-security-vulnerabilities-in-the-github-advisory-database
-  - /code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/browsing-security-vulnerabilities-in-the-github-advisory-database
-  - /code-security/dependabot/dependabot-alerts/browsing-security-vulnerabilities-in-the-github-advisory-database
-versions:
-  fpt: '*'
-  ghec: '*'
-  ghes: '*'
-  ghae: '*'
-type: how_to
-topics:
-  - Security advisories
-  - Alerts
-  - Dependabot
-  - Vulnerabilities
-  - CVEs
----
-<!--Marketing-LINK: From /features/security/software-supply-chain page "Browsing security vulnerabilities in the GitHub Advisory Database".-->
-
-## About the {% data variables.product.prodname_advisory_database %}
-
-The {% data variables.product.prodname_advisory_database %} contains a list of known security vulnerabilities {% ifversion GH-advisory-db-supports-malware %}and malware, {% endif %}grouped in two categories: {% data variables.product.company_short %}-reviewed advisories and unreviewed advisories.
-
-{% data reusables.repositories.tracks-vulnerabilities %}
-
-## About types of security advisories
-
-{% data reusables.advisory-database.beta-malware-advisories %}
-
-Each advisory in the {% data variables.product.prodname_advisory_database %} is for a vulnerability in open source projects{% ifversion GH-advisory-db-supports-malware %} or for malicious open source software{% endif %}. 
-
-{% data reusables.repositories.a-vulnerability-is %} Vulnerabilities in code are usually introduced by accident and fixed soon after they are discovered. You should update your code to use the fixed version of the dependency as soon as it is available.
-
-{% ifversion GH-advisory-db-supports-malware %}
-
-In contrast, malicious software, or malware, is code that is intentionally designed to perform unwanted or harmful functions. The malware may target hardware, software, confidential data, or users of any application that uses the malware. You need to remove the malware from your project and find an alternative, more secure replacement for the dependency.
-
-{% endif %}
-
-### {% data variables.product.company_short %}-reviewed advisories
-
-{% data variables.product.company_short %}-reviewed advisories are security vulnerabilities{% ifversion GH-advisory-db-supports-malware %} or malware{% endif %} that have been mapped to packages in ecosystems we support. We carefully review each advisory for validity and ensure that they have a full description, and contain both ecosystem and package information.
-
-Generally, we name our supported ecosystems after the software programming language's associated package registry. We review advisories if they are for a vulnerability in a package that comes from a supported registry.
-
-- Composer (registry: https://packagist.org/){% ifversion GH-advisory-db-erlang-support %}
-- Erlang (registry: https://hex.pm/){% endif %}
-- Go (registry: https://pkg.go.dev/)
-{%- ifversion fpt or ghec or ghes > 3.6 or ghae > 3.6 %}
-- GitHub Actions (https://github.com/marketplace?type=actions/) {% endif %}
-- Maven (registry: https://repo.maven.apache.org/maven2)
-- npm (registry: https://www.npmjs.com/)
-- NuGet (registry: https://www.nuget.org/)
-- pip (registry: https://pypi.org/){% ifversion dependency-graph-dart-support %}
-- pub (registry: https://pub.dev/packages/registry){% endif %}
-- RubyGems (registry: https://rubygems.org/)
-- Rust (registry: https://crates.io/)
-
-If you have a suggestion for a new ecosystem we should support, please open an [issue](https://github.com/github/advisory-database/issues) for discussion.
-
-If you enable {% data variables.product.prodname_dependabot_alerts %} for your repositories, you are automatically notified when a new {% data variables.product.company_short %}-reviewed advisory reports a vulnerability {% ifversion GH-advisory-db-supports-malware %}or malware{% endif %} for a package you depend on. For more information, see "[About {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)."
-
-### Unreviewed advisories
-
-Unreviewed advisories are security vulnerabilites that we publish automatically into the {% data variables.product.prodname_advisory_database %}, directly from the National Vulnerability Database feed. 
-
-{% data variables.product.prodname_dependabot %} doesn't create {% data variables.product.prodname_dependabot_alerts %} for unreviewed advisories as this type of advisory isn't checked for validity or completion.
-
-## About information in security advisories
-
-Each security advisory contains information about the vulnerability{% ifversion GH-advisory-db-supports-malware %} or malware,{% endif %} which may include the description, severity, affected package, package ecosystem, affected versions and patched versions, impact, and optional information such as references, workarounds, and credits. In addition, advisories from the National Vulnerability Database list contain a link to the CVE record, where you can read more details about the vulnerability, its CVSS scores, and its qualitative severity level. For more information, see the "[National Vulnerability Database](https://nvd.nist.gov/)" from the National Institute of Standards and Technology.
-
-The severity level is one of four possible levels defined in the "[Common Vulnerability Scoring System (CVSS), Section 5](https://www.first.org/cvss/specification-document)."
-- Low
-- Medium/Moderate
-- High
-- Critical
-
-The {% data variables.product.prodname_advisory_database %} uses the CVSS levels described above. If {% data variables.product.company_short %} obtains a CVE, the {% data variables.product.prodname_advisory_database %} uses CVSS version 3.1. If the CVE is imported, the {% data variables.product.prodname_advisory_database %} supports both CVSS versions 3.0 and 3.1.
-
-{% data reusables.repositories.github-security-lab %}
-
-## Accessing an advisory in the {% data variables.product.prodname_advisory_database %}
-
-1. Navigate to https://github.com/advisories.
-2. Optionally, to filter the list, use any of the drop-down menus.
-  ![Dropdown filters](/assets/images/help/security/advisory-database-dropdown-filters.png)
-   {% tip %}
-
-   **Tip:** You can use the sidebar on the left to explore  {% data variables.product.company_short %}-reviewed and unreviewed advisories separately.
-
-   {% endtip %}
-3. Click an advisory to view details. By default, you will see {% data variables.product.company_short %}-reviewed advisories for security vulnerabilities. {% ifversion GH-advisory-db-supports-malware %}To show malware advisories, use `type:malware` in the search bar.{% endif %}
-
-
-{% note %}
-
-The database is also accessible using the GraphQL API. {% ifversion GH-advisory-db-supports-malware %}By default, queries will return {% data variables.product.company_short %}-reviewed advisories for security vulnerabilities unless you specify `type:malware`.{% endif %} For more information, see the "[`security_advisory` webhook event](/webhooks/event-payloads/#security_advisory)."
-
-{% endnote %}
-
-## Editing an advisory in the {% data variables.product.prodname_advisory_database %}
-You can suggest improvements to any advisory in the {% data variables.product.prodname_advisory_database %}. For more information, see "[Editing security advisories in the {% data variables.product.prodname_advisory_database %}](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/editing-security-advisories-in-the-github-advisory-database)."
-
-## Searching the {% data variables.product.prodname_advisory_database %}
-
-You can search the database, and use qualifiers to narrow your search. For example, you can search for advisories created on a certain date, in a specific ecosystem, or in a particular library.
-
-{% data reusables.time_date.date_format %} {% data reusables.time_date.time_format %}
-
-{% data reusables.search.date_gt_lt %}
-
-| Qualifier  | Example |
-| ------------- | ------------- |
-| `type:reviewed`| [**type:reviewed**](https://github.com/advisories?query=type%3Areviewed) will show {% data variables.product.company_short %}-reviewed advisories for security vulnerabilities. |
-{% ifversion GH-advisory-db-supports-malware %}| `type:malware` | [**type:malware**](https://github.com/advisories?query=type%3Amalware) will show {% data variables.product.company_short %}-reviewed advisories for malware. |
-{% endif %}| `type:unreviewed`| [**type:unreviewed**](https://github.com/advisories?query=type%3Aunreviewed) will show unreviewed advisories. |
-| `GHSA-ID`| [**GHSA-49wp-qq6x-g2rf**](https://github.com/advisories?query=GHSA-49wp-qq6x-g2rf) will show the advisory with this {% data variables.product.prodname_advisory_database %} ID. |
-| `CVE-ID`| [**CVE-2020-28482**](https://github.com/advisories?query=CVE-2020-28482) will show the advisory with this CVE ID number. |
-| `ecosystem:ECOSYSTEM`| [**ecosystem:npm**](https://github.com/advisories?utf8=%E2%9C%93&query=ecosystem%3Anpm) will show only advisories affecting NPM packages. |
-| `severity:LEVEL`| [**severity:high**](https://github.com/advisories?utf8=%E2%9C%93&query=severity%3Ahigh) will show only advisories with a high severity level. |
-| `affects:LIBRARY`| [**affects:lodash**](https://github.com/advisories?utf8=%E2%9C%93&query=affects%3Alodash) will show only advisories affecting the lodash library. |
-| `cwe:ID`| [**cwe:352**](https://github.com/advisories?query=cwe%3A352) will show only advisories with this CWE number. |
-| `credit:USERNAME`| [**credit:octocat**](https://github.com/advisories?query=credit%3Aoctocat) will show only advisories credited to the "octocat" user account. |
-| `sort:created-asc`| [**sort:created-asc**](https://github.com/advisories?utf8=%E2%9C%93&query=sort%3Acreated-asc) will sort by the oldest advisories first. |
-| `sort:created-desc`| [**sort:created-desc**](https://github.com/advisories?utf8=%E2%9C%93&query=sort%3Acreated-desc) will sort by the newest advisories first. |
-| `sort:updated-asc`| [**sort:updated-asc**](https://github.com/advisories?utf8=%E2%9C%93&query=sort%3Aupdated-asc) will sort by the least recently updated first. |
-| `sort:updated-desc`| [**sort:updated-desc**](https://github.com/advisories?utf8=%E2%9C%93&query=sort%3Aupdated-desc) will sort by the most recently updated first. |
-| `is:withdrawn`| [**is:withdrawn**](https://github.com/advisories?utf8=%E2%9C%93&query=is%3Awithdrawn) will show only advisories that have been withdrawn. |
-| `created:YYYY-MM-DD`| [**created:2021-01-13**](https://github.com/advisories?utf8=%E2%9C%93&query=created%3A2021-01-13) will show only advisories created on this date. |
-| `updated:YYYY-MM-DD`| [**updated:2021-01-13**](https://github.com/advisories?utf8=%E2%9C%93&query=updated%3A2021-01-13) will show only advisories updated on this date. |
-
-## Viewing your vulnerable repositories
-
-For any {% data variables.product.company_short %}-reviewed advisory in the {% data variables.product.prodname_advisory_database %}, you can see which of your repositories are affected by that security vulnerability{% ifversion GH-advisory-db-supports-malware %} or malware{% endif %}. To see a vulnerable repository, you must have access to {% data variables.product.prodname_dependabot_alerts %} for that repository. For more information, see "[About {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies#access-to-dependabot-alerts)."
-
-1. Navigate to https://github.com/advisories.
-2. Click an advisory.
-3. At the top of the advisory page, click **Dependabot alerts**.
-   ![Dependabot alerts](/assets/images/help/security/advisory-database-dependabot-alerts.png)
-4. Optionally, to filter the list, use the search bar or the drop-down menus. The "Organization" drop-down menu allows you to filter the {% data variables.product.prodname_dependabot_alerts %} per owner (organization or user).
-   ![Search bar and drop-down menus to filter alerts](/assets/images/help/security/advisory-database-dependabot-alerts-filters.png)
-5. For more details about the advisory, and for advice on how to fix the vulnerable repository, click the repository name.
-
-{% ifversion security-advisories-ghes-ghae %}
-## Accessing the local advisory database on {% data variables.location.product_location %}
-
-If your site administrator has enabled {% data variables.product.prodname_github_connect %} for {% data variables.location.product_location %}, you can also browse reviewed advisories locally. For more information, see "[About {% data variables.product.prodname_github_connect %}](/admin/configuration/configuring-github-connect/about-github-connect)".
-
-You can use your local advisory database to check whether a specific security vulnerability is included, and therefore whether you'd get alerts for vulnerable dependencies. You can also view any vulnerable repositories. 
-
-1. Navigate to `https://HOSTNAME/advisories`.
-2. Optionally, to filter the list, use any of the drop-down menus.
-  ![Dropdown filters](/assets/images/help/security/advisory-database-dropdown-filters.png)
-   {% note %}
-
-   **Note:** Only reviewed advisories will be listed. Unreviewed advisories can be viewed in the {% data variables.product.prodname_advisory_database %} on {% data variables.product.prodname_dotcom_the_website %}. For more information, see "[Accessing an advisory in the GitHub Advisory Database](#accessing-an-advisory-in-the-github-advisory-database)". 
-
-   {% endnote %}
-3. Click an advisory to view details.{% ifversion GH-advisory-db-supports-malware %} By default, you will see {% data variables.product.company_short %}-reviewed advisories for security vulnerabilities. To show malware advisories, use `type:malware` in the search bar.{% endif %}
-
-You can also suggest improvements to any advisory directly from your local advisory database. For more information, see "[Editing advisories from {% data variables.location.product_location %}](/code-security/dependabot/dependabot-alerts/editing-security-advisories-in-the-github-advisory-database#editing-advisories-from-your-github-enterprise-server-instance)".
-
-### Viewing vulnerable repositories for {% data variables.location.product_location %}
-
-{% data reusables.repositories.enable-security-alerts %}
-
-In the local advisory database, you can see which repositories are affected by each security vulnerability{% ifversion GH-advisory-db-supports-malware %} or malware{% endif %}. To see a vulnerable repository, you must have access to {% data variables.product.prodname_dependabot_alerts %} for that repository. For more information, see "[About {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies#access-to-dependabot-alerts)."
-
-1. Navigate to `https://HOSTNAME/advisories`.
-2. Click an advisory.
-3. At the top of the advisory page, click **Dependabot alerts**.
-   ![Dependabot alerts](/assets/images/help/security/advisory-database-dependabot-alerts.png)
-4. Optionally, to filter the list, use the search bar or the drop-down menus. The "Organization" drop-down menu allows you to filter the {% data variables.product.prodname_dependabot_alerts %} per owner (organization or user).
-   ![Search bar and drop-down menus to filter alerts](/assets/images/help/security/advisory-database-dependabot-alerts-filters.png)
-5. For more details about the advisory, and for advice on how to fix the vulnerable repository, click the repository name.
-
-{% endif %}
-
-## Further reading
-
-- MITRE's [definition of "vulnerability"](https://www.cve.org/ResourcesSupport/Glossary#vulnerability)
diff --git a/translations/es-ES/content/code-security/dependabot/dependabot-alerts/editing-security-advisories-in-the-github-advisory-database.md b/translations/es-ES/content/code-security/dependabot/dependabot-alerts/editing-security-advisories-in-the-github-advisory-database.md
deleted file mode 100644
index bc319ee063..0000000000
--- a/translations/es-ES/content/code-security/dependabot/dependabot-alerts/editing-security-advisories-in-the-github-advisory-database.md
+++ /dev/null
@@ -1,55 +0,0 @@
----
-title: Editing security advisories in the GitHub Advisory Database
-intro: 'You can submit improvements to any advisory published in the {% data variables.product.prodname_advisory_database %}.'
-redirect_from:
-  - /code-security/security-advisories/editing-security-advisories-in-the-github-advisory-database
-  - /code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/editing-security-advisories-in-the-github-advisory-database
-versions:
-  fpt: '*'
-  ghec: '*'
-  ghes: '*'
-  ghae: '*'
-type: how_to
-topics:
-  - Security advisories
-  - Alerts
-  - Dependabot
-  - Vulnerabilities
-  - CVEs
-shortTitle: Edit Advisory Database
----
-
-## About editing advisories in the {% data variables.product.prodname_advisory_database %}
-Security advisories in the {% data variables.product.prodname_advisory_database %} at [github.com/advisories](https://github.com/advisories) are considered global advisories. Anyone can suggest improvements on any global security advisory in the {% data variables.product.prodname_advisory_database %}. You can edit or add any detail, including additionally affected ecosystems, severity level or description of who is impacted. The {% data variables.product.prodname_security %} curation team will review the submitted improvements and publish them onto the {% data variables.product.prodname_advisory_database %} if accepted.
-{% ifversion fpt or ghec %}
-Only repository owners and administrators can edit repository-level security advisories. For more information, see "[Editing a repository security advisory](/code-security/security-advisories/editing-a-security-advisory)."{% endif %}
-
-## Editing advisories in the GitHub Advisory Database
-
-1. Navigate to https://github.com/advisories.
-1. Select the security advisory you would like to contribute to.
-1. On the right-hand side of the page, click the **Suggest improvements for this vulnerability** link.
-   
-   ![Screenshot of the suggest improvements link](/assets/images/help/security/suggest-improvements-to-advisory.png)
-
-1. In the "Improve security advisory" form, make the desired improvements. You can edit or add any detail.{% ifversion fpt or ghec %} For information about correctly specifying information on the form, including affected versions, see "[Best practices for writing repository security advisories](/code-security/repository-security-advisories/best-practices-for-writing-repository-security-advisories)."{% endif %}{% ifversion security-advisories-reason-for-change %}
-1. Under **Reason for change**, explain why you want to make this improvement. If you include links to supporting material this will help our reviewers.
-   
-   ![Screenshot of the reason for change field](/assets/images/help/security/security-advisories-suggest-improvement-reason.png){% endif %}
-
-1. When you finish editing the advisory, click **Submit improvements**.
-1. Once you submit your improvements, a pull request containing your changes will be created for review in [github/advisory-database](https://github.com/github/advisory-database) by the {% data variables.product.prodname_security %} curation team. If the advisory originated from a {% data variables.product.prodname_dotcom %} repository, we will also tag the original publisher for optional commentary. You can view the pull request and get notifications when it is updated or closed.
-
-You can also open a pull request directly on an advisory file in the [github/advisory-database](https://github.com/github/advisory-database) repository. For more information, see the [contribution guidelines](https://github.com/github/advisory-database/blob/main/CONTRIBUTING.md). 
-
-{% ifversion security-advisories-ghes-ghae %}
-## Editing advisories from {% data variables.location.product_location %}
-
-If you have {% data variables.product.prodname_github_connect %} enabled for {% data variables.location.product_location %}, you will be able to see advisories by adding `/advisories` to the instance url. 
-
-1. Navigate to `https://HOSTNAME/advisories`.
-2. Select the security advisory you would like to contribute to.
-3. On the right-hand side of the page, click the **Suggest improvements for this vulnerability on {% data variables.product.prodname_dotcom_the_website %}.** link. A new tab opens with the same security advisory on {% data variables.product.prodname_dotcom_the_website %}.
-![Suggest improvements link](/assets/images/help/security/suggest-improvements-to-advisory-on-github-com.png)
-4. Edit the advisory, following steps four through six in "[Editing advisories in the GitHub Advisory Database](#editing-advisories-in-the-github-advisory-database)" above.
-{% endif %}
diff --git a/translations/es-ES/content/code-security/dependabot/dependabot-alerts/index.md b/translations/es-ES/content/code-security/dependabot/dependabot-alerts/index.md
index b2f79e71d0..4b0cb1d23c 100644
--- a/translations/es-ES/content/code-security/dependabot/dependabot-alerts/index.md
+++ b/translations/es-ES/content/code-security/dependabot/dependabot-alerts/index.md
@@ -15,8 +15,6 @@ topics:
   - Repositories
   - Dependencies
 children:
-  - /browsing-security-advisories-in-the-github-advisory-database
-  - /editing-security-advisories-in-the-github-advisory-database
   - /about-dependabot-alerts
   - /configuring-dependabot-alerts
   - /viewing-and-updating-dependabot-alerts
diff --git a/translations/es-ES/content/code-security/getting-started/adding-a-security-policy-to-your-repository.md b/translations/es-ES/content/code-security/getting-started/adding-a-security-policy-to-your-repository.md
index 19d8693f15..9c14fe91d4 100644
--- a/translations/es-ES/content/code-security/getting-started/adding-a-security-policy-to-your-repository.md
+++ b/translations/es-ES/content/code-security/getting-started/adding-a-security-policy-to-your-repository.md
@@ -1,6 +1,6 @@
 ---
-title: Agregar una política de seguridad a tu repositorio
-intro: Puedes dar instrucciones de cómo reportar una vulnerabilidad de seguridad en tu proyecto si agregas una política de seguridad a tu repositorio.
+title: Adding a security policy to your repository
+intro: You can give instructions for how to report a security vulnerability in your project by adding a security policy to your repository.
 redirect_from:
   - /articles/adding-a-security-policy-to-your-repository
   - /github/managing-security-vulnerabilities/adding-a-security-policy-to-your-repository
@@ -17,47 +17,49 @@ topics:
   - Repositories
   - Health
 shortTitle: Add a security policy
-ms.openlocfilehash: f081d6e6bd99f604e7e86bc094f76de9041adf4b
-ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
-ms.translationtype: HT
-ms.contentlocale: es-ES
-ms.lasthandoff: 09/10/2022
-ms.locfileid: '145091550'
 ---
-## Acerca de las políticas de seguridad
 
-Para proporcionar instrucciones sobre cómo notificar vulnerabilidades de seguridad en el proyecto,{% ifversion fpt or ghes or ghec %} puede agregar un archivo _SECURITY.md_ a la raíz, `docs`, o a la carpeta `.github` del repositorio.{% else %} puede agregar un archivo _SECURITY.md_ a la raíz o a la carpeta `docs` del repositorio.{% endif %} Cuando alguien cree una incidencia en el repositorio, verá un vínculo a la directiva de seguridad del proyecto.
+## About security policies
+
+To give people instructions for reporting security vulnerabilities in your project,{% ifversion fpt or ghes or ghec %} you can add a _SECURITY.md_ file to your repository's root, `docs`, or `.github` folder.{% else %} you can add a _SECURITY.md_ file to your repository's root, or `docs` folder.{% endif %} When someone creates an issue in your repository, they will see a link to your project's security policy.
 
 {% ifversion not ghae %}
 <!-- no public repos in GHAE -->
-Puedes crear una política de seguridad predeterminada para tu organización o cuenta personal. Para más información, vea "[Creación de un archivo de estado de la comunidad predeterminado](/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file)".
+You can create a default security policy for your organization or personal account. For more information, see "[Creating a default community health file](/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file)."
 {% endif %}
 
 {% tip %}
 
-**Sugerencia:** Para ayudar a los usuarios a encontrar su directiva de seguridad, puede vincular a su archivo _SECURITY.md_ desde otros lugares del repositorio, como un archivo Léame. Para más información, vea "[Acerca de los archivos Léame](/articles/about-readmes)".
+**Tip:** To help people find your security policy, you can link to your _SECURITY.md_ file from other places in your repository, such as your README file. For more information, see "[About READMEs](/articles/about-readmes)."
 
 {% endtip %}
 
-{% ifversion fpt or ghec %} Cuando alguien informa de una vulnerabilidad de seguridad en el proyecto, puede usar {% data variables.product.prodname_security_advisories %} para divulgar, corregir y publicar información sobre esta. Para obtener más información sobre el proceso de generación de informes y la divulgación de vulnerabilidades en {% data variables.product.prodname_dotcom %}, vea "[Acerca de la divulgación coordinada de vulnerabilidades de seguridad](/code-security/security-advisories/about-coordinated-disclosure-of-security-vulnerabilities#about-reporting-and-disclosing-vulnerabilities-in-projects-on-github)". Para más información sobre {% data variables.product.prodname_security_advisories %}, vea "[Acerca de {% data variables.product.prodname_security_advisories %}](/github/managing-security-vulnerabilities/about-github-security-advisories)".
+{% ifversion fpt or ghec %}
+After someone reports a security vulnerability in your project, you can use {% data variables.product.prodname_security_advisories %} to disclose, fix, and publish information about the vulnerability. For more information about the process of reporting and disclosing vulnerabilities in {% data variables.product.prodname_dotcom %}, see "[About coordinated disclosure of security vulnerabilities](/code-security/security-advisories/about-coordinated-disclosure-of-security-vulnerabilities#about-reporting-and-disclosing-vulnerabilities-in-projects-on-github)." For more information about repository security advisories, see "[About repository security advisories](/github/managing-security-vulnerabilities/about-github-security-advisories)."
 
-{% data reusables.repositories.github-security-lab %} {% endif %} {% ifversion ghes or ghae %}
+{% data reusables.repositories.github-security-lab %}
+{% endif %}
+{% ifversion ghes or ghae %}
 <!-- alternative to the content about GitHub Security Advisories in the dotcom article -->
-Cuando pones las instrucciones de reporte de seguridad claramente disponibles, facilitas a tus usurios el reportar cualquier vulnerabilidad de seguridad que encuentren en tu repositorio utilizando tu canal de comunicación preferido.
+By making security reporting instructions clearly available, you make it easy for your users to report any security vulnerabilities they find in your repository using your preferred communication channel.
 {% endif %}
 
-## Agregar una política de seguridad a tu repositorio
+## Adding a security policy to your repository
 
-{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %}
-3. En la barra lateral izquierda, haga clic en **Security policy** (Directiva de seguridad).
-  ![Pestaña Security policy (Directiva de seguridad)](/assets/images/help/security/security-policy-tab.png)
-4. Haga clic en **Iniciar configuración**.
-  ![Botón Start setup (Iniciar configuración)](/assets/images/help/security/start-setup-security-policy-button.png)
-5. En el nuevo archivo _SECURITY.md_, agregue información sobre las versiones admitidas del proyecto y cómo notificar una vulnerabilidad.
-{% data reusables.files.write_commit_message %} {% data reusables.files.choose-commit-email %} {% data reusables.files.choose_commit_branch %} {% data reusables.files.propose_file_change %}
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.sidebar-security %}
+3. In the left sidebar, click **Security policy**.
+  ![Security policy tab](/assets/images/help/security/security-policy-tab.png)
+4. Click **Start setup**.
+  ![Start setup button](/assets/images/help/security/start-setup-security-policy-button.png)
+5. In the new _SECURITY.md_ file, add information about supported versions of your project and how to report a vulnerability.
+{% data reusables.files.write_commit_message %}
+{% data reusables.files.choose-commit-email %}
+{% data reusables.files.choose_commit_branch %}
+{% data reusables.files.propose_file_change %}
 
-## Información adicional
+## Further reading
 
-- "[Protección del repositorio](/code-security/getting-started/securing-your-repository)"{% ifversion not ghae %}
-- "[Configuración del proyecto para contribuciones correctas](/communities/setting-up-your-project-for-healthy-contributions)"{% endif %}{% ifversion fpt or ghec %}
+- "[Securing your repository](/code-security/getting-started/securing-your-repository)"{% ifversion not ghae %}
+- "[Setting up your project for healthy contributions](/communities/setting-up-your-project-for-healthy-contributions)"{% endif %}{% ifversion fpt or ghec %}
 - [{% data variables.product.prodname_security %}]({% data variables.product.prodname_security_link %}){% endif %}
diff --git a/translations/es-ES/content/code-security/getting-started/github-security-features.md b/translations/es-ES/content/code-security/getting-started/github-security-features.md
index fe09160461..081272149c 100644
--- a/translations/es-ES/content/code-security/getting-started/github-security-features.md
+++ b/translations/es-ES/content/code-security/getting-started/github-security-features.md
@@ -28,7 +28,7 @@ Make it easy for your users to confidentially report security vulnerabilities th
 {% ifversion fpt or ghec %}
 ### Security advisories
 
-Privately discuss and fix security vulnerabilities in your repository's code. You can then publish a security advisory to alert your community to the vulnerability and encourage community members to upgrade. For more information, see "[About {% data variables.product.prodname_security_advisories %}](/github/managing-security-vulnerabilities/about-github-security-advisories)."
+Privately discuss and fix security vulnerabilities in your repository's code. You can then publish a security advisory to alert your community to the vulnerability and encourage community members to upgrade. For more information, see "[About repository security advisories](/github/managing-security-vulnerabilities/about-github-security-advisories)."
 
 {% endif %}
 {% ifversion fpt or ghec or ghes %}
diff --git a/translations/es-ES/content/code-security/getting-started/securing-your-organization.md b/translations/es-ES/content/code-security/getting-started/securing-your-organization.md
index f30c86cc01..63cff8ac9b 100644
--- a/translations/es-ES/content/code-security/getting-started/securing-your-organization.md
+++ b/translations/es-ES/content/code-security/getting-started/securing-your-organization.md
@@ -125,7 +125,7 @@ For more information, see "[Managing security and analysis settings for your org
 ## 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 {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts),"{% endif %} {% ifversion fpt or ghec or ghes %}"[Managing pull requests for dependency updates](/code-security/supply-chain-security/managing-pull-requests-for-dependency-updates)," {% endif %}"[Managing {% data variables.product.prodname_code_scanning %} for your repository](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository)," and "[Managing alerts from {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/managing-alerts-from-secret-scanning)."
 
-{% ifversion fpt or ghec %}If you have a security vulnerability, you can create a security advisory to privately discuss and fix the vulnerability. For more information, see "[About {% data variables.product.prodname_security_advisories %}](/code-security/security-advisories/about-github-security-advisories)" and "[Creating a security advisory](/code-security/security-advisories/creating-a-security-advisory)."
+{% 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 repository security advisories](/code-security/security-advisories/about-github-security-advisories)" and "[Creating a security advisory](/code-security/security-advisories/creating-a-security-advisory)."
 {% endif %}
 
 {% ifversion ghes or ghec or ghae %}You{% elsif fpt %}Organizations that use {% data variables.product.prodname_ghe_cloud %}{% endif %} can view, filter, and sort security alerts for repositories owned by {% ifversion ghes or ghec or ghae %}your{% elsif fpt %}their{% endif %} organization in the security overview. For more information, see{% ifversion ghes or ghec or ghae %} "[About the security overview](/code-security/security-overview/about-the-security-overview)."{% elsif fpt %} "[About the security overview](/enterprise-cloud@latest/code-security/security-overview/about-the-security-overview)" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% endif %}
diff --git a/translations/es-ES/content/code-security/getting-started/securing-your-repository.md b/translations/es-ES/content/code-security/getting-started/securing-your-repository.md
index 59b241eefe..3e84f7c163 100644
--- a/translations/es-ES/content/code-security/getting-started/securing-your-repository.md
+++ b/translations/es-ES/content/code-security/getting-started/securing-your-repository.md
@@ -133,5 +133,5 @@ You can set up {% data variables.product.prodname_code_scanning %} to automatica
 ## 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 {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts),"{% endif %} {% ifversion fpt or ghec or ghes %}"[Managing pull requests for dependency updates](/code-security/supply-chain-security/managing-pull-requests-for-dependency-updates)," {% endif %}"[Managing {% data variables.product.prodname_code_scanning %} for your repository](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository)," and "[Managing alerts from {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/managing-alerts-from-secret-scanning)."
 
-{% ifversion fpt or ghec %}If you have a security vulnerability, you can create a security advisory to privately discuss and fix the vulnerability. For more information, see "[About {% data variables.product.prodname_security_advisories %}](/code-security/security-advisories/about-github-security-advisories)" and "[Creating a security advisory](/code-security/security-advisories/creating-a-security-advisory)."
+{% 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 repository 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/es-ES/content/code-security/index.md b/translations/es-ES/content/code-security/index.md
index 3e04c8ba1a..e9d02c2953 100644
--- a/translations/es-ES/content/code-security/index.md
+++ b/translations/es-ES/content/code-security/index.md
@@ -1,7 +1,7 @@
 ---
-title: Seguridad de código
+title: Code security
 shortTitle: Code security
-intro: 'Crea la seguridad de tu flujo de trabajo de {% data variables.product.prodname_dotcom %} con características para mantener tus secretos y vulnerabilidades fuera de tu codebase {% ifversion not ghae %}, y para mantener la cadena de suministro de tu software{% endif %}.'
+intro: 'Build security into your {% data variables.product.prodname_dotcom %} workflow with features to keep secrets and vulnerabilities out of your codebase{% ifversion not ghae %}, and to maintain your software supply chain{% endif %}.'
 introLinks:
   overview: /code-security/getting-started/github-security-features
 featuredLinks:
@@ -53,16 +53,10 @@ children:
   - /adopting-github-advanced-security-at-scale
   - /secret-scanning
   - /code-scanning
-  - /repository-security-advisories
+  - /security-advisories
   - /supply-chain-security
   - /dependabot
   - /security-overview
   - /guides
-ms.openlocfilehash: 90d3ad046a6531849edd8e783db265866f118d90
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
-ms.translationtype: HT
-ms.contentlocale: es-ES
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147145243'
 ---
 
diff --git a/translations/es-ES/content/code-security/repository-security-advisories/about-github-security-advisories-for-repositories.md b/translations/es-ES/content/code-security/repository-security-advisories/about-github-security-advisories-for-repositories.md
deleted file mode 100644
index 65081968aa..0000000000
--- a/translations/es-ES/content/code-security/repository-security-advisories/about-github-security-advisories-for-repositories.md
+++ /dev/null
@@ -1,66 +0,0 @@
----
-title: Acerca de los avisos de seguridad de GitHub para repositorios
-intro: 'Puedes usar {% data variables.product.prodname_security_advisories %} para discutir, corregir y publicar información sobre vulnerabilidades de seguridad en tu repositorio.'
-redirect_from:
-  - /articles/about-maintainer-security-advisories
-  - /github/managing-security-vulnerabilities/about-maintainer-security-advisories
-  - /github/managing-security-vulnerabilities/about-github-security-advisories
-  - /code-security/security-advisories/about-github-security-advisories
-versions:
-  fpt: '*'
-  ghec: '*'
-type: overview
-topics:
-  - Security advisories
-  - Vulnerabilities
-  - CVEs
-shortTitle: Repository security advisories
-ms.openlocfilehash: 5c8ad99a2bee30f52a185fa15421bc6b23429fbf
-ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
-ms.translationtype: HT
-ms.contentlocale: es-ES
-ms.lasthandoff: 09/10/2022
-ms.locfileid: '145091532'
----
-{% data reusables.repositories.security-advisory-admin-permissions %}
-
-{% data reusables.security-advisory.security-researcher-cannot-create-advisory %}
-
-## About {% data variables.product.prodname_security_advisories %}
-
-{% data reusables.security-advisory.disclosing-vulnerabilities %} Para más información, vea "[Acerca de la divulgación coordinada de vulnerabilidades de seguridad](/code-security/repository-security-advisories/about-coordinated-disclosure-of-security-vulnerabilities)".
-
-{% data reusables.security-advisory.security-advisory-overview %}
-
-Con {% data variables.product.prodname_security_advisories %}, puedes:
-
-1. Crear un borrador de asesoría de seguridad y utilizarlo para debatir de manera privada sobre el impacto de la vulnerabilidad en tu proyecto. Para más información, vea "[Creación de un aviso de seguridad de repositorio](/code-security/repository-security-advisories/creating-a-repository-security-advisory)".
-2. Colaborar en privado para solucionar la vulnerabilidad en una bifurcación privada temporaria.
-3. Publica la asesoría de seguridad para alertar a tu comunidad sobre la vulnerabilidad una vez que se lance el parche. Para más información, vea "[Publicación de un aviso de seguridad de repositorio](/code-security/repository-security-advisories/publishing-a-repository-security-advisory)".
-
-{% data reusables.repositories.security-advisories-republishing %}
-
-Puedes dar crédito a los individuos que contribuyeron con una asesoría de seguridad. Para más información, vea "[Edición de un aviso de seguridad de repositorio](/code-security/repository-security-advisories/editing-a-repository-security-advisory#about-credits-for-security-advisories)".
-
-{% data reusables.repositories.security-guidelines %}
-
-Si creaste una asesoría de seguridad en tu repositorio, esta permanecerá en tu repositorio. Publicamos avisos de seguridad para todos los ecosistemas compatibles con el gráfico de dependencias en la {% data variables.product.prodname_advisory_database %} en [github.com/advisories](https://github.com/advisories). Cualquiera puede enviar un cambio de un aviso publicado en {% data variables.product.prodname_advisory_database %}. Para más información, vea "[Edición de avisos de seguridad en {% data variables.product.prodname_advisory_database %}](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/editing-security-advisories-in-the-github-advisory-database)".
-
-Si una asesoría de seguridad es específicamente para npm, también la publicamos en las asesorías de seguridad de npm. Para más información, vea [npmjs.com/advisories](https://www.npmjs.com/advisories).
-
-{% data reusables.repositories.github-security-lab %}
-
-## Números de identificación CVE
-
-Las {% data variables.product.prodname_security_advisories %} se construyen sobre las bases de la lista de Vulnerabilidades y Exposiciones Comunes (CVE, por sus siglas en inglés). El formato de asesoría de seguridad en {% data variables.product.prodname_dotcom %} es un formato estandarizado que coincide con el formato de descripción de CVE. 
-
-{% data variables.product.prodname_dotcom %} es una Autoridad de Numeración de CVE (CNA, por sus siglas en inglés) y está autorizado para asignar números de identificación de CVE. Para más información, vea "[Acerca de CVE](https://www.cve.org/About/Overview)" y "[Entidades de numeración de CVE](https://www.cve.org/ProgramOrganization/CNAs)" en el sitio web de CVE.
-
-Cuando creas una asesoría de seguridad para un repositorio público en {% data variables.product.prodname_dotcom %}, tienes la opción de proporcionar un número de identificación de CVE para la vulnerabilidad de seguridad. {% data reusables.repositories.request-security-advisory-cve-id %}
-
-Una vez que hayas publicado la asesoría de seguridad y que {% data variables.product.prodname_dotcom %} haya asignado un número de identificación CVE a la vulnerabilidad, {% data variables.product.prodname_dotcom %} publicará el CVE a la base de datos de MITRE.
-Para más información, vea "[Publicación de un aviso de seguridad de repositorio](/code-security/repository-security-advisories/publishing-a-repository-security-advisory)".
-
-## {% data variables.product.prodname_dependabot_alerts %} para las asesorías de seguridad publicadas
-
-{% data reusables.repositories.github-reviews-security-advisories %}
diff --git a/translations/es-ES/content/code-security/repository-security-advisories/adding-a-collaborator-to-a-repository-security-advisory.md b/translations/es-ES/content/code-security/repository-security-advisories/adding-a-collaborator-to-a-repository-security-advisory.md
deleted file mode 100644
index eace5e25f7..0000000000
--- a/translations/es-ES/content/code-security/repository-security-advisories/adding-a-collaborator-to-a-repository-security-advisory.md
+++ /dev/null
@@ -1,50 +0,0 @@
----
-title: Incorporación de un colaborador a un aviso de seguridad de repositorio
-intro: Puedes agregar otros usuarios o equipos para que colaboren contigo en un aviso de seguridad.
-redirect_from:
-  - /articles/adding-a-collaborator-to-a-maintainer-security-advisory
-  - /github/managing-security-vulnerabilities/adding-a-collaborator-to-a-maintainer-security-advisory
-  - /github/managing-security-vulnerabilities/adding-a-collaborator-to-a-security-advisory
-  - /code-security/security-advisories/adding-a-collaborator-to-a-security-advisory
-versions:
-  fpt: '*'
-  ghec: '*'
-type: how_to
-topics:
-  - Security advisories
-  - Vulnerabilities
-  - Collaboration
-shortTitle: Add collaborators
-ms.openlocfilehash: 6fa4062fab8e4ffc59724ceb0ba3b6b536871df9
-ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
-ms.translationtype: HT
-ms.contentlocale: es-ES
-ms.lasthandoff: 09/10/2022
-ms.locfileid: '147879428'
----
-Las personas con permisos de administrador en una asesoría de seguridad pueden añadir colaboradores a la misma.
-
-{% data reusables.security-advisory.repository-level-advisory-note %}
-
-## Añadir un colaborador a una asesoría de seguridad
-
-Los colaboradores tienen permisos de escritura para el aviso de seguridad. Para obtener más información, vea "[Niveles de permisos para avisos de seguridad del repositorio](/code-security/repository-security-advisories/permission-levels-for-repository-security-advisories)".
-
-{% note %}
-
-{% data reusables.repositories.security-advisory-collaborators-public-repositories %} Para obtener más información sobre cómo quitar un colaborador en un aviso de seguridad, vea "[Eliminación de un colaborador de un aviso de seguridad del repositorio](/code-security/repository-security-advisories/removing-a-collaborator-from-a-repository-security-advisory)".
-
-{% endnote %}
-
-{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %} {% data reusables.repositories.sidebar-advisories %}
-4. En la lista de "Asesorías de Seguridad", da clic en la asesoría a la cual quieras añadir un colaborador.
-5. En la parte derecha de la página, debajo de "Colaboradores", teclea el nombre de usuario o equipo que quieras añadir a la asesoría de seguridad.
-  ![Campo para escribir el nombre del equipo o el usuario](/assets/images/help/security/add-collaborator-field.png)
-6. Haga clic en **Agregar**.
-  ![Botón Agregar](/assets/images/help/security/security-advisory-add-collaborator-button.png)
-
-## Información adicional
-
-- "[Niveles de permiso para avisos de seguridad de repositorios](/code-security/repository-security-advisories/permission-levels-for-repository-security-advisories)"
-- "[Colaboración en una bifurcación privada temporal para resolver una vulnerabilidad de seguridad del repositorio](/code-security/repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability)"
-- "[Eliminación de un colaborador de un aviso de seguridad del repositorio](/code-security/repository-security-advisories/removing-a-collaborator-from-a-repository-security-advisory)".
diff --git a/translations/es-ES/content/code-security/repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability.md b/translations/es-ES/content/code-security/repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability.md
deleted file mode 100644
index 02d6f3712f..0000000000
--- a/translations/es-ES/content/code-security/repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability.md
+++ /dev/null
@@ -1,90 +0,0 @@
----
-title: Colaboración en una bifurcación privada temporal para resolver una vulnerabilidad de seguridad del repositorio
-intro: Puedes crear una bifurcación privada temporal para colaborar de manera privada en la resolución de una vulnerabilidad de seguridad en tu repositorio.
-redirect_from:
-  - /articles/collaborating-in-a-temporary-private-fork-to-resolve-a-security-vulnerability
-  - /github/managing-security-vulnerabilities/collaborating-in-a-temporary-private-fork-to-resolve-a-security-vulnerability
-  - /code-security/security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-security-vulnerability
-versions:
-  fpt: '*'
-  ghec: '*'
-type: how_to
-topics:
-  - Security advisories
-  - Vulnerabilities
-  - Collaboration
-  - Forks
-shortTitle: Temporary private forks
-ms.openlocfilehash: c03892c3ad1bd7345a7a066c9a9564858db4b84d
-ms.sourcegitcommit: ac00e2afa6160341c5b258d73539869720b395a4
-ms.translationtype: HT
-ms.contentlocale: es-ES
-ms.lasthandoff: 09/09/2022
-ms.locfileid: '147878540'
----
-{% data reusables.security-advisory.repository-level-advisory-note %}
-
-## Prerrequisitos
-
-Antes de que puedas colaborar en una bifurcación privada temporal, debes crear un borrador de asesoría de seguridad. Para más información, vea "[Creación de un aviso de seguridad de repositorio](/code-security/repository-security-advisories/creating-a-repository-security-advisory)".
-
-## Crear una bifurcación privada temporal
-
-Cualquier persona con permisos de administración para un aviso de seguridad puede crear una bifurcación privada temporal.
-
-Para garantizar la seguridad de la información sobre vulnerabilidades, las integraciones, entre las que se incluye CI, no pueden acceder a las bifurcaciones privadas temporales.
-
-{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %} {% data reusables.repositories.sidebar-advisories %}
-4. En la lista de "Asesorías de Seguridad", da clic en aquella en la cual desees crear una bifurcación privada temporal.
-  ![Aviso de seguridad en la lista](/assets/images/help/security/security-advisory-in-list.png)
-5. Haga clic en **Nueva bifurcación privada temporal**.
-  ![Botón Nueva bifurcación privada temporal](/assets/images/help/security/new-temporary-private-fork-button.png)
-
-## Añadir colaboradores a una bifurcación privada temporal
-
-Cualquiera con permisos de administrador en una asesoría de seguridad puede añadir colaboradores adicionales a la misma, y estos pueden acceder a la bifurcación privada temporal. Para más información, vea "[Adición de un colaborador a un aviso de seguridad de repositorio](/code-security/repository-security-advisories/adding-a-collaborator-to-a-repository-security-advisory)".
-
-## Agregar cambios a una bifurcación privada temporal
-
-Cualquier persona con permisos de escritura para un aviso de seguridad puede agregar cambios a una bifurcación privada temporal.
-
-{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %} {% data reusables.repositories.sidebar-advisories %}
-4. En la lista de "Asesorías de Seguridad", da clic sobre aquella en la que quieras añadir cambios.
-  ![Aviso de seguridad en la lista](/assets/images/help/security/security-advisory-in-list.png)
-5. Agrega tus cambios en {% data variables.product.product_name %} o localmente:
-   - Para añadir cambios en {% data variables.product.product_name %}, debajo de "Añadir cambios a este aviso", haga clic en **la bifurcación privada temporal**. Luego, crea una nueva rama y edita los archivos. Para más información, vea "[Creación y eliminación de ramas dentro del repositorio](/articles/creating-and-deleting-branches-within-your-repository)" y "[Edición de archivos](/repositories/working-with-files/managing-files/editing-files)".
-   - Para añadir cambios localmente, sigue las instrucciones descritas en "Clonar y crear una nueva rama" y "Haz tus cambios, posteriormente, súbelos".
-   ![Adición de cambios en este cuadro de aviso](/assets/images/help/security/add-changes-to-this-advisory-box.png)
-
-## Crear una solicitud de extracción desde una bifurcación privada temporal
-
-Cualquier persona con permisos de escritura para un aviso de seguridad puede crear una solicitud de extracción desde una bifurcación privada temporal.
-
-{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %} {% data reusables.repositories.sidebar-advisories %}
-4. En la lista de "Asesorías de Seguridad", da clic sobre aquella en la que desees crear una solicitud de extracción.
-  ![Aviso de seguridad en la lista](/assets/images/help/security/security-advisory-in-list.png)
-5. A la derecha del nombre de la rama, haga clic en **Comparar y solicitud de incorporación de cambios**.
-  ![Botón Comparar y solicitud de incorporación de cambios](/assets/images/help/security/security-advisory-compare-and-pr.png) {% data reusables.repositories.pr-title-description %} {% data reusables.repositories.create-pull-request %}
-
-{% data reusables.repositories.merge-all-pulls-together %} Para más información, vea "[Combinación de cambios en un aviso de seguridad](#merging-changes-in-a-security-advisory)".
-
-## Fusionar cambios en una asesoría de seguridad
-
-Cualquiera con permisos de administrador en una asesoría de seguridad puede fusionar los cambios en la misma.
-
-{% data reusables.repositories.merge-all-pulls-together %}
-
-Antes de que puedas fusionar cambios en una asesoría de seguridad, cada solicitud de extracción abierta en la bifurcación privada temporal debe ser fusionable. No puede haber conflictos de fusión, y se deben cumplir los requisitos de protección de la rama. Para garantizar la seguridad de la información sobre las vulnerabilidades, las verificaciones de estado no ejecutan solicitudes de extracción en bifurcaciones privadas temporales. Para más información, vea "[Acerca de las ramas protegidas](/articles/about-protected-branches)".
-
-{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %} {% data reusables.repositories.sidebar-advisories %}
-4. En el listado de "Asesorías de Seguridad", da clic sobre aquella que tiene los cambios que quieras fusionar.
-  ![Aviso de seguridad en la lista](/assets/images/help/security/security-advisory-in-list.png)
-5. Para combinar todas las solicitudes de incorporación de cambios abiertas en la bifurcación privada temporal, haga clic en **Combinar solicitudes de incorporación de cambios**.
-  ![Botón Combinar solicitudes de incorporación de cambios](/assets/images/help/security/merge-pull-requests-button.png)
-
-Después de que fusiones cambios en una asesoría de seguridad, puedes publicarla para alertar a tu comunidad sobre las vulnerabilidades de seguridad en versiones previas de tu proyecto. Para más información, vea "[Publicación de un aviso de seguridad de repositorio](/code-security/repository-security-advisories/publishing-a-repository-security-advisory)".
-
-## Información adicional
-
-- "[Niveles de permiso para avisos de seguridad de repositorios](/code-security/repository-security-advisories/permission-levels-for-repository-security-advisories)"
-- "[Publicación de un aviso de seguridad de repositorio](/code-security/repository-security-advisories/publishing-a-repository-security-advisory)"
diff --git a/translations/es-ES/content/code-security/repository-security-advisories/creating-a-repository-security-advisory.md b/translations/es-ES/content/code-security/repository-security-advisories/creating-a-repository-security-advisory.md
deleted file mode 100644
index 3a6ffba722..0000000000
--- a/translations/es-ES/content/code-security/repository-security-advisories/creating-a-repository-security-advisory.md
+++ /dev/null
@@ -1,44 +0,0 @@
----
-title: Creación de un aviso de seguridad de repositorio
-intro: Puedes crear un borrador de asesoría de seguridad para debatir en privado y arreglar una vulnerabilidad de seguridad en tu proyecto de código abierto.
-redirect_from:
-  - /articles/creating-a-maintainer-security-advisory
-  - /github/managing-security-vulnerabilities/creating-a-maintainer-security-advisory
-  - /github/managing-security-vulnerabilities/creating-a-security-advisory
-  - /code-security/security-advisories/creating-a-security-advisory
-versions:
-  fpt: '*'
-  ghec: '*'
-type: how_to
-topics:
-  - Security advisories
-  - Vulnerabilities
-shortTitle: Create repository advisories
-ms.openlocfilehash: d4b47f84b20873e97b18106448b768288fff3039
-ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
-ms.translationtype: HT
-ms.contentlocale: es-ES
-ms.lasthandoff: 09/10/2022
-ms.locfileid: '145119394'
----
-Cualquier usuario con permisos de administrador puede crear un aviso de seguridad.
-
-{% data reusables.security-advisory.security-researcher-cannot-create-advisory %}
-
-## Creación de un aviso de seguridad
-
-{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %} {% data reusables.repositories.sidebar-advisories %}
-4. Haga clic en **New draft security advisory**.
-  ![Botón Open draft advisory](/assets/images/help/security/security-advisory-new-draft-security-advisory-button.png)
-5. Escribe un título para tu aviso de seguridad.
-{% data reusables.repositories.security-advisory-edit-details %} {% data reusables.repositories.security-advisory-edit-severity %} {% data reusables.repositories.security-advisory-edit-cwe-cve %} {% data reusables.repositories.security-advisory-edit-description %}
-11. Haga clic en **Create draft security advisory**.
-  ![Botón Create security advisory](/assets/images/help/security/security-advisory-create-security-advisory-button.png)
-
-## Pasos siguientes
-
-- Comentar en el borrador de asesoría de seguridad para debatir sobre la vulnerabilidad con tu equipo.
-- Añadir colaboradores a la asesoría de seguridad. Para obtener más información, consulte "[Adición de un colaborador a un aviso de seguridad de repositorio](/code-security/repository-security-advisories/adding-a-collaborator-to-a-repository-security-advisory)".
-- Colaborar en privado para solucionar la vulnerabilidad en una bifurcación privada temporaria. Para más información, vea "[Colaboración en una bifurcación privada temporal para resolver una vulnerabilidad de seguridad del repositorio](/code-security/repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability)".
-- Agregar individuos que deberían recibir crédito por contribuir con la asesoría de seguridad. Para más información, vea "[Edición de un aviso de seguridad de repositorio](/code-security/repository-security-advisories/editing-a-repository-security-advisory#about-credits-for-security-advisories)".
-- Publicar la asesoría de seguridad para notificar a tu comunidad sobre la vulnerabilidad de seguridad en cuestión. Para más información, vea "[Publicación de un aviso de seguridad de repositorio](/code-security/repository-security-advisories/publishing-a-repository-security-advisory)".
diff --git a/translations/es-ES/content/code-security/repository-security-advisories/editing-a-repository-security-advisory.md b/translations/es-ES/content/code-security/repository-security-advisories/editing-a-repository-security-advisory.md
deleted file mode 100644
index 2bafa35a7c..0000000000
--- a/translations/es-ES/content/code-security/repository-security-advisories/editing-a-repository-security-advisory.md
+++ /dev/null
@@ -1,48 +0,0 @@
----
-title: Edición de un aviso de seguridad de repositorio
-intro: Puedes editar los metadatos y la descripción de una asesoría de seguridad de repositorio si necesitas actualizar los detalles o corregir los errores en esta.
-redirect_from:
-  - /github/managing-security-vulnerabilities/editing-a-security-advisory
-  - /code-security/security-advisories/editing-a-security-advisory
-versions:
-  fpt: '*'
-  ghec: '*'
-type: how_to
-topics:
-  - Security advisories
-  - Vulnerabilities
-shortTitle: Edit repository advisories
-ms.openlocfilehash: 2ea2f588374d83be677589b4f3bf4e74a7fc6e91
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
-ms.translationtype: HT
-ms.contentlocale: es-ES
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '145119386'
----
-Los usuarios con permisos de administrador para aviso de seguridad pueden editarlo.
-
-{% data reusables.security-advisory.repository-level-advisory-note %}
-
-## Acerca de los créditos para las asesorías de seguridad
-
-Puedes dar crédito a las personas que ayudaron a descubrir, reportar, o arreglar una vulnerabilidad de seguridad. Si le das crédito a alguien, ellos pueden elegir aceptarlo o declinarlo.
-
-Si alguien acepta el crédito, el nombre de usuario de la persona aparecerá en la sección "Créditos" de la asesoría de seguridad. Cualquiera con acceso de lectura al repositorio puede ver la asesoría y las personas que aceptaron el crédito por ella.
-
-Si crees que se te debería dar crédito por alguna asesoría de seguridad, por favor, contacta a la persona que la creó y pídele que edite la asesoría para incluir tu crédito. Solo el creador de la asesoría te puede dar crédito, asi que, por favor, no contactes al Soporte de GitHub pidiendo crédito para alguna asesoría de seguridad.
-
-## Editar una asesoría de seguridad
-
-{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %} {% data reusables.repositories.sidebar-advisories %}
-4. En el listado de "Asesorías de Seguridad", da clic en aquella que quieras editar.
-5. En la esquina superior derecha de los detalles del aviso de seguridad, haga clic en {% octicon "pencil" aria-label="The edit icon" %}.
-  ![Botón de edición para un aviso de seguridad](/assets/images/help/security/security-advisory-edit-button.png) {% data reusables.repositories.security-advisory-edit-details %} {% data reusables.repositories.security-advisory-edit-severity %} {% data reusables.repositories.security-advisory-edit-cwe-cve %} {% data reusables.repositories.security-advisory-edit-description %}
-11. Opcionalmente, puedes editar los "Créditos" para la asesoría de seguridad.
-  ![Créditos para un aviso de seguridad](/assets/images/help/security/security-advisory-credits.png)
-12. Haga clic en **Actualizar aviso de seguridad**.
-  ![Botón "Actualizar aviso de seguridad"](/assets/images/help/security/update-advisory-button.png)
-13. Las personas listadas en la sección de "Créditos" recibirán una notificación web o por correo electrónico que los invita a aceptar el crédito. Si la persona acepta, su nombre de usuario estará visible al público una vez que la asesoría de seguridad se publique.
-
-## Información adicional
-
-- "[Retirada de un aviso de seguridad de repositorio](/code-security/repository-security-advisories/withdrawing-a-repository-security-advisory)"
diff --git a/translations/es-ES/content/code-security/repository-security-advisories/index.md b/translations/es-ES/content/code-security/repository-security-advisories/index.md
deleted file mode 100644
index 0b66ac469f..0000000000
--- a/translations/es-ES/content/code-security/repository-security-advisories/index.md
+++ /dev/null
@@ -1,36 +0,0 @@
----
-title: Administrar las advertencias de seguridad de vulnerabilidades en tu proyecto
-shortTitle: Repository security advisories
-intro: 'Debate, arregla y divulga las vulnerabilidades de seguridad en tus repositorios utilizando asesorías de seguridad de repositorios.'
-redirect_from:
-  - /articles/managing-security-vulnerabilities-in-your-project
-  - /github/managing-security-vulnerabilities/managing-security-vulnerabilities-in-your-project
-  - /code-security/security-advisories
-versions:
-  fpt: '*'
-  ghec: '*'
-topics:
-  - Security advisories
-  - Vulnerabilities
-  - Repositories
-  - CVEs
-children:
-  - /about-coordinated-disclosure-of-security-vulnerabilities
-  - /about-github-security-advisories-for-repositories
-  - /permission-levels-for-repository-security-advisories
-  - /creating-a-repository-security-advisory
-  - /adding-a-collaborator-to-a-repository-security-advisory
-  - /removing-a-collaborator-from-a-repository-security-advisory
-  - /collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability
-  - /publishing-a-repository-security-advisory
-  - /editing-a-repository-security-advisory
-  - /withdrawing-a-repository-security-advisory
-  - /best-practices-for-writing-repository-security-advisories
-ms.openlocfilehash: 43efe7ceaf307da4a8a7c02c45f744a4967b05b0
-ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
-ms.translationtype: HT
-ms.contentlocale: es-ES
-ms.lasthandoff: 09/10/2022
-ms.locfileid: '145119385'
----
-
diff --git a/translations/es-ES/content/code-security/repository-security-advisories/permission-levels-for-repository-security-advisories.md b/translations/es-ES/content/code-security/repository-security-advisories/permission-levels-for-repository-security-advisories.md
deleted file mode 100644
index 0967ba8583..0000000000
--- a/translations/es-ES/content/code-security/repository-security-advisories/permission-levels-for-repository-security-advisories.md
+++ /dev/null
@@ -1,50 +0,0 @@
----
-title: Niveles de permiso para avisos de seguridad de repositorios
-intro: Las acciones que puedes tomar en una asesoría de seguridad de repositorio dependen de si tienes permisos de administrador o de escritura en esta.
-redirect_from:
-  - /articles/permission-levels-for-maintainer-security-advisories
-  - /github/managing-security-vulnerabilities/permission-levels-for-maintainer-security-advisories
-  - /github/managing-security-vulnerabilities/permission-levels-for-security-advisories
-  - /code-security/security-advisories/permission-levels-for-security-advisories
-versions:
-  fpt: '*'
-  ghec: '*'
-type: reference
-topics:
-  - Security advisories
-  - Vulnerabilities
-  - Permissions
-shortTitle: Permission levels
-ms.openlocfilehash: 9c2ad0d30b98b79786df09a224766bd826cb84f6
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
-ms.translationtype: HT
-ms.contentlocale: es-ES
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '145119393'
----
-Este artículo solo se aplica a los avisos de seguridad de nivel de repositorio. Cualquiera puede contribuir a los avisos de seguridad globales en {% data variables.product.prodname_advisory_database %} en [github.com/advisories](https://github.com/advisories). Las ediciones a las asesorías globales no cambiarán ni afectarán la forma en la que se muestra la asesoría en el repositorio.  Para más información, vea "[Edición de avisos de seguridad en {% data variables.product.prodname_advisory_database %}](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/editing-security-advisories-in-the-github-advisory-database)".
-
-## Introducción sobre los permisos
-
-{% data reusables.repositories.security-advisory-admin-permissions %} Para más información sobre cómo agregar un colaborador a un aviso de seguridad, vea "[Adición de un colaborador a un aviso de seguridad de repositorio](/code-security/repository-security-advisories/adding-a-collaborator-to-a-repository-security-advisory)".
-
-Acción | Permisos de escritura | Permisos de administrador |
------- | ----------------- | ----------------- |
-Ver un borrador de asesoría de seguridad | x | x |
-Agregar colaboradores al aviso de seguridad (vea "[Adición de un colaborador a un aviso de seguridad de repositorio](/code-security/repository-security-advisories/adding-a-collaborator-to-a-repository-security-advisory)") | | x |
-Editar y borrar cualquier comentario en la asesoría de seguridad | x | x |
-Crear una bifurcación privada temporal en el aviso de seguridad (vea "[Colaboración en una bifurcación privada temporal para resolver una vulnerabilidad de seguridad del repositorio](/code-security/repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability)") | | x |
-Agregar cambios a una bifurcación privada temporal en el aviso de seguridad (vea "[Colaboración en una bifurcación privada temporal para resolver una vulnerabilidad de seguridad del repositorio](/code-security/repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability)") | x | x |
-Crear solicitudes de incorporación de cambios en una bifurcación privada temporal (vea "[Colaboración en una bifurcación privada temporal para resolver una vulnerabilidad de seguridad del repositorio](/code-security/repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability)") | x | x |
-Combinar cambios en el aviso de seguridad (vea "[Colaboración en una bifurcación privada temporal para resolver una vulnerabilidad de seguridad del repositorio](/code-security/repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability)") | | x |
-Agregar y editar metadatos en el aviso de seguridad (vea "[Publicación de un aviso de seguridad de repositorio](/code-security/repository-security-advisories/publishing-a-repository-security-advisory)") | x | x |
-Agregar y quitar créditos en el aviso de seguridad (vea "[Edición de un aviso de seguridad de repositorio](/code-security/repository-security-advisories/editing-a-repository-security-advisory)") | x | x |
-Cerrar el borrador de la asesoría de seguridad | | x |
-Publicar el aviso de seguridad (vea "[Publicación de un aviso de seguridad de repositorio](/code-security/repository-security-advisories/publishing-a-repository-security-advisory)") | | x |
-
-## Información adicional
-
-- "[Adición de un colaborador a un aviso de seguridad de repositorio](/code-security/repository-security-advisories/adding-a-collaborator-to-a-repository-security-advisory)"
-- "[Colaboración en una bifurcación privada temporal para resolver una vulnerabilidad de seguridad del repositorio](/code-security/repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability)"
-- "[Eliminación de un colaborador de un aviso de seguridad del repositorio](/code-security/repository-security-advisories/removing-a-collaborator-from-a-repository-security-advisory)"
-- "[Retirada de un aviso de seguridad de repositorio](/code-security/repository-security-advisories/withdrawing-a-repository-security-advisory)"
diff --git a/translations/es-ES/content/code-security/repository-security-advisories/publishing-a-repository-security-advisory.md b/translations/es-ES/content/code-security/repository-security-advisories/publishing-a-repository-security-advisory.md
deleted file mode 100644
index 75aa926321..0000000000
--- a/translations/es-ES/content/code-security/repository-security-advisories/publishing-a-repository-security-advisory.md
+++ /dev/null
@@ -1,101 +0,0 @@
----
-title: Publicación de un aviso de seguridad de repositorio
-intro: Puedes publicar una asesoría de seguridad para alertar a tu comunidad sobre la vulnerabilidad de seguridad en tu proyecto.
-redirect_from:
-  - /articles/publishing-a-maintainer-security-advisory
-  - /github/managing-security-vulnerabilities/publishing-a-maintainer-security-advisory
-  - /github/managing-security-vulnerabilities/publishing-a-security-advisory
-  - /code-security/security-advisories/publishing-a-security-advisory
-versions:
-  fpt: '*'
-  ghec: '*'
-type: how_to
-topics:
-  - Security advisories
-  - Vulnerabilities
-  - CVEs
-  - Repositories
-shortTitle: Publish repository advisories
-ms.openlocfilehash: f3e3bfdb6b44ec1c86bb903c66271b854f4fb041
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
-ms.translationtype: HT
-ms.contentlocale: es-ES
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '145119378'
----
-<!--Marketing-LINK: From /features/security/software-supply-chain page "Publishing a security advisory".-->
-
-Cualquiera con permisos de administrador en una asesoría de seguridad puede publicarla.
-
-{% data reusables.security-advisory.repository-level-advisory-note %}
-
-## Prerrequisitos
-
-Antes de que puedas publicar una asesoría de seguridad o solicitar un número de identificación de CVE, debes crear un borrador de asesoría de seguridad y proporcionar información acerca de las versiones de tu proyecto que se vieron afectadas por la vulnerabilidad de seguridad. Para más información, vea "[Creación de un aviso de seguridad de repositorio](/code-security/repository-security-advisories/creating-a-repository-security-advisory)".
-
-Si creaste una asesoría de seguridad pero no has proporcionado detalles sobre las versiones de tu proyecto que afectó la vulnerabilidad, puedes editarla. Para más información, vea "[Edición de un aviso de seguridad de repositorio](/code-security/repository-security-advisories/editing-a-repository-security-advisory)".
-
-## Acerca de publicar una asesoría de seguridad
-
-Cuando publicas una asesoría de seguridad, notificas a tu comunidad acerca de la vulnerabilidad de seguridad que se dirige en dicha asesoría. El publicar una asesoría de seguridad facilita a tu comunidad el actualizar las dependencias de los paquetes y el investigar el impacto de la vulnerabilidad de seguridad.
-
-{% data reusables.repositories.security-advisories-republishing %}
-
-Antes de que publiques una asesoría de seguridad, puedes hacer una colaboración privada para arreglar la vulnerabilidad en una bifurcación privada. Para más información, vea "[Colaboración en una bifurcación privada temporal para resolver una vulnerabilidad de seguridad del repositorio](/code-security/repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability)".
-
-{% warning %}
-
-**Advertencia**: Siempre que sea posible, debe agregar una versión de corrección a un aviso de seguridad antes de publicar el aviso. Si no lo haces, la asesoría se publicará sin una versión corregida y el {% data variables.product.prodname_dependabot %} alertará a tus usuarios sobre este problema sin ofrecer una versión segura para actualizarse.
-
-Te recomendamos seguir estos pasos en estas situaciones:
-
-- Si una versión corregida está disponible inminentemente y puedes hacerlo, espera para divulgar el problema cuando la corrección ya esté lista.
-- Si aún se está desarrollando una versión corregida y no se encuentra disponible, menciónalo en la asesoría y edítala después de publicarla.
-- Si no planeas corregir el problema, aclara esto en la asesoría para que tus usuarios no te contacten para preguntar cuándo crearás la corrección. En este caso, es útil incluir pasos que puedan seguir los usuarios para mitigar el problema.
-
-{% endwarning %}
-
-Cuando publicas un borrador de asesoría desde un repositorio público, todos pueden ver:
-
-- La versión actual de los datos de la asesoría.
-- Cualquier asesoría atribuye que los usuarios acreditados han aceptado.
-  
-{% note %}
-
-**Nota**: El público general nunca tendrá acceso al historial de edición del aviso y solo verá la versión publicada.
-
-{% endnote %}
-
-Después de que publicas una asesoría de seguridad, la URL de la misa permanecerá tal como antes de publicarla. Cualquiera con acceso de lectura al repositorio puede verla. Los colaboradores de la asesoría de seguridad pueden seguir viendo las conversaciones pasadas, incluyendo el flujo completo de comentarios, en la asesoría de seguridad a menos de que alguien con permisos administrativos elimine al colaborador de la asesoría de seguridad. 
-
-Si necesitas actualizar o corregir información en una asesoría de seguridad que hayas publicado, puedes editarla. Para más información, vea "[Edición de un aviso de seguridad de repositorio](/code-security/repository-security-advisories/editing-a-repository-security-advisory)".
-
-## Publicar una asesoría de seguridad
-
-El publicar una asesoría de seguridad borra la bifurcación temporal privada para la misma.
-
-{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %} {% data reusables.repositories.sidebar-advisories %}
-4. En el listado de "Asesorías de Seguridad", da clic sobre la que quieras publicar.
-  ![Aviso de seguridad en la lista](/assets/images/help/security/security-advisory-in-list.png)
-5. En la parte inferior de la página, haga clic en **Publish advisory**.
-  ![Botón para publicar aviso](/assets/images/help/security/publish-advisory-button.png)
-  
-## {% data variables.product.prodname_dependabot_alerts %} para las asesorías de seguridad publicadas
-
-{% data reusables.repositories.github-reviews-security-advisories %}
-
-## Solicitar un número de identificación de CVE (Opcional)
-
-{% data reusables.repositories.request-security-advisory-cve-id %} Para más información, vea "[Acerca de {% data variables.product.prodname_security_advisories %} para repositorios](/code-security/repository-security-advisories/about-github-security-advisories-for-repositories#cve-identification-numbers)".
-
-{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %} {% data reusables.repositories.sidebar-advisories %}
-4. En el listado de "Asesorías de Seguridad", da clic en aquella para la cual quieras solicitar un número de identificación de CVE.
-  ![Aviso de seguridad en la lista](/assets/images/help/security/security-advisory-in-list.png)
-5. Use el menú desplegable **Publish advisory** y haga clic en **Request CVE**.
-  ![Solicitud de CVE en el menú desplegable](/assets/images/help/security/security-advisory-drop-down-request-cve.png)
-6. Haga clic en **Request CVE**.
-  ![Botón de solicitud de CVE](/assets/images/help/security/security-advisory-request-cve-button.png)
-
-## Información adicional
-
-- "[Retirada de un aviso de seguridad de repositorio](/code-security/repository-security-advisories/withdrawing-a-repository-security-advisory)"
diff --git a/translations/es-ES/content/code-security/repository-security-advisories/removing-a-collaborator-from-a-repository-security-advisory.md b/translations/es-ES/content/code-security/repository-security-advisories/removing-a-collaborator-from-a-repository-security-advisory.md
deleted file mode 100644
index 0fadfa2ed6..0000000000
--- a/translations/es-ES/content/code-security/repository-security-advisories/removing-a-collaborator-from-a-repository-security-advisory.md
+++ /dev/null
@@ -1,42 +0,0 @@
----
-title: Eliminación de un colaborador de un aviso de seguridad del repositorio
-intro: 'Cuando eliminas a un colaborador de una asesoría de seguridad de repositorio, este pierde el acceso de lectura y escritura en el debate y los metadatos de aquella.'
-redirect_from:
-  - /github/managing-security-vulnerabilities/removing-a-collaborator-from-a-security-advisory
-  - /code-security/security-advisories/removing-a-collaborator-from-a-security-advisory
-versions:
-  fpt: '*'
-  ghec: '*'
-type: how_to
-topics:
-  - Security advisories
-  - Vulnerabilities
-  - Collaboration
-shortTitle: Remove collaborators
-ms.openlocfilehash: ced0edd0614304c0d33ddd40dce3c6a24a9ffcfd
-ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
-ms.translationtype: HT
-ms.contentlocale: es-ES
-ms.lasthandoff: 09/10/2022
-ms.locfileid: '145119361'
----
-Las personas con permisos administrativos en una asesoría de seguridad pueden eliminar a los colaboradores de la misma.
-
-{% data reusables.security-advisory.repository-level-advisory-note %}
-
-## Eliminar un colaborador de una asesoría de seguridad
-
-{% data reusables.repositories.security-advisory-collaborators-public-repositories %}
-
-{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %} {% data reusables.repositories.sidebar-advisories %}
-4. En el listado de "Asesorías de Seguridad", da clic sobre aquella en la que quieras eliminar a algún colaborador.
-  ![Aviso de seguridad en la lista](/assets/images/help/security/security-advisory-in-list.png)
-5. En el lado derecho de la página, debajo de "Colaboradores", encuentra el nombre del usuario o equipo al que quieres eliminar de la asesoría de seguridad.
-  ![Colaborador de asesoría de seguridad](/assets/images/help/security/security-advisory-collaborator.png)
-6. Junto al colaborador que quiera quitar, haga clic en el icono **X**.
-  ![Icono X para quitar al colaborador de la asesoría de seguridad](/assets/images/help/security/security-advisory-remove-collaborator-x.png)
-
-## Información adicional
-
-- "[Niveles de permiso para avisos de seguridad de repositorios](/code-security/repository-security-advisories/permission-levels-for-repository-security-advisories)"
-- "[Adición de un colaborador a un aviso de seguridad de repositorio](/code-security/repository-security-advisories/adding-a-collaborator-to-a-repository-security-advisory)"
diff --git a/translations/es-ES/content/code-security/repository-security-advisories/withdrawing-a-repository-security-advisory.md b/translations/es-ES/content/code-security/repository-security-advisories/withdrawing-a-repository-security-advisory.md
deleted file mode 100644
index 53178e2491..0000000000
--- a/translations/es-ES/content/code-security/repository-security-advisories/withdrawing-a-repository-security-advisory.md
+++ /dev/null
@@ -1,28 +0,0 @@
----
-title: Retirada de un aviso de seguridad de repositorio
-intro: Puedes retirar una asesoría de seguridad de repositorio que hayas publicado.
-redirect_from:
-  - /github/managing-security-vulnerabilities/withdrawing-a-security-advisory
-  - /code-security/security-advisories/withdrawing-a-security-advisory
-versions:
-  fpt: '*'
-  ghec: '*'
-type: how_to
-topics:
-  - Security advisories
-  - Vulnerabilities
-shortTitle: Withdraw repository advisories
-ms.openlocfilehash: 1d85afddaadbd25c5b24ab945dac998b7842ae23
-ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
-ms.translationtype: HT
-ms.contentlocale: es-ES
-ms.lasthandoff: 09/10/2022
-ms.locfileid: '145119329'
----
-{% data reusables.security-advisory.repository-level-advisory-note %}
-
-Si publicas una asesoría de seguridad por error, puedes retirarla contactando a {% data variables.contact.contact_support %}.
-
-## Información adicional
-
-- "[Edición de un aviso de seguridad de repositorio](/code-security/repository-security-advisories/editing-a-repository-security-advisory)"
diff --git a/translations/es-ES/content/code-security/security-overview/about-the-security-overview.md b/translations/es-ES/content/code-security/security-overview/about-the-security-overview.md
index 69e55a8adc..c763b80753 100644
--- a/translations/es-ES/content/code-security/security-overview/about-the-security-overview.md
+++ b/translations/es-ES/content/code-security/security-overview/about-the-security-overview.md
@@ -67,17 +67,23 @@ The security overview displays active alerts raised by security features. If the
 
 At the organization-level, the security overview displays aggregate and repository-specific security information for repositories owned by your organization. You can filter information by security features at the organization-level.
 
+Organization owners and security managers for organizations have access to the organization-level security overview. {% ifversion ghec or ghes > 3.6 or ghae > 3.6 %}Organization members can access the organization-level security overview to view results for repositories where they have admin privileges or have been granted access to security alerts. For more information on managing security alert access, see "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)".{% endif %}
+
 {% ifversion ghec or ghes > 3.4 or ghae > 3.4 %}
 ### About the enterprise-level security overview
 At the enterprise-level, the security overview displays aggregate and repository-specific security information for your enterprise. You can view repositories owned by your enterprise that have security alerts, view all security alerts, or security feature-specific alerts from across your enterprise.
 
-Organization owners and security managers for organizations in your enterprise also have limited access to the enterprise-level security overview. They can only view repositories and alerts for the organizations that they have full access to.
+Organization owners and security managers for organizations in your enterprise have access to the enterprise-level security overview. They can view repositories and alerts for the organizations that they have full access to.
+
+Enterprise owners can only see alerts for organizations that they are an owner or a security manager of.{% ifversion ghec or ghes > 3.5 or ghae > 3.5 %} Enterprise owners can join an organization as an organization owner to see all of its alerts in the enterprise-level security overview. For more information, see "[Managing your role in an organization owned by your enterprise](/admin/user-management/managing-organizations-in-your-enterprise/managing-your-role-in-an-organization-owned-by-your-enterprise)."{% endif %}
 
 {% elsif fpt %}
 ### About the enterprise-level security overview
 At the enterprise-level, the security overview displays aggregate and repository-specific information for an enterprise. For more information, see "[About the enterprise-level security overview](/enterprise-cloud@latest/code-security/security-overview/about-the-security-overview#about-the-enterprise-level-security-overview)" in the {% data variables.product.prodname_ghe_cloud %} documentation.
 {% endif %}
 
+{% ifversion ghes < 3.7 or ghae < 3.7 %}
 ### About the team-level security overview
 At the team-level, the security overview displays repository-specific security information for repositories that the team has admin privileges for. For more information, see "[Managing team access to an organization repository](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository)."
 {% endif %}
+{% endif %}
diff --git a/translations/es-ES/content/codespaces/codespaces-reference/allowing-your-codespace-to-access-a-private-image-registry.md b/translations/es-ES/content/codespaces/codespaces-reference/allowing-your-codespace-to-access-a-private-image-registry.md
index 40094b5db2..fe7c29fd82 100644
--- a/translations/es-ES/content/codespaces/codespaces-reference/allowing-your-codespace-to-access-a-private-image-registry.md
+++ b/translations/es-ES/content/codespaces/codespaces-reference/allowing-your-codespace-to-access-a-private-image-registry.md
@@ -30,7 +30,7 @@ If you publish a container image to {% data variables.packages.prodname_ghcr_or_
 
 By default, when you publish a container image to {% data variables.packages.prodname_ghcr_or_npm_registry %}, the image inherits the access setting of the repository from which the image was published. For example, if the repository is public, the image is also public. If the repository is private, the image is also private, but is accessible from the repository.
 
-This behavior is controlled by the **Inherit access from repo** option. **Inherit access from repo** is selected by default when publishing via {% data variables.product.prodname_actions %}, but not when publishing directly to {% data variables.packages.prodname_ghcr_or_npm_registry %} using a % data variables.product.pat_generic %}.
+This behavior is controlled by the **Inherit access from repo** option. **Inherit access from repo** is selected by default when publishing via {% data variables.product.prodname_actions %}, but not when publishing directly to {% data variables.packages.prodname_ghcr_or_npm_registry %} using a {% data variables.product.pat_generic %}.
 
 If the **Inherit access from repo** option was not selected when the image was published, you can manually add the repository to the published container image's access controls. For more information, see "[Configuring a package's access control and visibility](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility#inheriting-access-for-a-container-image-from-a-repository)."
 
diff --git a/translations/es-ES/content/codespaces/guides.md b/translations/es-ES/content/codespaces/guides.md
index fc2c956683..9adf5f265b 100644
--- a/translations/es-ES/content/codespaces/guides.md
+++ b/translations/es-ES/content/codespaces/guides.md
@@ -15,6 +15,8 @@ includeGuides:
   - /codespaces/setting-up-your-project-for-codespaces/setting-up-your-python-project-for-codespaces
   - /codespaces/setting-up-your-project-for-codespaces/setting-up-your-dotnet-project-for-codespaces
   - /codespaces/setting-up-your-project-for-codespaces/setting-up-your-java-project-for-codespaces
+  - /codespaces/setting-up-your-project-for-codespaces/setting-a-minimum-specification-for-codespace-machines
+  - /codespaces/setting-up-your-project-for-codespaces/automatically-opening-files-in-the-codespaces-for-a-repository
   - /codespaces/setting-up-your-project-for-codespaces/adding-a-codespaces-badge
   - /codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project
   - /codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account
diff --git a/translations/es-ES/content/codespaces/setting-up-your-project-for-codespaces/index.md b/translations/es-ES/content/codespaces/setting-up-your-project-for-codespaces/index.md
index b192f5eb36..1f73e1b379 100644
--- a/translations/es-ES/content/codespaces/setting-up-your-project-for-codespaces/index.md
+++ b/translations/es-ES/content/codespaces/setting-up-your-project-for-codespaces/index.md
@@ -17,6 +17,7 @@ children:
   - /setting-up-your-java-project-for-codespaces
   - /setting-up-your-python-project-for-codespaces
   - /setting-a-minimum-specification-for-codespace-machines
+  - /automatically-opening-files-in-the-codespaces-for-a-repository
   - /adding-a-codespaces-badge
 ms.openlocfilehash: 1e172243dc351f0a173c8624b66914e1c3795495
 ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794
diff --git a/translations/es-ES/content/codespaces/setting-up-your-project-for-codespaces/setting-a-minimum-specification-for-codespace-machines.md b/translations/es-ES/content/codespaces/setting-up-your-project-for-codespaces/setting-a-minimum-specification-for-codespace-machines.md
index fa17010bbb..9bd36a5a2a 100644
--- a/translations/es-ES/content/codespaces/setting-up-your-project-for-codespaces/setting-a-minimum-specification-for-codespace-machines.md
+++ b/translations/es-ES/content/codespaces/setting-up-your-project-for-codespaces/setting-a-minimum-specification-for-codespace-machines.md
@@ -1,7 +1,7 @@
 ---
-title: Configurar una especificación mínima para las máquinas de los codespaces
+title: Setting a minimum specification for codespace machines
 shortTitle: Set a minimum machine spec
-intro: 'Puedes evitar que los tipos de máquina con recursos insuficientes se usen en los {% data variables.product.prodname_github_codespaces %} de tu repositorio.'
+intro: 'You can avoid under-resourced machine types being used for {% data variables.product.prodname_github_codespaces %} for your repository.'
 permissions: People with write permissions to a repository can create or edit the codespace configuration.
 versions:
   fpt: '*'
@@ -11,29 +11,24 @@ topics:
   - Codespaces
   - Set up
 product: '{% data reusables.gated-features.codespaces %}'
-ms.openlocfilehash: 368b7c73d13bb0624c9d838ac2d7bb18a2b050e3
-ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
-ms.translationtype: HT
-ms.contentlocale: es-ES
-ms.lasthandoff: 09/10/2022
-ms.locfileid: '147880810'
 ---
-## Información general
 
-Cada codespace que crees se hospeda en una máquina virtual independiente, y normalmente puedes elegir entre diferentes tipos de máquinas virtuales. Cada tipo de máquina tiene recursos diferentes (CPU, memoria, almacenamiento) y, de forma predeterminada, se usa el tipo de máquina con los recursos mínimos. Para obtener más información, consulte "[Cambio del tipo de máquina para el codespace](/codespaces/customizing-your-codespace/changing-the-machine-type-for-your-codespace#about-machine-types)".
+## Overview
 
-Si tu proyecto necesita cierto nivel de potencia de cómputo, puedes configurar {% data variables.product.prodname_github_codespaces %} para que solo los tipos de máquina que cumplan con estos requisitos se puedan usar de forma predeterminada o los puedan seleccionar los usuarios. Esta configuración se realiza en un archivo `devcontainer.json`.
+Each codespace that you create is hosted on a separate virtual machine, and you can usually choose from different types of virtual machines. Each machine type has different resources (processor cores, memory, storage) and, by default, the machine type with the least resources is used. For more information, see "[Changing the machine type for your codespace](/codespaces/customizing-your-codespace/changing-the-machine-type-for-your-codespace#about-machine-types)."
+
+If your project needs a certain level of compute power, you can configure {% data variables.product.prodname_github_codespaces %} so that only machine types that meet these requirements can be used by default, or selected by users. You configure this in a `devcontainer.json` file.
 
 {% note %}
 
-**Importante:** El acceso a algunos tipos de máquina puede estar restringido en el nivel de organización. Habitualmente, esto se hace para prevenir que las personas elijan máquinas con recursos superiores, las cuales se cobran en tazas más altas. Si tu repositorio se ve afectado por la política de tipos de máquina a nivel organizacional, debes asegurarte de que no configures una especificación mínima que impida que las personas seleccionen los tipos de máquina disponibles que necesitan. Para obtener más información, consulte "[Restringir el acceso a los tipos de máquina](/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types)".
+**Important:** Access to some machine types may be restricted at the organization level. Typically this is done to prevent people choosing higher resourced machines that are billed at a higher rate. If your repository is affected by an organization-level policy for machine types you should make sure you don't set a minimum specification that would leave no available machine types for people to choose. For more information, see "[Restricting access to machine types](/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types)."
 
 {% endnote %}
 
-## Configurar una especificación de máquina mínima
+## Setting a minimum machine specification
 
-1. Los {% data variables.product.prodname_github_codespaces %} del repositorio se configuran en un archivo `devcontainer.json`. Si el repositorio aún no contiene un archivo `devcontainer.json`, agregue uno ahora. Consulta "[Adición de una configuración de contenedor de desarrollo al repositorio](/free-pro-team@latest/codespaces/setting-up-your-project-for-codespaces/setting-up-your-project-for-codespaces)".
-1. Edite el archivo `devcontainer.json` y agregue una propiedad `hostRequirements` como esta:
+{% data reusables.codespaces.edit-devcontainer-json %}
+1. Edit the `devcontainer.json` file, adding the `hostRequirements` property at the top level of the file, within the enclosing JSON object. For example:
 
    ```json{:copy}
    "hostRequirements": {
@@ -43,16 +38,16 @@ Si tu proyecto necesita cierto nivel de potencia de cómputo, puedes configurar
    }
    ```
 
-   Puede especificar una de las opciones o todas: `cpus`, `memory` y `storage`.
+   You can specify any or all of the options: `cpus`, `memory`, and `storage`.
    
-   Para verificar las especificaciones de los tipos de máquina de {% data variables.product.prodname_github_codespaces %} que actualmente están disponibles para tu repositorio, realiza el proceso de crear un codespace hasta que veas la elección de tipos de máquina. Para obtener más información, consulte "[Crear un codespace](/codespaces/developing-in-codespaces/creating-a-codespace#creating-a-codespace)".
+   To check the specifications of the {% data variables.product.prodname_github_codespaces %} machine types that are currently available for your repository, step through the process of creating a codespace until you see the choice of machine types. For more information, see "[Creating a codespace](/codespaces/developing-in-codespaces/creating-a-codespace#creating-a-codespace)."
    
-1. Guarda el archivo y confirma tus cambios a la rama requerida del repositorio.
+1. Save the file and commit your changes to the required branch of the repository.
 
-   Ahora, cuando crees un codespace para esta rama del repositorio y vayas a las opciones de configuración de creación, solo podrás seleccionar tipos de máquina que coincidan con los recursos que especificaste o los excedan.
+   Now when you create a codespace for that branch of the repository, and you go to the creation configuration options, you will only be able to select machine types that match or exceed the resources you've specified.
 
-   ![Caja de diálogo que muestra una selección limitada de tipos de máquina](/assets/images/help/codespaces/machine-types-limited-choice.png)
+   ![Dialog box showing a limited choice of machine types](/assets/images/help/codespaces/machine-types-limited-choice.png)
 
-## Información adicional
+## Further reading
 
-- "[Introducción a los contenedores de desarrollo](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers)"
+- "[Introduction to dev containers](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers)"
diff --git a/translations/es-ES/content/packages/working-with-a-github-packages-registry/working-with-the-npm-registry.md b/translations/es-ES/content/packages/working-with-a-github-packages-registry/working-with-the-npm-registry.md
index f17d1a1b94..e687fd7b2b 100644
--- a/translations/es-ES/content/packages/working-with-a-github-packages-registry/working-with-the-npm-registry.md
+++ b/translations/es-ES/content/packages/working-with-a-github-packages-registry/working-with-the-npm-registry.md
@@ -142,14 +142,14 @@ You can use `publishConfig` element in the *package.json* file to specify the re
   {% endif %}
   ```shell
   "publishConfig": {
-    "registry":"https://{% ifversion fpt or ghec %}npm.pkg.github.com{% else %}npm.HOSTNAME/{% endif %}"
+    "registry": "https://{% ifversion fpt or ghec %}npm.pkg.github.com{% else %}npm.HOSTNAME/{% endif %}"
   },
   ```
   {% ifversion ghes %}
   If your instance has subdomain isolation disabled:
    ```shell
    "publishConfig": {
-     "registry":"https://HOSTNAME/_registry/npm/"
+     "registry": "https://HOSTNAME/_registry/npm/"
    },
   ```
   {% endif %}
diff --git a/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches.md b/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches.md
index 2b581bcc4d..a2808b957d 100644
--- a/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches.md
+++ b/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches.md
@@ -187,7 +187,7 @@ When you enable branch restrictions, only users, teams, or apps that have been g
 Optionally, you can apply the same restrictions to the creation of branches that match the rule. For example, if you create a rule that only allows a certain team to push to any branches that contain the word `release`, only members of that team would be able to create a new branch that contains the word `release`.
 {% endif %}
 
-You can only give push access to a protected branch, or give permission to create a matching 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 or create a matching branch.
+You can only give push access to a protected branch, or give permission to create a matching 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{% ifversion restrict-pushes-create-branch %} or create a matching branch{% endif %}.
 
 ### Allow force pushes
 
diff --git a/translations/es-ES/content/repositories/creating-and-managing-repositories/transferring-a-repository.md b/translations/es-ES/content/repositories/creating-and-managing-repositories/transferring-a-repository.md
index dff4c98d4d..ca7dd28f84 100644
--- a/translations/es-ES/content/repositories/creating-and-managing-repositories/transferring-a-repository.md
+++ b/translations/es-ES/content/repositories/creating-and-managing-repositories/transferring-a-repository.md
@@ -51,6 +51,12 @@ When you transfer a repository, its issues, pull requests, wiki, stars, and watc
   $ git remote set-url origin NEW_URL
   ```
 
+  {% warning %}
+
+  **Warning**: If you create a new repository under your account in the future, do not reuse the original name of the transferred repository. If you do, redirects to the transferred repository will no longer work.
+
+  {% endwarning %}
+
 - When you transfer a repository from an organization to a personal account, the repository's read-only collaborators will not be transferred. This is because collaborators can't have read-only access to repositories owned by a personal account. For more information about repository permission levels, see "[Permission levels for a personal account repository](/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository)" and "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)."{% ifversion fpt or ghec %}
 - Sponsors who have access to the repository through a sponsorship tier may be affected. For more information, see "[Adding a repository to a sponsorship tier](/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers#adding-a-repository-to-a-sponsorship-tier)".{% endif %}
 
diff --git a/translations/es-ES/data/learning-tracks/code-security.yml b/translations/es-ES/data/learning-tracks/code-security.yml
index a614b6945c..3b35eb0a73 100644
--- a/translations/es-ES/data/learning-tracks/code-security.yml
+++ b/translations/es-ES/data/learning-tracks/code-security.yml
@@ -4,15 +4,18 @@ security_advisories:
   description: 'Using repository security advisories to privately fix a reported vulnerability and get a CVE.'
   featured_track: '{% ifversion fpt or ghec %}true{% else %}false{% endif %}'
   guides:
-    - /code-security/repository-security-advisories/about-coordinated-disclosure-of-security-vulnerabilities
-    - /code-security/repository-security-advisories/creating-a-repository-security-advisory
-    - /code-security/repository-security-advisories/adding-a-collaborator-to-a-repository-security-advisory
-    - /code-security/repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability
-    - /code-security/repository-security-advisories/publishing-a-repository-security-advisory
-    - /code-security/repository-security-advisories/editing-a-repository-security-advisory
-    - /code-security/repository-security-advisories/withdrawing-a-repository-security-advisory
-    - /code-security/repository-security-advisories/removing-a-collaborator-from-a-repository-security-advisory
-    - /code-security/repository-security-advisories/best-practices-for-writing-repository-security-advisories
+    - /code-security/security-advisories/repository-security-advisories/about-coordinated-disclosure-of-security-vulnerabilities
+    - /code-security/security-advisories/global-security-advisories/about-the-github-advisory-database
+    - /code-security/security-advisories/global-security-advisories/about-global-security-advisories
+    - /code-security/security-advisories/repository-security-advisories/about-repository-security-advisories
+    - /code-security/security-advisories/repository-security-advisories/creating-a-repository-security-advisory
+    - /code-security/security-advisories/repository-security-advisories/adding-a-collaborator-to-a-repository-security-advisory
+    - /code-security/security-advisories/repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability
+    - /code-security/security-advisories/repository-security-advisories/publishing-a-repository-security-advisory
+    - /code-security/security-advisories/repository-security-advisories/editing-a-repository-security-advisory
+    - /code-security/security-advisories/repository-security-advisories/withdrawing-a-repository-security-advisory
+    - /code-security/security-advisories/repository-security-advisories/removing-a-collaborator-from-a-repository-security-advisory
+    - /code-security/security-advisories/guidance-on-reporting-and-writing/best-practices-for-writing-repository-security-advisories
 
 # Feature available on dotcom and GHES 3.3+, so articles available on GHAE and earlier GHES hidden to hide the learning track
 dependabot_alerts:
diff --git a/translations/es-ES/data/reusables/repositories/security-advisories-republishing.md b/translations/es-ES/data/reusables/repositories/security-advisories-republishing.md
index 06ee0dcb3c..c2f7cd1471 100644
--- a/translations/es-ES/data/reusables/repositories/security-advisories-republishing.md
+++ b/translations/es-ES/data/reusables/repositories/security-advisories-republishing.md
@@ -1,9 +1 @@
----
-ms.openlocfilehash: 0ac903914a15eacb9f6db488c4c1cac01a6411e6
-ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
-ms.translationtype: HT
-ms.contentlocale: es-ES
-ms.lasthandoff: 09/11/2022
-ms.locfileid: "145092576"
----
-También puedes utilizar {% data variables.product.prodname_security_advisories %} para volver a publicar los detalles de una vulnerabilidad de seguridad que ya has divulgado en otro lugar si copias y pegas los detalles de la vulnerabilidad en una asesoría de seguridad nueva.
+You can also use repository security advisories to republish the details of a security vulnerability that you have already disclosed elsewhere by copying and pasting the details of the vulnerability into a new security advisory.
diff --git a/translations/es-ES/data/reusables/secret-scanning/partner-secret-list-private-repo.md b/translations/es-ES/data/reusables/secret-scanning/partner-secret-list-private-repo.md
index be855d2fd0..3d68fc424b 100644
--- a/translations/es-ES/data/reusables/secret-scanning/partner-secret-list-private-repo.md
+++ b/translations/es-ES/data/reusables/secret-scanning/partner-secret-list-private-repo.md
@@ -90,6 +90,8 @@ Google | Google OAuth Refresh Token | google_oauth_refresh_token{% endif %}
 Grafana | Grafana API Key | grafana_api_key
 HashiCorp | Terraform Cloud / Enterprise API Token | terraform_api_token
 HashiCorp | HashiCorp Vault Batch Token | hashicorp_vault_batch_token
+{%- ifversion fpt or ghec or ghes > 3.8 or ghae > 3.8 %}
+HashiCorp | HashiCorp Vault Root Service Token | hashicorp_vault_root_service_token{% endif %}
 HashiCorp | HashiCorp Vault Service Token | hashicorp_vault_service_token
 Hubspot | Hubspot API Key | hubspot_api_key
 Intercom | Intercom Access Token | intercom_access_token
diff --git a/translations/es-ES/data/reusables/security-advisory/security-advisory-overview.md b/translations/es-ES/data/reusables/security-advisory/security-advisory-overview.md
index 8f18c6171b..3c4c6a964f 100644
--- a/translations/es-ES/data/reusables/security-advisory/security-advisory-overview.md
+++ b/translations/es-ES/data/reusables/security-advisory/security-advisory-overview.md
@@ -1,9 +1 @@
----
-ms.openlocfilehash: aa9f7cd0b911ddfc6e144c7c91cecd0374286b13
-ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
-ms.translationtype: HT
-ms.contentlocale: es-ES
-ms.lasthandoff: 09/10/2022
-ms.locfileid: "145137530"
----
-Las {% data variables.product.prodname_security_advisories %} permiten a los manenedores de repositorios debatir en privado y corregir vulnerabilidades de seguridad en los proyectos. Después de colaborar en una corrección, los mantenedores de repositorios pueden publicar el aviso de seguridad para revelar públicamente la vulnerabilidad de seguridad a la comunidad del proyecto. Al publicar avisos de seguridad, los mantenedores de repositorios facilitan a su comunidad la actualización de las dependencias de paquetes y la investigación del impacto de las vulnerabilidades de seguridad.
+Repository security advisories allow repository maintainers to privately discuss and fix a security vulnerability in a project. After collaborating on a fix, repository maintainers can publish the security advisory to publicly disclose the security vulnerability to the project's community. By publishing security advisories, repository maintainers make it easier for their community to update package dependencies and research the impact of the security vulnerabilities.
diff --git a/translations/es-ES/data/reusables/security-overview/permissions.md b/translations/es-ES/data/reusables/security-overview/permissions.md
index 2cf85d19c5..43dd55172d 100644
--- a/translations/es-ES/data/reusables/security-overview/permissions.md
+++ b/translations/es-ES/data/reusables/security-overview/permissions.md
@@ -1 +1 @@
-Organization owners and security managers can access the security overview for organizations{% ifversion ghec or ghes > 3.4 or ghae > 3.4 %} and view their organization's repositories via the enterprise-level security overview. Enterprise owners can use the enterprise-level security overview to view all repositories in their enterprise's organizations{% endif %}. Members of a team can see the security overview for repositories that the team has admin privileges for.
+{% ifversion not fpt %}Organization owners and security managers can access the organization-level security overview{% ifversion ghec or ghes > 3.4 or ghae > 3.4 %} and view alerts across multiple organizations via the enterprise-level security overview. Enterprise owners can only view repositories and alerts for organizations where they are added as an organization owner or security manager{% endif %}. {% ifversion ghec or ghes > 3.6 or ghae > 3.6 %}Organization members can access the organization-level security overview to view results for repositories where they have admin privileges or have been granted access to security alerts.{% else %}Members of a team can see the security overview for repositories that the team has admin privileges for.{% endif %}{% endif %}
diff --git a/translations/ja-JP/content/account-and-profile/managing-subscriptions-and-notifications-on-github/viewing-and-triaging-notifications/managing-notifications-from-your-inbox.md b/translations/ja-JP/content/account-and-profile/managing-subscriptions-and-notifications-on-github/viewing-and-triaging-notifications/managing-notifications-from-your-inbox.md
index ba60987068..a006c11816 100644
--- a/translations/ja-JP/content/account-and-profile/managing-subscriptions-and-notifications-on-github/viewing-and-triaging-notifications/managing-notifications-from-your-inbox.md
+++ b/translations/ja-JP/content/account-and-profile/managing-subscriptions-and-notifications-on-github/viewing-and-triaging-notifications/managing-notifications-from-your-inbox.md
@@ -161,7 +161,7 @@ For example, to see notifications from the octo-org organization, use `org:octo-
 
 ## {% data variables.product.prodname_dependabot %} custom filters
 
-{% ifversion fpt or ghec or ghes > 3.2 %}
+{% ifversion fpt or ghec or ghes %}
 If you use {% data variables.product.prodname_dependabot %} to keep your dependencies up-to-date, you can use and save these custom filters:
 - `is:repository_vulnerability_alert` to show notifications for {% data variables.product.prodname_dependabot_alerts %}.
 - `reason:security_alert` to show notifications for {% data variables.product.prodname_dependabot_alerts %} and security update pull requests.
@@ -170,7 +170,7 @@ If you use {% data variables.product.prodname_dependabot %} to keep your depende
 For more information about {% data variables.product.prodname_dependabot %}, see "[About {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)."
 {% endif %}
 
-{% ifversion ghes < 3.3 or ghae %}
+{% ifversion ghae %}
 
 If you use {% data variables.product.prodname_dependabot %} to tell you about insecure dependencies, you can use and save these custom filters to show notifications for {% data variables.product.prodname_dependabot_alerts %}:
 - `is:repository_vulnerability_alert` 
diff --git a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/about-your-organizations-profile.md b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/about-your-organizations-profile.md
index a2124b6092..e90733dfb6 100644
--- a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/about-your-organizations-profile.md
+++ b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/about-your-organizations-profile.md
@@ -24,7 +24,7 @@ Organizations that use {% data variables.product.prodname_ghe_cloud %} can confi
 To confirm your organization's identity and display a "Verified" badge on your organization profile page, you can verify your organization's domains with {% data variables.product.prodname_dotcom %}. For more information, see "[Verifying or approving a domain for your organization](/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization)."
 {% endif %}
 
-{% ifversion fpt or ghes > 3.2 or ghec %}
+{% ifversion fpt or ghes or ghec %}
 ![Sample organization profile page](/assets/images/help/organizations/org_profile_with_overview.png)
 {% else %}
 ![Sample organization profile page](/assets/images/help/profile/org_profile.png)
diff --git a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/setting-your-profile-to-private.md b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/setting-your-profile-to-private.md
index 9ef85f8450..33de873e4a 100644
--- a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/setting-your-profile-to-private.md
+++ b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/setting-your-profile-to-private.md
@@ -1,56 +1,62 @@
 ---
-title: Setting your profile to private
-intro: 'A private profile displays only limited information, and hides some activity.'
+title: プロファイルをプライベートに設定する
+intro: プライベート プロファイルには限られた情報のみが表示され、一部のアクティビティは表示されません。
 versions:
   fpt: '*'
 topics:
   - Profiles
 shortTitle: Set profile to private
+ms.openlocfilehash: c00718c84d99de95a9ca1352f32954279906451d
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: ja-JP
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148008670'
 ---
-## About private profiles
+## プライベート プロファイルについて
 
-To hide parts of your profile page, you can make your profile private. This also hides your activity in various social features on {% data variables.product.prodname_dotcom_the_website %}. A private profile hides information from all users, and there is currently no option to allow specified users to see your activity.
+プロファイル ページの一部を非表示にするには、プロファイルをプライベートにします。 これにより、{% data variables.product.prodname_dotcom_the_website %} のさまざまなソーシャル機能のアクティビティも非表示になります。 プライベート プロファイルでは、すべてのユーザーに対し情報が非表示になります。現在、指定したユーザーにアクティビティを表示するオプションはありません。
 
-After making your profile private, you can still view all your information when you visit your own profile.
+プロファイルをプライベートにした後も、自分のプロファイルにアクセスした場合、すべての情報が表示されます。
 
-Private profiles cannot receive sponsorships under [{% data variables.product.prodname_sponsors %}](/sponsors/getting-started-with-github-sponsors/about-github-sponsors). To be eligible for {% data variables.product.prodname_sponsors %}, your profile cannot be private.
+プライベート プロファイルでは、[{% data variables.product.prodname_sponsors %}](/sponsors/getting-started-with-github-sponsors/about-github-sponsors) のスポンサーシップを受けることができません。 {% data variables.product.prodname_sponsors %} の対象になるには、プロファイルをプライベートにしないでください。
 
-## Differences between private and public profiles
+## プライベートおよびパブリック プロファイルの違い
 
-When your profile is private, the following content is hidden from your profile page:
+プロファイルがプライベートの場合、プロファイル ページで次のコンテンツが非表示になります。
 
-- Achievements and highlights.
-- Activity overview and activity feed.
-- Contribution graph.
-- Follower and following counts.
-- Follow and Sponsor buttons.
-- Organization memberships.
-- Stars, projects, packages, and sponsoring tabs.
+- 実績とハイライト。
+- アクティビティの概要とアクティビティ フィード。
+- コントリビューション グラフ。
+- フォロワーと次の数。
+- フォローとスポンサーのボタン。
+- Organization メンバーシップ。
+- スター、プロジェクト、パッケージ、スポンサー タブ。
 
 {% note %}
 
-**Note**: When your profile is private, some optional fields are still publicly visible, such as the README, biography, and profile photo.
+**注**: プロファイルがプライベートの場合、README、経歴、プロフィール写真などの一部のオプション フィールドは引き続きパブリックに表示されます。
 
 {% endnote %}
 
-## Changes to reporting on your activities
+## アクティビティに対する通知の変更
 
-By making your profile private, you will not remove or hide past activity; this setting only applies to your activity while the private setting is enabled.
+プロフィールをプライベートにしても、過去のアクティビティは削除または非表示になりません。この設定は、プライベート設定が有効になっている間のアクティビティにのみ適用されます。
 
-When your profile is private, your {% data variables.product.prodname_dotcom_the_website %} activity will not appear in the following locations:
+プロファイルがプライベートの場合、{% data variables.product.prodname_dotcom_the_website %} アクティビティは次の場所に表示されません。
 
-- Activity feeds for other users.
-- Discussions leaderboards.
-- The [Trending](https://github.com/trending) page.
+- 他のユーザーのアクティビティ フィード。
+- ディスカッション ランキング。
+- [[トレンド]](https://github.com/trending) ページ。
 
 {% note %}
 
-**Note**: Your activity on public repositories will still be publicly visible to anyone viewing those repositories, and some activity data may still be available through the {% data variables.product.prodname_dotcom %} API.
+**注**: パブリック リポジトリ上のアクティビティは、それらのリポジトリを表示しているユーザーには引き続きパブリックに表示され、一部のアクティビティ データは {% data variables.product.prodname_dotcom %} API を通じて引き続き使用できます。
 
 {% endnote %}
 
-## Changing your profile's privacy settings
+## プロファイルのプライバシー設定を変更する
 
 {% data reusables.user-settings.access_settings %}
-1. Under "Contributions & Activity", select the checkbox next to **Make profile private and hide activity**.
+1. [コントリビューションとアクティビティ] で、 **[プロファイルを非公開にしてアクティビティを非表示にする]** の横にあるチェックボックスをオンにします。
 {% data reusables.user-settings.update-preferences %}
diff --git a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-settings-on-your-profile/why-are-my-contributions-not-showing-up-on-my-profile.md b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-settings-on-your-profile/why-are-my-contributions-not-showing-up-on-my-profile.md
index 3e24053ec8..fa16c3f01b 100644
--- a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-settings-on-your-profile/why-are-my-contributions-not-showing-up-on-my-profile.md
+++ b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-settings-on-your-profile/why-are-my-contributions-not-showing-up-on-my-profile.md
@@ -69,11 +69,15 @@ The email address in the `From:` field is the address that was set in the [local
 
 If the email address used for the commit is not connected to your account on {% data variables.location.product_location %}, {% ifversion ghae %}change the email address used to author commits in Git. For more information, see "[Setting your commit email address](/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address#setting-your-commit-email-address-in-git)."{% else %}you must [add the email address](/articles/adding-an-email-address-to-your-github-account) to your account on {% data variables.location.product_location %}. Your contributions graph will be rebuilt automatically when you add the new address.{% endif %}
 
-{% warning %}
+{% ifversion fpt or ghec %}
+{% note %}
 
-**Warning**: Generic email addresses, such as `jane@computer.local`, cannot be added to {% data variables.product.prodname_dotcom %} accounts. If you use such an email for your commits, the commits will not be linked to your {% data variables.product.prodname_dotcom %} profile and will not show up in your contribution graph.
+**Note**: If you use a {% data variables.enterprise.prodname_managed_user %}, you cannot add additional email addresses to the account, even if multiple email addresses are registered with your identity provider (IdP). Therefore, only commits that are authored by the primary email address registered with your IdP can be associated with your {% data variables.enterprise.prodname_managed_user %}.
 
-{% endwarning %}
+{% endnote %}
+{% endif %}
+
+Generic email addresses, such as `jane@computer.local`, cannot be added to {% data variables.product.prodname_dotcom %} accounts and linked to commits. If you've authored any commits using a generic email address, the commits will not be linked to your {% data variables.product.prodname_dotcom %} profile and will not show up in your contribution graph.
 
 ### Commit was not made in the default or `gh-pages` branch
 
diff --git a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/index.md b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/index.md
index 63b2860091..d72f863eba 100644
--- a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/index.md
+++ b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/index.md
@@ -1,6 +1,6 @@
 ---
 title: Setting up and managing your personal account on GitHub
-intro: You can manage settings for your personal account on {% ifversion fpt or ghec or ghes %}{% data variables.location.product_location %}{% elsif ghae %}{% data variables.product.product_name %}{% endif %}, including email preferences, access to personal repositories, and organization memberships. You can also manage the account itself.
+intro: 'You can manage settings for your personal account on {% ifversion fpt or ghec or ghes %}{% data variables.location.product_location %}{% elsif ghae %}{% data variables.product.product_name %}{% endif %}, including email preferences, access to personal repositories, and organization memberships. You can also manage the account itself.'
 shortTitle: Personal accounts
 redirect_from:
   - /categories/setting-up-and-managing-your-github-user-account
diff --git a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-accessibility-settings.md b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-accessibility-settings.md
index 20771e8187..68a58042b1 100644
--- a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-accessibility-settings.md
+++ b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-accessibility-settings.md
@@ -1,7 +1,7 @@
 ---
 title: Managing accessibility settings
 shortTitle: Manage accessibility settings
-intro: "{% data variables.product.product_name %}'s user interface can adapt to your vision, hearing, motor, cognitive, or learning needs."
+intro: '{% data variables.product.product_name %}''s user interface can adapt to your vision, hearing, motor, cognitive, or learning needs.'
 versions:
   feature: keyboard-shortcut-accessibility-setting
 redirect_from:
diff --git a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-security-and-analysis-settings-for-your-personal-account.md b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-security-and-analysis-settings-for-your-personal-account.md
index 9362dbfa30..52815b7a7d 100644
--- a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-security-and-analysis-settings-for-your-personal-account.md
+++ b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-security-and-analysis-settings-for-your-personal-account.md
@@ -1,10 +1,10 @@
 ---
-title: 個人アカウントのセキュリティと分析設定を管理する
-intro: '{% data variables.product.prodname_dotcom %} 上のプロジェクトのコードをセキュリティ保護し分析する機能を管理できます。'
+title: Managing security and analysis settings for your personal account
+intro: 'You can control features that secure and analyze the code in your projects on {% data variables.product.prodname_dotcom %}.'
 versions:
   fpt: '*'
   ghec: '*'
-  ghes: '>3.2'
+  ghes: '*'
 topics:
   - Accounts
 redirect_from:
@@ -12,47 +12,43 @@ redirect_from:
   - /github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-security-and-analysis-settings-for-your-user-account
   - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-security-and-analysis-settings-for-your-user-account
 shortTitle: Manage security & analysis
-ms.openlocfilehash: 61d1944219fd1b75f476c7aef8305018c85735c5
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
-ms.translationtype: HT
-ms.contentlocale: ja-JP
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '145165351'
 ---
-## セキュリティおよび分析設定の管理について
+## About management of security and analysis settings
 
-{% data variables.product.prodname_dotcom %} を使用してリポジトリを保護できます。 このトピックでは、既存または新規のすべてのリポジトリのセキュリティおよび分析機能を管理する方法について説明します。
+{% data variables.product.prodname_dotcom %} can help secure your repositories. This topic tells you how you can manage the security and analysis features for all your existing or new repositories.
 
-個々のリポジトリのセキュリティおよび分析機能は引き続き管理できます。 詳細については、「[リポジトリのセキュリティと分析の設定を管理する](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)」を参照してください。
+You can still manage the security and analysis features for individual repositories. For more information, see "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)."
 
-自分の個人アカウントに対するすべてのアクティビティのセキュリティ ログを確認することもできます。 詳細については、「[セキュリティ ログの確認](/authentication/keeping-your-account-and-data-secure/reviewing-your-security-log)」を参照してください。
+You can also review the security log for all activity on your personal account. For more information, see "[Reviewing your security log](/authentication/keeping-your-account-and-data-secure/reviewing-your-security-log)."
 
 {% data reusables.security.some-security-and-analysis-features-are-enabled-by-default %}
 
 {% data reusables.security.security-and-analysis-features-enable-read-only %}
 
-リポジトリレベル セキュリティの概要については、「[リポジトリをセキュリティで保護する](/code-security/getting-started/securing-your-repository)」を参照してください。
+For an overview of repository-level security, see "[Securing your repository](/code-security/getting-started/securing-your-repository)."
 
-## 既存のリポジトリに対して機能を有効または無効にする
+## Enabling or disabling features for existing repositories
 
-{% data reusables.user-settings.access_settings %} {% data reusables.user-settings.security-analysis %}
-3. [Code security and analysis] の下で機能の右にある **[Disable all]** または **[Enable all]** をクリックします。
-  {% ifversion ghes > 3.2 %}!["Configure security and analysis" 機能の "Enable all" または "Disable all" ボタン](/assets/images/enterprise/3.3/settings/security-and-analysis-disable-or-enable-all.png){% else %}!["Configure security and analysis" 機能の "Enable all" または "Disable all" ボタン](/assets/images/help/settings/security-and-analysis-disable-or-enable-all.png){% endif %}
-6. オプションで、自分が所有する新しいリポジトリに対して機能を既定で有効にできます。
-  {% ifversion ghes > 3.2 %}![新しいリポジトリの "Enable by default" オプション](/assets/images/enterprise/3.3/settings/security-and-analysis-enable-by-default-in-modal.png){% else %}![新しいリポジトリの "Enable by default" オプション](/assets/images/help/settings/security-and-analysis-enable-by-default-in-modal.png){% endif %}
-7. **[Disable FEATURE]** または **[Enable FEATURE]** をクリックし、所有するすべてのリポジトリに対してこの機能を無効または有効にします。
-  {% ifversion ghes > 3.2 %}![機能を無効または有効にするボタン](/assets/images/enterprise/3.3/settings/security-and-analysis-enable-dependency-graph.png){% else %}![機能を無効または有効にするボタン](/assets/images/help/settings/security-and-analysis-enable-dependency-graph.png){% endif %}
+{% data reusables.user-settings.access_settings %}
+{% data reusables.user-settings.security-analysis %}
+3. Under "Code security and analysis", to the right of the feature, click **Disable all** or **Enable all**.
+  {% ifversion ghes %}!["Enable all" or "Disable all" button for "Configure security and analysis" features](/assets/images/enterprise/3.3/settings/security-and-analysis-disable-or-enable-all.png){% else %}!["Enable all" or "Disable all" button for "Configure security and analysis" features](/assets/images/help/settings/security-and-analysis-disable-or-enable-all.png){% endif %}
+6. Optionally, enable the feature by default for new repositories that you own.
+  {% ifversion ghes %}!["Enable by default" option for new repositories](/assets/images/enterprise/3.3/settings/security-and-analysis-enable-by-default-in-modal.png){% else %}!["Enable by default" option for new repositories](/assets/images/help/settings/security-and-analysis-enable-by-default-in-modal.png){% endif %}
+7. Click **Disable FEATURE** or **Enable FEATURE** to disable or enable the feature for all the repositories you own.
+  {% ifversion ghes %}![Button to disable or enable feature](/assets/images/enterprise/3.3/settings/security-and-analysis-enable-dependency-graph.png){% else %}![Button to disable or enable feature](/assets/images/help/settings/security-and-analysis-enable-dependency-graph.png){% endif %}
 
 {% data reusables.security.displayed-information %}
 
-## 既存のリポジトリに対して機能を有効または無効にする
+## Enabling or disabling features for new repositories
 
-{% data reusables.user-settings.access_settings %} {% data reusables.user-settings.security-analysis %}
-3. 機能の右側にある [Code security and analysis] で、所有する新しいリポジトリに対して既定で機能を有効または無効にします
-  {% ifversion ghes > 3.2 %}![新しいリポジトリの機能を有効または無効にするチェックボックス](/assets/images/enterprise/3.3/settings/security-and-analysis-enable-or-disable-feature-checkbox.png){% else %}![新しいリポジトリの機能を有効または無効にするチェックボックス](/assets/images/help/settings/security-and-analysis-enable-or-disable-feature-checkbox.png){% endif %}
+{% data reusables.user-settings.access_settings %}
+{% data reusables.user-settings.security-analysis %}
+3. Under "Code security and analysis", to the right of the feature, enable or disable the feature by default for new repositories that you own.
+  {% ifversion ghes %}![Checkbox for enabling or disabling a feature for new repositories](/assets/images/enterprise/3.3/settings/security-and-analysis-enable-or-disable-feature-checkbox.png){% else %}![Checkbox for enabling or disabling a feature for new repositories](/assets/images/help/settings/security-and-analysis-enable-or-disable-feature-checkbox.png){% endif %}
 
-## 参考資料
+## Further reading
 
-- "[依存関係グラフについて](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)"
-- "[{% data variables.product.prodname_dependabot_alerts %} について](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)"
-- "[依存関係を自動的に更新する](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically)"
+- "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)"
+- "[About {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)"
+- "[Keeping your dependencies updated automatically](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically)"
diff --git a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-your-cookie-preferences-for-githubs-enterprise-marketing-pages.md b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-your-cookie-preferences-for-githubs-enterprise-marketing-pages.md
index 5a3355a14d..8e891c2997 100644
--- a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-your-cookie-preferences-for-githubs-enterprise-marketing-pages.md
+++ b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-your-cookie-preferences-for-githubs-enterprise-marketing-pages.md
@@ -9,12 +9,12 @@ versions:
 topics:
   - Accounts
 shortTitle: Manage cookie preferences
-ms.openlocfilehash: f2fdbcf8bd552902e7db491aa1b3c6622c5673ab
-ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794
+ms.openlocfilehash: 44f0324a91f8447a10947d5f5c7be111241ad091
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: ja-JP
-ms.lasthandoff: 09/09/2022
-ms.locfileid: '147760923'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148108809'
 ---
 ## エンタープライズ マーケティング ページでの Cookie の基本設定について
 
diff --git a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-your-theme-settings.md b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-your-theme-settings.md
index 80754b00c6..584121c0e5 100644
--- a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-your-theme-settings.md
+++ b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-your-theme-settings.md
@@ -1,6 +1,6 @@
 ---
-title: テーマ設定を管理する
-intro: 'システム設定に従うか、ライトまたはダーク モードを常に使用するようにテーマを設定することで、{% data variables.product.product_name %} の外観を管理できます。'
+title: Managing your theme settings
+intro: 'You can manage how {% data variables.product.product_name %} looks to you by setting a theme preference that either follows your system settings or always uses a light or dark mode.'
 versions:
   fpt: '*'
   ghae: '*'
@@ -13,52 +13,51 @@ redirect_from:
   - /github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings
   - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings
 shortTitle: Manage theme settings
-ms.openlocfilehash: 6251b265d99271f58a4ad02d2f6cb7fdf722cb6b
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
-ms.translationtype: HT
-ms.contentlocale: ja-JP
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147580448'
 ---
-{% data variables.product.product_name %} を使用時期と使用方法を選択して柔軟性を高めるために、テーマ設定をして {% data variables.product.product_name %} の外観を変更できます。 ライトとダークの 2 つのテーマから選択するか、システム設定に従うかを {% data variables.product.product_name %} で設定できます。
 
-ダーク テーマを使用して、特定のデバイスの電力消費量を削減したり、暗い場所で目の負担を減らしたり、テーマの外観を優先したりすることができます。
+For choice and flexibility in how and when you use {% data variables.product.product_name %}, you can configure theme settings to change how {% data variables.product.product_name %} looks to you. You can choose from themes that are light or dark, or you can configure {% data variables.product.product_name %} to follow your system settings.
 
-{% ifversion fpt or ghes > 3.2 or ghae or ghec %}弱視の方は、前景と背景の要素のコントラストが強いハイ コントラスト テーマの使用をお勧めします。{% endif %}{% ifversion fpt or ghae or ghec %}色覚障碍がある方には、ライトとダークの色覚障碍向けテーマをお勧めします。
+You may want to use a dark theme to reduce power consumption on certain devices, to reduce eye strain in low-light conditions, or because you prefer how the theme looks.
+
+If you have low vision, you may benefit from a high contrast theme, with greater contrast between foreground and background elements.{% ifversion fpt or ghae or ghec %} If you have colorblindness, you may benefit from our light and dark colorblind themes.
 
 {% endif %}
 
-{% data reusables.user-settings.access_settings %} {% data reusables.user-settings.appearance-settings %}
+{% data reusables.user-settings.access_settings %}
+{% data reusables.user-settings.appearance-settings %}
 
-1. [テーマ モード] で、ドロップダウン メニューを選択し、テーマの設定をクリックします。
+1. Under "Theme mode", select the drop-down menu, then click a theme preference.
 
-   ![テーマの設定を選択するための [テーマ モード] のドロップダウン メニュー](/assets/images/help/settings/theme-mode-drop-down-menu.png)
-1. 使いたいテーマをクリックしてください。
-    - 1 つのテーマを選択する場合は、そのテーマをクリックします。
+   ![Drop-down menu under "Theme mode" for selection of theme preference](/assets/images/help/settings/theme-mode-drop-down-menu.png)
+1. Click the theme you'd like to use.
+    - If you chose a single theme, click a theme.
 
-      {%- ifversion ghes = 3.5 %} {% note %}
+      {%- ifversion ghes = 3.5 %}
+      {% note %}
 
-      **注**: 明るいハイ コントラスト テーマは、{% data variables.product.product_name %} 3.5.0、3.5.1、3.5.2、および 3.5.3 では使用できませんでした。 このテーマは 3.5.4 以降で使用できます。 アップグレードの詳しい情報については、サイト管理者にお問い合わせください。
+      **Note**: The light high contrast theme was unavailable in {% data variables.product.product_name %} 3.5.0, 3.5.1, 3.5.2, and 3.5.3. The theme is available in 3.5.4 and later. For more information about upgrades, contact your site administrator.
 
-      使用する {% data variables.product.product_name %} のバージョンの決定について詳しくは、「[{% data variables.product.prodname_docs %} のバージョンについて](/get-started/learning-about-github/about-versions-of-github-docs#github-enterprise-server)」を参照してください。
-      {% endnote %} {%- endif %}
+      For more information about determining the version of {% data variables.product.product_name %} you're using, see "[About versions of  {% data variables.product.prodname_docs %}](/get-started/learning-about-github/about-versions-of-github-docs#github-enterprise-server)."
+      {% endnote %}
+      {%- endif %}
 
-      {% ifversion fpt or ghes > 3.2 or ghae or ghec %}![1 つのテーマを選択するためのラジオ ボタン](/assets/images/help/settings/theme-choose-a-single-theme-highcontrast.png){% else %}![1 つのテーマを選択するためのラジオ ボタン](/assets/images/help/settings/theme-choose-a-single-theme.png){% endif %}
-    - システム設定に従うことを選択した場合は、昼のテーマと夜のテーマをクリックします。
+      ![Radio buttons for the choice of a single theme](/assets/images/help/settings/theme-choose-a-single-theme-highcontrast.png)
+    - If you chose to follow your system settings, click a day theme and a night theme.
 
-      {% ifversion fpt or ghes > 3.2 or ghae or ghec %}![システム設定と同期するテーマを選択するためのボタン](/assets/images/help/settings/theme-choose-a-day-and-night-theme-to-sync-highcontrast.png){% else %}![システム設定と同期するテーマを選択するためのボタン](/assets/images/help/settings/theme-choose-a-day-and-night-theme-to-sync.png){% endif %} {% ifversion fpt or ghec %}
-    - 現在パブリック ベータ版のテーマを選択する場合は、まず機能プレビューでそれを有効にする必要があります。 詳細については、「[機能プレビューを使用した早期アクセス リリースを探索する](/get-started/using-github/exploring-early-access-releases-with-feature-preview)」を参照してください。{% endif %}
+      ![Buttons for the choice of a theme to sync with the system setting](/assets/images/help/settings/theme-choose-a-day-and-night-theme-to-sync-highcontrast.png)
+    {% ifversion fpt or ghec %}
+    - If you would like to choose a theme which is currently in public beta, you will first need to enable it with feature preview. For more information, see "[Exploring early access releases with feature preview](/get-started/using-github/exploring-early-access-releases-with-feature-preview)."{% endif %}
 
 {% ifversion command-palette %}
 
 {% note %}
 
-**注:** コマンド パレットを使用してテーマの設定を変更することもできます。 詳細については、「[{% data variables.product.prodname_command_palette %}](/get-started/using-github/github-command-palette)」を参照してください。
+**Note:** You can also change your theme settings with the command palette. For more information, see "[{% data variables.product.prodname_command_palette %}](/get-started/using-github/github-command-palette)".
 
 {% endnote %}
 
 {% endif %}
 
-## 参考資料
+## Further reading
 
-- [{% data variables.product.prodname_desktop %}](/desktop/installing-and-configuring-github-desktop/setting-a-theme-for-github-desktop) の設定方法
+- "[Setting a theme for {% data variables.product.prodname_desktop %}](/desktop/installing-and-configuring-github-desktop/setting-a-theme-for-github-desktop)"
diff --git a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/permission-levels-for-a-personal-account-repository.md b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/permission-levels-for-a-personal-account-repository.md
index 44076f88da..e113259b91 100644
--- a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/permission-levels-for-a-personal-account-repository.md
+++ b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/permission-levels-for-a-personal-account-repository.md
@@ -1,6 +1,6 @@
 ---
-title: 個人アカウントのリポジトリの権限レベル
-intro: 個人アカウントが所有するリポジトリには、リポジトリ所有者とコラボレーターという 2 つのアクセス許可レベルがあります。
+title: Permission levels for a personal account repository
+intro: 'A repository owned by a personal account has two permission levels: the repository owner and collaborators.'
 redirect_from:
   - /articles/permission-levels-for-a-user-account-repository
   - /github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository
@@ -14,84 +14,79 @@ versions:
 topics:
   - Accounts
 shortTitle: Repository permissions
-ms.openlocfilehash: e7c7a542204c7b1ce69bc19ac326fb248bbbff12
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
-ms.translationtype: HT
-ms.contentlocale: ja-JP
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147066307'
 ---
-## 個人アカウント リポジトリのアクセス許可レベルについて
+## About permissions levels for a personal account repository
 
-個人アカウントが所有するリポジトリの所有者は 1 人です。 所有権のアクセス許可を別の個人アカウントと共有することはできません。
+Repositories owned by personal accounts have one owner. Ownership permissions can't be shared with another personal account.
 
-{% data variables.product.product_name %} のユーザーをコラボレーターとしてリポジトリに{% ifversion fpt or ghec %}招待{% else %}追加{% endif %}することもできます。 詳細については、「[コラボレーターを個人リポジトリに招待する](/github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository)」を参照してください。
+You can also {% ifversion fpt or ghec %}invite{% else %}add{% endif %} users on {% data variables.product.product_name %} to your repository as collaborators. For more information, see "[Inviting collaborators to a personal repository](/github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository)."
 
 {% tip %}
 
-**ヒント:** 個人アカウントが所有しているリポジトリに対して、より詳細なアクセス権が必要な場合には、リポジトリを Organization に移譲することを検討してください。 詳細については、「[リポジトリを移譲する](/github/administering-a-repository/transferring-a-repository#transferring-a-repository-owned-by-your-personal-account)」を参照してください。
+**Tip:** If you require more granular access to a repository owned by your personal account, consider transferring the repository to an organization. For more information, see "[Transferring a repository](/github/administering-a-repository/transferring-a-repository#transferring-a-repository-owned-by-your-personal-account)."
 
 {% endtip %}
 
-## 個人アカウントが所有しているリポジトリに対する所有者アクセス権
+## Owner access for a repository owned by a personal account
 
-リポジトリオーナーは、リポジトリを完全に制御することができます。 コラボレータが実行できるアクションに加えて、リポジトリオーナーは次のアクションを実行できます。
+The repository owner has full control of the repository. In addition to the actions that any collaborator can perform, the repository owner can perform the following actions.
 
-| アクション | 説明を見る |
+| Action | More information |
 | :- | :- |
-| {% ifversion fpt or ghec %}コラボレーターの招待{% else %}コラボレーターの追加{% endif %} | 「[コラボレーターを個人リポジトリに招待する](/github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository)」 |
-| リポジトリの表示変更 | 「[リポジトリの可視性を設定する](/github/administering-a-repository/setting-repository-visibility)」 |{% ifversion fpt or ghec %}
-| リポジトリとのインタラクションの制限 | 「[リポジトリでのインタラクションを制限する](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository)」 |{% endif %}
-| デフォルトブランチを含むブランチ名の変更 | 「[ブランチの名前を変更する](/github/administering-a-repository/renaming-a-branch)」 |
-| 保護されたブランチで、レビューの承認がなくてもプルリクエストをマージする | 「[保護されたブランチについて](/github/administering-a-repository/about-protected-branches)」 |
-| リポジトリを削除する | 「[リポジトリの削除](/repositories/creating-and-managing-repositories/deleting-a-repository)」 |
-| リポジトリのトピックの管理 | 「[トピックでリポジトリを分類する](/github/administering-a-repository/classifying-your-repository-with-topics)」 |{% ifversion fpt or ghec %}
-| リポジトリのセキュリティおよび分析設定の管理 | 「[リポジトリのセキュリティと分析設定を管理する](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)」 |{% endif %}{% ifversion fpt or ghec %}
-| プライベートリポジトリの依存関係グラフの有効化 | 「[リポジトリの依存関係を調べる](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository#enabling-and-disabling-the-dependency-graph-for-a-private-repository)」 |{% endif %}
-| パッケージの削除および復元 | 「[パッケージを削除および復元する](/packages/learn-github-packages/deleting-and-restoring-a-package)」 |
-| リポジトリのソーシャルメディア向けプレビューのカスタマイズ | 「[リポジトリのソーシャルメディア向けプレビューをカスタマイズする](/github/administering-a-repository/customizing-your-repositorys-social-media-preview)」 |
-| リポジトリからのテンプレートの作成 | 「[テンプレートリポジトリを作成する](/github/creating-cloning-and-archiving-repositories/creating-a-template-repository)」 |
-| Control access to {% data variables.product.prodname_dependabot_alerts %} へのアクセスを制御する| 「[リポジトリのセキュリティと分析設定を管理する](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts)」 |{% ifversion fpt or ghec %}
-| リポジトリで {% data variables.product.prodname_dependabot_alerts %} を閉じる | "[{% data variables.product.prodname_dependabot_alerts %} の表示と更新](/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts)" |
-| プライベートリポジトリのデータ利用の管理 | 「[プライベート リポジトリ用のデータ利用設定の管理](/get-started/privacy-on-github/managing-data-use-settings-for-your-private-repository)」|{% endif %}
-| リポジトリのコードオーナーを定義する | 「[コード オーナーについて](/github/creating-cloning-and-archiving-repositories/about-code-owners)」 |
-| リポジトリのアーカイブ | 「[リポジトリのアーカイブ](/repositories/archiving-a-github-repository/archiving-repositories)」 |{% ifversion fpt or ghec %}
-| セキュリティアドバイザリの作成 | 「[{% data variables.product.prodname_security_advisories %}について](/github/managing-security-vulnerabilities/about-github-security-advisories)」 |
-| スポンサーボタンの表示 | 「[リポジトリにスポンサーボタンを表示する](/github/administering-a-repository/displaying-a-sponsor-button-in-your-repository)」 |{% endif %}
-| プルリクエストの自動マージを許可または禁止 | 「[リポジトリ内のプル リクエストの自動マージを管理する](/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository)」 | 
+| {% ifversion fpt or ghec %}Invite collaborators{% else %}Add collaborators{% endif %} | "[Inviting collaborators to a personal repository](/github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository)" |
+| Change the visibility of the repository | "[Setting repository visibility](/github/administering-a-repository/setting-repository-visibility)" |{% ifversion fpt or ghec %}
+| Limit interactions with the repository | "[Limiting interactions in your repository](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository)" |{% endif %}
+| Rename a branch, including the default branch | "[Renaming a branch](/github/administering-a-repository/renaming-a-branch)" |
+| Merge a pull request on a protected branch, even if there are no approving reviews | "[About protected branches](/github/administering-a-repository/about-protected-branches)" |
+| Delete the repository | "[Deleting a repository](/repositories/creating-and-managing-repositories/deleting-a-repository)" |
+| Manage the repository's topics | "[Classifying your repository with topics](/github/administering-a-repository/classifying-your-repository-with-topics)" |{% ifversion fpt or ghec %}
+| Manage security and analysis settings for the repository | "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)" |{% endif %}{% ifversion fpt or ghec %}
+| Enable the dependency graph for a private repository | "[Exploring the dependencies of a repository](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository#enabling-and-disabling-the-dependency-graph-for-a-private-repository)" |{% endif %}
+| Delete and restore packages | "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)" |
+| 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)" |
+| Control access to {% data variables.product.prodname_dependabot_alerts %}| "[Managing security and analysis settings for your repository](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts)" |{% ifversion fpt or ghec %}
+| Dismiss {% data variables.product.prodname_dependabot_alerts %} in the repository | "[Viewing and updating {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts)" |
+| Manage data use for a private repository | "[Managing data use settings for your private repository](/get-started/privacy-on-github/managing-data-use-settings-for-your-private-repository)"|{% endif %}
+| Define code owners for the repository | "[About code owners](/github/creating-cloning-and-archiving-repositories/about-code-owners)" |
+| Archive the repository | "[Archiving repositories](/repositories/archiving-a-github-repository/archiving-repositories)" |{% ifversion fpt or ghec %}
+| Create security advisories | "[About repository security advisories](/github/managing-security-vulnerabilities/about-github-security-advisories)" |
+| Display a sponsor button | "[Displaying a sponsor button in your repository](/github/administering-a-repository/displaying-a-sponsor-button-in-your-repository)" |{% endif %}
+| Allow or disallow auto-merge for pull requests | "[Managing auto-merge for pull requests in your repository](/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository)" | 
+| Manage webhooks and deploy keys	| "[Managing deploy keys](/developers/overview/managing-deploy-keys#deploy-keys)" |
 
-## 個人アカウントが所有しているリポジトリに対するコラボレーター アクセス権
+## Collaborator access for a repository owned by a personal account
 
-個人リポジトリのコラボレータは、リポジトリのコンテンツをプル（読み取り）したり、リポジトリに変更をプッシュ（書き込み）したりすることができます。
+Collaborators on a personal repository can pull (read) the contents of the repository and push (write) changes to the repository.
 
 {% note %}
 
-**注:** プライベート リポジトリでは、リポジトリ オーナーはコラボレーターに書き込みアクセスしか付与できません。 個人アカウントが所有するリポジトリに対して、コラボレーターが読み取り専用アクセス権を持つことはできません。
+**Note:** In a private repository, repository owners can only grant write access to collaborators. Collaborators can't have read-only access to repositories owned by a personal account.
 
 {% endnote %}
 
-コラボレータは、次のアクションを実行することもできます。
+Collaborators can also perform the following actions.
 
-| アクション | 説明を見る |
+| Action | More information |
 | :- | :- |
-| リポジトリのフォーク | 「[フォークについて](/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks)」 |
-| デフォルトブランチ以外のブランチ名の変更 | 「[ブランチの名前を変更する](/github/administering-a-repository/renaming-a-branch)」 |
-| リポジトリ内のコミット、プルリクエスト、Issue に関するコメントの作成、編集、削除 | <ul><li>「[Issue について](/github/managing-your-work-on-github/about-issues)」</li><li>「[プル リクエストへコメントする](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request)」</li><li>「[混乱を生むコメントを管理する](/communities/moderating-comments-and-conversations/managing-disruptive-comments)」</li></ul> |
-| リポジトリ内の Issue の作成、割り当て、クローズ、再オープン | 「[Issue で作業を管理する](/github/managing-your-work-on-github/managing-your-work-with-issues)」 |
-| リポジトリ内の Issue とプルリクエストのラベル管理 | 「[Issue と Pull Request のラベル付け](/github/managing-your-work-on-github/labeling-issues-and-pull-requests)」 |
-| リポジトリ内の Issue とプルリクエストのマイルストーン管理 | 「[Issue と Pull Request のマイルストーンの作成と削除](/github/managing-your-work-on-github/creating-and-editing-milestones-for-issues-and-pull-requests)」 |
-| リポジトリ内の Issue またはプルリクエストを重複としてマーク | 「[Issue と Pull Request の重複について](/github/managing-your-work-on-github/about-duplicate-issues-and-pull-requests)」 |
-| リポジトリ内のプルリクエストの作成、マージ、クローズ | 「[プル リクエストで、作業に対する変更を提案する](/github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests)」 |
-| プルリクエストの自動マージの有効化または無効化 | 「[プル リクエストを自動的にマージする](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request)」
-| リポジトリ内のプルリクエストに提案された変更を適用 |「[プル リクエストでのフィードバックを取り込む](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/incorporating-feedback-in-your-pull-request)」 |
-| リポジトリのフォークからプルリクエストを作成 | 「[フォークからプル リクエストを作成する](/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request-from-a-fork)」 |
-| プルリクエストのマージ可能性に影響するプルリクエストについてレビューを送信 | 「[プル リクエストで提案された変更をレビューする](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request)」 |
-| リポジトリ用のウィキの作成と編集 | 「[ウィキについて](/communities/documenting-your-project-with-wikis/about-wikis)」 |
-| リポジトリ用のリリースの作成と編集 | 「[リポジトリのリリースを管理する](/github/administering-a-repository/managing-releases-in-a-repository)」 |
-| リポジトリのコードオーナーの定義 | 「[コード オーナーについて](/articles/about-code-owners)」 |{% ifversion fpt or ghae or ghec %}
-| パッケージの公開、表示、インストール | 「[パッケージの公開と管理](/github/managing-packages-with-github-packages/publishing-and-managing-packages)」 |{% endif %}
-| リポジトリでコラボレーターである自身を削除する | 「[コラボレーターのリポジトリから自分を削除する](/github/setting-up-and-managing-your-github-user-account/removing-yourself-from-a-collaborators-repository)」 |
+| Fork the repository | "[About forks](/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks)" |
+| Rename a branch other than the default branch | "[Renaming a branch](/github/administering-a-repository/renaming-a-branch)" |
+| Create, edit, and delete comments on commits, pull requests, and issues in the repository | <ul><li>"[About issues](/github/managing-your-work-on-github/about-issues)"</li><li>"[Commenting on a pull request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request)"</li><li>"[Managing disruptive comments](/communities/moderating-comments-and-conversations/managing-disruptive-comments)"</li></ul> |
+| Create, assign, close, and re-open issues in the repository | "[Managing your work with issues](/github/managing-your-work-on-github/managing-your-work-with-issues)" |
+| Manage labels for issues and pull requests in the repository | "[Labeling issues and pull requests](/github/managing-your-work-on-github/labeling-issues-and-pull-requests)" |
+| Manage milestones for issues and pull requests in the repository | "[Creating and editing milestones for issues and pull requests](/github/managing-your-work-on-github/creating-and-editing-milestones-for-issues-and-pull-requests)" |
+| Mark an issue or pull request in the repository as a duplicate | "[About duplicate issues and pull requests](/github/managing-your-work-on-github/about-duplicate-issues-and-pull-requests)" |
+| Create, merge, and close pull requests in the repository | "[Proposing changes to your work with pull requests](/github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests)" |
+| Enable and disable auto-merge for a pull request | "[Automatically merging a pull request](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request)"
+| Apply suggested changes to pull requests in the repository |"[Incorporating feedback in your pull request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/incorporating-feedback-in-your-pull-request)" |
+| Create a pull request from a fork of the repository | "[Creating a pull request from a fork](/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request-from-a-fork)" |
+| Submit a review on a pull request that affects the mergeability of the pull request | "[Reviewing proposed changes in a pull request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request)" |
+| Create and edit a wiki for the repository | "[About wikis](/communities/documenting-your-project-with-wikis/about-wikis)" |
+| Create and edit releases for the repository | "[Managing releases in a repository](/github/administering-a-repository/managing-releases-in-a-repository)" |
+| Act as a code owner for the repository | "[About code owners](/articles/about-code-owners)" |{% ifversion fpt or ghae or ghec %}
+| Publish, view, or install packages | "[Publishing and managing packages](/github/managing-packages-with-github-packages/publishing-and-managing-packages)" |{% endif %}
+| Remove themselves as collaborators on the repository | "[Removing yourself from a collaborator's repository](/github/setting-up-and-managing-your-github-user-account/removing-yourself-from-a-collaborators-repository)" |
 
-## 参考資料
+## Further reading
 
-- 「[Organization のリポジトリ ロール](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)」
+- "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)"
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 5409856a9d..6fd1dab0b3 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
@@ -231,19 +231,11 @@ For example, this `cleanup.js` will only run on Linux-based runners:
 
 ### `runs.steps`
 
-{% ifversion fpt or ghes > 3.2 or ghae or ghec %}
 **Required** The steps that you plan to run in this action. These can be either `run` steps or `uses` steps.
-{% else %}
-**Required** The steps that you plan to run in this action.
-{% endif %}
 
 #### `runs.steps[*].run`
 
-{% ifversion fpt or ghes > 3.2 or ghae or ghec %}
 **Optional** The command you want to run. This can be inline or a script in your action repository:
-{% else %}
-**Required** The command you want to run. This can be inline or a script in your action repository:
-{% endif %}
 
 {% raw %}
 ```yaml
@@ -269,11 +261,7 @@ For more information, see "[`github context`](/actions/reference/context-and-exp
 
 #### `runs.steps[*].shell`
 
-{% ifversion fpt or ghes > 3.2 or ghae or ghec %}
 **Optional** The shell where you want to run the command. You can use any of the shells listed [here](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepsshell). Required if `run` is set.
-{% else %}
-**Required** The shell where you want to run the command. You can use any of the shells listed [here](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepsshell). Required if `run` is set.
-{% endif %}
 
 {% ifversion fpt or ghes > 3.3 or ghae > 3.3 or ghec %}
 #### `runs.steps[*].if`
@@ -322,7 +310,6 @@ steps:
 
 **Optional**  Specifies the working directory where the command is run.
 
-{% ifversion fpt or ghes > 3.2 or ghae or ghec %}
 #### `runs.steps[*].uses`
 
 **Optional**  Selects an action to run as part of a step in your job. An action is a reusable unit of code. You can use an action defined in the same repository as the workflow, a public repository, or in a [published Docker container image](https://hub.docker.com/).
@@ -371,7 +358,6 @@ runs:
         middle_name: The
         last_name: Octocat
 ```
-{% endif %}
 
 {% ifversion ghes > 3.5 or ghae > 3.5 %}
 
diff --git a/translations/ja-JP/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-hashicorp-vault.md b/translations/ja-JP/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-hashicorp-vault.md
index 9d8f3e75a0..d6e76d766c 100644
--- a/translations/ja-JP/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-hashicorp-vault.md
+++ b/translations/ja-JP/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-hashicorp-vault.md
@@ -1,7 +1,7 @@
 ---
-title: Configuring OpenID Connect in HashiCorp Vault
+title: HashiCorp Vault での OpenID Connect の構成
 shortTitle: OpenID Connect in HashiCorp Vault
-intro: Use OpenID Connect within your workflows to authenticate with HashiCorp Vault.
+intro: ワークフロー内で OpenID Connect を使用して HashiCorp Vault で認証します。
 miniTocMaxHeadingLevel: 3
 versions:
   fpt: '*'
@@ -10,31 +10,35 @@ versions:
 type: tutorial
 topics:
   - Security
+ms.openlocfilehash: 174243818443709ee6ffe3b22aa668cff254266f
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: ja-JP
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148106630'
 ---
+{% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %}
 
-{% data reusables.actions.enterprise-beta %}
-{% data reusables.actions.enterprise-github-hosted-runners %}
+## 概要
 
-## Overview
+OpenID Connect (OIDC) を使うと、{% data variables.product.prodname_actions %} ワークフローが HashiCorp Vault で認証し、シークレットを取得できます。
 
-OpenID Connect (OIDC) allows your {% data variables.product.prodname_actions %} workflows to authenticate with a HashiCorp Vault to retrieve secrets.
+このガイドでは、HashiCorp Vault が {% data variables.product.prodname_dotcom %} の OIDC をフェデレーション ID として信頼するように構成する方法の概要について説明します。また、この構成を [hashicorp/vault-action](https://github.com/hashicorp/vault-action) アクションで使って HashiCorp Vault からシークレットを取得する方法を示します。
 
-This guide gives an overview of how to configure HashiCorp Vault to trust {% data variables.product.prodname_dotcom %}'s OIDC as a federated identity, and demonstrates how to use this configuration in the [hashicorp/vault-action](https://github.com/hashicorp/vault-action) action to retrieve secrets from HashiCorp Vault.
-
-## Prerequisites
+## 前提条件
 
 {% data reusables.actions.oidc-link-to-intro %}
 
 {% data reusables.actions.oidc-security-notice %}
 
-## Adding the identity provider to HashiCorp Vault
+## HashiCorp Vault への ID プロバイダーの追加
 
-To use OIDC with HashiCorp Vault, you will need to add a trust configuration for the {% data variables.product.prodname_dotcom %} OIDC provider. For more information, see the HashiCorp Vault [documentation](https://www.vaultproject.io/docs/auth/jwt).
+HashiCorp Vault と共に OIDC を使うには、{% data variables.product.prodname_dotcom %} OIDC プロバイダーの信頼構成を追加する必要があります。 詳細については、HashiCorp Vault の[ドキュメント](https://www.vaultproject.io/docs/auth/jwt)を参照してください。
 
-To configure your Vault server to accept JSON Web Tokens (JWT) for authentication:
+認証に JSON Web トークン (JWT) を受け入れるように Vault サーバーを構成します。
 
-1. Enable the JWT `auth` method, and use `write` to apply the configuration to your Vault. 
-  For `oidc_discovery_url` and `bound_issuer` parameters, use {% ifversion ghes %}`https://HOSTNAME/_services/token`{% else %}`https://token.actions.githubusercontent.com`{% endif %}. These parameters allow the Vault server to verify the received JSON Web Tokens (JWT) during the authentication process.
+1. JWT `auth` メソッドを有効にし、`write` を使用して Vault に構成を適用します。 
+  `oidc_discovery_url` および `bound_issuer` パラメーターの場合は、{% ifversion ghes %}`https://HOSTNAME/_services/token`{% else %}`https://token.actions.githubusercontent.com`{% endif %} を使います。 これらのパラメーターを使用すると、Vault サーバーは認証プロセス中に受信した JSON Web トークン (JWT) を確認できます。
 
     ```sh{:copy}
     vault auth enable jwt
@@ -45,7 +49,7 @@ To configure your Vault server to accept JSON Web Tokens (JWT) for authenticatio
       bound_issuer="{% ifversion ghes %}https://HOSTNAME/_services/token{% else %}https://token.actions.githubusercontent.com{% endif %}" \
       oidc_discovery_url="{% ifversion ghes %}https://HOSTNAME/_services/token{% else %}https://token.actions.githubusercontent.com{% endif %}"
     ```
-2. Configure a policy that only grants access to the specific paths your workflows will use to retrieve secrets. For more advanced policies, see the HashiCorp Vault [Policies documentation](https://www.vaultproject.io/docs/concepts/policies).
+2. ワークフローがシークレットの取得に使用する特定のパスへのアクセスのみを許可するポリシーを構成します。 詳細なポリシーについては、HashiCorp Vault の [「ポリシー」のドキュメント](https://www.vaultproject.io/docs/concepts/policies)を参照してください。
 
     ```sh{:copy}
     vault policy write myproject-production - <<EOF
@@ -56,7 +60,7 @@ To configure your Vault server to accept JSON Web Tokens (JWT) for authenticatio
     }
     EOF
     ```
-3. Configure roles to group different policies together. If the authentication is successful, these policies are attached to the resulting Vault access token.
+3. 異なるポリシーをグループ化するようにロールを構成します。 認証が成功した場合、これらのポリシーは結果の Vault アクセス トークンにアタッチされます。
 
     ```sh{:copy}
     vault write auth/jwt/role/myproject-production -<<EOF
@@ -72,51 +76,51 @@ To configure your Vault server to accept JSON Web Tokens (JWT) for authenticatio
     EOF
     ```
 
-- `ttl` defines the validity of the resulting access token.
-- Ensure that the `bound_claims` parameter is defined for your security requirements, and has at least one condition. Optionally, you can also set the `bound_subject` as well as the `bound_audiences` parameter.
-- To check arbitrary claims in the received JWT payload, the `bound_claims` parameter contains a set of claims and their required values. In the above example, the role will accept any incoming authentication requests from the `repo-name` repository owned by the `user-or-org-name` account.
-- To see all the available claims supported by {% data variables.product.prodname_dotcom %}'s OIDC provider, see ["Configuring the OIDC trust with the cloud"](/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect#configuring-the-oidc-trust-with-the-cloud).
+- `ttl` によって、結果のアクセス トークンの有効性が定義されます。
+- `bound_claims` パラメーターがセキュリティ要件に対して定義されており、少なくとも 1 つの条件があることを確認します。 必要に応じて、`bound_subject` だけでなく、`bound_audiences` パラメーターも設定できます。
+- 受信した JWT ペイロード内の任意の要求を確認するために、`bound_claims` パラメーターには一連の要求とその必須の値が含まれています。 上記の例では、ロールは、`user-or-org-name` アカウントによって所有される `repo-name` リポジトリからの受信認証要求を受け取ります。
+- {% data variables.product.prodname_dotcom %} の OIDC プロバイダーでサポートされている使用可能なすべての要求を確認するには、「[クラウドを使った OIDC 信頼の構成](/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect#configuring-the-oidc-trust-with-the-cloud)」を参照してください。
 
-For more information, see the HashiCorp Vault [documentation](https://www.vaultproject.io/docs/auth/jwt).
+詳細については、HashiCorp Vault の[ドキュメント](https://www.vaultproject.io/docs/auth/jwt)を参照してください。
 
-## Updating your {% data variables.product.prodname_actions %} workflow
+## {% data variables.product.prodname_actions %} ワークフローを更新する
 
-To update your workflows for OIDC, you will need to make two changes to your YAML:
-1. Add permissions settings for the token.
-2. Use the [`hashicorp/vault-action`](https://github.com/hashicorp/vault-action) action to exchange the OIDC token (JWT) for a cloud access token.
+OIDC のワークフローを更新するには、YAML に 2 つの変更を行う必要があります。
+1. トークンのアクセス許可設定を追加します。
+2. この [`hashicorp/vault-action`](https://github.com/hashicorp/vault-action) アクションを使って、OIDC トークン (JWT) をクラウド アクセス トークンと交換します。
 
 
-To add OIDC integration to your workflows that allow them to access secrets in Vault, you will need to add the following code changes:
+Vault のシークレットにアクセスできるようにワークフローに OIDC 統合を追加するには、次のコード変更を追加する必要があります。
 
-- Grant permission to fetch the token from the {% data variables.product.prodname_dotcom %} OIDC provider:
-  - The workflow needs `permissions:` settings with the `id-token` value set to `write`. This lets you fetch the OIDC token from every job in the workflow.
-- Request the JWT from the {% data variables.product.prodname_dotcom %} OIDC provider, and present it to HashiCorp Vault to receive an access token:
-  - You can use the [`hashicorp/vault-action`](https://github.com/hashicorp/vault-action) action to fetch the JWT and receive the access token from Vault, or you could use the [Actions toolkit](https://github.com/actions/toolkit/) to fetch the tokens for your job.
+- {% data variables.product.prodname_dotcom %} OIDC プロバイダーからトークンをフェッチするアクセス許可を付与します。
+  - ワークフローには、`id-token` の値が `write` に設定された `permissions:` 設定が必要です。 これにより、ワークフロー内のすべてのジョブから OIDC トークンをフェッチすることができます。
+- {% data variables.product.prodname_dotcom %} OIDC プロバイダーに JWT を要求し、それを HashiCorp Vault に提示してアクセス トークンを受け取ります。
+  - [`hashicorp/vault-action`](https://github.com/hashicorp/vault-action) アクションを使って、JWT をフェッチし、Vault からアクセス トークンを受け取ることができます。または、[Actions ツールキット](https://github.com/actions/toolkit/)を使ってジョブのトークンをフェッチすることもできます。
 
-This example demonstrates how to use OIDC with the official action to request a secret from HashiCorp Vault.
+この例は、HashiCorp Vault からシークレットを要求するために、公式のアクションと共に OIDC を使う方法を示しています。
 
-### Adding permissions settings
+### アクセス許可設定の追加
 
  {% data reusables.actions.oidc-permissions-token %}
 
 {% note %}
 
-**Note**:
+**注**:
 
-When the `permissions` key is used, all unspecified permissions are set to _no access_, with the exception of the metadata scope, which always gets _read_ access. As a result, you may need to add other permissions, such as `contents: read`. See [Automatic token authentication](/actions/security-guides/automatic-token-authentication) for more information.
+`permissions` キーを使用すると、すべての未指定のアクセス許可が "アクセスなし" に設定されます。ただし、メタデータ スコープは例外であり、常に "読み取り" アクセス権を取得します。  その結果、`contents: read` のような他のアクセス許可を追加することが必要になる場合があります。 詳しくは、「[自動トークン認証](/actions/security-guides/automatic-token-authentication)」を参照してください。
 
 {% endnote %}
 
-### Requesting the access token
+### アクセス トークンの要求
 
-The `hashicorp/vault-action` action receives a JWT from the {% data variables.product.prodname_dotcom %} OIDC provider, and then requests an access token from your HashiCorp Vault instance to retrieve secrets. For more information, see the HashiCorp Vault GitHub Action [documentation](https://github.com/hashicorp/vault-action).
+`hashicorp/vault-action` アクションは、{% data variables.product.prodname_dotcom %} OIDC プロバイダーから JWT を受け取り、HashiCorp Vault インスタンスにアクセス トークンを要求し、シークレットを取得します。 詳しくは、HashiCorp Vault の GitHub Action の[ドキュメント](https://github.com/hashicorp/vault-action)を参照してください。
 
-This example demonstrates how to create a job that requests a secret from HashiCorp Vault.
+この例では、HashiCorp Vault にシークレットを要求するジョブを作成する方法を示しています。
 
-- `<Vault URL>`: Replace this with the URL of your HashiCorp Vault.
-- `<Vault Namespace>`: Replace this with the Namespace you've set in HashiCorp Vault. For example: `admin`.
-- `<Role name>`: Replace this with the role you've set in the HashiCorp Vault trust relationship.
-- `<Secret-Path>`: Replace this with the path to the secret you're retrieving from HashiCorp Vault. For example: `secret/data/production/ci npmToken`.
+- `<Vault URL>`: これを HashiCorp Vault の URL に置き換えます。
+- `<Vault Namespace>`: これを HashiCorp Vault で設定した名前空間に置き換えます。 (例: `admin`)。
+- `<Role name>`: これを HashiCorp Vault の信頼関係で設定したロールに置き換えます。
+- `<Secret-Path>`: これを HashiCorp Vault から取得するシークレットのパスに置き換えます。 たとえば、「`secret/data/production/ci npmToken`」のように入力します。
 
 ```yaml{:copy}
 jobs:
@@ -142,19 +146,19 @@ jobs:
 
 {% note %}
 
-**Note**:
+**注**:
 
-- If your Vault server is not accessible from the public network, consider using a self-hosted runner with other available Vault [auth methods](https://www.vaultproject.io/docs/auth). For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners)."
-- `<Vault Namespace>` must be set for a Vault Enterprise (including HCP Vault) deployment. For more information, see [Vault namespace](https://www.vaultproject.io/docs/enterprise/namespaces).
+- Vault サーバーにパブリック ネットワークからアクセスできない場合は、他の使用可能な Vault の[認証方法](https://www.vaultproject.io/docs/auth)でセルフホステッド ランナーを使用することを検討してください。 詳細については、[セルフホステッド ランナー](/actions/hosting-your-own-runners/about-self-hosted-runners)に関する記述をご覧ください。
+- `<Vault Namespace>` は、Vault Enterprise (HCP Vault を含む) デプロイに対して設定する必要があります。 詳しくは、[Vault 名前空間](https://www.vaultproject.io/docs/enterprise/namespaces)に関するページを参照してください。
 
 {% endnote %}
 
-### Revoking the access token
+### アクセス トークンの取り消し
 
-By default, the Vault server will automatically revoke access tokens when their TTL is expired, so you don't have to manually revoke the access tokens. However, if you do want to revoke access tokens immediately after your job has completed or failed, you can manually revoke the issued token using the [Vault API](https://www.vaultproject.io/api/auth/token#revoke-a-token-self).
+既定で、Vault サーバーでは TTL の有効期限が切れたときにアクセス トークンを自動的に取り消します。そのため、アクセス トークンを手動で取り消す必要はありません。 ただし、ジョブが完了または失敗した直後にアクセス トークンを取り消す場合は、[Vault API](https://www.vaultproject.io/api/auth/token#revoke-a-token-self) を使用して発行されたトークンを手動で取り消すことができます。
 
-1. Set the `exportToken` option to `true` (default: `false`). This exports the issued Vault access token as an environment variable: `VAULT_TOKEN`.
-2. Add a step to call the [Revoke a Token (Self)](https://www.vaultproject.io/api/auth/token#revoke-a-token-self) Vault API to revoke the access token.
+1. `exportToken` オプションを `true` (既定値: `false`) に設定します。 これにより、発行された Vault アクセス トークンが環境変数としてエクスポートされます: `VAULT_TOKEN`。
+2. [トークンの取り消し (自己)](https://www.vaultproject.io/api/auth/token#revoke-a-token-self) Vault API を呼び出してアクセス トークンを取り消すステップを追加します。
 
 ```yaml{:copy}
 jobs:
@@ -183,4 +187,4 @@ jobs:
         run: |
           curl -X POST -sv -H "X-Vault-Token: {% raw %}${{ env.VAULT_TOKEN }}{% endraw %}" \
             <Vault URL>/v1/auth/token/revoke-self
-```
\ No newline at end of file
+```
diff --git a/translations/ja-JP/content/actions/examples/using-the-github-cli-on-a-runner.md b/translations/ja-JP/content/actions/examples/using-the-github-cli-on-a-runner.md
index 351014a933..e08f35533a 100644
--- a/translations/ja-JP/content/actions/examples/using-the-github-cli-on-a-runner.md
+++ b/translations/ja-JP/content/actions/examples/using-the-github-cli-on-a-runner.md
@@ -1,7 +1,7 @@
 ---
-title: Using the GitHub CLI on a runner
+title: ランナーでの GitHub CLI の使用
 shortTitle: Use the GitHub CLI on a runner
-intro: 'How to use advanced {% data variables.product.prodname_actions %} features for continuous integration (CI).'
+intro: '継続的インテグレーション (CI) のために高度な {% data variables.product.prodname_actions %} 機能を使用する方法。'
 versions:
   fpt: '*'
   ghes: '> 3.1'
@@ -10,40 +10,34 @@ versions:
 type: how_to
 topics:
   - Workflows
+ms.openlocfilehash: e0787d09cd194de0038d259c1aff777cc91a4a6a
+ms.sourcegitcommit: bf11c3e08cbb5eab6320e0de35b32ade6d863c03
+ms.translationtype: HT
+ms.contentlocale: ja-JP
+ms.lasthandoff: 10/27/2022
+ms.locfileid: '148111586'
 ---
-
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Example overview
+## サンプルの概要
 
-{% data reusables.actions.example-workflow-intro-ci %} When this workflow is triggered, it automatically runs a script that checks whether the {% data variables.product.prodname_dotcom %} Docs site has any broken links. If any broken links are found, the workflow uses the {% data variables.product.prodname_dotcom %} CLI to create a {% data variables.product.prodname_dotcom %} issue with the details.
+{% data reusables.actions.example-workflow-intro-ci %}このワークフローがトリガーされると、{% data variables.product.prodname_dotcom %} Docs サイトに壊れたリンクがあるかどうかを確認するスクリプトが自動的に実行されます。 壊れたリンクが見つかった場合、ワークフローで詳しい情報を含む {% data variables.product.prodname_dotcom %} のイシューが {% data variables.product.prodname_dotcom %} CLI を使用して作成されます。
 
 {% data reusables.actions.example-diagram-intro %}
 
-![Overview diagram of workflow steps](/assets/images/help/images/overview-actions-using-cli-ci-example.png)
+![ワークフローのステップの概要図](/assets/images/help/images/overview-actions-using-cli-ci-example.png)
 
-## Features used in this example
+## この例で使用されている機能
 
 {% data reusables.actions.example-table-intro %}
 
-| **Feature**  | **Implementation** |
+| **機能**  | **実装** |
 | --- | --- |
-{% data reusables.actions.cron-table-entry %}
-{% data reusables.actions.permissions-table-entry %}
-{% data reusables.actions.if-conditions-table-entry %}
-{% data reusables.actions.secrets-table-entry %}
-{% data reusables.actions.checkout-action-table-entry %}
-{% data reusables.actions.setup-node-table-entry %}
-| Using a third-party action: | [`peter-evans/create-issue-from-file`](https://github.com/peter-evans/create-issue-from-file)|
-| Running shell commands on the runner: | [`run`](/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idstepsrun) |
-| Running a script on the runner: | Using `script/check-english-links.js` |
-| Generating an output file: | Piping the output using the `>` operator |
-| Checking for existing issues using {% data variables.product.prodname_cli %}: | [`gh issue list`](https://cli.github.com/manual/gh_issue_list) |
-| Commenting on an issue using {% data variables.product.prodname_cli %}: | [`gh issue comment`](https://cli.github.com/manual/gh_issue_comment) |
+{% data reusables.actions.cron-table-entry %} {% data reusables.actions.permissions-table-entry %} {% data reusables.actions.if-conditions-table-entry %} {% data reusables.actions.secrets-table-entry %} {% data reusables.actions.checkout-action-table-entry %} {% data reusables.actions.setup-node-table-entry %} | サード パーティのアクションの使用: | [`peter-evans/create-issue-from-file`](https://github.com/peter-evans/create-issue-from-file)| | ランナーでのシェル コマンドの実行: | [`run`](/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idstepsrun) | | ランナーでのスクリプトの実行: | `script/check-english-links.js` の使用 | | 出力ファイルの生成: | `>` 演算子を使用した出力のパイプ処理 | | {% data variables.product.prodname_cli %} を使用した既存のイシューの確認: | [`gh issue list`](https://cli.github.com/manual/gh_issue_list) | | {% data variables.product.prodname_cli %} を使用したイシューへのコメント: | [`gh issue comment`](https://cli.github.com/manual/gh_issue_comment) |
 
-## Example workflow
+## ワークフローの例
 
-{% data reusables.actions.example-docs-engineering-intro %} [`check-all-english-links.yml`](https://github.com/github/docs/blob/main/.github/workflows/check-all-english-links.yml).
+{% data reusables.actions.example-docs-engineering-intro %} [`check-all-english-links.yml`](https://github.com/github/docs/blob/6e01c0653836c10d7e092a17566a2c88b10504ce/.github/workflows/check-all-english-links.yml)。
 
 {% data reusables.actions.note-understanding-example %}
 
@@ -178,15 +172,15 @@ jobs:
 </tbody>
 </table>
 
-## Understanding the example
+## 例の説明
 
 {% data reusables.actions.example-explanation-table-intro %}
 
 <table style="table-layout: fixed;">
 <thead>
   <tr>
-    <th style="width:60%"><b>Code</b></th>
-    <th style="width:40%"><b>Explanation</b></th>
+    <th style="width:60%">"<b>コード</b>"</th>
+    <th style="width:40%"><b>説明</b></th>
   </tr>
 </thead>
 <tbody>
@@ -214,10 +208,10 @@ on:
 </td>
 <td>
 
-Defines the `workflow_dispatch` and `scheduled` as triggers for the workflow:
+ワークフローのトリガーとして `workflow_dispatch` と `scheduled` を定義します。
 
-* The `workflow_dispatch` lets you manually run this workflow from the UI. For more information, see [`workflow_dispatch`](/actions/using-workflows/events-that-trigger-workflows#workflow_dispatch).
-* The `schedule` event lets you use `cron` syntax to define a regular interval for automatically triggering the workflow. For more information, see [`schedule`](/actions/reference/events-that-trigger-workflows#schedule).
+* `workflow_dispatch` を使用すると、UI からこのワークフローを手動で実行できます。 詳細については、「[`workflow_dispatch`](/actions/using-workflows/events-that-trigger-workflows#workflow_dispatch)」を参照してください。
+* `schedule` イベントにより、`cron` 構文を使用して、ワークフローを自動的にトリガーするための一定の間隔を定義できます。 詳細については、「[`schedule`](/actions/reference/events-that-trigger-workflows#schedule)」を参照してください。
 </td>
 </tr>
 <tr>
@@ -231,7 +225,7 @@ permissions:
 </td>
 <td>
 
-Modifies the default permissions granted to `GITHUB_TOKEN`. This will vary depending on the needs of your workflow. For more information, see "[Assigning permissions to jobs](/actions/using-jobs/assigning-permissions-to-jobs)."
+`GITHUB_TOKEN` に付与される既定のアクセス許可を変更します。 これはワークフローのニーズによって異なります。 詳しい情報については、「[ジョブへのアクセス許可の割り当て](/actions/using-jobs/assigning-permissions-to-jobs)」を参照してください。
 </td>
 </tr>
 <tr>
@@ -243,7 +237,7 @@ jobs:
 </td>
 <td>
 
-Groups together all the jobs that run in the workflow file.
+ワークフロー ファイルで実行されるすべてのジョブをグループ化します。
 </td>
 </tr>
 <tr>
@@ -256,7 +250,7 @@ Groups together all the jobs that run in the workflow file.
 </td>
 <td>
 
-Defines a job with the ID `check_all_english_links`, and the name `Check all links`, that is stored within the `jobs` key.
+ID `check_all_english_links` と名前 `Check all links` を持つジョブを定義します。これは `jobs` キー内に格納されます。
 </td>
 </tr>
 <tr>
@@ -268,7 +262,7 @@ if: github.repository == 'github/docs-internal'
 </td>
 <td>
 
-Only run the `check_all_english_links` job if the repository is named `docs-internal` and is within the `github` organization. Otherwise, the job is marked as _skipped_.
+リポジトリが `docs-internal` という名前で、`github` という Organization 内にある場合のみ、`check_all_english_links` ジョブを実行します。 それ以外の場合、ジョブは _"スキップ済み"_ としてマークされます。
 </td>
 </tr>
 <tr>
@@ -280,7 +274,7 @@ runs-on: ubuntu-latest
 </td>
 <td>
 
-Configures the job to run on an Ubuntu Linux runner. This means that the job will execute on a fresh virtual machine hosted by {% data variables.product.prodname_dotcom %}. For syntax examples using other runners, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idruns-on)."
+Ubuntu Linux ランナーで実行するようにジョブを設定します。 これは、ジョブが {% data variables.product.prodname_dotcom %} によってホストされている新しい仮想マシンで実行されるということです。 他のランナーを使う構文例については、「[{% data variables.product.prodname_actions %} のワークフロー構文](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idruns-on)」を参照してください。
 </td>
 </tr>
 <tr>
@@ -296,7 +290,7 @@ Configures the job to run on an Ubuntu Linux runner. This means that the job wil
 </td>
 <td>
 
-Creates custom environment variables, and redefines the built-in `GITHUB_TOKEN` variable to use a custom [secret](/actions/security-guides/encrypted-secrets). These variables will be referenced later in the workflow.
+カスタム環境変数を作成し、組み込み `GITHUB_TOKEN` 変数を再定義してカスタム [シークレット](/actions/security-guides/encrypted-secrets)を使用します。 これらの変数は、ワークフローで後から参照されます。
 </td>
 </tr>
 <tr>
@@ -308,7 +302,7 @@ Creates custom environment variables, and redefines the built-in `GITHUB_TOKEN`
 </td>
 <td>
 
-Groups together all the steps that will run as part of the `check_all_english_links` job. Each job in the workflow has its own `steps` section.
+`check_all_english_links` ジョブの一部として実行されるすべてのステップをグループ化します。 ワークフロー内の各ジョブには、独自の `steps` セクションがあります。
 </td>
 </tr>
 <tr>
@@ -321,7 +315,7 @@ Groups together all the steps that will run as part of the `check_all_english_li
 </td>
 <td>
 
-The `uses` keyword tells the job to retrieve the action named `actions/checkout`. This is an action that checks out your repository and downloads it to the runner, allowing you to run actions against your code (such as testing tools). You must use the checkout action any time your workflow will run against the repository's code or you are using an action defined in the repository.
+`uses` キーワードは、`actions/checkout` という名前のアクションを取得するようにジョブに指示します。 これは、リポジトリをチェックアウトしてランナーにダウンロードし、コードに対してアクション（テストツールなど）を実行できるようにします。 ワークフローがリポジトリのコードに対して実行されるとき、またはリポジトリで定義されたアクションを使用しているときはいつでも、チェックアウトアクションを使用する必要があります。
 </td>
 </tr>
 <tr>
@@ -337,7 +331,7 @@ The `uses` keyword tells the job to retrieve the action named `actions/checkout`
 </td>
 <td>
 
-This step uses the `actions/setup-node` action to install the specified version of the `node` software package on the runner, which gives you access to the `npm` command.
+このステップでは、`actions/setup-node` アクションを使用して、指定したバージョンの `node` ソフトウェア パッケージをランナーにインストールします。これにより、`npm` コマンドにアクセスできるようになります。
 </td>
 </tr>
 <tr>
@@ -352,7 +346,7 @@ This step uses the `actions/setup-node` action to install the specified version
 </td>
 <td>
 
-The `run` keyword tells the job to execute a command on the runner. In this case, the `npm ci` and `npm run build` commands are run as separate steps to install and build the Node.js application in the repository.
+`run` キーワードは、ランナーでコマンドを実行するようにジョブに指示します。 この場合、Node.js アプリケーションをリポジトリにインストールしてビルドするための個別のステップとして、`npm ci` コマンドと `npm run build` コマンドが実行されます。
 </td>
 </tr>
 <tr>
@@ -366,7 +360,7 @@ The `run` keyword tells the job to execute a command on the runner. In this case
 </td>
 <td>
 
-This `run` command executes a script that is stored in the repository at `script/check-english-links.js`, and pipes the output to a file called `broken_links.md`.
+この `run` コマンドは、リポジトリの `script/check-english-links.js` に保存されているスクリプトを実行し、出力を `broken_links.md` というファイルにパイプで渡します。
 </td>
 </tr>
 <tr>
@@ -385,7 +379,7 @@ This `run` command executes a script that is stored in the repository at `script
 </td>
 <td>
 
-If the `check-english-links.js` script detects broken links and returns a non-zero (failure) exit status, then use a [workflow command](/actions/using-workflows/workflow-commands-for-github-actions#setting-an-output-parameter) to set an output that has the value of the first line of the `broken_links.md` file (this is used the next step).
+`check-english-links.js` スクリプトで壊れたリンクが検出され、0 以外 (失敗) の終了状態が返された場合は、[ワークフロー コマンド](/actions/using-workflows/workflow-commands-for-github-actions#setting-an-output-parameter)を使用して、`broken_links.md` ファイルの先頭行の値を持つ出力を設定します (これは次のステップで使用されます)。
 </td>
 </tr>
 <tr>
@@ -407,7 +401,7 @@ If the `check-english-links.js` script detects broken links and returns a non-ze
 </td>
 <td>
 
-Uses the `peter-evans/create-issue-from-file` action to create a new {% data variables.product.prodname_dotcom %} issue. This example is pinned to a specific version of the action, using the `b4f9ee0a9d4abbfc6986601d9b1a4f8f8e74c77e` SHA.
+`peter-evans/create-issue-from-file` アクションを使用して、新しい {% data variables.product.prodname_dotcom %} のイシューを作成します。 この例は、`b4f9ee0a9d4abbfc6986601d9b1a4f8f8e74c77e` SHA を使用して、特定のバージョンのアクションに合わせて固定されています。
 </td>
 </tr>
 <tr>
@@ -435,9 +429,9 @@ Uses the `peter-evans/create-issue-from-file` action to create a new {% data var
 </td>
 <td>
 
-Uses [`gh issue list`](https://cli.github.com/manual/gh_issue_list) to locate the previously created issue from earlier runs. This is [aliased](https://cli.github.com/manual/gh_alias_set) to `gh list-reports` for simpler processing in later steps. To get the issue URL, the `jq` expression processes the resulting JSON output.
+[`gh issue list`](https://cli.github.com/manual/gh_issue_list) を使用して、以前の実行から以前に作成したイシューを見つけます。 これには、後のステップでの処理を簡単にするために、`gh list-reports` という[別名](https://cli.github.com/manual/gh_alias_set)が付けられます。 イシューの URL を取得するために、`jq` 式で結果の JSON 出力を処理します。
 
-[`gh issue comment`](https://cli.github.com/manual/gh_issue_comment) is then used to add a comment to the new issue that links to the previous one.
+次に [`gh issue comment`](https://cli.github.com/manual/gh_issue_comment) を使用して、以前のイシューにリンクするコメントを新しいイシューに追加します。
 </td>
 </tr>
 <tr>
@@ -455,7 +449,7 @@ Uses [`gh issue list`](https://cli.github.com/manual/gh_issue_list) to locate th
 </td>
 <td>
 
-If an issue from a previous run is open and assigned to someone, then use [`gh issue comment`](https://cli.github.com/manual/gh_issue_comment) to add a comment with a link to the new issue.
+以前の実行でのイシューが未解決であり誰かに割り当てられている場合は、[`gh issue comment`](https://cli.github.com/manual/gh_issue_comment) を使用して、新しいイシューへのリンクを含むコメントを追加します。
 </td>
 </tr>
 <tr>
@@ -476,16 +470,16 @@ If an issue from a previous run is open and assigned to someone, then use [`gh i
 </td>
 <td>
 
-If an issue from a previous run is open and is not assigned to anyone, then:
+以前の実行でのイシューが未解決であり誰にも割り当てられない場合は、次のようになります。
 
-* Use [`gh issue comment`](https://cli.github.com/manual/gh_issue_comment) to add a comment with a link to the new issue.
-* Use [`gh issue close`](https://cli.github.com/manual/gh_issue_close) to close the old issue.
-* Use [`gh issue edit`](https://cli.github.com/manual/gh_issue_edit) to edit the old issue to remove it from a specific {% data variables.product.prodname_dotcom %} project board.
+* [`gh issue comment`](https://cli.github.com/manual/gh_issue_comment) を使用して、新しいイシューへのリンクを含むコメントを追加します。
+* [`gh issue close`](https://cli.github.com/manual/gh_issue_close) を使用して以前のイシューを閉じます。
+* [`gh issue edit`](https://cli.github.com/manual/gh_issue_edit) を使用して以前のイシューを編集し、特定の {% data variables.product.prodname_dotcom %} プロジェクト ボードから削除します。
 </td>
 </tr>
 </tbody>
 </table>
 
-## Next steps
+## 次の手順
 
 {% data reusables.actions.learning-actions %}
diff --git a/translations/ja-JP/content/actions/hosting-your-own-runners/about-self-hosted-runners.md b/translations/ja-JP/content/actions/hosting-your-own-runners/about-self-hosted-runners.md
index f66ea675e4..1f447b00f9 100644
--- a/translations/ja-JP/content/actions/hosting-your-own-runners/about-self-hosted-runners.md
+++ b/translations/ja-JP/content/actions/hosting-your-own-runners/about-self-hosted-runners.md
@@ -69,13 +69,10 @@ You can use any machine as a self-hosted runner as long at it meets these requir
 * The machine has enough hardware resources for the type of workflows you plan to run. The self-hosted runner application itself only requires minimal resources.
 * If you want to run workflows that use Docker container actions or service containers, you must use a Linux machine and Docker must be installed.
 
-{% ifversion fpt or ghes > 3.2 or ghec or ghae %}
 ## Autoscaling your self-hosted runners
 
 You can automatically increase or decrease the number of self-hosted runners in your environment in response to the webhook events you receive. For more information, see "[Autoscaling with self-hosted runners](/actions/hosting-your-own-runners/autoscaling-with-self-hosted-runners)."
 
-{% endif %}
-
 ## Usage limits
 
 There are some limits on {% data variables.product.prodname_actions %} usage when using self-hosted runners. These limits are subject to change.
@@ -249,7 +246,6 @@ codeload.github.com
 
 {% endnote %}
 
-
 {% endif %}
 
 ## Self-hosted runner security
diff --git a/translations/ja-JP/content/actions/hosting-your-own-runners/adding-self-hosted-runners.md b/translations/ja-JP/content/actions/hosting-your-own-runners/adding-self-hosted-runners.md
index 3ccfe230c8..3ea5bd9887 100644
--- a/translations/ja-JP/content/actions/hosting-your-own-runners/adding-self-hosted-runners.md
+++ b/translations/ja-JP/content/actions/hosting-your-own-runners/adding-self-hosted-runners.md
@@ -32,7 +32,7 @@ For more information, see "[About self-hosted runners](/github/automating-your-w
 {% endwarning %}
 {% endif %}
 
-{% ifversion fpt or ghec or ghes > 3.2 %}
+{% ifversion fpt or ghec or ghes %}
 
 You can set up automation to scale the number of self-hosted runners. For more information, see "[Autoscaling with self-hosted runners](/actions/hosting-your-own-runners/autoscaling-with-self-hosted-runners)."
 
diff --git a/translations/ja-JP/content/actions/hosting-your-own-runners/autoscaling-with-self-hosted-runners.md b/translations/ja-JP/content/actions/hosting-your-own-runners/autoscaling-with-self-hosted-runners.md
index 89ba5d874e..01c8c1cb9f 100644
--- a/translations/ja-JP/content/actions/hosting-your-own-runners/autoscaling-with-self-hosted-runners.md
+++ b/translations/ja-JP/content/actions/hosting-your-own-runners/autoscaling-with-self-hosted-runners.md
@@ -5,7 +5,7 @@ intro: You can automatically scale your self-hosted runners in response to webho
 versions:
   fpt: '*'
   ghec: '*'
-  ghes: '>3.2'
+  ghes: '*'
   ghae: '*'
 type: overview
 ---
diff --git a/translations/ja-JP/content/actions/learn-github-actions/contexts.md b/translations/ja-JP/content/actions/learn-github-actions/contexts.md
index 2629ad6dba..bdf5bb0bfb 100644
--- a/translations/ja-JP/content/actions/learn-github-actions/contexts.md
+++ b/translations/ja-JP/content/actions/learn-github-actions/contexts.md
@@ -608,7 +608,7 @@ jobs:
 
 ## `secrets` context
 
-The `secrets` context contains the names and values of secrets that are available to a workflow run. The `secrets` context is not available for composite actions. For more information about secrets, see "[Encrypted secrets](/actions/security-guides/encrypted-secrets)."
+The `secrets` context contains the names and values of secrets that are available to a workflow run. The `secrets` context is not available for composite actions due to security reasons. If you want to pass a secret to a composite action, you need to do it explicitly as an input. For more information about secrets, see "[Encrypted secrets](/actions/security-guides/encrypted-secrets)."
 
 `GITHUB_TOKEN` is a secret that is automatically created for every workflow run, and is always included in the `secrets` context. For more information, see "[Automatic token authentication](/actions/security-guides/automatic-token-authentication)."
 
diff --git a/translations/ja-JP/content/actions/security-guides/automatic-token-authentication.md b/translations/ja-JP/content/actions/security-guides/automatic-token-authentication.md
index a7a52992a7..ba4f2ce5f5 100644
--- a/translations/ja-JP/content/actions/security-guides/automatic-token-authentication.md
+++ b/translations/ja-JP/content/actions/security-guides/automatic-token-authentication.md
@@ -87,9 +87,7 @@ The following table shows the permissions granted to the `GITHUB_TOKEN` by defau
 | issues        | read/write  | none | read |
 | metadata      | read        | read | read |
 | packages      | read/write  | none | read |
-{%- ifversion fpt or ghec or ghes > 3.2 or ghae %}
 | pages         | read/write  | none | read |
-{%- endif %}
 | pull-requests | read/write  | none | read |
 | repository-projects | read/write | none | read |
 | security-events     | read/write | none | read |
diff --git a/translations/ja-JP/content/actions/security-guides/encrypted-secrets.md b/translations/ja-JP/content/actions/security-guides/encrypted-secrets.md
index cd8cf7b99a..693eb7bb34 100644
--- a/translations/ja-JP/content/actions/security-guides/encrypted-secrets.md
+++ b/translations/ja-JP/content/actions/security-guides/encrypted-secrets.md
@@ -7,6 +7,8 @@ redirect_from:
   - /actions/configuring-and-managing-workflows/creating-and-storing-encrypted-secrets
   - /actions/configuring-and-managing-workflows/using-variables-and-secrets-in-a-workflow
   - /actions/reference/encrypted-secrets
+  - /actions/managing-workflows/storing-secrets
+  
 miniTocMaxHeadingLevel: 3
 versions:
   fpt: '*'
diff --git a/translations/ja-JP/content/actions/using-github-hosted-runners/controlling-access-to-larger-runners.md b/translations/ja-JP/content/actions/using-github-hosted-runners/controlling-access-to-larger-runners.md
index d8fba11f7c..97c4628d94 100644
--- a/translations/ja-JP/content/actions/using-github-hosted-runners/controlling-access-to-larger-runners.md
+++ b/translations/ja-JP/content/actions/using-github-hosted-runners/controlling-access-to-larger-runners.md
@@ -1,50 +1,49 @@
 ---
-title: より大きなランナーへのアクセスの制御
-intro: 'Organization または Enterprise に追加された {% data variables.actions.hosted_runner %} へのアクセスを、ポリシーを使って制限できます。'
+title: Controlling access to larger runners
+shortTitle: 'Control access to {% data variables.actions.hosted_runner %}s'
+intro: 'You can use policies to limit access to {% data variables.actions.hosted_runner %}s that have been added to an organization or enterprise.'
 product: '{% data reusables.gated-features.hosted-runners %}'
 versions:
   feature: actions-hosted-runners
 type: tutorial
-shortTitle: 'Controlling access to {% data variables.actions.hosted_runner %}s'
-ms.openlocfilehash: 6761f05ef04d18ebba7b9ef8a2894d7effd2622b
-ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794
-ms.translationtype: HT
-ms.contentlocale: ja-JP
-ms.lasthandoff: 09/09/2022
-ms.locfileid: '147764022'
 ---
-{% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## ランナー グループについて
+{% data reusables.actions.enterprise-beta %}
+{% data reusables.actions.enterprise-github-hosted-runners %}
 
-{% data reusables.actions.about-runner-groups %} {% ifversion fpt %}詳しくは、[{% data variables.product.prodname_ghe_cloud %} のドキュメント](/enterprise-cloud@latest/actions/using-github-hosted-runners/controlling-access-to-larger-runners)をご覧ください。{% endif %}
+## About runner groups
+
+{% data reusables.actions.about-runner-groups %} {% ifversion fpt %}For more information, see the [{% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest/actions/using-github-hosted-runners/controlling-access-to-larger-runners).{% endif %}
 
 {% ifversion ghec or ghes or ghae %}
 
-## Organization のランナー グループを作成する
+## Creating a runner group for an organization
 
-{% data reusables.actions.hosted-runner-security-admonition %} {% data reusables.actions.creating-a-runner-group-for-an-organization %}
+{% data reusables.actions.hosted-runner-security-admonition %}
+{% data reusables.actions.creating-a-runner-group-for-an-organization %}
 
-## Enterprise のランナー グループを作成する
+## Creating a runner group for an enterprise
 
-{% data reusables.actions.hosted-runner-security-admonition %} {% data reusables.actions.creating-a-runner-group-for-an-enterprise %}
+{% data reusables.actions.hosted-runner-security-admonition %}
+{% data reusables.actions.creating-a-runner-group-for-an-enterprise %}
 
 {% endif %}
 
-## ランナー グループのアクセス ポリシーを変更する
+## Changing the access policy of a runner group
 
-{% data reusables.actions.hosted-runner-security-admonition %} {% data reusables.actions.changing-the-access-policy-of-a-runner-group %}
+{% data reusables.actions.hosted-runner-security-admonition %}
+{% data reusables.actions.changing-the-access-policy-of-a-runner-group %}
 
-## ランナー グループの名前を変更する
+## Changing the name of a runner group
 
 {% data reusables.actions.changing-the-name-of-a-runner-group %}
 
 {% ifversion ghec or ghes or ghae %}
-## ランナーをグループに移動する
+## Moving a runner to a group
 
 {% data reusables.actions.moving-a-runner-to-a-group %}
 
-## ランナー グループを削除する
+## Removing a runner group
 
 {% data reusables.actions.removing-a-runner-group %}
 
diff --git a/translations/ja-JP/content/actions/using-github-hosted-runners/using-larger-runners.md b/translations/ja-JP/content/actions/using-github-hosted-runners/using-larger-runners.md
index ed6b379be2..b0f14df4a0 100644
--- a/translations/ja-JP/content/actions/using-github-hosted-runners/using-larger-runners.md
+++ b/translations/ja-JP/content/actions/using-github-hosted-runners/using-larger-runners.md
@@ -1,11 +1,11 @@
 ---
 title: Using larger runners
-shortTitle: 'Larger runners'
+shortTitle: Larger runners
 intro: '{% data variables.product.prodname_dotcom %} offers larger runners with more RAM and CPU.'
 miniTocMaxHeadingLevel: 3
 product: '{% data reusables.gated-features.hosted-runners %}'
 versions:
-  feature: 'actions-hosted-runners'
+  feature: actions-hosted-runners
 ---
 
 ## Overview of {% data variables.actions.hosted_runner %}s
diff --git a/translations/ja-JP/content/actions/using-workflows/workflow-commands-for-github-actions.md b/translations/ja-JP/content/actions/using-workflows/workflow-commands-for-github-actions.md
index 190fb29822..710052edb7 100644
--- a/translations/ja-JP/content/actions/using-workflows/workflow-commands-for-github-actions.md
+++ b/translations/ja-JP/content/actions/using-workflows/workflow-commands-for-github-actions.md
@@ -139,8 +139,8 @@ The following table shows which toolkit functions are available within a workflo
 | Toolkit function | Equivalent workflow command |
 | ----------------- |  ------------- |
 | `core.addPath`    | Accessible using environment file `GITHUB_PATH` |
-| `core.debug`      | `debug` |{% ifversion fpt or ghes > 3.2 or ghae or ghec %}
-| `core.notice`     | `notice` |{% endif %}
+| `core.debug`      | `debug` |
+| `core.notice`     | `notice` |
 | `core.error`      | `error` |
 | `core.endGroup`   | `endgroup` |
 | `core.exportVariable` | Accessible using environment file `GITHUB_ENV` |
@@ -216,8 +216,6 @@ Write-Output "::debug::Set the Octocat variable"
 
 {% endpowershell %}
 
-{% ifversion fpt or ghes > 3.2 or ghae or ghec %}
-
 ## Setting a notice message
 
 Creates a notice message and prints the message to the log. {% data reusables.actions.message-annotation-explanation %}
@@ -245,7 +243,6 @@ Write-Output "::notice file=app.js,line=1,col=5,endColumn=7::Missing semicolon"
 ```
 
 {% endpowershell %}
-{% endif %}
 
 ## Setting a warning message
 
@@ -584,6 +581,8 @@ console.log("The running PID from the main action is: " +  process.env.STATE_pro
 
 During the execution of a workflow, the runner generates temporary files that can be used to perform certain actions. The path to these files are exposed via environment variables. You will need to use UTF-8 encoding when writing to these files to ensure proper processing of the commands. Multiple commands can be written to the same file, separated by newlines.
 
+Most commands in the following examples use double quotes for echoing strings, which will attempt to interpolate characters like `$` for shell variable names. To always use literal values in quoted strings, you can use single quotes instead.
+
 {% powershell %}
 
 {% note %}
diff --git a/translations/ja-JP/content/actions/using-workflows/workflow-syntax-for-github-actions.md b/translations/ja-JP/content/actions/using-workflows/workflow-syntax-for-github-actions.md
index 5c778a85ca..4969f6b53e 100644
--- a/translations/ja-JP/content/actions/using-workflows/workflow-syntax-for-github-actions.md
+++ b/translations/ja-JP/content/actions/using-workflows/workflow-syntax-for-github-actions.md
@@ -32,7 +32,7 @@ The name of your workflow. {% data variables.product.prodname_dotcom %} displays
 {% ifversion actions-run-name %}
 ## `run-name`
 
-The name for workflow runs generated from the workflow. {% data variables.product.prodname_dotcom %} displays the workflow run name in the list of workflow runs on your repository's "Actions" tab. If you omit `run-name`, the run name is set to event-specific information for the workflow run. For example, for a workflow triggered by a `push` or `pull_request` event, it is set as the commit message.
+The name for workflow runs generated from the workflow. {% data variables.product.prodname_dotcom %} displays the workflow run name in the list of workflow runs on your repository's "Actions" tab. If `run-name` is omitted or is only whitespace, then the run name is set to event-specific information for the workflow run. For example, for a workflow triggered by a `push` or `pull_request` event, it is set as the commit message.
 
 This value can include expressions and can reference the [`github`](/actions/learn-github-actions/contexts#github-context) and [`inputs`](/actions/learn-github-actions/contexts#inputs-context) contexts.
 
diff --git a/translations/ja-JP/content/admin/code-security/managing-github-advanced-security-for-your-enterprise/configuring-dependency-review-for-your-appliance.md b/translations/ja-JP/content/admin/code-security/managing-github-advanced-security-for-your-enterprise/configuring-dependency-review-for-your-appliance.md
index ef0b9fc8fc..192df3affc 100644
--- a/translations/ja-JP/content/admin/code-security/managing-github-advanced-security-for-your-enterprise/configuring-dependency-review-for-your-appliance.md
+++ b/translations/ja-JP/content/admin/code-security/managing-github-advanced-security-for-your-enterprise/configuring-dependency-review-for-your-appliance.md
@@ -1,7 +1,7 @@
 ---
 title: Configuring dependency review for your appliance
 shortTitle: Configuring dependency review
-intro: 'To helps users understand dependency changes when reviewing pull requests, you can enable, configure, and disable dependency review for {% data variables.location.product_location %}.' 
+intro: 'To helps users understand dependency changes when reviewing pull requests, you can enable, configure, and disable dependency review for {% data variables.location.product_location %}.'
 product: '{% data reusables.gated-features.dependency-review %}'
 miniTocMaxHeadingLevel: 3
 versions:
@@ -14,8 +14,6 @@ topics:
   - Security
 ---
 
-{% data reusables.dependency-review.beta %}
-
 ## About dependency review
 
 {% data reusables.dependency-review.feature-overview %}  
diff --git a/translations/ja-JP/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/about-supply-chain-security-for-your-enterprise.md b/translations/ja-JP/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/about-supply-chain-security-for-your-enterprise.md
index ee72a7d813..d0e0a0fefc 100644
--- a/translations/ja-JP/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/about-supply-chain-security-for-your-enterprise.md
+++ b/translations/ja-JP/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/about-supply-chain-security-for-your-enterprise.md
@@ -15,6 +15,6 @@ topics:
 
 You can allow users to identify their projects' dependencies by {% ifversion ghes %}enabling{% elsif ghae %}using{% endif %} the dependency graph for {% data variables.location.product_location %}. For more information, see "{% ifversion ghes %}[Enabling the dependency graph for your enterprise](/admin/code-security/managing-supply-chain-security-for-your-enterprise/enabling-the-dependency-graph-for-your-enterprise){% elsif ghae %}[About the dependency graph](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph){% endif %}."
 
-You can also allow users on {% data variables.location.product_location %} to find and fix vulnerabilities in their code dependencies by enabling {% data variables.product.prodname_dependabot_alerts %}{% ifversion ghes > 3.2 %} and {% data variables.product.prodname_dependabot_updates %}{% endif %}. For more information, see "[Enabling {% data variables.product.prodname_dependabot %} for your enterprise](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise)."
+You can also allow users on {% data variables.location.product_location %} to find and fix vulnerabilities in their code dependencies by enabling {% data variables.product.prodname_dependabot_alerts %}{% ifversion ghes %} and {% data variables.product.prodname_dependabot_updates %}{% endif %}. For more information, see "[Enabling {% data variables.product.prodname_dependabot %} for your enterprise](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise)."
 
 After you enable {% data variables.product.prodname_dependabot_alerts %}, you can view vulnerability data from the {% data variables.product.prodname_advisory_database %} on {% data variables.location.product_location %} and manually sync the data. For more information, see "[Viewing the vulnerability data for your enterprise](/admin/code-security/managing-supply-chain-security-for-your-enterprise/viewing-the-vulnerability-data-for-your-enterprise)."
diff --git a/translations/ja-JP/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/enabling-the-dependency-graph-for-your-enterprise.md b/translations/ja-JP/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/enabling-the-dependency-graph-for-your-enterprise.md
index d4d24029d2..eb2b304a79 100644
--- a/translations/ja-JP/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/enabling-the-dependency-graph-for-your-enterprise.md
+++ b/translations/ja-JP/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/enabling-the-dependency-graph-for-your-enterprise.md
@@ -16,7 +16,7 @@ topics:
 
 {% data reusables.dependabot.about-the-dependency-graph %} For more information, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)"
 
-After you enable the dependency graph for your enterprise, you can enable {% data variables.product.prodname_dependabot %} to detect insecure dependencies in your repository{% ifversion ghes > 3.2 %} and automatically fix the vulnerabilities{% endif %}. For more information, see "[Enabling {% data variables.product.prodname_dependabot %} for your enterprise](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise)."
+After you enable the dependency graph for your enterprise, you can enable {% data variables.product.prodname_dependabot %} to detect insecure dependencies in your repository{% ifversion ghes %} and automatically fix the vulnerabilities{% endif %}. For more information, see "[Enabling {% data variables.product.prodname_dependabot %} for your enterprise](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise)."
 
 {% ifversion ghes %}
 You can enable the dependency graph via the {% data variables.enterprise.management_console %} or the administrative shell. We recommend using the {% data variables.enterprise.management_console %} unless {% data variables.location.product_location %} uses clustering.
diff --git a/translations/ja-JP/content/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise.md b/translations/ja-JP/content/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise.md
index 8fa01e4e0d..d0b14cf91e 100644
--- a/translations/ja-JP/content/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise.md
+++ b/translations/ja-JP/content/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise.md
@@ -1,6 +1,6 @@
 ---
 title: Enabling Dependabot for your enterprise
-intro: 'You can allow users of {% data variables.location.product_location %} to find and fix vulnerabilities in code dependencies by enabling {% data variables.product.prodname_dependabot_alerts %}{% ifversion ghes > 3.2 %} and {% data variables.product.prodname_dependabot_updates %}{% endif %}.'
+intro: 'You can allow users of {% data variables.location.product_location %} to find and fix vulnerabilities in code dependencies by enabling {% data variables.product.prodname_dependabot_alerts %}{% ifversion ghes %} and {% data variables.product.prodname_dependabot_updates %}{% endif %}.'
 miniTocMaxHeadingLevel: 3
 shortTitle: Dependabot
 redirect_from:
@@ -26,7 +26,7 @@ topics:
 
 ## About {% data variables.product.prodname_dependabot %} for {% data variables.product.product_name %}
 
-{% data variables.product.prodname_dependabot %} helps users of {% data variables.location.product_location %} find and fix vulnerabilities in their dependencies.{% ifversion ghes > 3.2 %} You can enable {% data variables.product.prodname_dependabot_alerts %} to notify users about vulnerable dependencies and {% data variables.product.prodname_dependabot_updates %} to fix the vulnerabilities and keep dependencies updated to the latest version.
+{% data variables.product.prodname_dependabot %} helps users of {% data variables.location.product_location %} find and fix vulnerabilities in their dependencies.{% ifversion ghes %} You can enable {% data variables.product.prodname_dependabot_alerts %} to notify users about vulnerable dependencies and {% data variables.product.prodname_dependabot_updates %} to fix the vulnerabilities and keep dependencies updated to the latest version.
 
 ### About {% data variables.product.prodname_dependabot_alerts %}
 {% endif %}
@@ -51,7 +51,7 @@ When {% data variables.location.product_location %} receives information about a
 
 For repositories with {% data variables.product.prodname_dependabot_alerts %} enabled, scanning is triggered on any push to the default branch that contains a manifest file or lock file. Additionally, when a new vulnerability record is added to {% data variables.location.product_location %}, {% data variables.product.product_name %} scans all existing repositories on {% data variables.location.product_location %} and generates alerts for any repository that is vulnerable. For more information, see "[About {% data variables.product.prodname_dependabot_alerts %}](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)."
 
-{% ifversion ghes > 3.2 %}
+{% ifversion ghes %}
 ### About {% data variables.product.prodname_dependabot_updates %}
 
 {% data reusables.dependabot.beta-security-and-version-updates %}
@@ -124,7 +124,7 @@ After you enable {% data variables.product.prodname_dependabot_alerts %} for you
    ![Screenshot of the dropdown menu to enable updating vulnerable dependencies](/assets/images/enterprise/site-admin-settings/dependabot-updates-button.png)
 
 {% endif %}
-{% ifversion ghes > 3.2 %}
+{% ifversion ghes %}
 
 When you enable {% data variables.product.prodname_dependabot_alerts %}, you should consider also setting up {% data variables.product.prodname_actions %} for {% data variables.product.prodname_dependabot_security_updates %}. This feature allows developers to fix vulnerabilities in their dependencies. For more information, see "[Managing self-hosted runners for {% data variables.product.prodname_dependabot_updates %} on your enterprise](/admin/github-actions/enabling-github-actions-for-github-enterprise-server/managing-self-hosted-runners-for-dependabot-updates)."
 
diff --git a/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/configuring-host-keys-for-your-instance.md b/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/configuring-host-keys-for-your-instance.md
index 0930d0297d..6c4cc51477 100644
--- a/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/configuring-host-keys-for-your-instance.md
+++ b/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/configuring-host-keys-for-your-instance.md
@@ -2,7 +2,7 @@
 title: Configuring host keys for your instance
 shortTitle: Configure host keys
 intro: 'You can increase the security of {% data variables.location.product_location %} by configuring the algorithms that your instance uses to generate and advertise host keys for incoming SSH connections.'
-permissions: "Site administrators can configure the host keys for a {% data variables.product.product_name %} instance."
+permissions: 'Site administrators can configure the host keys for a {% data variables.product.product_name %} instance.'
 versions:
   ghes: '>= 3.6'
 type: how_to
diff --git a/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/configuring-ssh-connections-to-your-instance.md b/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/configuring-ssh-connections-to-your-instance.md
index c76cd8b27b..3d8a2df2fe 100644
--- a/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/configuring-ssh-connections-to-your-instance.md
+++ b/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/configuring-ssh-connections-to-your-instance.md
@@ -2,7 +2,7 @@
 title: Configuring SSH connections to your instance
 shortTitle: Configure SSH connections
 intro: 'You can increase the security of {% data variables.location.product_location %} by configuring the SSH algorithms that clients can use to establish a connection.'
-permissions: "Site administrators can configure SSH connections to a {% data variables.product.product_name %} instance."
+permissions: 'Site administrators can configure SSH connections to a {% data variables.product.product_name %} instance.'
 versions:
   ghes: '>= 3.6'
 type: how_to
diff --git a/translations/ja-JP/content/admin/enterprise-management/caching-repositories/about-repository-caching.md b/translations/ja-JP/content/admin/enterprise-management/caching-repositories/about-repository-caching.md
index 31e7fefdbf..814f55de38 100644
--- a/translations/ja-JP/content/admin/enterprise-management/caching-repositories/about-repository-caching.md
+++ b/translations/ja-JP/content/admin/enterprise-management/caching-repositories/about-repository-caching.md
@@ -1,26 +1,21 @@
 ---
-title: リポジトリのキャッシュについて
-intro: リポジトリのキャッシュを使用して、分散チームと CI ファームでの Git 読み取り操作のパフォーマンスを向上させることができます。
+title: About repository caching
+intro: You can increase the performance of Git read operations for distributed teams and CI farms with repository caching.
 versions:
-  ghes: '>=3.3'
+  ghes: '*'
 type: overview
 topics:
   - Enterprise
-ms.openlocfilehash: 06a0dd3ba202c73f1ee035d61f7865fadd13b415
-ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
-ms.translationtype: HT
-ms.contentlocale: ja-JP
-ms.lasthandoff: 09/11/2022
-ms.locfileid: '145120645'
 ---
+
 {% data reusables.enterprise.repository-caching-release-phase %}
 
-世界中にチームと CI ファームがある場合、{% data variables.product.prodname_ghe_server %} のプライマリ インスタンスのパフォーマンスが低下する可能性があります。 アクティブ geo レプリカを使うと読み取り要求のパフォーマンスが向上しますが、書き込みスループットが制限されます。 プライマリ インスタンスの負荷を軽減し、書き込みスループットのパフォーマンスを向上させるには、これらの地理的に分散したクライアントの近くに配置されたリポジトリの非同期読み取り専用ミラーであるリポジトリ キャッシュを構成できます。 
+If you have teams and CI farms located around the world, you may experience reduced performance on your primary {% data variables.product.prodname_ghe_server %} instance. While active geo-replicas can improve the performance of read requests, this comes at the cost of limiting write throughput. To reduce load on your primary instance and improve write throughput performance, you can configure a repository cache, an asynchronous read-only mirror of repositories located near these geographically-distributed clients. 
 
-リポジトリ キャッシュを使うと、CI ファームや分散チームの近くにリポジトリ データが提供されるため、{% data variables.product.product_name %} は、複数のクライアントにサービスを提供するために、同じ Git データを長距離ネットワーク リンク経由で何回も送信する必要がなくなります。 たとえば、プライマリ インスタンスが北米にあり、アジアの多くの場所でもそれを利用している場合は、アジアの CI ランナーが使用するためのリポジトリ キャッシュをアジアに設けるとメリットがあります。
+A repository cache eliminates the need for {% data variables.product.product_name %} to transmit the same Git data over a long-haul network link multiple times to serve multiple clients, by serving your repository data close to CI farms and distributed teams. For instance, if your primary instance is in North America and you also have a large presence in Asia, you will benefit from setting up the repository cache in Asia for use by CI runners there.
 
-リポジトリ キャッシュは、プライマリ インスタンス (単一インスタンスでも、geo レプリケートされたインスタンスのセットでも) で、Git データの変更をリッスンします。 CI ファームや他の読み取り負荷の高いコンシューマーは、プライマリ インスタンスの代わりにリポジトリ キャッシュからクローンしてフェッチします。 変更は、クライアントごとに 1 回ではなく、キャッシュ インスタンスごとに 1 回ずつ、定期的にネットワーク全体に反映されます。 通常、Git データは、データがプライマリ インスタンスにプッシュされてから数分以内に、リポジトリ キャッシュで使用できるようになります。  {% ifversion ghes > 3.3 %}CI システムは、[`cache_sync` Webhook](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#cache_sync) を使うことで、キャッシュで使用可能になったデータに対応できます。{% endif %}
+The repository cache listens to the primary instance, whether that's a single instance or a geo-replicated set of instances, for changes to Git data. CI farms and other read-heavy consumers clone and fetch from the repository cache instead of the primary instance. Changes are propagated across the network, at periodic intervals, once per cache instance rather than once per client. Git data will typically be visible on the repository cache within several minutes after the data is pushed to the primary instance.  {% ifversion ghes > 3.3 %}The [`cache_sync` webhook](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#cache_sync) can be used by CI systems to react to data being available in the cache.{% endif %}
 
-リポジトリ キャッシュと同期できるようにするリポジトリを、きめ細かく制御できます。 Git データは、ユーザーが指定した場所にのみレプリケートされます。
+You have fine-grained control over which repositories are allowed to sync to the repository cache. Git data will only be replicated to the locations you specify.
 
-{% data reusables.enterprise.repository-caching-config-summary %}詳しくは、「[リポジトリ キャッシュを構成する](/admin/enterprise-management/caching-repositories/configuring-a-repository-cache)」をご覧ください。
+{% data reusables.enterprise.repository-caching-config-summary %} For more information, see "[Configuring a repository cache](/admin/enterprise-management/caching-repositories/configuring-a-repository-cache)."
diff --git a/translations/ja-JP/content/admin/enterprise-management/caching-repositories/configuring-a-repository-cache.md b/translations/ja-JP/content/admin/enterprise-management/caching-repositories/configuring-a-repository-cache.md
index 424faf2ecb..26b4536eea 100644
--- a/translations/ja-JP/content/admin/enterprise-management/caching-repositories/configuring-a-repository-cache.md
+++ b/translations/ja-JP/content/admin/enterprise-management/caching-repositories/configuring-a-repository-cache.md
@@ -1,107 +1,105 @@
 ---
-title: リポジトリ キャッシュの構成
-intro: リポジトリ キャッシュを構成するには、新しいアプライアンスを作成し、リポジトリ キャッシュをプライマリ アプライアンスに接続し、リポジトリ キャッシュに対するリポジトリ ネットワークのレプリケーションを構成します。
+title: Configuring a repository cache
+intro: 'You can configure a repository cache by creating a new appliance, connecting the repository cache to your primary appliance, and configuring replication of repository networks to the repository cache.'
 versions:
-  ghes: '>=3.3'
+  ghes: '*'
 type: how_to
 topics:
   - Enterprise
-ms.openlocfilehash: dced49e1e6795407e2e41f12275a310c3a98aaf1
-ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
-ms.translationtype: HT
-ms.contentlocale: ja-JP
-ms.lasthandoff: 09/10/2022
-ms.locfileid: '146332011'
 ---
+
 {% data reusables.enterprise.repository-caching-release-phase %}
 
-## リポジトリ キャッシュの構成について
+## About configuration for repository caching
 
-{% data reusables.enterprise.repository-caching-config-summary %}次に、リポジトリ キャッシュにレプリケートされるリポジトリ ネットワークを管理するデータの場所ポリシーを設定できます。
+{% data reusables.enterprise.repository-caching-config-summary %} Then, you can set data location policies that govern which repository networks are replicated to the repository cache.
 
-クラスタリングでは、リポジトリ キャッシュはサポートされていません。
+Repository caching is not supported with clustering.
 
-## リポジトリ キャッシュの DNS
+## DNS for repository caches
 
-プライマリ インスタンスとリポジトリ キャッシュの DNS 名は異なっている必要があります。 たとえば、プライマリ インスタンスが `github.example.com` にある場合は、キャッシュ名は `europe-ci.github.example.com` や `github.asia.example.com` に決定できます。
+The primary instance and repository cache should have different DNS names. For example, if your primary instance is at `github.example.com`, you might decide to name a cache `europe-ci.github.example.com` or `github.asia.example.com`.
 
-CI マシンで、プライマリ インスタンスではなくリポジトリ キャッシュからフェッチするには、Git の `url.<base>.insteadOf` 構成設定を使用できます。 詳細については、Git ドキュメントにある「[`git-config`](https://git-scm.com/docs/git-config#Documentation/git-config.txt-urlltbasegtinsteadOf)」を参照してください。 
+To have your CI machines fetch from the repository cache instead of the primary instance, you can use Git's `url.<base>.insteadOf` configuration setting. For more information, see [`git-config`](https://git-scm.com/docs/git-config#Documentation/git-config.txt-urlltbasegtinsteadOf) in the Git documentation. 
 
-たとえば、CI マシンのグローバル `.gitconfig` には、次の行が含まれます。
+For example, the global `.gitconfig` for the CI machine would include these lines.
 
 ```
 [url "https://europe-ci.github.example.com/"]
-    insteadOf = https://github.example.com/
+	insteadOf = https://github.example.com/
 ```
 
-次に、`https://github.example.com/myorg/myrepo` をフェッチするように Git に要求すると、代わりに `https://europe-ci.github.example.com/myorg/myrepo` からフェッチされます。
+Then, when told to fetch `https://github.example.com/myorg/myrepo`, Git will instead fetch from `https://europe-ci.github.example.com/myorg/myrepo`.
 
-## リポジトリ キャッシュの構成
+## Configuring a repository cache
 
 {% ifversion ghes = 3.3 %}
-1. プライマリ {% data variables.product.prodname_ghe_server %} アプライアンスで、リポジトリ キャッシュの機能フラグを有効にします。
+1. On your primary {% data variables.product.prodname_ghe_server %} appliance, enable the feature flag for repository caching.
    
    ```
    $ ghe-config cluster.cache-enabled true
    ```
 {%- endif %}
-1. 新しい {% data variables.product.prodname_ghe_server %} アプライアンスを希望するプラットフォームにセットアップします。 このアプライアンスがリポジトリ キャッシュになります。 詳細については、「[{% data variables.product.prodname_ghe_server %} インスタンスをセットアップする](/admin/guides/installation/setting-up-a-github-enterprise-server-instance)」を参照してください。
+1. Set up a new {% data variables.product.prodname_ghe_server %} appliance on your desired platform. This appliance will be your repository cache. For more information, see "[Setting up a {% data variables.product.prodname_ghe_server %} instance](/admin/guides/installation/setting-up-a-github-enterprise-server-instance)."
 {% data reusables.enterprise_installation.replica-steps %}
-1. SSH を使用して、リポジトリ キャッシュの IP アドレスに接続します。
+1. Connect to the repository cache's IP address using SSH.
 
    ```shell
-   $ ssh -p 122 admin@<em>REPLICA IP</em>
+   $ ssh -p 122 admin@REPLICA-IP
    ```
 {%- ifversion ghes = 3.3 %}
-1. キャッシュ レプリカで、リポジトリ キャッシュの機能フラグを有効にします。
+1. On your cache replica, enable the feature flag for repository caching.
    
    ```
    $ ghe-config cluster.cache-enabled true
    ```
-{%- endif %} {% data reusables.enterprise_installation.generate-replication-key-pair %} {% data reusables.enterprise_installation.add-ssh-key-to-primary %}
-1. プライマリへの接続を確認し、リポジトリ キャッシュに対してレプリカ モードを有効にするには、`ghe-repl-setup` をもう一度実行します。
+{%- endif %}
+{% data reusables.enterprise_installation.generate-replication-key-pair %}
+{% data reusables.enterprise_installation.add-ssh-key-to-primary %}
+1. To verify the connection to the primary and enable replica mode for the repository cache, run `ghe-repl-setup` again.
 
    ```shell
-   $ ghe-repl-setup <em>PRIMARY IP</em>
+   $ ghe-repl-setup PRIMARY-IP
    ```
 
-1. *CACHE-LOCATION* を、キャッシュがデプロイされているリージョンなどの英数字識別子に置き換えて、リポジトリ キャッシュに対して `cache_location` を設定します。 また、このキャッシュのデータセンター名も設定します。新しいキャッシュでは、同じデータセンター内の別のキャッシュからシード処理を試みます。
+1. Set a `cache_location` for the repository cache, replacing *CACHE-LOCATION* with an alphanumeric identifier, such as the region where the cache is deployed. Also set a datacenter name for this cache; new caches will attempt to seed from another cache in the same datacenter.
 
    ```shell
-   $ ghe-repl-node --cache <em>CACHE-LOCATION</em> --datacenter <em>REPLICA-DC-NAME</em>
+   $ ghe-repl-node --cache CACHE-LOCATION --datacenter REPLICA-DC-NAME
    ```
 
-{% data reusables.enterprise_installation.replication-command %} {% data reusables.enterprise_installation.verify-replication-channel %}
-1. リポジトリ キャッシュへのリポジトリ ネットワークのレプリケーションを有効にするには、データの場所ポリシーを設定します。 詳細については、「[データの場所ポリシー](#data-location-policies)」を参照してください。
+{% data reusables.enterprise_installation.replication-command %}
+{% data reusables.enterprise_installation.verify-replication-channel %}
+1. To enable replication of repository networks to the repository cache, set a data location policy. For more information, see "[Data location policies](#data-location-policies)."
 
-## データの場所ポリシー
+## Data location policies
 
-`spokesctl cache-policy` コマンドでリポジトリのデータの場所ポリシーを構成して、データの局所性を制御できます。 データの場所ポリシーによって、どのリポジトリ ネットワークがどのリポジトリ キャッシュにレプリケートされているかが決まります。 既定では、データの場所ポリシーが構成されるまで、どのリポジトリ キャッシュにもリポジトリ ネットワークはレプリケートされません。
+You can control data locality by configuring data location policies for your repositories with the `spokesctl cache-policy` command. Data location policies determine which repository networks are replicated on which repository caches. By default, no repository networks will be replicated on any repository caches until a data location policy is configured.
 
-データの場所ポリシーは、Git コンテンツにのみ影響します。 Issue や pull request コメントなどのデータベース内のコンテンツは、ポリシーに関係なくすべてのノードにレプリケートされます。
+Data location policies affect only Git content. Content in the database, such as issues and pull request comments, will be replicated to all nodes regardless of policy.
 
 {% note %}
 
-**注:** データの場所ポリシーは、アクセス制御と同じではありません。 リポジトリにアクセスできるユーザーを制御するには、リポジトリ ロールを使用する必要があります。 リポジトリ ロールの詳細については、「[Organization のリポジトリ ロール](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)」を参照してください。
+**Note:** Data location policies are not the same as access control. You must use repository roles to control which users may access a repository. For more information about repository roles, see "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)."
 
 {% endnote %} 
 
-`--default` フラグを使用して、すべてのネットワークをレプリケートするようにポリシーを構成できます。 たとえば、次のコマンドでは、すべてのリポジトリ ネットワークの 1 つのコピーを、`cache_location` が "kansas" であるリポジトリ キャッシュのセットにレプリケートするポリシーが作成されます。
+You can configure a policy to replicate all networks with the `--default` flag. For example, this command will create a policy to replicate a single copy of every repository network to the set of repository caches whose `cache_location` is "kansas".
 
  ```
  $ ghe-spokesctl cache-policy set --default 1 kansas
  ```
 
-リポジトリ ネットワークのレプリケーションを構成するには、ネットワークのルートであるリポジトリを指定します。 リポジトリ ネットワークには、リポジトリとリポジトリのすべてのフォークが含まれます。 ネットワーク全体をレプリケートしないと、ネットワークの一部をレプリケートすることはできません。
+To configure replication for a repository network, specify the repository that is the root of the network. A repository network includes a repository and all of the repository's forks. You cannot replicate part of a network without replicating the whole network.
 
 ```
 $ ghe-spokesctl cache-policy set <owner/repository> 1 kansas
 ```
 
-ネットワークのレプリカ数を 0 に指定すると、すべてのネットワークをレプリケートし、特定のネットワークを除外するポリシーをオーバーライドできます。 たとえば、次のコマンドでは、場所 "kansas" 内のリポジトリ キャッシュに、そのネットワークのコピーを含めることができないことが指定されます。
+You can override a policy that replicates all networks and exclude specific networks by specifying a replica count of zero for the network. For example, this command specifies that any repository cache in location "kansas" cannot contain any copies of that network.
 
 ```
 $ ghe-spokesctl cache-policy set <owner/repository> 0 kansas
 ```
 
-特定のキャッシュの場所で、1 より大きいレプリカ数はサポートされていません。
+Replica counts greater than one in a given cache location are not supported.
diff --git a/translations/ja-JP/content/admin/enterprise-management/caching-repositories/index.md b/translations/ja-JP/content/admin/enterprise-management/caching-repositories/index.md
index 62947f4f84..f84a25d1cc 100644
--- a/translations/ja-JP/content/admin/enterprise-management/caching-repositories/index.md
+++ b/translations/ja-JP/content/admin/enterprise-management/caching-repositories/index.md
@@ -1,18 +1,13 @@
 ---
-title: リポジトリのキャッシュ
-intro: ユーザーと CI クライアントに近い読み取り専用ミラーを提供するリポジトリ キャッシュを使用して、地理的に分散した Team のパフォーマンスを向上させることができます。
+title: Caching repositories
+intro: 'You can improve performance for your geographically-distributed team with repository caching, which provides read-only mirrors close to your users and CI clients.'
 versions:
-  ghes: '>=3.3'
+  ghes: '*'
 topics:
   - Enterprise
 children:
   - /about-repository-caching
   - /configuring-a-repository-cache
-ms.openlocfilehash: 4c019db4ea99bc2383c4496fb9632e8723a7a02b
-ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
-ms.translationtype: HT
-ms.contentlocale: ja-JP
-ms.lasthandoff: 09/11/2022
-ms.locfileid: '145112798'
 ---
+
 {% data reusables.enterprise.repository-caching-release-phase %}
diff --git a/translations/ja-JP/content/admin/enterprise-management/configuring-high-availability/about-geo-replication.md b/translations/ja-JP/content/admin/enterprise-management/configuring-high-availability/about-geo-replication.md
index 7eedd8aa5e..99e8a4d951 100644
--- a/translations/ja-JP/content/admin/enterprise-management/configuring-high-availability/about-geo-replication.md
+++ b/translations/ja-JP/content/admin/enterprise-management/configuring-high-availability/about-geo-replication.md
@@ -1,6 +1,6 @@
 ---
-title: Geo-replicationについて
-intro: '{% data variables.product.prodname_ghe_server %} 上の Geo-replication は、地理的に分散したデータセンターからの要求を満たすために、複数のアクティブなレプリカを使用します。'
+title: About geo-replication
+intro: 'Geo-replication on {% data variables.product.prodname_ghe_server %} uses multiple active replicas to fulfill requests from geographically distributed data centers.'
 redirect_from:
   - /enterprise/admin/installation/about-geo-replication
   - /enterprise/admin/enterprise-management/about-geo-replication
@@ -11,32 +11,26 @@ type: overview
 topics:
   - Enterprise
   - High availability
-ms.openlocfilehash: 0e4e2feb161dd897172385bf25cf997268527fd3
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
-ms.translationtype: HT
-ms.contentlocale: ja-JP
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '146332809'
 ---
-アクティブなレプリカが複数あれば、最も近いレプリカへの距離を短くできます。 たとえばサンフランシスコ、ニューヨーク、ロンドンにオフィスを持つ組織は、プライマリのアプライアンスをニューヨークの近くのデータセンター内で動作させ、2つのレプリカをサンフランシスコとロンドンの近くのデータセンターで動作させることができます。 地理的な場所を認識するDNSを利用すれば、ユーザーは利用可能な最も近いサーバへ振り分けられ、リポジトリのデータに高速にアクセスできます。 ニューヨークの近くにあるアプライアンスをプライマリにすれば、ロンドンへのレイテンシが大きいサンフランシスコ近くのアプライアンスをプライマリにする場合に比べ、ホスト間のレイテンシの削減に役立ちます。
+Multiple active replicas can provide a shorter distance to the nearest replica. For example, an organization with offices in San Francisco, New York, and London could run the primary appliance in a datacenter near New York and two replicas in datacenters near San Francisco and London. Using geolocation-aware DNS, users can be directed to the closest server available and access repository data faster. Designating the appliance near New York as the primary helps reduce the latency between the hosts, compared to the appliance near San Francisco being the primary which has a higher latency to London.
 
-アクティブなレプリカは、自身では処理できないリクエストをプライマリインスタンスに中継します。 レプリカは、すべてのSSL接続をターミネートする接続点として機能します。 ホスト間のトラフィックは、暗号化されたVPN接続を通じて送信されます。これは、Geo-replicationなしの2ノードのHigh Availability構成に似ています。
+The active replica proxies requests that it can't process itself to the primary instance. The replicas function as a point of presence terminating all SSL connections. Traffic between hosts is sent through an encrypted VPN connection, similar to a two-node high availability configuration without geo-replication.
 
-Git リクエストと、LFS やファイルアップロードなどの特定のファイルサーバーリクエストは、プライマリからデータをロードせずにレプリカから直接処理できます。 Webリクエストは常にプライマリにルーティングされますが、レプリカがユーザに近ければ、近くでSSLのターミネーションが行われることからリクエストは高速に処理されます。
+Git requests and specific file server requests, such as LFS and file uploads, can be served directly from the replica without loading any data from the primary. Web requests are always routed to the primary, but if the replica is closer to the user the requests are faster due to the closer SSL termination.
 
-[Amazon の Route 53 サービス](http://docs.aws.amazon.com/Route53/latest/DeveloperGuide/routing-policy.html#routing-policy-geo)など、Geo DNS は、geo レプリケーションがシームレスに機能するために必要です。 インスタンスのホスト名は、ユーザの場所に最も近いレプリカに解決されるべきです。
+Geo DNS, such as [Amazon's Route 53 service](http://docs.aws.amazon.com/Route53/latest/DeveloperGuide/routing-policy.html#routing-policy-geo), is required for geo-replication to work seamlessly. The hostname for the instance should resolve to the replica that is closest to the user's location.
 
-## 制限事項
+## Limitations
 
-レプリカへの書き込みリクエストには、データをプライマリとすべてのレプリカへ送信することが必要です。 これは、すべての書き込みのパフォーマンスが最も遅いレプリカによって制限されることを意味しますが、新しい Geo-replication レプリカは、プライマリからではなく、既存の同じ場所に配置された Geo-replication レプリカからデータの大部分をシードできます。 {% ifversion ghes > 3.2 %}書き込みスループットに影響を与えず、分散チームと大規模 CI ファームによって引き起こされる待機時間と帯域幅を減らすには、代わりにリポジトリ キャッシュを構成できます。 詳細については、「[About repository caching](/admin/enterprise-management/caching-repositories/about-repository-caching)」(リポジトリのキャッシュについて) を参照してください。{% endif %}
+Writing requests to the replica requires sending the data to the primary and all replicas. This means that the performance of all writes is limited by the slowest replica, although new geo-replicas can seed the majority of their data from existing co-located geo-replicas, rather than from the primary. To reduce the latency and bandwidth caused by distributed teams and large CI farms without impacting write throughput, you can configure repository caching instead. For more information, see "[About repository caching](/admin/enterprise-management/caching-repositories/about-repository-caching)."
 
-Geo-replication は、{% data variables.product.prodname_ghe_server %} インスタンスに容量を追加したり、不十分な CPU やメモリリソースに関連するパフォーマンスの問題を解決したりしません。 プライマリのアプライアンスがオフラインである場合、アクティブなレプリカはいかなる読み込みや書き込みのリクエストも処理できません。 
+Geo-replication will not add capacity to a {% data variables.product.prodname_ghe_server %} instance or solve performance issues related to insufficient CPU or memory resources. If the primary appliance is offline, active replicas will be unable to serve any read or write requests. 
 
 {% data reusables.enterprise_installation.replica-limit %}
 
-## Geo-replication設定のモニタリング
+## Monitoring a geo-replication configuration
 
 {% data reusables.enterprise_installation.monitoring-replicas %}
 
-## 参考資料
-- 「[geo レプリケーションレプリカの作成](/enterprise/admin/guides/installation/creating-a-high-availability-replica/#creating-geo-replication-replicas)」
+## Further reading
+- "[Creating geo-replication replicas](/enterprise/admin/guides/installation/creating-a-high-availability-replica/#creating-geo-replication-replicas)"
diff --git a/translations/ja-JP/content/admin/enterprise-management/configuring-high-availability/about-high-availability-configuration.md b/translations/ja-JP/content/admin/enterprise-management/configuring-high-availability/about-high-availability-configuration.md
index b8c4366d1a..2254343985 100644
--- a/translations/ja-JP/content/admin/enterprise-management/configuring-high-availability/about-high-availability-configuration.md
+++ b/translations/ja-JP/content/admin/enterprise-management/configuring-high-availability/about-high-availability-configuration.md
@@ -13,12 +13,12 @@ topics:
   - High availability
   - Infrastructure
 shortTitle: About HA configuration
-ms.openlocfilehash: 921a1a935bbfa930c77e2c72d7856f00d54d6016
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: b54ca60c6cf1d79b9435ca8deedebec09ed39396
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: ja-JP
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '146332746'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148109001'
 ---
 High Availability設定をする際には、プライマリからレプリカアプライアンスへのすべてのデータストア（Gitリポジトリ、MySQL、Redis、Elasticsearch）の一方方向の非同期レプリケーションが、自動的にセットアップされます。 ほとんどの {% data variables.product.prodname_ghe_server %} 構成設定も、{% data variables.enterprise.management_console %} パスワードを含めてレプリケートされます。 詳細については、「[Accessing the management console](/admin/configuration/configuring-your-enterprise/accessing-the-management-console)」 (管理コンソールへのアクセス) を参照してください。
 
@@ -35,8 +35,8 @@ High Availability設定をする際には、プライマリからレプリカア
 
 High Availability設定は、以下に対するソリューションとしては適切ではありません。
 
-  - **スケールアウト**: geo レプリケーションを使えば地理的にトラフィックを分散させることができるものの、書き込みのパフォーマンスはプライマリ アプライアンスの速度と可用性によって制限されます。 詳細については、「[geo レプリケーションについて](/enterprise/admin/guides/installation/about-geo-replication/)」を参照してください。{% ifversion ghes > 3.2 %}
-  - **CI/CD の読み込み**: プライマリ インスタンスから地理的に離れている多数の CI クライアントがある場合は、リポジトリ キャッシュを構成するとメリットが得られる場合があります。 詳細については、「[About repository caching](/admin/enterprise-management/caching-repositories/about-repository-caching)」(リポジトリのキャッシュについて) を参照してください。{% endif %}
+  - **スケールアウト**: geo レプリケーションを使えば地理的にトラフィックを分散させることができるものの、書き込みのパフォーマンスはプライマリ アプライアンスの速度と可用性によって制限されます。 詳細については、「[geo レプリケーションについて](/enterprise/admin/guides/installation/about-geo-replication/)」を参照してください。
+  - **CI/CD の読み込み**: プライマリ インスタンスから地理的に離れている多数の CI クライアントがある場合は、リポジトリ キャッシュを構成するとメリットが得られる場合があります。 詳細については、「[About repository caching](/admin/enterprise-management/caching-repositories/about-repository-caching)」(リポジトリのキャッシュについて) を参照してください。
   - **プライマリ アプライアンスのバックアップ**: High Availabilityレプリカは、システム災害復旧計画のオフサイトバックアップを置き換えるものではありません。 データ破壊や損失の中には、プライマリからレプリカへ即座にレプリケーションされてしまうものもあります。 安定した過去の状態への安全なロールバックを保証するには、履歴スナップショットでの定期的なバックアップを行う必要があります。
   - **ダウンタイムなしのアップグレード**: コントロールされた昇格のシナリオにおけるデータ損失やスプリットブレインの状況を避けるには、プライマリアプライアンスをメンテナンスモードにして、すべての書き込みが完了するのを待ってからレプリカを昇格させてください。
 
diff --git a/translations/ja-JP/content/admin/enterprise-management/configuring-high-availability/creating-a-high-availability-replica.md b/translations/ja-JP/content/admin/enterprise-management/configuring-high-availability/creating-a-high-availability-replica.md
index b3f1c3ec05..e70b4f1225 100644
--- a/translations/ja-JP/content/admin/enterprise-management/configuring-high-availability/creating-a-high-availability-replica.md
+++ b/translations/ja-JP/content/admin/enterprise-management/configuring-high-availability/creating-a-high-availability-replica.md
@@ -39,7 +39,7 @@ shortTitle: Create HA replica
 
 This example configuration uses a primary and two replicas, which are located in three different geographic regions. While the three nodes can be in different networks, all nodes are required to be reachable from all the other nodes. At the minimum, the required administrative ports should be open to all the other nodes. For more information about the port requirements, see "[Network Ports](/enterprise/admin/guides/installation/network-ports/#administrative-ports)."
 
-{% data reusables.enterprise_clustering.network-latency %}{% ifversion ghes > 3.2 %} If latency is more than 70 milliseconds, we recommend cache replica nodes instead. For more information, see "[Configuring a repository cache](/admin/enterprise-management/caching-repositories/configuring-a-repository-cache)."{% endif %}
+{% data reusables.enterprise_clustering.network-latency %} If latency is more than 70 milliseconds, we recommend cache replica nodes instead. For more information, see "[Configuring a repository cache](/admin/enterprise-management/caching-repositories/configuring-a-repository-cache)."
 
 1. Create the first replica the same way you would for a standard two node configuration by running `ghe-repl-setup` on the first replica.
   ```shell
diff --git a/translations/ja-JP/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrade-requirements.md b/translations/ja-JP/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrade-requirements.md
index 24cfb85f46..5b9ed639d1 100644
--- a/translations/ja-JP/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrade-requirements.md
+++ b/translations/ja-JP/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrade-requirements.md
@@ -17,7 +17,6 @@ topics:
 {% note %}
 
 **Notes:**
-{% ifversion ghes < 3.3 %}- Features such as {% data variables.product.prodname_actions %}, {% data variables.product.prodname_registry %}, {% data variables.product.prodname_mobile %} and {% data variables.product.prodname_GH_advanced_security %} are available on {% data variables.product.prodname_ghe_server %} 3.0 or higher. We highly recommend upgrading to 3.0 or later releases to take advantage of critical security updates, bug fixes and feature enhancements.{% endif %}
 - Upgrade packages are available at [enterprise.github.com](https://enterprise.github.com/releases) for supported versions. Verify the availability of the upgrade packages you will need to complete the upgrade. If a package is not available, contact {% data variables.contact.contact_ent_support %} for assistance.
 - If you're using {% data variables.product.prodname_ghe_server %} Clustering, see "[Upgrading a cluster](/enterprise/admin/guides/clustering/upgrading-a-cluster/)" in the {% data variables.product.prodname_ghe_server %} Clustering Guide for specific instructions unique to clustering.
 - The release notes for {% data variables.product.prodname_ghe_server %} provide a comprehensive list of new features for every version of {% data variables.product.prodname_ghe_server %}. For more information, see the [releases page](https://enterprise.github.com/releases).
diff --git a/translations/ja-JP/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server.md b/translations/ja-JP/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server.md
index c1c8100472..b4203f0a1d 100644
--- a/translations/ja-JP/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server.md
+++ b/translations/ja-JP/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server.md
@@ -23,7 +23,6 @@ topics:
 shortTitle: Upgrading GHES
 ---
 
-{% ifversion ghes < 3.3 %}{% data reusables.enterprise.upgrade-ghes-for-features %}{% endif %}
 
 ## Preparing to upgrade
 
@@ -70,8 +69,7 @@ There are two types of snapshots:
 | Azure | VM | <https://docs.microsoft.com/azure/backup/backup-azure-vms-first-look-arm>
 | Hyper-V | VM | <https://docs.microsoft.com/windows-server/virtualization/hyper-v/manage/enable-or-disable-checkpoints-in-hyper-v>
 | Google Compute Engine | Disk | <https://cloud.google.com/compute/docs/disks/create-snapshots>
-| VMware | VM | <https://pubs.vmware.com/vsphere-50/topic/com.vmware.wssdk.pg.doc_50/PG_Ch11_VM_Manage.13.3.html>{% ifversion ghes < 3.3 %}
-| XenServer | VM | <https://docs.citrix.com/en-us/xencenter/current-release/vms-snapshots.html>{% endif %}
+| VMware | VM | <https://pubs.vmware.com/vsphere-50/topic/com.vmware.wssdk.pg.doc_50/PG_Ch11_VM_Manage.13.3.html>
 
 ## Upgrading with a hotpatch
 
diff --git a/translations/ja-JP/content/admin/github-actions/advanced-configuration-and-troubleshooting/backing-up-and-restoring-github-enterprise-server-with-github-actions-enabled.md b/translations/ja-JP/content/admin/github-actions/advanced-configuration-and-troubleshooting/backing-up-and-restoring-github-enterprise-server-with-github-actions-enabled.md
index 986fa1a462..bb63cf03cc 100644
--- a/translations/ja-JP/content/admin/github-actions/advanced-configuration-and-troubleshooting/backing-up-and-restoring-github-enterprise-server-with-github-actions-enabled.md
+++ b/translations/ja-JP/content/admin/github-actions/advanced-configuration-and-troubleshooting/backing-up-and-restoring-github-enterprise-server-with-github-actions-enabled.md
@@ -41,4 +41,4 @@ To restore a backup of {% data variables.location.product_location %} with {% da
    ```
 {% data reusables.actions.apply-configuration-and-enable %}
 1. After {% data variables.product.prodname_actions %} is configured and enabled, to restore the rest of the data from the backup, use the `ghe-restore` command. For more information, see "[Restoring a backup](/admin/configuration/configuring-backups-on-your-appliance#restoring-a-backup)."
-1. Re-register your self-hosted runners on the destination instance. For more information, see "[Adding self-hosted runners](/actions/hosting-your-own-runners/adding-self-hosted-runners)."
\ No newline at end of file
+1. Re-register your self-hosted runners on the destination instance. For more information, see "[Adding self-hosted runners](/actions/hosting-your-own-runners/adding-self-hosted-runners)."
diff --git a/translations/ja-JP/content/admin/github-actions/advanced-configuration-and-troubleshooting/troubleshooting-github-actions-for-your-enterprise.md b/translations/ja-JP/content/admin/github-actions/advanced-configuration-and-troubleshooting/troubleshooting-github-actions-for-your-enterprise.md
index c38c209a49..71088f9285 100644
--- a/translations/ja-JP/content/admin/github-actions/advanced-configuration-and-troubleshooting/troubleshooting-github-actions-for-your-enterprise.md
+++ b/translations/ja-JP/content/admin/github-actions/advanced-configuration-and-troubleshooting/troubleshooting-github-actions-for-your-enterprise.md
@@ -156,7 +156,7 @@ If any of these services are at or near 100% CPU utilization, or the memory is n
     When running `ghe-config-apply`, if you see output like `Failed to run nomad job '/etc/nomad-jobs/<name>.hcl'`, then the change has likely over-allocated CPU or memory resources. If this happens, edit the configuration files again and lower the allocated CPU or memory, then re-run `ghe-config-apply`.
 1. After the configuration is applied, run `ghe-actions-check` to verify that the {% data variables.product.prodname_actions %} services are operational.
 
-{% ifversion fpt or ghec or ghes > 3.2 %}
+{% ifversion fpt or ghec or ghes %}
 ## Troubleshooting failures when {% data variables.product.prodname_dependabot %} triggers existing workflows
 
 {% data reusables.dependabot.beta-security-and-version-updates %}
diff --git a/translations/ja-JP/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/index.md b/translations/ja-JP/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/index.md
index e9cbd20df8..3b7a7be889 100644
--- a/translations/ja-JP/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/index.md
+++ b/translations/ja-JP/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/index.md
@@ -12,11 +12,11 @@ children:
   - /enabling-github-actions-with-minio-gateway-for-nas-storage
   - /managing-self-hosted-runners-for-dependabot-updates
 shortTitle: Enable GitHub Actions
-ms.openlocfilehash: 675bbbe0ccbb68d676602b0553c8534f1601bcf6
-ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d
+ms.openlocfilehash: 273e03407dd8c3c0a125e2c215a973c88aaf884b
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: ja-JP
-ms.lasthandoff: 09/11/2022
-ms.locfileid: '145120446'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148109060'
 ---
 
diff --git a/translations/ja-JP/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/about-github-actions-for-enterprises.md b/translations/ja-JP/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/about-github-actions-for-enterprises.md
index c8553798a2..921d01760d 100644
--- a/translations/ja-JP/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/about-github-actions-for-enterprises.md
+++ b/translations/ja-JP/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/about-github-actions-for-enterprises.md
@@ -12,13 +12,6 @@ topics:
   - Enterprise
 ---
 
-{% ifversion ghes < 3.3 %}
-{% note %}
-
-**Note:** {% data reusables.enterprise.upgrade-ghes-for-actions %}
-
-{% endnote %}
-{% endif %}
 
 ## About {% data variables.product.prodname_actions %} for enterprises
 
@@ -56,7 +49,6 @@ You can create your own unique automations, or you can use and adapt workflows f
 After you finish planning, you can follow the instructions for getting started with {% data variables.product.prodname_actions %}. For more information, see {% ifversion ghec %}"[Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_cloud %}](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-cloud)."{% elsif ghae %}"[Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_managed %}](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-ae)."{% endif %}
 {% endif %}
 
-
 ## Further reading
 
 - "[Understanding {% data variables.product.prodname_actions %}](/actions/learn-github-actions/understanding-github-actions)"{% ifversion ghec %}
diff --git a/translations/ja-JP/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server.md b/translations/ja-JP/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server.md
index 739cb96d5d..5b79fefc07 100644
--- a/translations/ja-JP/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server.md
+++ b/translations/ja-JP/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server.md
@@ -23,8 +23,6 @@ topics:
 
 This article explains how site administrators can configure {% data variables.product.prodname_ghe_server %} to use {% data variables.product.prodname_actions %}.
 
-{% data reusables.enterprise.upgrade-ghes-for-actions %}
-
 {% data reusables.actions.ghes-actions-not-enabled-by-default %} You'll need to determine whether your instance has adequate CPU and memory resources to handle the load from {% data variables.product.prodname_actions %} without causing performance loss, and possibly increase those resources. You'll also need to decide which storage provider you'll use for the blob storage required to store artifacts{% ifversion actions-caching %} and caches{% endif %} generated by workflow runs. Then, you'll enable {% data variables.product.prodname_actions %} for your enterprise, manage access permissions, and add self-hosted runners to run workflows.
 
 {% data reusables.actions.introducing-enterprise %}
@@ -33,7 +31,6 @@ This article explains how site administrators can configure {% data variables.pr
 
 ## Review hardware requirements
 
-
 {%- ifversion ghes < 3.6 %}
 
 The CPU and memory resources available to {% data variables.location.product_location %} determine the number of jobs that can be run concurrently without performance loss. {% data reusables.actions.minimum-hardware %}
@@ -50,14 +47,6 @@ The peak quantity of connected runners without performance loss depends on such
 
 {% endif %}
 
-{%- ifversion ghes = 3.2 %}
-
-{% data reusables.actions.hardware-requirements-3.2 %}
-
-Maximum concurrency was measured using multiple repositories, job duration of approximately 10 minutes, and 10 MB artifact uploads. You may experience different performance depending on the overall levels of activity on your instance.
-
-{%- endif %}
-
 {%- ifversion ghes = 3.3 %}
 
 {% data reusables.actions.hardware-requirements-3.3 %}
@@ -88,7 +77,6 @@ Maximum concurrency was measured using multiple repositories, job duration of ap
 
 {%- endif %}
 
-
 {%- ifversion ghes = 3.6 %}
 
 {% data reusables.actions.hardware-requirements-3.6 %}
@@ -114,8 +102,7 @@ For more information about minimum hardware requirements for {% data variables.l
 - [Google Cloud Platform](/admin/installation/installing-github-enterprise-server-on-google-cloud-platform#hardware-considerations)
 - [Hyper-V](/admin/installation/installing-github-enterprise-server-on-hyper-v#hardware-considerations)
 - [OpenStack KVM](/admin/installation/installing-github-enterprise-server-on-openstack-kvm#hardware-considerations)
-- [VMware](/admin/installation/installing-github-enterprise-server-on-vmware#hardware-considerations){% ifversion ghes < 3.3 %}
-- [XenServer](/admin/installation/installing-github-enterprise-server-on-xenserver#hardware-considerations){% endif %}
+- [VMware](/admin/installation/installing-github-enterprise-server-on-vmware#hardware-considerations)
 
 {% data reusables.enterprise_installation.about-adjusting-resources %}
 
diff --git a/translations/ja-JP/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-self-hosted-runners-for-your-enterprise.md b/translations/ja-JP/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-self-hosted-runners-for-your-enterprise.md
index 8fc4c6c049..0c3418282c 100644
--- a/translations/ja-JP/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-self-hosted-runners-for-your-enterprise.md
+++ b/translations/ja-JP/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-self-hosted-runners-for-your-enterprise.md
@@ -32,9 +32,7 @@ This guide shows you how to apply a centralized management approach to self-host
 1. Deploy a self-hosted runner for your enterprise
 1. Create a group to manage access to the runners available to your enterprise
 1. Optionally, further restrict the repositories that can use the runner
-{%- ifversion ghec or ghae or ghes > 3.2 %}
 1. Optionally, build custom tooling to automatically scale your self-hosted runners
-{% endif %}
 
 You'll also find additional information about how to monitor and secure your self-hosted runners,{% ifversion ghes or ghae %} how to access actions from {% data variables.product.prodname_dotcom_the_website %},{% endif %} and how to customize the software on your runner machines.
 
@@ -122,14 +120,10 @@ Optionally, organization owners can further restrict the access policy of the ru
 
 For more information, see "[Managing access to self-hosted runners using groups](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#changing-the-access-policy-of-a-self-hosted-runner-group)."
 
-{% ifversion ghec or ghae or ghes > 3.2 %}
-
 ## 5. Automatically scale your self-hosted runners
 
 Optionally, you can build custom tooling to automatically scale the self-hosted runners for {% ifversion ghec or ghae %}your enterprise{% elsif ghes %}{% data variables.location.product_location %}{% endif %}. For example, your tooling can respond to webhook events from {% data variables.location.product_location %} to automatically scale a cluster of runner machines. For more information, see "[Autoscaling with self-hosted runners](/actions/hosting-your-own-runners/autoscaling-with-self-hosted-runners)."
 
-{% endif %}
-
 ## Next steps
 
 - You can monitor self-hosted runners and troubleshoot common issues. For more information, see "[Monitoring and troubleshooting self-hosted runners](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners)."
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 8ac0a99e29..625a34aa98 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
@@ -18,8 +18,6 @@ topics:
 
 ![Diagram of jobs running on self-hosted runners](/assets/images/help/images/actions-enterprise-overview.png)
 
-{% data reusables.enterprise.upgrade-ghes-for-actions %}
-
 Before you introduce {% data variables.product.prodname_actions %} to a large enterprise, you first need to plan your adoption and make decisions about how your enterprise will use {% data variables.product.prodname_actions %} to best support your unique needs.
 
 ## Governance and compliance
@@ -102,7 +100,7 @@ You may need to upgrade the CPU and memory resources for {% data variables.locat
 
 You also have to decide where to add each runner. You can add a self-hosted runner to an individual repository, or you can make the runner available to an entire organization or your entire enterprise. Adding runners at the organization or enterprise levels allows sharing of runners, which might reduce the size of your runner infrastructure. You can use policies to limit access to self-hosted runners at the organization and enterprise levels by assigning groups of runners to specific repositories or organizations. For more information, see "[Adding self-hosted runners](/actions/hosting-your-own-runners/adding-self-hosted-runners)" and "[Managing access to self-hosted runners using groups](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups)."
 
-{% ifversion ghec or ghes > 3.2 %}
+{% ifversion ghec or ghes %}
 You should consider using autoscaling to automatically increase or decrease the number of available self-hosted runners. For more information, see "[Autoscaling with self-hosted runners](/actions/hosting-your-own-runners/autoscaling-with-self-hosted-runners)."
 {% endif %}
 
diff --git a/translations/ja-JP/content/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect.md b/translations/ja-JP/content/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect.md
index 709907e154..79a2892040 100644
--- a/translations/ja-JP/content/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect.md
+++ b/translations/ja-JP/content/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect.md
@@ -31,7 +31,7 @@ Alternatively, if you want stricter control over which actions are allowed in yo
 
 {% data reusables.actions.github-connect-resolution %}
 
-If a user has already created an organization and repository in your enterprise that matches an organization and repository name on {% data variables.product.prodname_dotcom_the_website %}, the repository on your enterprise will be used instead of the {% data variables.product.prodname_dotcom_the_website %} repository. {% ifversion ghes < 3.3 or ghae %}A malicious user could take advantage of this behavior to run code as part of a workflow{% else %}For more information, see "[Automatic retirement of namespaces for actions accessed on {% data variables.product.prodname_dotcom_the_website%}](#automatic-retirement-of-namespaces-for-actions-accessed-on-githubcom)."
+If a user has already created an organization and repository in your enterprise that matches an organization and repository name on {% data variables.product.prodname_dotcom_the_website %}, the repository on your enterprise will be used instead of the {% data variables.product.prodname_dotcom_the_website %} repository. {% ifversion ghae %}A malicious user could take advantage of this behavior to run code as part of a workflow.{% else %}For more information, see "[Automatic retirement of namespaces for actions accessed on {% data variables.product.prodname_dotcom_the_website%}](#automatic-retirement-of-namespaces-for-actions-accessed-on-githubcom)."
 {% endif %}
 
 ## Enabling automatic access to all {% data variables.product.prodname_dotcom_the_website %} actions
@@ -46,8 +46,6 @@ Before enabling access to all actions from {% data variables.product.prodname_do
   ![Drop-down menu to actions from GitHub.com in workflows runs](/assets/images/enterprise/site-admin-settings/enable-marketplace-actions-drop-down-ae.png)
 1. {% data reusables.actions.enterprise-limit-actions-use %}
 
-{% ifversion ghes > 3.2 or ghae %}
-
 ## Automatic retirement of namespaces for actions accessed on {% data variables.product.prodname_dotcom_the_website %}
 
 When you enable {% data variables.product.prodname_github_connect %}, users see no change in behavior for existing workflows because {% data variables.product.prodname_actions %} searches {% data variables.location.product_location %} for each action before falling back to {% data variables.product.prodname_dotcom_the_website%}. This ensures that any custom versions of actions your enterprise has created are used in preference to their counterparts on {% data variables.product.prodname_dotcom_the_website%}.
@@ -67,5 +65,3 @@ After using an action from {% data variables.product.prodname_dotcom_the_website
    **Tip:** When you unretire a namespace, always create the new repository with that name as soon as possible. If a workflow calls the associated action on {% data variables.product.prodname_dotcom_the_website %} before you create the local repository, the namespace will be retired again. For actions used in workflows that run frequently, you may find that a namespace is retired again before you have time to create the local repository. In this case, you can temporarily disable the relevant workflows until you have created the new repository.
 
    {% endtip %}
-
-{% endif %}
diff --git a/translations/ja-JP/content/admin/github-actions/managing-access-to-actions-from-githubcom/manually-syncing-actions-from-githubcom.md b/translations/ja-JP/content/admin/github-actions/managing-access-to-actions-from-githubcom/manually-syncing-actions-from-githubcom.md
index e44a1c5cf1..7e1756c530 100644
--- a/translations/ja-JP/content/admin/github-actions/managing-access-to-actions-from-githubcom/manually-syncing-actions-from-githubcom.md
+++ b/translations/ja-JP/content/admin/github-actions/managing-access-to-actions-from-githubcom/manually-syncing-actions-from-githubcom.md
@@ -33,13 +33,11 @@ If your machine has access to both systems at the same time, you can do the sync
 
 The `actions-sync` tool can only download actions from {% data variables.product.prodname_dotcom_the_website %} that are stored in public repositories.
 
-{% ifversion ghes > 3.2 or ghae %}
 {% note %}
 
 **Note:** The `actions-sync` tool is intended for use in systems where {% data variables.product.prodname_github_connect %} is not enabled. If you run the tool on a system with {% data variables.product.prodname_github_connect %} enabled, you may see the error `The repository <repo_name> has been retired and cannot be reused`. This indicates that a workflow has used that action directly on {% data variables.product.prodname_dotcom_the_website %} and the namespace is retired on {% data variables.location.product_location %}. For more information, see "[Automatic retirement of namespaces for actions accessed on {% data variables.product.prodname_dotcom_the_website%}](/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect#automatic-retirement-of-namespaces-for-actions-accessed-on-githubcom)." 
 
 {% endnote %}
-{% endif %}
 
 ## Prerequisites
 
diff --git a/translations/ja-JP/content/admin/github-actions/managing-access-to-actions-from-githubcom/using-the-latest-version-of-the-official-bundled-actions.md b/translations/ja-JP/content/admin/github-actions/managing-access-to-actions-from-githubcom/using-the-latest-version-of-the-official-bundled-actions.md
index c75e4e6eef..585957f8c6 100644
--- a/translations/ja-JP/content/admin/github-actions/managing-access-to-actions-from-githubcom/using-the-latest-version-of-the-official-bundled-actions.md
+++ b/translations/ja-JP/content/admin/github-actions/managing-access-to-actions-from-githubcom/using-the-latest-version-of-the-official-bundled-actions.md
@@ -47,10 +47,8 @@ Once {% data variables.product.prodname_github_connect %} is configured, you can
 1. Configure your workflow's YAML to use `{% data reusables.actions.action-checkout %}`.
 1. Each time your workflow runs, the runner will use the specified version of `actions/checkout` from {% data variables.product.prodname_dotcom_the_website %}.
 
-   {% ifversion ghes > 3.2 or ghae %}
    {% note %}
 
    **Note:** The first time the `checkout` action is used from {% data variables.product.prodname_dotcom_the_website %}, the `actions/checkout` namespace is automatically retired on {% data variables.location.product_location %}. If you ever want to revert to using a local copy of the action, you first need to remove the namespace from retirement. For more information, see "[Automatic retirement of namespaces for actions accessed on {% data variables.product.prodname_dotcom_the_website%}](/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect#automatic-retirement-of-namespaces-for-actions-accessed-on-githubcom)."
 
    {% endnote %}
-   {% endif %}
diff --git a/translations/ja-JP/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-enterprise-managed-users.md b/translations/ja-JP/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-enterprise-managed-users.md
index a448aa318d..2015dcd47d 100644
--- a/translations/ja-JP/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-enterprise-managed-users.md
+++ b/translations/ja-JP/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-enterprise-managed-users.md
@@ -1,5 +1,5 @@
 ---
-title: About Enterprise Managed Users
+title: About {% data variables.product.prodname_emus %}
 shortTitle: About managed users
 intro: 'You can centrally manage identity and access for your enterprise members on {% data variables.product.prodname_dotcom %} from your identity provider.'
 redirect_from:
@@ -16,6 +16,7 @@ topics:
   - Authentication
   - Enterprise
   - SSO
+allowTitleToDifferFromFilename: true
 ---
 
 ## About {% data variables.product.prodname_emus %}
@@ -24,8 +25,6 @@ With {% data variables.product.prodname_emus %}, you can control the user accoun
 
 In your IdP, you can give each {% data variables.enterprise.prodname_managed_user %} the role of user, enterprise owner, or billing manager. {% data variables.enterprise.prodname_managed_users_caps %} can own organizations within your enterprise and can add other {% data variables.enterprise.prodname_managed_users %} to the organizations and teams within. For more information, see "[Roles in an enterprise](/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/roles-in-an-enterprise)" and "[About organizations](/organizations/collaborating-with-groups-in-organizations/about-organizations)."
 
-Organization membership can be managed manually, or you can update membership automatically as {% data variables.enterprise.prodname_managed_users %} are added to IdP groups that are connected to teams within the organization. When a {% data variables.enterprise.prodname_managed_user %} is manually added to an organization, unassigning them from the {% data variables.product.prodname_emu_idp_application %} application on your IdP will suspend the user but not remove them from the organization. For more information about managing organization and team membership automatically, see "[Managing team memberships with identity provider groups](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/managing-team-memberships-with-identity-provider-groups)."
-
 {% ifversion oidc-for-emu %}
 
 {% data reusables.enterprise-accounts.emu-cap-validates %} For more information, see "[About support for your IdP's Conditional Access Policy](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-support-for-your-idps-conditional-access-policy)."
@@ -46,6 +45,17 @@ To use {% data variables.product.prodname_emus %}, you need a separate type of e
 
 {% endnote %}
 
+## About organization membership management
+
+Organization memberships can be managed manually, or you can update memberships automatically using IdP groups. To manage organization memberships through your IdP, the members must be added to an IdP group, and the IdP group must be connected to a team within the organization. For more information about managing organization and team memberships automatically, see "[Managing team memberships with identity provider groups](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/managing-team-memberships-with-identity-provider-groups)."
+
+The way a member is added to an organization owned by your enterprise (through IdP groups or manually) determines how they must be removed from an organization. 
+
+- If a member was added to an organization manually, you must remove them manually. Unassigning them from the {% data variables.product.prodname_emu_idp_application %} application on your IdP will suspend the user but not remove them from the organization.
+- If a user became a member of an organization because they were added to IdP groups mapped to one or more teams in the organization, removing them from _all_ of the mapped IdP groups associated with the organization will remove them from the organization.
+
+To discover how a member was added to an organization, you can filter the member list by type. For more information, see "[Viewing people in your enterprise](/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise#filtering-by-member-type-in-an-enterprise-with-managed-users)."
+
 ## Identity provider support
 
 {% data variables.product.prodname_emus %} supports the following IdPs{% ifversion oidc-for-emu %} and authentication methods:
diff --git a/translations/ja-JP/content/admin/identity-and-access-management/using-ldap-for-enterprise-iam/using-ldap.md b/translations/ja-JP/content/admin/identity-and-access-management/using-ldap-for-enterprise-iam/using-ldap.md
index 1054fee109..29ea2a82d2 100644
--- a/translations/ja-JP/content/admin/identity-and-access-management/using-ldap-for-enterprise-iam/using-ldap.md
+++ b/translations/ja-JP/content/admin/identity-and-access-management/using-ldap-for-enterprise-iam/using-ldap.md
@@ -145,7 +145,13 @@ After you enable LDAP sync, a synchronization job will run at the specified time
 A synchronization job will also run at the specified time interval to perform the following operations on each team that has been mapped to an LDAP group:
 
 - If a team's corresponding LDAP group has been removed, remove all members from the team.
-- If LDAP member entries have been removed from the LDAP group, remove the corresponding users from the team. If the user is no longer a member of any team in the organization, remove the user from the organization. If the user loses access to any repositories as a result, delete any private forks the user has of those repositories.
+- If LDAP member entries have been removed from the LDAP group, remove the corresponding users from the team. If the user is no longer a member of any team in the organization and is not an owner of the organization, remove the user from the organization. If the user loses access to any repositories as a result, delete any private forks the user has of those repositories.
+
+  {% note %}
+
+  **Note:** LDAP Sync will not remove a user from an organization if the user is an owner of that organization. Another organization owner will need to manually remove the user instead.
+
+  {% endnote %}
 - If LDAP member entries have been added to the LDAP group, add the corresponding users to the team. If the user regains access to any repositories as a result, restore any private forks of the repositories that were deleted because the user lost access in the past 90 days.
 
 {% data reusables.enterprise_user_management.ldap-sync-nested-teams %}
diff --git a/translations/ja-JP/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/configuring-saml-single-sign-on-for-your-enterprise-using-okta.md b/translations/ja-JP/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/configuring-saml-single-sign-on-for-your-enterprise-using-okta.md
index 23d0a0af3e..30d03c2a46 100644
--- a/translations/ja-JP/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/configuring-saml-single-sign-on-for-your-enterprise-using-okta.md
+++ b/translations/ja-JP/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/configuring-saml-single-sign-on-for-your-enterprise-using-okta.md
@@ -15,12 +15,12 @@ topics:
   - Enterprise
 type: how_to
 shortTitle: Configure SAML SSO with Okta
-ms.openlocfilehash: 2772285f266a2593e8fc0900b39602325d30c46d
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: e9cbf6e70fb5e07f9cd2c5e27d9b952921e18fdc
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: ja-JP
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147094807'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148109667'
 ---
 {% data reusables.enterprise-accounts.emu-saml-note %}
 
diff --git a/translations/ja-JP/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/troubleshooting-saml-authentication.md b/translations/ja-JP/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/troubleshooting-saml-authentication.md
index 3688464fb7..34adc3917c 100644
--- a/translations/ja-JP/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/troubleshooting-saml-authentication.md
+++ b/translations/ja-JP/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/troubleshooting-saml-authentication.md
@@ -108,4 +108,4 @@ Ensure that you set the value for `Audience` on your IdP to the `EntityId` for {
 
 {% ifversion ghec %}
 {% data reusables.saml.authentication-loop %}
-{% endif %}
\ No newline at end of file
+{% endif %}
diff --git a/translations/ja-JP/content/admin/index.md b/translations/ja-JP/content/admin/index.md
index 7b1bb2788b..f9430e64fa 100644
--- a/translations/ja-JP/content/admin/index.md
+++ b/translations/ja-JP/content/admin/index.md
@@ -105,14 +105,6 @@ featuredLinks:
     - '{% ifversion ghec %}/admin/monitoring-activity-in-your-enterprise/exploring-user-activity/managing-global-webhooks{% endif %}'
     - /billing/managing-your-license-for-github-enterprise/using-visual-studio-subscription-with-github-enterprise/setting-up-visual-studio-subscription-with-github-enterprise
     - /admin/enterprise-support/about-github-enterprise-support
-  videos:
-    - title: GitHub in the Enterprise – Maya Ross
-      href: 'https://www.youtube-nocookie.com/embed/1-i39RqaxRs'
-    - title: What's new for GitHub Enterprise – Jarryd McCree
-      href: 'https://www.youtube-nocookie.com/embed/ZZviWZgrqhM'
-    - title: Enforcing information security policy through GitHub Enterprise – Thomas Worley
-      href: 'https://www.youtube-nocookie.com/embed/DCu-ZTT7WTI'
-  videosHeading: GitHub Universe 2021 videos
 layout: product-landing
 versions:
   ghec: '*'
@@ -133,11 +125,11 @@ children:
   - /guides
   - /release-notes
   - /all-releases
-ms.openlocfilehash: ebd1473538d42928ff3d9abb3c0e2bd9f12767f5
-ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.openlocfilehash: 3980ad01e56bf1e38dd6473c5e5246c6d45350eb
+ms.sourcegitcommit: 3268914369fb29540e4d88ee5e56bc7a41f2a60e
 ms.translationtype: HT
 ms.contentlocale: ja-JP
-ms.lasthandoff: 09/11/2022
-ms.locfileid: '147881156'
+ms.lasthandoff: 10/26/2022
+ms.locfileid: '148111313'
 ---
 
diff --git a/translations/ja-JP/content/admin/installation/setting-up-a-github-enterprise-server-instance/index.md b/translations/ja-JP/content/admin/installation/setting-up-a-github-enterprise-server-instance/index.md
index 9a50077926..3136c7cc0d 100644
--- a/translations/ja-JP/content/admin/installation/setting-up-a-github-enterprise-server-instance/index.md
+++ b/translations/ja-JP/content/admin/installation/setting-up-a-github-enterprise-server-instance/index.md
@@ -18,14 +18,13 @@ children:
   - /installing-github-enterprise-server-on-hyper-v
   - /installing-github-enterprise-server-on-openstack-kvm
   - /installing-github-enterprise-server-on-vmware
-  - /installing-github-enterprise-server-on-xenserver
   - /setting-up-a-staging-instance
 shortTitle: Set up an instance
-ms.openlocfilehash: 23fe586f2c4baa87a2e2b388685bf8e42d5e10a4
-ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.openlocfilehash: 7c23ae31e8e976f2acc664f87fbff82ffe025a0e
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: ja-JP
-ms.lasthandoff: 09/11/2022
-ms.locfileid: '147881462'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148109000'
 ---
 
diff --git a/translations/ja-JP/content/admin/installation/setting-up-a-github-enterprise-server-instance/setting-up-a-staging-instance.md b/translations/ja-JP/content/admin/installation/setting-up-a-github-enterprise-server-instance/setting-up-a-staging-instance.md
index ecfcde73e0..6ae6322477 100644
--- a/translations/ja-JP/content/admin/installation/setting-up-a-github-enterprise-server-instance/setting-up-a-staging-instance.md
+++ b/translations/ja-JP/content/admin/installation/setting-up-a-github-enterprise-server-instance/setting-up-a-staging-instance.md
@@ -5,7 +5,7 @@ redirect_from:
   - /enterprise/admin/installation/setting-up-a-staging-instance
   - /admin/installation/setting-up-a-staging-instance
 versions:
-  ghes: "*"
+  ghes: '*'
 type: how_to
 topics:
   - Enterprise
diff --git a/translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/about-the-audit-log-for-your-enterprise.md b/translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/about-the-audit-log-for-your-enterprise.md
index fd9d8dacf6..82146c1824 100644
--- a/translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/about-the-audit-log-for-your-enterprise.md
+++ b/translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/about-the-audit-log-for-your-enterprise.md
@@ -46,9 +46,7 @@ As an enterprise owner{% ifversion ghes %} or site administrator{% endif %}, you
 {%- ifversion ghes %}
 - You can forward audit and system logs, from your enterprise to an third-party hosted monitoring system. For more information, see "[Log forwarding](/admin/monitoring-activity-in-your-enterprise/exploring-user-activity/log-forwarding)."
 {%- endif %}
-{%- ifversion ghec or ghes > 3.2 or ghae %}
 - You can use the Audit log API to view actions performed in your enterprise. For more information, see "[Using the audit log API for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/using-the-audit-log-api-for-your-enterprise)."
-{%- endif %}
 
 For a full list of audit log actions that may appear in your enterprise audit log, see "[Audit log actions for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise)."
 
diff --git a/translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise.md b/translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise.md
index 863a314cec..c4610e9a26 100644
--- a/translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise.md
+++ b/translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise.md
@@ -265,7 +265,6 @@ Action                        | Description
 | `config_entry.update` | A configuration setting was edited. These events are only visible in the site admin audit log. The type of events recorded relate to:</br>- Enterprise settings and policies</br>- Organization and repository permissions and settings</br>- Git, Git LFS, {% data variables.product.prodname_github_connect %}, {% data variables.product.prodname_registry %}, project, and code security settings.
 {%- endif %}
 
-{%- ifversion fpt or ghec or ghes > 3.2 or ghae %}
 ## `dependabot_alerts` category actions
 
 | Action | Description
@@ -285,9 +284,8 @@ Action                        | Description
 | Action | Description
 |--------|-------------
 | `dependabot_repository_access.repositories_updated` | The repositories that {% data variables.product.prodname_dependabot %} can access were updated.
-{%- endif %}
 
-{%- ifversion fpt or ghec or ghes > 3.2 %}
+{%- ifversion fpt or ghec or ghes %}
 ## `dependabot_security_updates` category actions
 
 | Action | Description
@@ -1341,7 +1339,7 @@ Before you'll see `git` category actions, you must enable Git events in the audi
 |--------|-------------
 | `staff.disable_repo`          | An organization{% ifversion ghes %}, repository or site{% else %} or repository{% endif %} administrator disabled access to a repository and all of its forks.
 | `staff.enable_repo`           | An organization{% ifversion ghes %}, repository or site{% else %} or repository{% endif %} administrator re-enabled access to a repository and all of its forks.
-{%- ifversion ghes > 3.2 or ghae %}
+{%- ifversion ghes or ghae %}
 | `staff.exit_fake_login`       | An enterprise owner{% ifversion ghes %} or site administrator{% endif %} ended an impersonation session on {% data variables.product.product_name %}.
 | `staff.fake_login`            | An enterprise owner{% ifversion ghes %} or site administrator{% endif %} signed into {% data variables.product.product_name %} as another user.
 {%- endif %}
diff --git a/translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/configuring-the-audit-log-for-your-enterprise.md b/translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/configuring-the-audit-log-for-your-enterprise.md
index 0bcdaf5744..5c4f84902a 100644
--- a/translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/configuring-the-audit-log-for-your-enterprise.md
+++ b/translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/configuring-the-audit-log-for-your-enterprise.md
@@ -1,8 +1,8 @@
 ---
 title: Configuring the audit log for your enterprise
-intro: "You can configure settings for your enterprise's audit log."
+intro: You can configure settings for your enterprise's audit log.
 shortTitle: Configure audit logs
-permissions: 'Enterprise owners can configure the audit log.'
+permissions: Enterprise owners can configure the audit log.
 versions:
   feature: audit-data-retention-tab
 type: how_to
@@ -53,4 +53,4 @@ Before you can enable Git events in the audit log, you must configure a retentio
    ![Screenshot of the checkbox to enable Git events in the audit log](/assets/images/help/enterprises/enable-git-events-checkbox.png)
 1. Click **Save**.
 
-{% endif %}
\ No newline at end of file
+{% endif %}
diff --git a/translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/using-the-audit-log-api-for-your-enterprise.md b/translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/using-the-audit-log-api-for-your-enterprise.md
index eb7ca4cae4..2d570ef443 100644
--- a/translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/using-the-audit-log-api-for-your-enterprise.md
+++ b/translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/using-the-audit-log-api-for-your-enterprise.md
@@ -1,6 +1,6 @@
 ---
 title: Using the audit log API for your enterprise
-intro: 'You can programmatically retrieve enterprise events with the{% ifversion ghec or ghes > 3.2 %} REST or{% endif %} GraphQL API.'
+intro: 'You can programmatically retrieve enterprise events with the REST or GraphQL API.'
 shortTitle: Audit log API
 permissions: 'Enterprise owners {% ifversion ghes %}and site administrators {% endif %}can use the audit log API.'
 miniTocMaxHeadingLevel: 3
@@ -18,7 +18,7 @@ topics:
 
 ## Using the audit log API
 
-You can interact with the audit log using the GraphQL API{% ifversion ghec or ghes > 3.2 or ghae %} or the REST API{% endif %}. 
+You can interact with the audit log using the GraphQL API or the REST API. 
 
 Timestamps and date fields in the API response are measured in [UTC epoch milliseconds](http://en.wikipedia.org/wiki/Unix_time).
 
@@ -106,7 +106,6 @@ This query uses the [AuditEntry](/graphql/reference/interfaces#auditentry) inter
 
 For more query examples, see the [platform-samples repository](https://github.com/github/platform-samples/blob/master/graphql/queries).
 
-{% ifversion ghec or ghes > 3.2 or ghae %}
 ## Querying the audit log REST API
 
 To ensure your intellectual property is secure, and you maintain compliance for your enterprise, you can use the audit log REST API to keep copies of your audit log data and monitor:
@@ -137,5 +136,3 @@ curl -H "Authorization: Bearer TOKEN" \
 --request GET \
 "https://api.github.com/enterprises/avocado-corp/audit-log?phrase=action:pull_request+created:>=2022-01-01+actor:octocat"
 ```
-
-{% endif %}
diff --git a/translations/ja-JP/content/admin/overview/about-upgrades-to-new-releases.md b/translations/ja-JP/content/admin/overview/about-upgrades-to-new-releases.md
index 46374ba031..94a48882a7 100644
--- a/translations/ja-JP/content/admin/overview/about-upgrades-to-new-releases.md
+++ b/translations/ja-JP/content/admin/overview/about-upgrades-to-new-releases.md
@@ -9,15 +9,13 @@ type: overview
 topics:
   - Enterprise
   - Upgrades
-ms.openlocfilehash: 196745ee4ededaf78bd5afe876e4afa09141e930
-ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.openlocfilehash: b3a2d340ef73ffe92f2117caf38a84e76ba0c8d1
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: ja-JP
-ms.lasthandoff: 09/11/2022
-ms.locfileid: '145120205'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148108851'
 ---
-{% ifversion ghes < 3.3 %}{% data reusables.enterprise.upgrade-ghes-for-features %}{% endif %}
-
 {% data reusables.enterprise.constantly-improving %}{% ifversion ghae %}{% data variables.product.prodname_ghe_managed %} はフルマネージドサービスであるため、{% data variables.product.company_short %} が Enterprise のアップグレードプロセスを完了します。{% endif %}
 
 通常、機能リリースは四半期ごとに行われ、新機能と機能のアップグレードが含まれます。 {% ifversion ghae %}{% data variables.product.company_short %} は、エンタープライズを最新の機能リリースにアップグレードします。 Enterprise で予定されているダウンタイムについては、事前に通知されます。{% endif %}
diff --git a/translations/ja-JP/content/admin/packages/migrating-your-enterprise-to-the-container-registry-from-the-docker-registry.md b/translations/ja-JP/content/admin/packages/migrating-your-enterprise-to-the-container-registry-from-the-docker-registry.md
index 9305406cc8..9a64fab4c6 100644
--- a/translations/ja-JP/content/admin/packages/migrating-your-enterprise-to-the-container-registry-from-the-docker-registry.md
+++ b/translations/ja-JP/content/admin/packages/migrating-your-enterprise-to-the-container-registry-from-the-docker-registry.md
@@ -2,9 +2,9 @@
 title: Migrating your enterprise to the Container registry from the Docker registry
 intro: 'You can migrate Docker images previously stored in the Docker registry on {% data variables.location.product_location %} to the {% data variables.product.prodname_container_registry %}.'
 product: '{% data reusables.gated-features.packages %}'
-permissions: "Enterprise owners can migrate Docker images to the {% data variables.product.prodname_container_registry %}."
+permissions: 'Enterprise owners can migrate Docker images to the {% data variables.product.prodname_container_registry %}.'
 versions:
-  feature: 'docker-ghcr-enterprise-migration'
+  feature: docker-ghcr-enterprise-migration
 shortTitle: Migrate to Container registry
 topics:
   - Containers
diff --git a/translations/ja-JP/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-projects-in-your-enterprise.md b/translations/ja-JP/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-projects-in-your-enterprise.md
index c23c175953..6a82551b48 100644
--- a/translations/ja-JP/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-projects-in-your-enterprise.md
+++ b/translations/ja-JP/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-projects-in-your-enterprise.md
@@ -20,12 +20,12 @@ topics:
   - Policies
   - Projects
 shortTitle: Project board policies
-ms.openlocfilehash: 2066ab3fd36814150ff79457930d05909027513e
-ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794
+ms.openlocfilehash: 2bb72b21094fadea8f584eb4749ed0cea69619ee
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: ja-JP
-ms.lasthandoff: 09/09/2022
-ms.locfileid: '147854136'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148108797'
 ---
 ## エンタープライズ内のプロジェクトのポリシーについて
 
diff --git a/translations/ja-JP/content/admin/policies/index.md b/translations/ja-JP/content/admin/policies/index.md
index a9b6fca97b..d18ecee533 100644
--- a/translations/ja-JP/content/admin/policies/index.md
+++ b/translations/ja-JP/content/admin/policies/index.md
@@ -14,11 +14,11 @@ children:
   - /enforcing-policies-for-your-enterprise
   - /enforcing-policy-with-pre-receive-hooks
 shortTitle: Set policies
-ms.openlocfilehash: 075d4f949435539c9c45ae651aedb0878f3317db
-ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d
+ms.openlocfilehash: 6fae4d9a9aa9c137be114b51eb90d79eb16d71df
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: ja-JP
-ms.lasthandoff: 09/11/2022
-ms.locfileid: '147400371'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148109115'
 ---
 
diff --git a/translations/ja-JP/content/admin/user-management/managing-organizations-in-your-enterprise/index.md b/translations/ja-JP/content/admin/user-management/managing-organizations-in-your-enterprise/index.md
index b9e44eabf6..f549b95eb5 100644
--- a/translations/ja-JP/content/admin/user-management/managing-organizations-in-your-enterprise/index.md
+++ b/translations/ja-JP/content/admin/user-management/managing-organizations-in-your-enterprise/index.md
@@ -33,11 +33,11 @@ children:
   - /managing-projects-using-jira
   - /continuous-integration-using-jenkins
 shortTitle: Manage organizations
-ms.openlocfilehash: 5d1430bc4efff03e6cddfe81f3c018d4f2064155
-ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d
+ms.openlocfilehash: 333d9b8d50bcdb86f709a447fee5a4078353dfe2
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: ja-JP
-ms.lasthandoff: 09/11/2022
-ms.locfileid: '147884246'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148109114'
 ---
 
diff --git a/translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/impersonating-a-user.md b/translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/impersonating-a-user.md
index 874c4cddc2..4cb891b65b 100644
--- a/translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/impersonating-a-user.md
+++ b/translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/impersonating-a-user.md
@@ -3,7 +3,7 @@ title: ユーザーの偽装
 intro: トラブルシューティング、ブロック解除、その他の正当な理由のために、ユーザーを偽装し、ユーザーに代わってアクションを実行できます。
 permissions: Enterprise owners can impersonate users within their enterprise.
 versions:
-  ghes: '>3.2'
+  ghes: '*'
   ghae: '*'
 type: how_to
 topics:
@@ -11,12 +11,12 @@ topics:
   - Enterprise
   - User account
 shortTitle: Impersonate a user
-ms.openlocfilehash: 8e237c6ace7e7feb4badefcbd863b0974c983732
-ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.openlocfilehash: df0513c3ca2931378e656f228939540dd5ea5816
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: ja-JP
-ms.lasthandoff: 09/11/2022
-ms.locfileid: '145116269'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148109291'
 ---
 ## ユーザーの偽装について
 
diff --git a/translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/index.md b/translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/index.md
index 7c31b6ef5c..e96df0c9c6 100644
--- a/translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/index.md
+++ b/translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/index.md
@@ -36,11 +36,11 @@ children:
   - /customizing-user-messages-for-your-enterprise
   - /rebuilding-contributions-data
 shortTitle: Manage users
-ms.openlocfilehash: 9ec6d7dc6822e71ff72542dd6b67ded031a1c44d
-ms.sourcegitcommit: ac00e2afa6160341c5b258d73539869720b395a4
+ms.openlocfilehash: 763277882c2af96505c2a6d4c236c05475ab9f3f
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: ja-JP
-ms.lasthandoff: 09/09/2022
-ms.locfileid: '147878519'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148008663'
 ---
 
diff --git a/translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise.md b/translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise.md
index 0596124afa..9fed0e1cbb 100644
--- a/translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise.md
+++ b/translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise.md
@@ -1,7 +1,7 @@
 ---
 title: Viewing people in your enterprise
 intro: 'To audit access to enterprise-owned resources or user license usage, enterprise owners can view every administrator and member of the enterprise.'
-permissions: 'Enterprise owners can view the people in an enterprise.'
+permissions: Enterprise owners can view the people in an enterprise.
 redirect_from:
   - /github/setting-up-and-managing-your-enterprise-account/viewing-people-in-your-enterprise-account
   - /articles/viewing-people-in-your-enterprise-account
@@ -116,7 +116,7 @@ If you use {% data variables.product.prodname_vss_ghe %}, the list of pending in
 
 ## Viewing suspended members in an {% data variables.enterprise.prodname_emu_enterprise %}
 
-If your enterprise uses {% data variables.product.prodname_emus %}, you can also view suspended users. Suspended users are members who have been deprovisioned after being unassigned from the {% data variables.product.prodname_emu_idp_application %} application or deleted from the identity provider. For more information, see "[About Enterprise Managed Users](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/about-enterprise-managed-users)."
+If your enterprise uses {% data variables.product.prodname_emus %}, you can view suspended users. Suspended users are members who have been deprovisioned after being unassigned from the {% data variables.product.prodname_emu_idp_application %} application or deleted from the identity provider. For more information, see "[About {% data variables.product.prodname_emus %}](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/about-enterprise-managed-users)."
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.people-tab %}
@@ -129,6 +129,21 @@ If your enterprise uses {% data variables.product.prodname_emus %}, you can also
 
 You can view a list of all dormant users {% ifversion ghes or ghae %} who have not been suspended and {% endif %}who are not site administrators. {% data reusables.enterprise-accounts.dormant-user-activity-threshold %} For more information, see "[Managing dormant users](/admin/user-management/managing-users-in-your-enterprise/managing-dormant-users)."
 
+{% ifversion filter-by-enterprise-member-type %}
+## Filtering by member type{% ifversion ghec %} in an {% data variables.enterprise.prodname_emu_enterprise %}{% endif %}
+
+{% ifversion ghec %}If your enterprise uses {% data variables.product.prodname_emus %}, you{% elsif ghes or ghae %}You{% endif %} can filter the member list of an organization by type to determine if memberships are managed through an IdP or managed directly. Memberships managed through an IdP were added through an IdP group, and the IdP group was connected to a team within the organization. Memberships managed directly were added to the organization manually. The way a membership is mananaged in an organization determines how it must be removed. You can use this filter to determine how members were added to an organization, so you know how to remove them.{% ifversion ghec %} For more information, see "[About {% data variables.product.prodname_emus %}](/enterprise-cloud@latest/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/about-enterprise-managed-users#about-organization-membership-management)."{% endif %}
+
+{% data reusables.enterprise-accounts.access-enterprise %}
+1. Under "Organizations," in the search bar, begin typing the organization's name until the organization appears in the search results, then click the name of the organization.
+   ![Screenshot of the search field for organizations](/assets/images/help/enterprises/organization-search.png)
+1. Under the organization name, click {% octicon "person" aria-label="The Person icon" %} **People**.
+   ![Screenshot of the People tab](/assets/images/help/enterprises/emu-organization-people-tab.png)
+1. Above the list of members, click **Type**, then select the type of members you want to view.
+   ![Screenshot of the "Type" button](/assets/images/help/enterprises/filter-by-member-type.png)
+
+{% endif %}
+
 {% ifversion ghec or ghes %}
 ## Viewing members without an email address from a verified domain
 
diff --git a/translations/ja-JP/content/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on.md b/translations/ja-JP/content/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on.md
index c0787f5ae1..b2c8f13f0b 100644
--- a/translations/ja-JP/content/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on.md
+++ b/translations/ja-JP/content/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on.md
@@ -24,13 +24,15 @@ If you can't access {% data variables.product.product_name %}, contact your loca
 
 {% endif %}
 
-{% ifversion fpt or ghec %}
+{% ifversion ghec %}
 
 {% data reusables.saml.dotcom-saml-explanation %} Organization owners can invite your personal account on {% data variables.product.prodname_dotcom %} to join their organization that uses SAML SSO, which allows you to contribute to the organization and retain your existing identity and contributions on {% data variables.product.prodname_dotcom %}.
 
 If you're a member of an {% data variables.enterprise.prodname_emu_enterprise %}, you will instead use a new account that is provisioned for you and controlled by your enterprise. {% data reusables.enterprise-accounts.emu-more-info-account %}
 
-When you access private resources within an organization that uses SAML SSO, {% data variables.product.prodname_dotcom %} will redirect you to the organization's SAML IdP to authenticate. After you successfully authenticate with your account on the IdP, the IdP redirects you back to {% data variables.product.prodname_dotcom %}, where you can access the organization's resources.
+When you attempt to access most resources within an organization that uses SAML SSO, {% data variables.product.prodname_dotcom %} will redirect you to the organization's SAML IdP to authenticate. After you successfully authenticate with your account on the IdP, the IdP redirects you back to {% data variables.product.prodname_dotcom %}, where you can access the organization's resources.
+
+{% data reusables.saml.resources-without-sso %}
 
 {% data reusables.saml.outside-collaborators-exemption %}
 
diff --git a/translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token.md b/translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token.md
index 88febb34fe..2a8409c383 100644
--- a/translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token.md
+++ b/translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token.md
@@ -1,6 +1,6 @@
 ---
 title: Creating a personal access token
-intro: You can create a {% data variables.product.pat_generic %} to use in place of a password with the command line or with the API.
+intro: 'You can create a {% data variables.product.pat_generic %} to use in place of a password with the command line or with the API.'
 redirect_from:
   - /articles/creating-an-oauth-token-for-command-line-use
   - /articles/creating-an-access-token-for-command-line-use
@@ -17,7 +17,7 @@ versions:
 topics:
   - Identity
   - Access management
-shortTitle: Create a {% data variables.product.pat_generic %}
+shortTitle: 'Create a {% data variables.product.pat_generic %}'
 ---
 
 {% warning %}
@@ -112,9 +112,9 @@ If you selected an organization as the resource owner and the organization requi
 {% ifversion pat-v2 %}1. In the left sidebar, under **{% octicon "key" aria-label="The key icon" %} {% data variables.product.pat_generic_caps %}s**, click **Tokens (classic)**.{% else %}{% data reusables.user-settings.personal_access_tokens %}{% endif %}
 {% ifversion pat-v2%}1. Select **Generate new token**, then click **Generate new token (classic)**.{% else %}{% data reusables.user-settings.generate_new_token %}{% endif %}
 5. Give your token a descriptive name.
-   ![Token description field](/assets/images/help/settings/token_description.png){% ifversion fpt or ghes > 3.2 or ghae or ghec %}
+   ![Token description field](/assets/images/help/settings/token_description.png)
 6. To give your token an expiration, select the **Expiration** drop-down menu, then click a default or use the calendar picker.
-   ![Token expiration field](/assets/images/help/settings/token_expiration.png){% endif %}
+   ![Token expiration field](/assets/images/help/settings/token_expiration.png)
 7. Select the scopes you'd like to grant this token. To use your token to access repositories from the command line, select **repo**. A token with no assigned scopes can only access public information. For more information, see "[Available scopes](/apps/building-oauth-apps/scopes-for-oauth-apps#available-scopes)".
    {% ifversion fpt or ghes or ghec %}
    ![Selecting token scopes](/assets/images/help/settings/token_scopes.gif)
@@ -143,5 +143,5 @@ Instead of manually entering your {% data variables.product.pat_generic %} for e
 
 ## Further reading
 
-- "[About authentication to GitHub](/github/authenticating-to-github/about-authentication-to-github)"{% ifversion fpt or ghae or ghes > 3.2 or ghec %}
-- "[Token expiration and revocation](/github/authenticating-to-github/keeping-your-account-and-data-secure/token-expiration-and-revocation)"{% endif %}
+- "[About authentication to GitHub](/github/authenticating-to-github/about-authentication-to-github)"
+- "[Token expiration and revocation](/github/authenticating-to-github/keeping-your-account-and-data-secure/token-expiration-and-revocation)"
diff --git a/translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/reviewing-your-security-log.md b/translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/reviewing-your-security-log.md
index 477a01b0a1..ca865d3bdf 100644
--- a/translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/reviewing-your-security-log.md
+++ b/translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/reviewing-your-security-log.md
@@ -109,7 +109,7 @@ An overview of some of the most common actions that are recorded as events in th
 | Action | Description
 |------------------|-------------------
 | `create` | Triggered when you [grant access to an {% data variables.product.prodname_oauth_app %}](/github/authenticating-to-github/keeping-your-account-and-data-secure/authorizing-oauth-apps).
-| `destroy` | Triggered when you [revoke an {% data variables.product.prodname_oauth_app %}'s access to your account](/articles/reviewing-your-authorized-integrations){% ifversion fpt or ghae or ghes > 3.2 or ghec %} and when [authorizations are revoked or expire](/github/authenticating-to-github/keeping-your-account-and-data-secure/token-expiration-and-revocation).{% else %}.{% endif %}
+| `destroy` | Triggered when you [revoke an {% data variables.product.prodname_oauth_app %}'s access to your account](/articles/reviewing-your-authorized-integrations) and when [authorizations are revoked or expire](/github/authenticating-to-github/keeping-your-account-and-data-secure/token-expiration-and-revocation).
 
 {% ifversion fpt or ghec %}
 
diff --git a/translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/token-expiration-and-revocation.md b/translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/token-expiration-and-revocation.md
index 877fedd33b..4b4832b39c 100644
--- a/translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/token-expiration-and-revocation.md
+++ b/translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/token-expiration-and-revocation.md
@@ -14,7 +14,7 @@ redirect_from:
   - /github/authenticating-to-github/keeping-your-account-and-data-secure/token-expiration-and-revocation
 ---
 
-When a token {% ifversion fpt or ghae or ghes > 3.2 or ghec %}has expired or {% endif %} has been revoked, it can no longer be used to authenticate Git and API requests. It is not possible to restore an expired or revoked token, you or the application will need to create a new token.
+When a token has expired or has been revoked, it can no longer be used to authenticate Git and API requests. It is not possible to restore an expired or revoked token, you or the application will need to create a new token.
 
 This article explains the possible reasons your {% data variables.product.product_name %} token might be revoked or expire.
 
@@ -24,11 +24,9 @@ This article explains the possible reasons your {% data variables.product.produc
 
 {% endnote %}
 
-{% ifversion fpt or ghae or ghes > 3.2 or ghec %}
 ## Token revoked after reaching its expiration date
 
 When you create a {% data variables.product.pat_generic %}, we recommend that you set an expiration for your token. Upon reaching your token's expiration date, the token is automatically revoked. For more information, see "[Creating a {% data variables.product.pat_generic %}](/github/authenticating-to-github/keeping-your-account-and-data-secure/creating-a-personal-access-token)."
-{% endif %}
 
 {% ifversion fpt or ghec %}
 ## Token revoked when pushed to a public repository or public gist
diff --git a/translations/ja-JP/content/authentication/managing-commit-signature-verification/signing-commits.md b/translations/ja-JP/content/authentication/managing-commit-signature-verification/signing-commits.md
index 203deb10cc..b522f9eec2 100644
--- a/translations/ja-JP/content/authentication/managing-commit-signature-verification/signing-commits.md
+++ b/translations/ja-JP/content/authentication/managing-commit-signature-verification/signing-commits.md
@@ -15,12 +15,12 @@ versions:
 topics:
   - Identity
   - Access management
-ms.openlocfilehash: 9b37417ab81bf51e39e41fcbed3a9b64cb4fe7bc
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: 8550393cc31571756099ac364698434f38b02cfa
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: ja-JP
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147653227'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148106750'
 ---
 {% data reusables.gpg.desktop-support-for-commit-signing %}
 
@@ -42,7 +42,7 @@ Git バージョン 2.0.0 以降で、ローカル リポジトリ用に既定
 
 1. ローカルブランチに変更をコミットする場合、 -S フラグをGitコミットコマンドに追加します。
   ```shell
-  $ git commit -S -m <em>"your commit message"</em>
+  $ git commit -S -m "YOUR_COMMIT_MESSAGE"
   # Creates a signed commit
   ```
 2. GPG を使用している場合は、コミットを作成した後、[GPG キーを生成](/articles/generating-a-new-gpg-key)したときに設定したパスフレーズを指定します。
diff --git a/translations/ja-JP/content/authentication/managing-commit-signature-verification/signing-tags.md b/translations/ja-JP/content/authentication/managing-commit-signature-verification/signing-tags.md
index 5ec53bdfe9..15f50e1148 100644
--- a/translations/ja-JP/content/authentication/managing-commit-signature-verification/signing-tags.md
+++ b/translations/ja-JP/content/authentication/managing-commit-signature-verification/signing-tags.md
@@ -14,23 +14,23 @@ versions:
 topics:
   - Identity
   - Access management
-ms.openlocfilehash: d93cfae4a6e128c2aef79ee1494fb66f30afcf1b
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: 22bdc1c5095a8fa82d2ac406a19dc633f8f44fc6
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: ja-JP
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147653363'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148106678'
 ---
 {% data reusables.gpg.desktop-support-for-commit-signing %}
 
 1. タグに署名するには、`git tag` コマンドに `-s` を追加します。
   ```shell
-  $ git tag -s <em>mytag</em>
+  $ git tag -s MYTAG
   # Creates a signed tag
   ```
 2. `git tag -v [tag-name]` を実行して署名されたタグを検証します。
   ```shell
-  $ git tag -v <em>mytag</em>
+  $ git tag -v MYTAG
   # Verifies the signed tag
   ```
 
diff --git a/translations/ja-JP/content/billing/index.md b/translations/ja-JP/content/billing/index.md
index 28a077d3de..eb7972bf01 100644
--- a/translations/ja-JP/content/billing/index.md
+++ b/translations/ja-JP/content/billing/index.md
@@ -54,11 +54,11 @@ children:
   - /managing-billing-for-github-marketplace-apps
   - /managing-billing-for-git-large-file-storage
   - /setting-up-paid-organizations-for-procurement-companies
-ms.openlocfilehash: 816bfb699135974a180ccf350aa04bc36dfbf25a
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: 977d170024ddec1d49f51723b654ee7171915e94
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: ja-JP
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147110899'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148109292'
 ---
 
diff --git a/translations/ja-JP/content/billing/managing-billing-for-github-codespaces/index.md b/translations/ja-JP/content/billing/managing-billing-for-github-codespaces/index.md
index b565c2a921..839d5dc496 100644
--- a/translations/ja-JP/content/billing/managing-billing-for-github-codespaces/index.md
+++ b/translations/ja-JP/content/billing/managing-billing-for-github-codespaces/index.md
@@ -11,3 +11,4 @@ children:
   - /viewing-your-github-codespaces-usage
   - /managing-spending-limits-for-github-codespaces
 ---
+
diff --git a/translations/ja-JP/content/billing/managing-billing-for-github-codespaces/viewing-your-github-codespaces-usage.md b/translations/ja-JP/content/billing/managing-billing-for-github-codespaces/viewing-your-github-codespaces-usage.md
index 9652fd43bd..68d34a6ab0 100644
--- a/translations/ja-JP/content/billing/managing-billing-for-github-codespaces/viewing-your-github-codespaces-usage.md
+++ b/translations/ja-JP/content/billing/managing-billing-for-github-codespaces/viewing-your-github-codespaces-usage.md
@@ -54,4 +54,4 @@ Enterprise owners and billing managers can view {% data variables.product.prodna
 
 ## Further reading
 
-- "[Listing the codespaces in your organization](/codespaces/managing-codespaces-for-your-organization/listing-the-codespaces-in-your-organization)"
\ No newline at end of file
+- "[Listing the codespaces in your organization](/codespaces/managing-codespaces-for-your-organization/listing-the-codespaces-in-your-organization)"
diff --git a/translations/ja-JP/content/billing/managing-billing-for-your-github-account/about-per-user-pricing.md b/translations/ja-JP/content/billing/managing-billing-for-your-github-account/about-per-user-pricing.md
index 5f06513eaa..57706ab231 100644
--- a/translations/ja-JP/content/billing/managing-billing-for-your-github-account/about-per-user-pricing.md
+++ b/translations/ja-JP/content/billing/managing-billing-for-your-github-account/about-per-user-pricing.md
@@ -72,9 +72,12 @@ In addition to licensed seats, your bill may include other charges, such as {% d
 - Enterprise owners who are a member or owner of at least one organization in the enterprise
 - Organization members, including owners
 - Outside collaborators on private or internal repositories owned by your organization, excluding forks
+- Dormant users
+
+If your enterprise does not use {% data variables.product.prodname_emus %}, you will also be billed for each of the following accounts:
+
 - Anyone with a pending invitation to become an organization owner or member
 - Anyone with a pending invitation to become an outside collaborator on private or internal repositories owned by your organization, excluding forks
-- Dormant users
 
 {% note %}
 
diff --git a/translations/ja-JP/content/code-security/adopting-github-advanced-security-at-scale/index.md b/translations/ja-JP/content/code-security/adopting-github-advanced-security-at-scale/index.md
index f099033153..f05b439418 100644
--- a/translations/ja-JP/content/code-security/adopting-github-advanced-security-at-scale/index.md
+++ b/translations/ja-JP/content/code-security/adopting-github-advanced-security-at-scale/index.md
@@ -18,11 +18,11 @@ children:
   - /phase-4-create-internal-documentation
   - /phase-5-rollout-and-scale-code-scanning
   - /phase-6-rollout-and-scale-secret-scanning
-ms.openlocfilehash: c5624ca33d347e1be1c7bfc9a687f1c06bb828ed
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: 5430d24ecf8979f5421c6f3fea9f10ad3f580e4c
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: ja-JP
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147145433'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148109721'
 ---
 
diff --git a/translations/ja-JP/content/code-security/adopting-github-advanced-security-at-scale/introduction-to-adopting-github-advanced-security-at-scale.md b/translations/ja-JP/content/code-security/adopting-github-advanced-security-at-scale/introduction-to-adopting-github-advanced-security-at-scale.md
index 5291f45737..ca20e5f4d1 100644
--- a/translations/ja-JP/content/code-security/adopting-github-advanced-security-at-scale/introduction-to-adopting-github-advanced-security-at-scale.md
+++ b/translations/ja-JP/content/code-security/adopting-github-advanced-security-at-scale/introduction-to-adopting-github-advanced-security-at-scale.md
@@ -14,12 +14,12 @@ redirect_from:
   - /admin/advanced-security/deploying-github-advanced-security-in-your-enterprise
   - /admin/code-security/managing-github-advanced-security-for-your-enterprise/deploying-github-advanced-security-in-your-enterprise
 miniTocMaxHeadingLevel: 2
-ms.openlocfilehash: 0993205a2f51262c0766062995caa1c2e2714742
-ms.sourcegitcommit: 76b840f45ba85fb79a7f0c1eb43bc663b3eadf2b
+ms.openlocfilehash: f42a461b3c53565725d6909680fa8e6a202c0439
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: ja-JP
-ms.lasthandoff: 09/12/2022
-ms.locfileid: '147145426'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148109716'
 ---
 ## これらの記事について
 
diff --git a/translations/ja-JP/content/code-security/adopting-github-advanced-security-at-scale/phase-1-align-on-your-rollout-strategy-and-goals.md b/translations/ja-JP/content/code-security/adopting-github-advanced-security-at-scale/phase-1-align-on-your-rollout-strategy-and-goals.md
index 1a0a6f1d2b..8d534fbf93 100644
--- a/translations/ja-JP/content/code-security/adopting-github-advanced-security-at-scale/phase-1-align-on-your-rollout-strategy-and-goals.md
+++ b/translations/ja-JP/content/code-security/adopting-github-advanced-security-at-scale/phase-1-align-on-your-rollout-strategy-and-goals.md
@@ -9,12 +9,12 @@ topics:
   - Advanced Security
 shortTitle: 1. Align on strategy
 miniTocMaxHeadingLevel: 3
-ms.openlocfilehash: 63154ac960e4b3a9d29f41e72cd925230838069c
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: b2677cf11c300ad657f9bd6b8862fb1f292c2fb7
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: ja-JP
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147145401'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148109709'
 ---
 {% note %}
 
diff --git a/translations/ja-JP/content/code-security/adopting-github-advanced-security-at-scale/phase-2-preparing-to-enable-at-scale.md b/translations/ja-JP/content/code-security/adopting-github-advanced-security-at-scale/phase-2-preparing-to-enable-at-scale.md
index 4c7306d6c1..ddf5131541 100644
--- a/translations/ja-JP/content/code-security/adopting-github-advanced-security-at-scale/phase-2-preparing-to-enable-at-scale.md
+++ b/translations/ja-JP/content/code-security/adopting-github-advanced-security-at-scale/phase-2-preparing-to-enable-at-scale.md
@@ -9,12 +9,12 @@ topics:
   - Advanced Security
 shortTitle: 2. Preparation
 miniTocMaxHeadingLevel: 3
-ms.openlocfilehash: a34711765e8beb6d57215c0c8fd16519e975539d
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: 79368897c125ff23541520a253a34a2aae8c7c27
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: ja-JP
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147145393'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148109715'
 ---
 {% note %}
 
diff --git a/translations/ja-JP/content/code-security/adopting-github-advanced-security-at-scale/phase-3-pilot-programs.md b/translations/ja-JP/content/code-security/adopting-github-advanced-security-at-scale/phase-3-pilot-programs.md
index 90864af28a..c5d40cda24 100644
--- a/translations/ja-JP/content/code-security/adopting-github-advanced-security-at-scale/phase-3-pilot-programs.md
+++ b/translations/ja-JP/content/code-security/adopting-github-advanced-security-at-scale/phase-3-pilot-programs.md
@@ -9,12 +9,12 @@ topics:
   - Advanced Security
 shortTitle: 3. Pilot programs
 miniTocMaxHeadingLevel: 3
-ms.openlocfilehash: 3df893158c402b9180260ddd1c82c96f62b84717
-ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d
+ms.openlocfilehash: d56427173580558a192d0709ae700cbd497e2935
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: ja-JP
-ms.lasthandoff: 09/11/2022
-ms.locfileid: '147145394'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148109109'
 ---
 {% note %}
 
diff --git a/translations/ja-JP/content/code-security/adopting-github-advanced-security-at-scale/phase-4-create-internal-documentation.md b/translations/ja-JP/content/code-security/adopting-github-advanced-security-at-scale/phase-4-create-internal-documentation.md
index 9da136bdc0..5e87bf25c1 100644
--- a/translations/ja-JP/content/code-security/adopting-github-advanced-security-at-scale/phase-4-create-internal-documentation.md
+++ b/translations/ja-JP/content/code-security/adopting-github-advanced-security-at-scale/phase-4-create-internal-documentation.md
@@ -9,12 +9,12 @@ topics:
   - Advanced Security
 shortTitle: 4. Create internal documentation
 miniTocMaxHeadingLevel: 3
-ms.openlocfilehash: e9852eacc95b98eca5358aafb9a9b13811888f15
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: caf35f06c3f836ea7532b7c5e9dfb419ba8c325b
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: ja-JP
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147145385'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148109108'
 ---
 {% note %}
 
diff --git a/translations/ja-JP/content/code-security/adopting-github-advanced-security-at-scale/phase-5-rollout-and-scale-code-scanning.md b/translations/ja-JP/content/code-security/adopting-github-advanced-security-at-scale/phase-5-rollout-and-scale-code-scanning.md
index 72e531fe38..28899aa01f 100644
--- a/translations/ja-JP/content/code-security/adopting-github-advanced-security-at-scale/phase-5-rollout-and-scale-code-scanning.md
+++ b/translations/ja-JP/content/code-security/adopting-github-advanced-security-at-scale/phase-5-rollout-and-scale-code-scanning.md
@@ -9,12 +9,12 @@ topics:
   - Advanced Security
 shortTitle: 5. Rollout code scanning
 miniTocMaxHeadingLevel: 3
-ms.openlocfilehash: 69c5a4e88c5490cbd7dcddca902426862047dff5
-ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.openlocfilehash: abbcdf4c1e4a231a568e8d8cd488877ebdf2fd9f
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: ja-JP
-ms.lasthandoff: 09/11/2022
-ms.locfileid: '147145386'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148109103'
 ---
 {% note %}
 
diff --git a/translations/ja-JP/content/code-security/adopting-github-advanced-security-at-scale/phase-6-rollout-and-scale-secret-scanning.md b/translations/ja-JP/content/code-security/adopting-github-advanced-security-at-scale/phase-6-rollout-and-scale-secret-scanning.md
index f764f3fee2..7cf84a8886 100644
--- a/translations/ja-JP/content/code-security/adopting-github-advanced-security-at-scale/phase-6-rollout-and-scale-secret-scanning.md
+++ b/translations/ja-JP/content/code-security/adopting-github-advanced-security-at-scale/phase-6-rollout-and-scale-secret-scanning.md
@@ -1,6 +1,6 @@
 ---
-title: 'フェーズ 6: secret scanning のロールアウトとスケーリング'
-intro: 'この最後のフェーズでは、{% data variables.product.prodname_secret_scanning %} のロールアウトについて重点的に取り上げます。 {% data variables.product.prodname_secret_scanning_caps %} は、必要な構成が少ないため、{% data variables.product.prodname_code_scanning %} よりも簡単にロールアウトできるツールですが、新しい結果と古い結果を処理するための戦略を策定することが重要です。'
+title: 'Phase 6: Rollout and scale secret scanning'
+intro: 'For the final phase, you will focus on the rollout of {% data variables.product.prodname_secret_scanning %}. {% data variables.product.prodname_secret_scanning_caps %} is a more straightforward tool to rollout than {% data variables.product.prodname_code_scanning %}, as it involves less configuration, but it''s critical to have a strategy for handling new and old results.'
 versions:
   ghes: '*'
   ghae: '*'
@@ -9,103 +9,98 @@ topics:
   - Advanced Security
 shortTitle: 6. Rollout secret scanning
 miniTocMaxHeadingLevel: 3
-ms.openlocfilehash: f116bd8aad09639fb3c2fad4aa85bfa9a8b3401d
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
-ms.translationtype: HT
-ms.contentlocale: ja-JP
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147650390'
 ---
+
 {% note %}
 
-この記事は、{% data variables.product.prodname_GH_advanced_security %} の大規模な導入に関するシリーズの一部です。 このシリーズの前の記事については、「[フェーズ 5: code scanning のロールアウトとスケーリング](/code-security/adopting-github-advanced-security-at-scale/phase-5-rollout-and-scale-code-scanning)」を参照してください。
+This article is part of a series on adopting {% data variables.product.prodname_GH_advanced_security %} at scale. For the previous article in this series, see "[Phase 5: Rollout and scale code scanning](/code-security/adopting-github-advanced-security-at-scale/phase-5-rollout-and-scale-code-scanning)."
 
 {% endnote %}
 
-Organization 内の個々のリポジトリまたはすべてのリポジトリに対して secret scanning を有効にすることができます。 詳しい情報については、「[リポジトリのセキュリティと分析設定を管理する](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-security-and-analysis-settings-for-your-repository)」または「[Organization のセキュリティと分析設定を管理する](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)」を参照してください。
+You can enable secret scanning for individual repositories or for all repositories in an organization. For more information, see "[Managing security and analysis settings for your repository](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-security-and-analysis-settings-for-your-repository)" or "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)."
 
-この記事では、Organization 内のすべてのリポジトリに対する {% data variables.product.prodname_secret_scanning %} の有効化に重点を置いてプロセスの概要について説明します。 この記事で説明する原則は、時間をずらして、個々のリポジトリに対して {% data variables.product.prodname_secret_scanning %} を有効にする場合でも適用できます。 
+This article explains a high-level process focusing on enabling {% data variables.product.prodname_secret_scanning %} for all repositories in an organization. The principles described in this article can still be applied even if you take a more staggered approach of enabling {% data variables.product.prodname_secret_scanning %} for individual repositories. 
 
-### 1. 新しくコミットされたシークレットに集中する
+### 1. Focus on newly committed secrets
 
-{% data variables.product.prodname_secret_scanning %} を有効にする場合、secret scanning によって検出された、新しくコミットされた資格情報の修復に集中する必要があります。 コミットされた資格情報のクリーンアップに集中すると、開発者は誤って新しい視覚情報をプッシュし続ける可能性があります。つまり、シークレットの合計数は、意図したとおりに減少せず、ほぼ同じレベルにとどまります。 現在のシークレットを取り消すことに集中する前に、新しい資格情報が漏洩するのを止めることが不可欠なのは、このためです。
+When you enable {% data variables.product.prodname_secret_scanning %}, you should focus on remediating any newly committed credentials detected by secret scanning. If you focus on cleaning up committed credentials, developers could continue to accidentally push new credentials, which means your total secret count will stay around the same level, not decrease as intended. This is why it is essential to stop new credentials being leaked before focusing on revoking any current secrets.
 
-新しくコミットされた資格情報に取り組むためのアプローチはいくつかありますが、その一例は次のとおりです。
+There are a few approaches for tackling newly committed credentials, but one example approach would be:
 
-1. **通知**: Webhook を使用して、新しいシークレット アラートが、可能な限り迅速に適切なチームに表示されるようにします。 Webhook は、シークレット アラートが作成または解決されるか、もう一度開かれたときに発生します。 その後、Webhook ペイロードを解析し、Slack、Teams、Splunk、メールなど、自分やチームが使用するツールと統合できます。 詳しい情報については、「[Webhook について](/developers/webhooks-and-events/webhooks/about-webhooks)」および「[Webhook イベントとペイロード](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#secret_scanning_alert)」を参照してください。
-2. **フォローアップ**: すべてのシークレットの種類に対して機能する高度な修復プロセスを作成します。 たとえば、シークレットをコミットした開発者とそのプロジェクトの技術リーダーに連絡し、シークレットを GitHub にコミットする危険性を強調し、検出されたシークレットの取り消しと更新を依頼することができます。
+1. **Notify**: Use webhooks to ensure that any new secret alerts are seen by the right teams as quickly as possible. A webhook fires when a secret alert is either created, resolved, or reopened. You can then parse the webhook payload, and integrate it into any tools you and your team use such Slack, Teams, Splunk, or email. For more information, see "[About webhooks](/developers/webhooks-and-events/webhooks/about-webhooks)" and "[Webhook events and payloads](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#secret_scanning_alert)."
+2. **Follow Up**: Create a high-level remediation process that works for all secret types. For example, you could contact the developer who committed the secret and their technical lead on that project, highlighting the dangers of committing secrets to GitHub, and asking the them to revoke, and update the detected secret.
 
   {% note %}
   
-  **注:** この手順を自動化できます。 数百のリポジトリを持つ大規模な Enterprise および Organization の場合、手動によるフォローアップを持続するのは不可能です。 最初の手順で定義した Webhook プロセスに自動化を取り入れることができます。 Webhook ペイロードには、漏洩したシークレットに関するリポジトリおよび Organization 情報が含まれます。 この情報を使って、リポジトリの現在のメンテナンス担当者に連絡し、責任者宛のメールやメッセージを作成したり、issue を開いたりすることができます。
+  **Note:** You can automate this step. For large enterprises and organizations with hundreds of repositories, manually following up is unsustainable. You could incorporate automation into the webhook process defined in the first step. The webhook payload contains repository and organization information about the leaked secret. Using this information, you can contact the current maintainers on the repository and create an email/message to the responsible people or open an issue.
   
   {% endnote %} 
-3. **教育**: シークレットをコミットした開発者に割り当てる内部トレーニング ドキュメントを作成します。 このトレーニング ドキュメントでは、シークレットをコミットすることによって生じるリスクを説明し、開発中のシークレットの安全な使用についてベスト プラクティス情報を指示します。 開発者が経験から学ばず、シークレットのコミットを続ける場合、エスカレーション プロセスを作成できますが、通常は教育する方が効果的です。
+3. **Educate**: Create an internal training document assigned to the developer who committed the secret. Within this training document, you can explain the risks created by committing secrets and direct them to your best practice information about using secrets securely in development. If the a developer doesn't learn from the experience and continues to commit secrets, you could create an escalation process, but education usually works well.
 
-漏洩した新しいシークレットについて最後の 2 つの手順を繰り返します。 このプロセスにより、開発者はコードで使用されるシークレットを安全に管理することに対して責任を負うようになり、新しくコミットされたシークレットの削減を測定できます。
+Repeat the last two steps for any new secrets leaked. This process encourages developers to take responsibility for managing the secrets used in their code securely, and allows you to measure the reduction in newly committed secrets.
 
 {% note %}
 
-**注:** より先進的な組織では、特定の種類のシークレットの自動修正を実行することが必要な場合があります。 [GitHub Secret Scanner Auto Remediator](https://github.com/NickLiffen/GSSAR) と呼ばれるオープンソース イニシアチブがあります。これを AWS、Azure、または GCP 環境にデプロイし、最も重要として定義した内容に基づいて特定の種類のシークレットを自動的に取り消すように調整できます。 これは、より自動化されたアプローチでコミットされる新しいシークレットに対応できる優れた方法でもあります。
+**Note:** More advanced organizations may want to perform auto-remediation of certain types of secrets. There is an open-source initiative called [GitHub Secret Scanner Auto Remediator](https://github.com/NickLiffen/GSSAR) which you can deploy into your AWS, Azure, or GCP environment and tailor to automatically revoke certain types of secrets based on what you define as the most critical. This is also an excellent way to react to new secrets being committed with a more automated approach.
 
 {% endnote %}
 
-### 2. 以前にコミットされたシークレットを最も重要なものから順に修復する
+### 2. Remediate previously committed secrets, starting with the most critical
 
-新しく公開されたシークレットを監視、通知、修復するプロセスを確立したら、{% data variables.product.prodname_GH_advanced_security %} が導入される前にコミットされたシークレットの作業を開始できます。
+After you have established a process to monitor, notify and remediate newly published secrets, you can start work on secrets committed before {% data variables.product.prodname_GH_advanced_security %} was introduced.
 
-最も重要なシークレットを定義する方法は、Organization のプロセスと統合によって異なります。 たとえば、企業は Slack を使用していない場合、Slack Incoming Webhook のシークレットについて心配しない可能性があります。 Organization にとって最も重要な資格情報の種類の上位 5 つに注目することから始めると便利な場合があります。
+How you define your most critical secrets will depend on your organization's processes and integrations. For example, a company likely isn’t worried about a Slack Incoming Webhook secret if they don’t use Slack. You may find it useful to start by focusing on the top five most critical credential types for your organization.
 
-シークレットの種類を決定したら、次の手順を実行できます。
+Once you have decided on the secret types, you can do the following:
 
-1. 各種類のシークレットを修復するためのプロセスを定義します。 多くの場合、実際の手順は、シークレットの種類によって大きく異なります。 ドキュメントまたは内部のナレッジ ベースに、シークレットの種類ごとのプロセスを書き留めます。
+1. Define a process for remediating each type of secret. The actual procedure for each secret type is often drastically different. Write down the process for each type of secret in a document or internal knowledge base.
   
   {% note %}
   
-  **注:** シークレットを取り消すためのプロセスを作成する場合、中央のチームではなく、リポジトリを保守しているチームにシークレットを取り消す責任を与えます。 GHAS の原則の 1 つは、特に、開発者がセキュリティ イシューを作成した場合、開発者がセキュリティの所有権を取得し、セキュリティ イシューを修正する責任を担うことです。
+  **Note:** When you create the process for revoking secrets, try and give the responsibility for revoking secrets to the team maintaining the repository instead of a central team. One of the principles of GHAS is developers taking ownership of security and having the responsibility of fixing security issues, especially if they have created them.
 
   {% endnote %}
 
-2. 資格情報を取り消すためにチームが従うプロセスを作成したら、シークレットの種類と、漏洩したシークレットに関連付けられているその他のメタデータに関する情報を照合して、新しいプロセスの伝達先を識別することができます。
+2. When you have created the process that teams will follow for revoking credentials, you can collate information about the types of secrets and other metadata associated with the leaked secrets so you can discern who to communicate the new process to.
   
   {% ifversion not ghae %}
   
-  この情報を収集するには、セキュリティの概要を使用できます。 セキュリティの概要の使用に関する詳しい情報については、「[セキュリティの概要でのアラートのフィルタリング](/code-security/security-overview/filtering-alerts-in-the-security-overview)」を参照してください。
+  You can use the security overview to collect this information. For more information about using the security overview, see "[Filtering alerts in the security overview](/code-security/security-overview/filtering-alerts-in-the-security-overview)."
   
   {% endif %}
   
-  収集する必要がある情報としては、次のものがあります。
+  Some information you may want to collect includes:
   
     - Organization
-    - リポジトリ
-    - シークレットの種類
-    - シークレット値
-    - 連絡先のリポジトリの保守管理者
+    - Repository
+    - Secret type
+    - Secret value
+    - Maintainers on repository to contact
   
   {% note %}
   
-  **注:** その種類の漏洩したシークレットが少ない場合は、UI を使用します。 数百ものシークレットが漏洩した場合は、API を使用して情報を収集します。 詳しい情報については、「[secret scanning REST API](/rest/reference/secret-scanning)」を参照してください。
+  **Note:** Use the UI if you have few secrets leaked of that type. If you have hundreds of leaked secrets, use the API to collect information. For more information, see "[Secret scanning REST API](/rest/reference/secret-scanning)."
     
   {% endnote %}
 
-3. 漏洩したシークレットに関する情報を収集したら、シークレットの各種類によって影響を受けるリポジトリを保守しているユーザーを対象とした通信計画を作成します。 電子メールまたはメッセージングを使用でき、影響を受けるリポジトリに GitHub イシューを作成することもできます。 これらのツールによって提供される API を使用して自動的に連絡を送信できる場合、これにより、複数のシークレットの種類にまたがって簡単にスケーリングできます。
+3. After you collect information about leaked secrets, create a targeted communication plan for the users who maintain the repositories affected by each secret type. You could use email, messaging, or even create GitHub issues in the affected repositories. If you can use APIs provided by these tools to send out the communications in an automated manner, this will make it easier for you to scale across multiple secret types.
 
-### 3. プログラムを拡張してより多くのシークレットの種類とカスタム パターンを含める
+### 3. Expand the program to include more secret types and custom patterns
 
-これで、5 つの最も重要なシークレットの種類を超えて、教育にさらに焦点を当てた、より包括的なリストに拡張できます。 対象としたさまざまなシークレットの種類について前の手順を繰り返し、以前にコミットされたシークレットを修正できます。
+You can now expand beyond the five most critical secret types into a more comprehensive list, with an additional focus on education. You can repeat the previous step, remediating previously committed secrets, for the different secret types you have targeted.
 
-また、初期のフェーズで照合されたより多くのカスタム パターンを含めて、さらに多くのパターンを送信するようにセキュリティ チームや開発者チームに促し、新しいシークレットの種類タイプが作成されたときに新しいパターンを送信するプロセスを確立することもできます。 詳細については、[シークレット スキャンのカスタム パターンの定義](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning)に関する記事を参照してください。
+You can also include more of the custom patterns collated in the earlier phases and invite security teams and developer teams to submit more patterns, establishing a process for submitting new patterns as new secret types are created. For more information, see "[Defining custom patterns for secret scanning](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning)."
 
 {% ifversion secret-scanning-push-protection %}
 
-また、secret scanning を使用してプッシュ保護を有効にすることもできます。 有効にすると、secret scanning により、信頼度の高いシークレットについてプッシュがチェックされ、ブロックされます。 詳細については、「[Protecting pushes with secret scanning (シークレット スキャンによるプッシュの保護)](/code-security/secret-scanning/protecting-pushes-with-secret-scanning#using-secret-scanning-as-a-push-protection-from-the-command-line)」を参照してください。
+You can also enable push protection with secret scanning. Once enabled, secret scanning checks pushes for high-confidence secrets and blocks the push. For more information, see "[Protecting pushes with secret scanning](/code-security/secret-scanning/protecting-pushes-with-secret-scanning#using-secret-scanning-as-a-push-protection-from-the-command-line)."
 
 {% endif %}
 
-他のシークレットの種類の修復プロセスを引き続き構築する際は、組織内の GitHub のすべての開発者と共有できるプロアクティブなトレーニング資料の作成を開始します。 この時点まで、焦点の多くはリアクティブでした。 焦点をプロアクティブに変えて、まず、開発者が GitHub に資格情報をプッシュしないように促すことは、優れたアイデアです。 これは複数の方法で実現できますが、リスクと理由を説明する短いドキュメントを作成することが出発点として適しています。
+As you continue to build your remediation processes for other secret types, start to create proactive training material that can be shared with all developers of GitHub in your organization. Until this point, a lot of the focus has been reactive. It is an excellent idea to shift focus to being proactive and encourage developers not to push credentials to GitHub in the first place. This can be achieved in multiple ways but creating a short document explaining the risks and reasons would be a great place to start.
 
 {% note %}
 
-これは、{% data variables.product.prodname_GH_advanced_security %} の大規模な導入に関するシリーズの最後の記事です。 ご質問がある場合、またはサポートが必要な場合は、「[{% data variables.product.prodname_GH_advanced_security %} の大規模な導入の概要](/code-security/adopting-github-advanced-security-at-scale/introduction-to-adopting-github-advanced-security-at-scale#github-support-and-professional-services)」にある {% data variables.contact.github_support %} と {% data variables.product.prodname_professional_services_team %} に関するセクションを参照してください。
+This is the final article of a series on adopting {% data variables.product.prodname_GH_advanced_security %} at scale. If you have questions or need support, see the section on {% data variables.contact.github_support %} and {% data variables.product.prodname_professional_services_team %} in "[Introduction to adopting {% data variables.product.prodname_GH_advanced_security %} at scale](/code-security/adopting-github-advanced-security-at-scale/introduction-to-adopting-github-advanced-security-at-scale#github-support-and-professional-services)."
 
 {% endnote %}
diff --git a/translations/ja-JP/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning.md b/translations/ja-JP/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning.md
index e7a4e2b032..bfb8740fb1 100644
--- a/translations/ja-JP/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning.md
+++ b/translations/ja-JP/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning.md
@@ -73,9 +73,7 @@ By default, the {% data variables.product.prodname_codeql_workflow %} uses the `
 
 If you scan on push, then the results appear in the **Security** tab for your repository. For more information, see "[Managing code scanning alerts for your repository](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository#viewing-the-alerts-for-a-repository)."
 
-{% ifversion fpt or ghes > 3.2 or ghae or ghec %}
 Additionally, when an `on:push` scan returns results that can be mapped to an open pull request, these alerts will automatically appear on the pull request in the same places as other pull request alerts. The alerts are identified by comparing the existing analysis of the head of the branch to the analysis for the target branch. For more information on {% data variables.product.prodname_code_scanning %} alerts in pull requests, see "[Triaging {% data variables.product.prodname_code_scanning %} alerts in pull requests](/code-security/secure-coding/triaging-code-scanning-alerts-in-pull-requests)."
-{% endif %}
 
 ### Scanning pull requests
 
@@ -85,9 +83,7 @@ For more information about the `pull_request` event, see "[Events that trigger w
 
 If you scan pull requests, then the results appear as alerts in a pull request check. For more information, see "[Triaging code scanning alerts in pull requests](/code-security/secure-coding/triaging-code-scanning-alerts-in-pull-requests)."
 
-{% ifversion fpt or ghes > 3.2 or ghae or ghec %}
- Using the `pull_request` trigger, configured to scan the pull request's merge commit rather than the head commit, will produce more efficient and accurate results than scanning the head of the branch on each push. However, if you use a CI/CD system that cannot be configured to trigger on pull requests, you can still use the `on:push` trigger and {% data variables.product.prodname_code_scanning %} will map the results to open pull requests on the branch and add the alerts as annotations on the pull request. For more information, see "[Scanning on push](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning#scanning-on-push)."
-{% endif %}
+Using the `pull_request` trigger, configured to scan the pull request's merge commit rather than the head commit, will produce more efficient and accurate results than scanning the head of the branch on each push. However, if you use a CI/CD system that cannot be configured to trigger on pull requests, you can still use the `on:push` trigger and {% data variables.product.prodname_code_scanning %} will map the results to open pull requests on the branch and add the alerts as annotations on the pull request. For more information, see "[Scanning on push](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning#scanning-on-push)."
 
 ### Defining the severities causing pull request check failure
 
diff --git a/translations/ja-JP/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-the-codeql-workflow-for-compiled-languages.md b/translations/ja-JP/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-the-codeql-workflow-for-compiled-languages.md
index 9135c91197..1220575d5d 100644
--- a/translations/ja-JP/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-the-codeql-workflow-for-compiled-languages.md
+++ b/translations/ja-JP/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-the-codeql-workflow-for-compiled-languages.md
@@ -41,7 +41,7 @@ For general information about configuring {% data variables.product.prodname_cod
 ##  About autobuild for {% data variables.product.prodname_codeql %}
 
 {% data variables.product.prodname_code_scanning_capc %} works by running queries against one or more databases. Each database contains a representation of all of the code in a single language in your repository.   
-For the compiled languages C/C++, C#, and Java, the process of populating this database involves building the code and extracting data. {% data reusables.code-scanning.analyze-go %}
+For the compiled languages C/C++, C#,{% ifversion codeql-go-autobuild %} Go,{% endif %} and Java, the process of populating this database involves building the code and extracting data. {% data reusables.code-scanning.analyze-go %}
 
 {% data reusables.code-scanning.autobuild-compiled-languages %}
 
@@ -90,6 +90,20 @@ The `autobuild` process attempts to autodetect a suitable build method for C# us
 If `autobuild` detects multiple solution or project files at the same (shortest) depth from the top level directory, it will attempt to build all of them.
 3. Invoke a script that looks like a build script—_build_ and _build.sh_ (in that order, for Linux) or _build.bat_, _build.cmd_, _and build.exe_ (in that order, for Windows).
 
+### Go
+
+| Supported system type | System name |
+|----|----|
+| Operating system | Windows, macOS, and Linux |
+| Build system | Go modules, `dep` and Glide, as well as build scripts including Makefiles and Ninja scripts |
+
+The `autobuild` process attempts to autodetect a suitable way to install the dependencies needed by a Go repository before extracting all `.go` files:
+
+1. Invoke `make`, `ninja`, `./build` or `./build.sh` (in that order) until one of these commands succeeds and a subsequent `go list ./...` also succeeds, indicating that the needed dependencies have been installed.
+2. If none of those commands succeeded, look for `go.mod`, `Gopkg.toml` or `glide.yaml`, and run `go get` (unless vendoring is in use), `dep ensure -v` or `glide install` respectively to try to install dependencies.
+3. Finally, if configurations files for these dependency managers are not found, rearrange the repository directory structure suitable for addition to `GOPATH`, and use `go get` to install dependencies. The directory structure reverts to normal after extraction completes.
+4. Extract all Go code in the repository, similar to running `go build ./...`.
+
 ### Java
 
 | Supported system type | System name |
@@ -107,12 +121,12 @@ The `autobuild` process tries to determine the build system for Java codebases b
 
 {% data reusables.code-scanning.autobuild-add-build-steps %} For information on how to edit the workflow file, see  "[Configuring {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/configuring-code-scanning#editing-a-code-scanning-workflow)."
 
-After removing the `autobuild` step, uncomment the `run` step and add build commands that are suitable for your repository. The workflow `run` step runs command-line programs using the operating system's shell. You can modify these commands and add more commands to customize the build process. 
+After removing the `autobuild` step, uncomment the `run` step and add build commands that are suitable for your repository. The workflow `run` step runs command-line programs using the operating system's shell. You can modify these commands and add more commands to customize the build process.
 
 ``` yaml
 - run: |
-  make bootstrap
-  make release
+    make bootstrap
+    make release
 ```
 
 For more information about the `run` keyword, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepsrun)."
diff --git a/translations/ja-JP/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository.md b/translations/ja-JP/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository.md
index 56ea5e3cc3..d4e421b540 100644
--- a/translations/ja-JP/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository.md
+++ b/translations/ja-JP/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository.md
@@ -153,12 +153,9 @@ The names of the {% data variables.product.prodname_code_scanning %} analysis ch
 
 When the {% data variables.product.prodname_code_scanning %} jobs complete, {% data variables.product.prodname_dotcom %} works out whether any alerts were added by the pull request and adds the "{% data variables.product.prodname_code_scanning_capc %} results / TOOL NAME" entry to the list of checks. After {% data variables.product.prodname_code_scanning %} has been performed at least once, you can click **Details** to view the results of the analysis.
 
-{% ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4  %}
-<!--Troubleshooting section no longer relevant-->
-{% elsif ghes < 3.5 or ghae %}
-If you used a pull request to add {% data variables.product.prodname_code_scanning %} to the repository, you will initially see {% ifversion ghes > 3.2 or ghae %}an "Analysis not found"{% elsif ghes = 3.2 %}a "Missing analysis"{% endif %} message when you click **Details** on the "{% data variables.product.prodname_code_scanning_capc %} results / TOOL NAME" check.
+{% ifversion ghes < 3.5 or ghae %}
+If you used a pull request to add {% data variables.product.prodname_code_scanning %} to the repository, you will initially see an "Analysis not found" message when you click **Details** on the "{% data variables.product.prodname_code_scanning_capc %} results / TOOL NAME" check.
 
-{% ifversion ghes > 3.2 or ghae %}
   ![Analysis not found for commit message](/assets/images/enterprise/3.4/repository/code-scanning-analysis-not-found.png)
 
 The table lists one or more categories. Each category relates to specific analyses, for the same tool and commit, performed on a different language or a different part of the code. For each category, the table shows the two analyses that {% data variables.product.prodname_code_scanning %} attempted to compare to determine which alerts were introduced or fixed in the pull request.
@@ -167,13 +164,8 @@ For example, in the screenshot above, {% data variables.product.prodname_code_sc
 
 ### Reasons for the "Analysis not found" message
 
-{% elsif ghes = 3.2 %}
-  ![Missing analysis for commit message](/assets/images/enterprise/3.2/repository/code-scanning-missing-analysis.png)
 
-### Reasons for the "Missing analysis" message
-{% endif %}
-
-After {% data variables.product.prodname_code_scanning %} has analyzed the code in a pull request, it needs to compare the analysis of the topic branch (the branch you used to create the pull request) with the analysis of the base branch (the branch into which you want to merge the pull request). This allows {% data variables.product.prodname_code_scanning %} to compute which alerts are newly introduced by the pull request, which alerts were already present in the base branch, and whether any existing alerts are fixed by the changes in the pull request. Initially, if you use a pull request to add {% data variables.product.prodname_code_scanning %} to a repository, the base branch has not yet been analyzed, so it's not possible to compute these details. In this case, when you click through from the results check on the pull request you will see the {% ifversion ghes > 3.2 or ghae %}"Analysis not found"{% elsif ghes = 3.2 %}"Missing analysis for base commit SHA-HASH"{% endif %} message.
+After {% data variables.product.prodname_code_scanning %} has analyzed the code in a pull request, it needs to compare the analysis of the topic branch (the branch you used to create the pull request) with the analysis of the base branch (the branch into which you want to merge the pull request). This allows {% data variables.product.prodname_code_scanning %} to compute which alerts are newly introduced by the pull request, which alerts were already present in the base branch, and whether any existing alerts are fixed by the changes in the pull request. Initially, if you use a pull request to add {% data variables.product.prodname_code_scanning %} to a repository, the base branch has not yet been analyzed, so it's not possible to compute these details. In this case, when you click through from the results check on the pull request you will see the "Analysis not found" message.
 
 There are other situations where there may be no analysis for the latest commit to the base branch for a pull request. These include:
 
diff --git a/translations/ja-JP/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/triaging-code-scanning-alerts-in-pull-requests.md b/translations/ja-JP/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/triaging-code-scanning-alerts-in-pull-requests.md
index ec6da4e48a..acf7f647a3 100644
--- a/translations/ja-JP/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/triaging-code-scanning-alerts-in-pull-requests.md
+++ b/translations/ja-JP/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/triaging-code-scanning-alerts-in-pull-requests.md
@@ -35,9 +35,7 @@ In repositories where {% data variables.product.prodname_code_scanning %} is con
 
 If you have write permission for the repository, you can see any existing {% data variables.product.prodname_code_scanning %} alerts on the **Security** tab. For information about repository alerts, see "[Managing {% data variables.product.prodname_code_scanning %} alerts for your repository](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository)."
 
-{% ifversion fpt or ghes > 3.2 or ghae or ghec %}
 In repositories where {% data variables.product.prodname_code_scanning %} is configured to scan each time code is pushed, {% data variables.product.prodname_code_scanning %} will also map the results to any open pull requests and add the alerts as annotations in the same places as other pull request checks. For more information, see "[Scanning on push](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning#scanning-on-push)."
-{% endif %}
 
 If your pull request targets a protected branch that uses {% data variables.product.prodname_code_scanning %}, and the repository owner has configured required status checks, then the "{% data variables.product.prodname_code_scanning_capc %} results" check must pass before you can merge the pull request. For more information, see "[About protected branches](/github/administering-a-repository/about-protected-branches#require-status-checks-before-merging)."
 
@@ -49,10 +47,9 @@ There are many options for configuring {% data variables.product.prodname_code_s
 
 For all configurations of {% data variables.product.prodname_code_scanning %}, the check that contains the results of {% data variables.product.prodname_code_scanning %} is: **{% data variables.product.prodname_code_scanning_capc %} results**. The results for each analysis tool used are shown separately. Any new alerts caused by changes in the pull request are shown as annotations. 
 
-{% ifversion fpt or ghes > 3.2 or ghae or ghec %} To see the full set of alerts for the analyzed branch, click **View all branch alerts**. This opens the full alert view where you can filter all the alerts on the branch by type, severity, tag, etc. For more information, see "[Managing code scanning alerts for your repository](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository#filtering-and-searching-for-code-scanning-alerts)."
+To see the full set of alerts for the analyzed branch, click **View all branch alerts**. This opens the full alert view where you can filter all the alerts on the branch by type, severity, tag, etc. For more information, see "[Managing code scanning alerts for your repository](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository#filtering-and-searching-for-code-scanning-alerts)."
 
 ![{% data variables.product.prodname_code_scanning_capc %} results check on a pull request](/assets/images/help/repository/code-scanning-results-check.png)
-{% endif %}
 
 ### {% data variables.product.prodname_code_scanning_capc %} results check failures
 
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 658d44b582..11529ccbee 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
@@ -49,7 +49,7 @@ To produce more detailed logging output, you can enable step debug logging. For
 ## Creating {% data variables.product.prodname_codeql %} debugging artifacts
 
 You can obtain artifacts to help you debug {% data variables.product.prodname_codeql %}.
-The debug artifacts will be uploaded to the workflow run as an artifact named `debug-artifacts`. The data contains the {% data variables.product.prodname_codeql %} logs, {% data variables.product.prodname_codeql %} database(s), and any SARIF file(s) produced by the workflow. 
+The debug artifacts will be uploaded to the workflow run as an artifact named `debug-artifacts`. The data contains the {% data variables.product.prodname_codeql %} logs, {% data variables.product.prodname_codeql %} database(s), and any SARIF file(s) produced by the workflow.
 
 These artifacts will help you debug problems with {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %}. If you contact GitHub support, they might ask for this data.
 
@@ -59,11 +59,10 @@ These artifacts will help you debug problems with {% data variables.product.prod
 
 ### Creating {% data variables.product.prodname_codeql %} debugging artifacts by re-running jobs with debug logging enabled
 
-You can create {% data variables.product.prodname_codeql %} debugging artifacts by enabling debug logging and re-running the jobs. For more information about re-running {% data variables.product.prodname_actions %} workflows and jobs, see "[Re-running workflows and jobs](/actions/managing-workflow-runs/re-running-workflows-and-jobs)." 
+You can create {% data variables.product.prodname_codeql %} debugging artifacts by enabling debug logging and re-running the jobs. For more information about re-running {% data variables.product.prodname_actions %} workflows and jobs, see "[Re-running workflows and jobs](/actions/managing-workflow-runs/re-running-workflows-and-jobs)."
 
 You need to ensure that you select **Enable debug logging** . This option enables runner diagnostic logging and step debug logging for the run. You'll then be able to download `debug-artifacts` to investigate further. You do not need to modify the workflow file when creating {% data variables.product.prodname_codeql %} debugging artifacts by re-running jobs.
 
-
 {% endif %}
 
 {% ifversion fpt or ghec or ghes > 3.3 or ghae > 3.3 %}
@@ -87,7 +86,7 @@ If an automatic build of code for a compiled language within your project fails,
 
 - Remove the `autobuild` step from your {% data variables.product.prodname_code_scanning %} workflow and add specific build steps. For information about editing the workflow, see  "[Configuring {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/configuring-code-scanning#editing-a-code-scanning-workflow)." For more information about replacing the `autobuild` step, see "[Configuring the {% data variables.product.prodname_codeql %} workflow for compiled languages](/code-security/secure-coding/configuring-the-codeql-workflow-for-compiled-languages#adding-build-steps-for-a-compiled-language)."
 
-- If your workflow doesn't explicitly specify the languages to analyze, {% data variables.product.prodname_codeql %} implicitly detects the supported languages in your code base. In this configuration, out of the compiled languages C/C++, C#, and Java, {% data variables.product.prodname_codeql %} only analyzes the language with the most source files. Edit the workflow and add a matrix specifying the languages you want to analyze. The default CodeQL analysis workflow uses such a matrix.
+- If your workflow doesn't explicitly specify the languages to analyze, {% data variables.product.prodname_codeql %} implicitly detects the supported languages in your code base. In this configuration, out of the compiled languages C/C++, C#,{% ifversion codeql-go-autobuild %} Go,{% endif %} and Java, {% data variables.product.prodname_codeql %} only analyzes the language with the most source files. Edit the workflow and add a matrix specifying the languages you want to analyze. The default CodeQL analysis workflow uses such a matrix.
 
   The following extracts from a workflow show how you can use a matrix within the job strategy to specify languages, and then reference each language within the "Initialize {% data variables.product.prodname_codeql %}" step:
 
@@ -131,14 +130,15 @@ If your workflow fails with an error `No source code was seen during the build`
   ```
 
    For more information, see the workflow extract in "[Automatic build for a compiled language fails](#automatic-build-for-a-compiled-language-fails)" above.
-1. Your {% data variables.product.prodname_code_scanning %} workflow is analyzing a compiled language (C, C++, C#, or Java), but the code was not compiled. By default, the {% data variables.product.prodname_codeql %} analysis workflow contains an `autobuild` step, however, this step represents a best effort process, and may not succeed in building your code, depending on your specific build environment. Compilation may also fail if you have removed the `autobuild` step and did not include build steps manually.  For more information about specifying build steps, see "[Configuring the {% data variables.product.prodname_codeql %} workflow for compiled languages](/code-security/secure-coding/configuring-the-codeql-workflow-for-compiled-languages#adding-build-steps-for-a-compiled-language)."
-1. Your workflow is analyzing a compiled language (C, C++, C#, or Java), but portions of your build are cached to improve performance (most likely to occur with build systems like Gradle or Bazel). Since {% data variables.product.prodname_codeql %} observes the activity of the compiler to understand the data flows in a repository, {% data variables.product.prodname_codeql %} requires a complete build to take place in order to perform analysis. 
-1. Your workflow is analyzing a compiled language (C, C++, C#, or Java), but compilation does not occur between the `init` and `analyze` steps in the workflow. {% data variables.product.prodname_codeql %} requires that your build happens in between these two steps in order to observe the activity of the compiler and perform analysis. 
-1. Your compiled code (in C, C++, C#, or Java) was compiled successfully, but {% data variables.product.prodname_codeql %} was unable to detect the compiler invocations. The most common causes are:
 
-   * Running your build process in a separate container to {% data variables.product.prodname_codeql %}. For more information, see "[Running CodeQL code scanning in a container](/code-security/secure-coding/running-codeql-code-scanning-in-a-container)."
-   * Building using a distributed build system external to GitHub Actions, using a daemon process.
-   * {% data variables.product.prodname_codeql %} isn't aware of the specific compiler you are using.
+1. Your {% data variables.product.prodname_code_scanning %} workflow is analyzing a compiled language (C, C++, C#,{% ifversion codeql-go-autobuild %} Go,{% endif %} or Java), but the code was not compiled. By default, the {% data variables.product.prodname_codeql %} analysis workflow contains an `autobuild` step, however, this step represents a best effort process, and may not succeed in building your code, depending on your specific build environment. Compilation may also fail if you have removed the `autobuild` step and did not include build steps manually.  For more information about specifying build steps, see "[Configuring the {% data variables.product.prodname_codeql %} workflow for compiled languages](/code-security/secure-coding/configuring-the-codeql-workflow-for-compiled-languages#adding-build-steps-for-a-compiled-language)."
+1. Your workflow is analyzing a compiled language (C, C++, C#,{% ifversion codeql-go-autobuild %} Go,{% endif %} or Java), but portions of your build are cached to improve performance (most likely to occur with build systems like Gradle or Bazel). Since {% data variables.product.prodname_codeql %} observes the activity of the compiler to understand the data flows in a repository, {% data variables.product.prodname_codeql %} requires a complete build to take place in order to perform analysis.
+1. Your workflow is analyzing a compiled language (C, C++, C#,{% ifversion codeql-go-autobuild %} Go,{% endif %} or Java), but compilation does not occur between the `init` and `analyze` steps in the workflow. {% data variables.product.prodname_codeql %} requires that your build happens in between these two steps in order to observe the activity of the compiler and perform analysis.
+1. Your compiled code (in C, C++, C#,{% ifversion codeql-go-autobuild %} Go,{% endif %} or Java) was compiled successfully, but {% data variables.product.prodname_codeql %} was unable to detect the compiler invocations. The most common causes are:
+
+   - Running your build process in a separate container to {% data variables.product.prodname_codeql %}. For more information, see "[Running CodeQL code scanning in a container](/code-security/secure-coding/running-codeql-code-scanning-in-a-container)."
+   - Building using a distributed build system external to GitHub Actions, using a daemon process.
+   - {% data variables.product.prodname_codeql %} isn't aware of the specific compiler you are using.
 
   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.
   
@@ -151,9 +151,10 @@ If your workflow fails with an error `No source code was seen during the build`
 
   If you encounter another problem with your specific compiler or configuration, contact {% data variables.contact.contact_support %}.
 
-For more information about specifying build steps, see "[Configuring the {% data variables.product.prodname_codeql %} workflow for compiled languages](/code-security/secure-coding/configuring-the-codeql-workflow-for-compiled-languages#adding-build-steps-for-a-compiled-language)." 
+For more information about specifying build steps, see "[Configuring the {% data variables.product.prodname_codeql %} workflow for compiled languages](/code-security/secure-coding/configuring-the-codeql-workflow-for-compiled-languages#adding-build-steps-for-a-compiled-language)."
 
 {% ifversion fpt or ghes > 3.1  or ghae or ghec %}
+
 ## Lines of code scanned are lower than expected
 
 For compiled languages like C/C++, C#, Go, and Java, {% data variables.product.prodname_codeql %} only scans files that are built during the analysis. Therefore the number of lines of code scanned will be lower than expected if some of the source code isn't compiled correctly. This can happen for several reasons:
@@ -163,12 +164,13 @@ For compiled languages like C/C++, C#, Go, and Java, {% data variables.product.p
 
 If your {% data variables.product.prodname_codeql %} analysis scans fewer lines of code than expected, there are several approaches you can try to make sure all the necessary source files are compiled.
 
-### Replace the `autobuild` step 
+### Replace the `autobuild` step
 
 Replace the `autobuild` step with the same build commands you would use in production. This makes sure that {% data variables.product.prodname_codeql %} knows exactly how to compile all of the source files you want to scan.
-For more information, see "[Configuring the {% data variables.product.prodname_codeql %} workflow for compiled languages](/code-security/secure-coding/configuring-the-codeql-workflow-for-compiled-languages#adding-build-steps-for-a-compiled-language)." 
+For more information, see "[Configuring the {% data variables.product.prodname_codeql %} workflow for compiled languages](/code-security/secure-coding/configuring-the-codeql-workflow-for-compiled-languages#adding-build-steps-for-a-compiled-language)."
 
 ### Inspect the copy of the source files in the {% data variables.product.prodname_codeql %} database
+
 You may be able to understand why some source files haven't been analyzed by inspecting the copy of the source code included with the {% data variables.product.prodname_codeql %} database. To obtain the database from your Actions workflow, modify the `init` step of your {% data variables.product.prodname_codeql %} workflow file and set `debug: true`.
 
 ```yaml
@@ -188,12 +190,13 @@ The artifact will contain an archived copy of the source files scanned by {% dat
 
 ## Extraction errors in the database
 
-The {% data variables.product.prodname_codeql %} team constantly works on critical extraction errors to make sure that all source files can be scanned. However, the {% data variables.product.prodname_codeql %} extractors do occasionally generate errors during database creation. {% data variables.product.prodname_codeql %} provides information about extraction errors and warnings generated during database creation in a log file. 
+The {% data variables.product.prodname_codeql %} team constantly works on critical extraction errors to make sure that all source files can be scanned. However, the {% data variables.product.prodname_codeql %} extractors do occasionally generate errors during database creation. {% data variables.product.prodname_codeql %} provides information about extraction errors and warnings generated during database creation in a log file.
 The extraction diagnostics information gives an indication of overall database health. Most extractor errors do not significantly impact the analysis. A small number of extractor errors is healthy and typically indicates a good state of analysis.
 
 However, if you see extractor errors in the overwhelming majority of files that were compiled during database creation, you should look into the errors in more detail to try to understand why some source files weren't extracted properly.
 
 {% else %}
+
 ## Portions of my repository were not analyzed using `autobuild`
 
 The {% data variables.product.prodname_codeql %} `autobuild` feature uses heuristics to build the code in a repository, however, sometimes this approach results in incomplete analysis of a repository. For example, when multiple `build.sh` commands exist in a single repository, the analysis may not complete since the `autobuild` step will only execute one of the commands. The solution is to replace the `autobuild` step with build steps which build all of the source code which you wish to analyze. For more information, see "[Configuring the {% data variables.product.prodname_codeql %} workflow for compiled languages](/code-security/secure-coding/configuring-the-codeql-workflow-for-compiled-languages#adding-build-steps-for-a-compiled-language)."
@@ -201,7 +204,7 @@ The {% data variables.product.prodname_codeql %} `autobuild` feature uses heuris
 
 ## The build takes too long
 
-If your build with {% data variables.product.prodname_codeql %} analysis takes too long to run, there are several approaches you can try to reduce the build time. 
+If your build with {% data variables.product.prodname_codeql %} analysis takes too long to run, there are several approaches you can try to reduce the build time.
 
 ### Increase the memory or cores
 
@@ -225,7 +228,7 @@ If your analysis is still too slow to be run during `push` or `pull_request` eve
 
 ### Check which query suites the workflow runs
 
-By default, there are three main query suites available for each language. If you have optimized the CodeQL database build and the process is still too long, you could reduce the number of queries you run. The default query suite is run automatically; it contains the fastest security queries with the lowest rates of false positive results. 
+By default, there are three main query suites available for each language. If you have optimized the CodeQL database build and the process is still too long, you could reduce the number of queries you run. The default query suite is run automatically; it contains the fastest security queries with the lowest rates of false positive results.
 
 You may be running extra queries or query suites in addition to the default queries. Check whether the workflow defines an additional query suite or additional queries to run using the `queries` element. You can experiment with disabling the additional query suite or queries. For more information, see "[Configuring {% data variables.product.prodname_code_scanning %}](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning#using-queries-in-ql-packs)."
 
@@ -237,6 +240,7 @@ You may be running extra queries or query suites in addition to the default quer
 {% endif %}
 
 {% ifversion fpt or ghec %}
+
 ## Results differ between analysis platforms
 
 If you are analyzing code written in Python, you may see different results depending on whether you run the {% data variables.product.prodname_codeql_workflow %} on Linux, macOS, or Windows.
@@ -256,11 +260,13 @@ On very large projects, {% data variables.product.prodname_codeql %} may run out
 {% else %}If you encounter this issue, try increasing the memory on the runner.{% endif %}
 
 {% ifversion fpt or ghec %}
+
 ## Error: 403 "Resource not accessible by integration" when using {% data variables.product.prodname_dependabot %}
 
 {% data variables.product.prodname_dependabot %} is considered untrusted when it triggers a workflow run, and the workflow will run with read-only scopes. Uploading {% data variables.product.prodname_code_scanning %} results for a branch usually requires the `security_events: write` scope. However, {% data variables.product.prodname_code_scanning %} always allows the uploading of results when the `pull_request` event triggers the action run. This is why, for {% data variables.product.prodname_dependabot %} branches, we recommend you use the `pull_request` event instead of the `push` event.
 
 A simple approach is to run on pushes to the default branch and any other important long-running branches, as well as pull requests opened against this set of branches:
+
 ```yaml
 on:
   push:
@@ -270,7 +276,9 @@ on:
     branches:
       - main
 ```
+
 An alternative approach is to run on all pushes except for {% data variables.product.prodname_dependabot %} branches:
+
 ```yaml
 on:
   push:
@@ -282,6 +290,7 @@ on:
 ### Analysis still failing on the default branch
 
 If the {% data variables.product.prodname_codeql_workflow %} still fails on a commit made on the default branch, you need to check:
+
 - whether {% data variables.product.prodname_dependabot %} authored the commit
 - whether the pull request that includes the commit has been merged using `@dependabot squash and merge`
 
diff --git a/translations/ja-JP/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/about-codeql-code-scanning-in-your-ci-system.md b/translations/ja-JP/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/about-codeql-code-scanning-in-your-ci-system.md
index 370ce281d8..6390bcc50e 100644
--- a/translations/ja-JP/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/about-codeql-code-scanning-in-your-ci-system.md
+++ b/translations/ja-JP/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/about-codeql-code-scanning-in-your-ci-system.md
@@ -49,21 +49,12 @@ redirect_from:
 Use the {% data variables.product.prodname_codeql_cli %} to analyze:
 
 - Dynamic languages, for example, JavaScript and Python.
-- Compiled languages, for example, C/C++, C# and Java.
+- Compiled languages, for example, C/C++, C#,{% ifversion codeql-go-autobuild %} Go,{% endif %} and Java.
 - Codebases written in a mixture of languages.
 
 For more information, see "[Installing {% data variables.product.prodname_codeql_cli %} in your CI system](/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system/installing-codeql-cli-in-your-ci-system)."
 
 {% data reusables.code-scanning.licensing-note %}
 
-{% ifversion ghes = 3.2 %}
-<!-- Content for GHES 3.2 only. CodeQL CLI 2.6.2, which introduces full feature parity between CodeQL CLI and CodeQL runner, is officially recommended for GHES 3.0+ -->
-
-Since version 2.6.3, the {% data variables.product.prodname_codeql_cli %} has had full feature parity with the {% data variables.product.prodname_codeql_runner %}.
-
-{% data reusables.code-scanning.deprecation-codeql-runner %}
-
-{% endif %}
 
 <!--Content for GHES 3.1 only. Both CodeQL CLI and CodeQL runner are available -->
-
diff --git a/translations/ja-JP/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-cli-in-your-ci-system.md b/translations/ja-JP/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-cli-in-your-ci-system.md
index 1a0e74ad50..09f10cd3f0 100644
--- a/translations/ja-JP/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-cli-in-your-ci-system.md
+++ b/translations/ja-JP/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-cli-in-your-ci-system.md
@@ -78,8 +78,8 @@ You can display the command-line help for any command using the <nobr>`--help`</
 | <nobr>`--command`</nobr> | | Recommended. Use to specify the build command or script that invokes the build process for the codebase. Commands are run from the current folder or, where it is defined, from <nobr>`--source-root`</nobr>. Not needed for Python and JavaScript/TypeScript analysis. |
 | <nobr>`--db-cluster`</nobr> | | Optional. Use in multi-language codebases to generate one database for each language specified by <nobr>`--language`</nobr>.
 | <nobr>`--no-run-unnecessary-builds`</nobr> | | Recommended. Use to suppress the build command for languages where the {% data variables.product.prodname_codeql_cli %} does not need to monitor the build (for example, Python and JavaScript/TypeScript).
-| <nobr>`--source-root`</nobr> | | Optional. Use if you run the CLI outside the checkout root of the repository. By default, the `database create` command assumes that the current directory is the root directory for the source files, use this option to specify a different location. |{% ifversion fpt or ghec or ghes > 3.2 or ghae %}
-| <nobr>`--codescanning-config`</nobr> | | Optional (Advanced). Use if you have a configuration file that specifies how to create the {% data variables.product.prodname_codeql %} databases and what queries to run in later steps. For more information, see "[Using a custom configuration file](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning#using-a-custom-configuration-file)" and "[database create](https://codeql.github.com/docs/codeql-cli/manual/database-create/#cmdoption-codeql-database-create-codescanning-config)." |{% endif %}
+| <nobr>`--source-root`</nobr> | | Optional. Use if you run the CLI outside the checkout root of the repository. By default, the `database create` command assumes that the current directory is the root directory for the source files, use this option to specify a different location. |
+| <nobr>`--codescanning-config`</nobr> | | Optional (Advanced). Use if you have a configuration file that specifies how to create the {% data variables.product.prodname_codeql %} databases and what queries to run in later steps. For more information, see "[Using a custom configuration file](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning#using-a-custom-configuration-file)" and "[database create](https://codeql.github.com/docs/codeql-cli/manual/database-create/#cmdoption-codeql-database-create-codescanning-config)." |
 
 For more information, see [Creating {% data variables.product.prodname_codeql %} databases](https://codeql.github.com/docs/codeql-cli/creating-codeql-databases/) in the documentation for the {% data variables.product.prodname_codeql_cli %}.
 
diff --git a/translations/ja-JP/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-runner-in-your-ci-system.md b/translations/ja-JP/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-runner-in-your-ci-system.md
index e9d72e176b..c02304f43a 100644
--- a/translations/ja-JP/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-runner-in-your-ci-system.md
+++ b/translations/ja-JP/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-runner-in-your-ci-system.md
@@ -115,7 +115,7 @@ $ /path/to-runner/codeql-runner-linux init --config-file .github/codeql/codeql-c
 
 ## Configuring {% data variables.product.prodname_code_scanning %} for compiled languages
 
-For the compiled languages C/C++, C#, and Java, {% data variables.product.prodname_codeql %} builds the code before analyzing it. {% data reusables.code-scanning.analyze-go %}
+For the compiled languages C/C++, C#,{% ifversion codeql-go-autobuild %} Go,{% endif %} and Java, {% data variables.product.prodname_codeql %} builds the code before analyzing it. {% data reusables.code-scanning.analyze-go %}
 
 For many common build systems, the {% data variables.product.prodname_codeql_runner %} can build the code automatically. To attempt to build the code automatically, run `autobuild` between the `init` and `analyze` steps. Note that if your repository requires a specific version of a build tool, you may need to install the build tool manually first. 
 
diff --git a/translations/ja-JP/content/code-security/dependabot/dependabot-alerts/about-dependabot-alerts.md b/translations/ja-JP/content/code-security/dependabot/dependabot-alerts/about-dependabot-alerts.md
index fa3ad2ded3..7b93d6bb64 100644
--- a/translations/ja-JP/content/code-security/dependabot/dependabot-alerts/about-dependabot-alerts.md
+++ b/translations/ja-JP/content/code-security/dependabot/dependabot-alerts/about-dependabot-alerts.md
@@ -76,7 +76,7 @@ For information about access requirements for actions related to {% data variabl
 
 When {% data variables.product.product_name %} identifies a vulnerable dependency{% ifversion GH-advisory-db-supports-malware %} or malware{% endif %}, we generate a {% data variables.product.prodname_dependabot %} alert and display it {% ifversion fpt or ghec or ghes %} on the Security tab for the repository and{% endif %} in the repository's dependency graph. The alert includes {% ifversion fpt or ghec or ghes %}a link to the affected file in the project, and {% endif %}information about a fixed version. {% data variables.product.product_name %} may also notify the maintainers of affected repositories about the new alert according to their notification preferences. For more information, see "[Configuring notifications for {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/configuring-notifications-for-dependabot-alerts)."
 
-{% ifversion fpt or ghec or ghes > 3.2 %}
+{% ifversion fpt or ghec or ghes %}
 For repositories where {% data variables.product.prodname_dependabot_security_updates %} are enabled, the alert may also contain a link to a pull request to update the manifest or lock file to the minimum version that resolves the vulnerability. For more information, see "[About {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)."
 {% endif %}
 
@@ -98,7 +98,7 @@ By default, we notify people with admin permissions in the affected repositories
 
 You can also see all the {% data variables.product.prodname_dependabot_alerts %} that correspond to a particular advisory in the {% data variables.product.prodname_advisory_database %}. {% data reusables.security-advisory.link-browsing-advisory-db %}
 
-{% ifversion fpt or ghec or ghes > 3.2 %}
+{% ifversion fpt or ghec or ghes %}
 ## Further reading
 
 - "[About {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)"
diff --git a/translations/ja-JP/content/code-security/dependabot/dependabot-alerts/browsing-security-advisories-in-the-github-advisory-database.md b/translations/ja-JP/content/code-security/dependabot/dependabot-alerts/browsing-security-advisories-in-the-github-advisory-database.md
deleted file mode 100644
index 663dc63e1b..0000000000
--- a/translations/ja-JP/content/code-security/dependabot/dependabot-alerts/browsing-security-advisories-in-the-github-advisory-database.md
+++ /dev/null
@@ -1,188 +0,0 @@
----
-title: Browsing security advisories in the GitHub Advisory Database
-intro: 'You can browse the {% data variables.product.prodname_advisory_database %} to find advisories for security risks in open source projects that are hosted on {% data variables.product.company_short %}.'
-shortTitle: Browse Advisory Database
-miniTocMaxHeadingLevel: 3
-redirect_from:
-  - /github/managing-security-vulnerabilities/browsing-security-vulnerabilities-in-the-github-advisory-database
-  - /code-security/supply-chain-security/browsing-security-vulnerabilities-in-the-github-advisory-database
-  - /code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/browsing-security-vulnerabilities-in-the-github-advisory-database
-  - /code-security/dependabot/dependabot-alerts/browsing-security-vulnerabilities-in-the-github-advisory-database
-versions:
-  fpt: '*'
-  ghec: '*'
-  ghes: '*'
-  ghae: '*'
-type: how_to
-topics:
-  - Security advisories
-  - Alerts
-  - Dependabot
-  - Vulnerabilities
-  - CVEs
----
-<!--Marketing-LINK: From /features/security/software-supply-chain page "Browsing security vulnerabilities in the GitHub Advisory Database".-->
-
-## About the {% data variables.product.prodname_advisory_database %}
-
-The {% data variables.product.prodname_advisory_database %} contains a list of known security vulnerabilities {% ifversion GH-advisory-db-supports-malware %}and malware, {% endif %}grouped in two categories: {% data variables.product.company_short %}-reviewed advisories and unreviewed advisories.
-
-{% data reusables.repositories.tracks-vulnerabilities %}
-
-## About types of security advisories
-
-{% data reusables.advisory-database.beta-malware-advisories %}
-
-Each advisory in the {% data variables.product.prodname_advisory_database %} is for a vulnerability in open source projects{% ifversion GH-advisory-db-supports-malware %} or for malicious open source software{% endif %}. 
-
-{% data reusables.repositories.a-vulnerability-is %} Vulnerabilities in code are usually introduced by accident and fixed soon after they are discovered. You should update your code to use the fixed version of the dependency as soon as it is available.
-
-{% ifversion GH-advisory-db-supports-malware %}
-
-In contrast, malicious software, or malware, is code that is intentionally designed to perform unwanted or harmful functions. The malware may target hardware, software, confidential data, or users of any application that uses the malware. You need to remove the malware from your project and find an alternative, more secure replacement for the dependency.
-
-{% endif %}
-
-### {% data variables.product.company_short %}-reviewed advisories
-
-{% data variables.product.company_short %}-reviewed advisories are security vulnerabilities{% ifversion GH-advisory-db-supports-malware %} or malware{% endif %} that have been mapped to packages in ecosystems we support. We carefully review each advisory for validity and ensure that they have a full description, and contain both ecosystem and package information.
-
-Generally, we name our supported ecosystems after the software programming language's associated package registry. We review advisories if they are for a vulnerability in a package that comes from a supported registry.
-
-- Composer (registry: https://packagist.org/){% ifversion GH-advisory-db-erlang-support %}
-- Erlang (registry: https://hex.pm/){% endif %}
-- Go (registry: https://pkg.go.dev/)
-{%- ifversion fpt or ghec or ghes > 3.6 or ghae > 3.6 %}
-- GitHub Actions (https://github.com/marketplace?type=actions/) {% endif %}
-- Maven (registry: https://repo.maven.apache.org/maven2)
-- npm (registry: https://www.npmjs.com/)
-- NuGet (registry: https://www.nuget.org/)
-- pip (registry: https://pypi.org/){% ifversion dependency-graph-dart-support %}
-- pub (registry: https://pub.dev/packages/registry){% endif %}
-- RubyGems (registry: https://rubygems.org/)
-- Rust (registry: https://crates.io/)
-
-If you have a suggestion for a new ecosystem we should support, please open an [issue](https://github.com/github/advisory-database/issues) for discussion.
-
-If you enable {% data variables.product.prodname_dependabot_alerts %} for your repositories, you are automatically notified when a new {% data variables.product.company_short %}-reviewed advisory reports a vulnerability {% ifversion GH-advisory-db-supports-malware %}or malware{% endif %} for a package you depend on. For more information, see "[About {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)."
-
-### Unreviewed advisories
-
-Unreviewed advisories are security vulnerabilites that we publish automatically into the {% data variables.product.prodname_advisory_database %}, directly from the National Vulnerability Database feed. 
-
-{% data variables.product.prodname_dependabot %} doesn't create {% data variables.product.prodname_dependabot_alerts %} for unreviewed advisories as this type of advisory isn't checked for validity or completion.
-
-## About information in security advisories
-
-Each security advisory contains information about the vulnerability{% ifversion GH-advisory-db-supports-malware %} or malware,{% endif %} which may include the description, severity, affected package, package ecosystem, affected versions and patched versions, impact, and optional information such as references, workarounds, and credits. In addition, advisories from the National Vulnerability Database list contain a link to the CVE record, where you can read more details about the vulnerability, its CVSS scores, and its qualitative severity level. For more information, see the "[National Vulnerability Database](https://nvd.nist.gov/)" from the National Institute of Standards and Technology.
-
-The severity level is one of four possible levels defined in the "[Common Vulnerability Scoring System (CVSS), Section 5](https://www.first.org/cvss/specification-document)."
-- Low
-- Medium/Moderate
-- High
-- Critical
-
-The {% data variables.product.prodname_advisory_database %} uses the CVSS levels described above. If {% data variables.product.company_short %} obtains a CVE, the {% data variables.product.prodname_advisory_database %} uses CVSS version 3.1. If the CVE is imported, the {% data variables.product.prodname_advisory_database %} supports both CVSS versions 3.0 and 3.1.
-
-{% data reusables.repositories.github-security-lab %}
-
-## Accessing an advisory in the {% data variables.product.prodname_advisory_database %}
-
-1. Navigate to https://github.com/advisories.
-2. Optionally, to filter the list, use any of the drop-down menus.
-  ![Dropdown filters](/assets/images/help/security/advisory-database-dropdown-filters.png)
-   {% tip %}
-
-   **Tip:** You can use the sidebar on the left to explore  {% data variables.product.company_short %}-reviewed and unreviewed advisories separately.
-
-   {% endtip %}
-3. Click an advisory to view details. By default, you will see {% data variables.product.company_short %}-reviewed advisories for security vulnerabilities. {% ifversion GH-advisory-db-supports-malware %}To show malware advisories, use `type:malware` in the search bar.{% endif %}
-
-
-{% note %}
-
-The database is also accessible using the GraphQL API. {% ifversion GH-advisory-db-supports-malware %}By default, queries will return {% data variables.product.company_short %}-reviewed advisories for security vulnerabilities unless you specify `type:malware`.{% endif %} For more information, see the "[`security_advisory` webhook event](/webhooks/event-payloads/#security_advisory)."
-
-{% endnote %}
-
-## Editing an advisory in the {% data variables.product.prodname_advisory_database %}
-You can suggest improvements to any advisory in the {% data variables.product.prodname_advisory_database %}. For more information, see "[Editing security advisories in the {% data variables.product.prodname_advisory_database %}](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/editing-security-advisories-in-the-github-advisory-database)."
-
-## Searching the {% data variables.product.prodname_advisory_database %}
-
-You can search the database, and use qualifiers to narrow your search. For example, you can search for advisories created on a certain date, in a specific ecosystem, or in a particular library.
-
-{% data reusables.time_date.date_format %} {% data reusables.time_date.time_format %}
-
-{% data reusables.search.date_gt_lt %}
-
-| Qualifier  | Example |
-| ------------- | ------------- |
-| `type:reviewed`| [**type:reviewed**](https://github.com/advisories?query=type%3Areviewed) will show {% data variables.product.company_short %}-reviewed advisories for security vulnerabilities. |
-{% ifversion GH-advisory-db-supports-malware %}| `type:malware` | [**type:malware**](https://github.com/advisories?query=type%3Amalware) will show {% data variables.product.company_short %}-reviewed advisories for malware. |
-{% endif %}| `type:unreviewed`| [**type:unreviewed**](https://github.com/advisories?query=type%3Aunreviewed) will show unreviewed advisories. |
-| `GHSA-ID`| [**GHSA-49wp-qq6x-g2rf**](https://github.com/advisories?query=GHSA-49wp-qq6x-g2rf) will show the advisory with this {% data variables.product.prodname_advisory_database %} ID. |
-| `CVE-ID`| [**CVE-2020-28482**](https://github.com/advisories?query=CVE-2020-28482) will show the advisory with this CVE ID number. |
-| `ecosystem:ECOSYSTEM`| [**ecosystem:npm**](https://github.com/advisories?utf8=%E2%9C%93&query=ecosystem%3Anpm) will show only advisories affecting NPM packages. |
-| `severity:LEVEL`| [**severity:high**](https://github.com/advisories?utf8=%E2%9C%93&query=severity%3Ahigh) will show only advisories with a high severity level. |
-| `affects:LIBRARY`| [**affects:lodash**](https://github.com/advisories?utf8=%E2%9C%93&query=affects%3Alodash) will show only advisories affecting the lodash library. |
-| `cwe:ID`| [**cwe:352**](https://github.com/advisories?query=cwe%3A352) will show only advisories with this CWE number. |
-| `credit:USERNAME`| [**credit:octocat**](https://github.com/advisories?query=credit%3Aoctocat) will show only advisories credited to the "octocat" user account. |
-| `sort:created-asc`| [**sort:created-asc**](https://github.com/advisories?utf8=%E2%9C%93&query=sort%3Acreated-asc) will sort by the oldest advisories first. |
-| `sort:created-desc`| [**sort:created-desc**](https://github.com/advisories?utf8=%E2%9C%93&query=sort%3Acreated-desc) will sort by the newest advisories first. |
-| `sort:updated-asc`| [**sort:updated-asc**](https://github.com/advisories?utf8=%E2%9C%93&query=sort%3Aupdated-asc) will sort by the least recently updated first. |
-| `sort:updated-desc`| [**sort:updated-desc**](https://github.com/advisories?utf8=%E2%9C%93&query=sort%3Aupdated-desc) will sort by the most recently updated first. |
-| `is:withdrawn`| [**is:withdrawn**](https://github.com/advisories?utf8=%E2%9C%93&query=is%3Awithdrawn) will show only advisories that have been withdrawn. |
-| `created:YYYY-MM-DD`| [**created:2021-01-13**](https://github.com/advisories?utf8=%E2%9C%93&query=created%3A2021-01-13) will show only advisories created on this date. |
-| `updated:YYYY-MM-DD`| [**updated:2021-01-13**](https://github.com/advisories?utf8=%E2%9C%93&query=updated%3A2021-01-13) will show only advisories updated on this date. |
-
-## Viewing your vulnerable repositories
-
-For any {% data variables.product.company_short %}-reviewed advisory in the {% data variables.product.prodname_advisory_database %}, you can see which of your repositories are affected by that security vulnerability{% ifversion GH-advisory-db-supports-malware %} or malware{% endif %}. To see a vulnerable repository, you must have access to {% data variables.product.prodname_dependabot_alerts %} for that repository. For more information, see "[About {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies#access-to-dependabot-alerts)."
-
-1. Navigate to https://github.com/advisories.
-2. Click an advisory.
-3. At the top of the advisory page, click **Dependabot alerts**.
-   ![Dependabot alerts](/assets/images/help/security/advisory-database-dependabot-alerts.png)
-4. Optionally, to filter the list, use the search bar or the drop-down menus. The "Organization" drop-down menu allows you to filter the {% data variables.product.prodname_dependabot_alerts %} per owner (organization or user).
-   ![Search bar and drop-down menus to filter alerts](/assets/images/help/security/advisory-database-dependabot-alerts-filters.png)
-5. For more details about the advisory, and for advice on how to fix the vulnerable repository, click the repository name.
-
-{% ifversion security-advisories-ghes-ghae %}
-## Accessing the local advisory database on {% data variables.location.product_location %}
-
-If your site administrator has enabled {% data variables.product.prodname_github_connect %} for {% data variables.location.product_location %}, you can also browse reviewed advisories locally. For more information, see "[About {% data variables.product.prodname_github_connect %}](/admin/configuration/configuring-github-connect/about-github-connect)".
-
-You can use your local advisory database to check whether a specific security vulnerability is included, and therefore whether you'd get alerts for vulnerable dependencies. You can also view any vulnerable repositories. 
-
-1. Navigate to `https://HOSTNAME/advisories`.
-2. Optionally, to filter the list, use any of the drop-down menus.
-  ![Dropdown filters](/assets/images/help/security/advisory-database-dropdown-filters.png)
-   {% note %}
-
-   **Note:** Only reviewed advisories will be listed. Unreviewed advisories can be viewed in the {% data variables.product.prodname_advisory_database %} on {% data variables.product.prodname_dotcom_the_website %}. For more information, see "[Accessing an advisory in the GitHub Advisory Database](#accessing-an-advisory-in-the-github-advisory-database)". 
-
-   {% endnote %}
-3. Click an advisory to view details.{% ifversion GH-advisory-db-supports-malware %} By default, you will see {% data variables.product.company_short %}-reviewed advisories for security vulnerabilities. To show malware advisories, use `type:malware` in the search bar.{% endif %}
-
-You can also suggest improvements to any advisory directly from your local advisory database. For more information, see "[Editing advisories from {% data variables.location.product_location %}](/code-security/dependabot/dependabot-alerts/editing-security-advisories-in-the-github-advisory-database#editing-advisories-from-your-github-enterprise-server-instance)".
-
-### Viewing vulnerable repositories for {% data variables.location.product_location %}
-
-{% data reusables.repositories.enable-security-alerts %}
-
-In the local advisory database, you can see which repositories are affected by each security vulnerability{% ifversion GH-advisory-db-supports-malware %} or malware{% endif %}. To see a vulnerable repository, you must have access to {% data variables.product.prodname_dependabot_alerts %} for that repository. For more information, see "[About {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies#access-to-dependabot-alerts)."
-
-1. Navigate to `https://HOSTNAME/advisories`.
-2. Click an advisory.
-3. At the top of the advisory page, click **Dependabot alerts**.
-   ![Dependabot alerts](/assets/images/help/security/advisory-database-dependabot-alerts.png)
-4. Optionally, to filter the list, use the search bar or the drop-down menus. The "Organization" drop-down menu allows you to filter the {% data variables.product.prodname_dependabot_alerts %} per owner (organization or user).
-   ![Search bar and drop-down menus to filter alerts](/assets/images/help/security/advisory-database-dependabot-alerts-filters.png)
-5. For more details about the advisory, and for advice on how to fix the vulnerable repository, click the repository name.
-
-{% endif %}
-
-## Further reading
-
-- MITRE's [definition of "vulnerability"](https://www.cve.org/ResourcesSupport/Glossary#vulnerability)
diff --git a/translations/ja-JP/content/code-security/dependabot/dependabot-alerts/editing-security-advisories-in-the-github-advisory-database.md b/translations/ja-JP/content/code-security/dependabot/dependabot-alerts/editing-security-advisories-in-the-github-advisory-database.md
deleted file mode 100644
index 688f003461..0000000000
--- a/translations/ja-JP/content/code-security/dependabot/dependabot-alerts/editing-security-advisories-in-the-github-advisory-database.md
+++ /dev/null
@@ -1,55 +0,0 @@
----
-title: Editing security advisories in the GitHub Advisory Database
-intro: 'You can submit improvements to any advisory published in the {% data variables.product.prodname_advisory_database %}.'
-redirect_from:
-  - /code-security/security-advisories/editing-security-advisories-in-the-github-advisory-database
-  - /code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/editing-security-advisories-in-the-github-advisory-database
-versions:
-  fpt: '*'
-  ghec: '*'
-  ghes: '*'
-  ghae: '*'
-type: how_to
-topics:
-  - Security advisories
-  - Alerts
-  - Dependabot
-  - Vulnerabilities
-  - CVEs
-shortTitle: Edit Advisory Database
----
-
-## About editing advisories in the {% data variables.product.prodname_advisory_database %}
-Security advisories in the {% data variables.product.prodname_advisory_database %} at [github.com/advisories](https://github.com/advisories) are considered global advisories. Anyone can suggest improvements on any global security advisory in the {% data variables.product.prodname_advisory_database %}. You can edit or add any detail, including additionally affected ecosystems, severity level or description of who is impacted. The {% data variables.product.prodname_security %} curation team will review the submitted improvements and publish them onto the {% data variables.product.prodname_advisory_database %} if accepted.
-{% ifversion fpt or ghec %}
-Only repository owners and administrators can edit repository-level security advisories. For more information, see "[Editing a repository security advisory](/code-security/security-advisories/editing-a-security-advisory)."{% endif %}
-
-## Editing advisories in the GitHub Advisory Database
-
-1. Navigate to https://github.com/advisories.
-1. Select the security advisory you would like to contribute to.
-1. On the right-hand side of the page, click the **Suggest improvements for this vulnerability** link.
-   
-   ![Screenshot of the suggest improvements link](/assets/images/help/security/suggest-improvements-to-advisory.png)
-
-1. In the "Improve security advisory" form, make the desired improvements. You can edit or add any detail.{% ifversion fpt or ghec %} For information about correctly specifying information on the form, including affected versions, see "[Best practices for writing repository security advisories](/code-security/repository-security-advisories/best-practices-for-writing-repository-security-advisories)."{% endif %}{% ifversion security-advisories-reason-for-change %}
-1. Under **Reason for change**, explain why you want to make this improvement. If you include links to supporting material this will help our reviewers.
-   
-   ![Screenshot of the reason for change field](/assets/images/help/security/security-advisories-suggest-improvement-reason.png){% endif %}
-
-1. When you finish editing the advisory, click **Submit improvements**.
-1. Once you submit your improvements, a pull request containing your changes will be created for review in [github/advisory-database](https://github.com/github/advisory-database) by the {% data variables.product.prodname_security %} curation team. If the advisory originated from a {% data variables.product.prodname_dotcom %} repository, we will also tag the original publisher for optional commentary. You can view the pull request and get notifications when it is updated or closed.
-
-You can also open a pull request directly on an advisory file in the [github/advisory-database](https://github.com/github/advisory-database) repository. For more information, see the [contribution guidelines](https://github.com/github/advisory-database/blob/main/CONTRIBUTING.md). 
-
-{% ifversion security-advisories-ghes-ghae %}
-## Editing advisories from {% data variables.location.product_location %}
-
-If you have {% data variables.product.prodname_github_connect %} enabled for {% data variables.location.product_location %}, you will be able to see advisories by adding `/advisories` to the instance url. 
-
-1. Navigate to `https://HOSTNAME/advisories`.
-2. Select the security advisory you would like to contribute to.
-3. On the right-hand side of the page, click the **Suggest improvements for this vulnerability on Github.com.** link. A new tab opens with the same security advisory on {% data variables.product.prodname_dotcom_the_website %}.
-![Suggest improvements link](/assets/images/help/security/suggest-improvements-to-advisory-on-github-com.png)
-4. Edit the advisory, following steps four through six in "[Editing advisories in the GitHub Advisory Database](#editing-advisories-in-the-github-advisory-database)" above.
-{% endif %}
diff --git a/translations/ja-JP/content/code-security/dependabot/dependabot-alerts/index.md b/translations/ja-JP/content/code-security/dependabot/dependabot-alerts/index.md
index 8bf3cc268f..4f4b684e45 100644
--- a/translations/ja-JP/content/code-security/dependabot/dependabot-alerts/index.md
+++ b/translations/ja-JP/content/code-security/dependabot/dependabot-alerts/index.md
@@ -15,8 +15,6 @@ topics:
   - Repositories
   - Dependencies
 children:
-  - /browsing-security-advisories-in-the-github-advisory-database
-  - /editing-security-advisories-in-the-github-advisory-database
   - /about-dependabot-alerts
   - /configuring-dependabot-alerts
   - /viewing-and-updating-dependabot-alerts
diff --git a/translations/ja-JP/content/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts.md b/translations/ja-JP/content/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts.md
index 28df5d5e99..94166566bd 100644
--- a/translations/ja-JP/content/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts.md
+++ b/translations/ja-JP/content/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts.md
@@ -26,13 +26,13 @@ topics:
 {% data reusables.dependabot.beta-security-and-version-updates %}
 {% data reusables.dependabot.enterprise-enable-dependabot %}
 
-Your repository's {% data variables.product.prodname_dependabot_alerts %} tab lists all open and closed {% data variables.product.prodname_dependabot_alerts %}{% ifversion fpt or ghec or ghes > 3.2 %} and corresponding {% data variables.product.prodname_dependabot_security_updates %}{% endif %}. You can{% ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4 %} filter alerts by package, ecosystem, or manifest. You can {% endif %} sort the list of alerts, and you can click into specific alerts for more details. {% ifversion dependabot-bulk-alerts %}You can also dismiss or reopen alerts, either one by one or by selecting multiple alerts at once.{% else %}You can also dismiss or reopen alerts. {% endif %} For more information, see "[About {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)." 
+Your repository's {% data variables.product.prodname_dependabot_alerts %} tab lists all open and closed {% data variables.product.prodname_dependabot_alerts %}{% ifversion fpt or ghec or ghes %} and corresponding {% data variables.product.prodname_dependabot_security_updates %}{% endif %}. You can{% ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4 %} filter alerts by package, ecosystem, or manifest. You can {% endif %} sort the list of alerts, and you can click into specific alerts for more details. {% ifversion dependabot-bulk-alerts %}You can also dismiss or reopen alerts, either one by one or by selecting multiple alerts at once.{% else %}You can also dismiss or reopen alerts. {% endif %} For more information, see "[About {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)." 
 
-{% ifversion fpt or ghec or ghes > 3.2 %}
+{% ifversion fpt or ghec or ghes %}
 You can enable automatic security updates for any repository that uses {% data variables.product.prodname_dependabot_alerts %} and the dependency graph. For more information, see "[About {% data variables.product.prodname_dependabot_security_updates %}](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-dependabot-security-updates)."
 {% endif %}
 
-{% ifversion fpt or ghec or ghes > 3.2 %}
+{% ifversion fpt or ghec or ghes %}
 ## About updates for vulnerable dependencies in your repository
 
 {% data variables.product.product_name %} generates {% data variables.product.prodname_dependabot_alerts %} when we detect that your codebase is using dependencies with known security risks. For repositories where {% data variables.product.prodname_dependabot_security_updates %} are enabled, when {% data variables.product.product_name %} detects a vulnerable dependency in the default branch, {% data variables.product.prodname_dependabot %} creates a pull request to fix it. The pull request will upgrade the dependency to the minimum possible secure version needed to avoid the vulnerability.
@@ -144,16 +144,16 @@ For supported languages, {% data variables.product.prodname_dependabot %} detect
 ### Fixing vulnerable dependencies
 
 1. View the details for an alert. For more information, see "[Viewing {% data variables.product.prodname_dependabot_alerts %}](#viewing-dependabot-alerts)" (above).
-{% ifversion fpt or ghec or ghes > 3.2 %}
+{% ifversion fpt or ghec or ghes %}
 1. If you have {% data variables.product.prodname_dependabot_security_updates %} enabled, there may be a link to a pull request that will fix the dependency. Alternatively, you can click **Create {% data variables.product.prodname_dependabot %} security update** at the top of the alert details page to create a pull request.
   ![Create {% data variables.product.prodname_dependabot %} security update button](/assets/images/help/repository/create-dependabot-security-update-button-ungrouped.png)
 1. Optionally, if you do not use {% data variables.product.prodname_dependabot_security_updates %}, you can use the information on the page to decide which version of the dependency to upgrade to and create a pull request to update the dependency to a secure version.
-{% elsif ghes < 3.3 or ghae %}
+{% elsif ghae %}
 1. You can use the information on the page to decide which version of the dependency to upgrade to and create a pull request to the manifest or lock file to a secure version.
 {% endif %}
 1. When you're ready to update your dependency and resolve the vulnerability, merge the pull request. 
 
-{% ifversion fpt or ghec or ghes > 3.2 %}
+{% ifversion fpt or ghec or ghes %}
    Each pull request raised by {% data variables.product.prodname_dependabot %} includes information on commands you can use to control {% data variables.product.prodname_dependabot %}. For more information, see "[Managing pull requests for dependency updates](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/managing-pull-requests-for-dependency-updates#managing-dependabot-pull-requests-with-comment-commands)."
 {% endif %}
 
diff --git a/translations/ja-JP/content/code-security/dependabot/dependabot-security-updates/configuring-dependabot-security-updates.md b/translations/ja-JP/content/code-security/dependabot/dependabot-security-updates/configuring-dependabot-security-updates.md
index 320c6a0c45..0e0910c214 100644
--- a/translations/ja-JP/content/code-security/dependabot/dependabot-security-updates/configuring-dependabot-security-updates.md
+++ b/translations/ja-JP/content/code-security/dependabot/dependabot-security-updates/configuring-dependabot-security-updates.md
@@ -13,7 +13,7 @@ redirect_from:
 versions:
   fpt: '*'
   ghec: '*'
-  ghes: '>3.2'
+  ghes: '*'
 type: how_to
 topics:
   - Dependabot
diff --git a/translations/ja-JP/content/code-security/dependabot/dependabot-security-updates/index.md b/translations/ja-JP/content/code-security/dependabot/dependabot-security-updates/index.md
index 57a51497e5..126a3bffce 100644
--- a/translations/ja-JP/content/code-security/dependabot/dependabot-security-updates/index.md
+++ b/translations/ja-JP/content/code-security/dependabot/dependabot-security-updates/index.md
@@ -5,7 +5,7 @@ allowTitleToDifferFromFilename: true
 versions:
   fpt: '*'
   ghec: '*'
-  ghes: '>3.2'
+  ghes: '*'
 topics:
   - Repositories
   - Dependabot
@@ -16,11 +16,11 @@ shortTitle: Dependabot security updates
 children:
   - /about-dependabot-security-updates
   - /configuring-dependabot-security-updates
-ms.openlocfilehash: 046ef28084ce31c1a4178355f5db6644b5ba0f12
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: e18b6331f762a81b82c759de5fdbc6eeed300308
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: ja-JP
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '145124877'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148108899'
 ---
 
diff --git a/translations/ja-JP/content/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file.md b/translations/ja-JP/content/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file.md
index 38b4b62926..eaefe0047a 100644
--- a/translations/ja-JP/content/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file.md
+++ b/translations/ja-JP/content/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file.md
@@ -11,7 +11,7 @@ miniTocMaxHeadingLevel: 3
 versions:
   fpt: '*'
   ghec: '*'
-  ghes: '>3.2'
+  ghes: '*'
 type: reference
 topics:
   - Dependabot
diff --git a/translations/ja-JP/content/code-security/dependabot/dependabot-version-updates/customizing-dependency-updates.md b/translations/ja-JP/content/code-security/dependabot/dependabot-version-updates/customizing-dependency-updates.md
index 0b06af8cfa..4ec0f0cac8 100644
--- a/translations/ja-JP/content/code-security/dependabot/dependabot-version-updates/customizing-dependency-updates.md
+++ b/translations/ja-JP/content/code-security/dependabot/dependabot-version-updates/customizing-dependency-updates.md
@@ -1,6 +1,6 @@
 ---
-title: 依存関係の更新をカスタマイズする
-intro: '{% data variables.product.prodname_dependabot %} が依存関係を維持する方法をカスタマイズできます。'
+title: Customizing dependency updates
+intro: 'You can customize how {% data variables.product.prodname_dependabot %} maintains your dependencies.'
 permissions: 'People with write permissions to a repository can configure {% data variables.product.prodname_dependabot %} for the repository.'
 redirect_from:
   - /github/administering-a-repository/customizing-dependency-updates
@@ -9,7 +9,7 @@ redirect_from:
 versions:
   fpt: '*'
   ghec: '*'
-  ghes: '>3.2'
+  ghes: '*'
 type: how_to
 topics:
   - Dependabot
@@ -20,40 +20,36 @@ topics:
   - Pull requests
   - Vulnerabilities
 shortTitle: Customize updates
-ms.openlocfilehash: 6cb6db974fe880bccc76c89447dc077e0617df9a
-ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
-ms.translationtype: HT
-ms.contentlocale: ja-JP
-ms.lasthandoff: 09/11/2022
-ms.locfileid: '145124842'
 ---
-{% data reusables.dependabot.beta-security-and-version-updates %} {% data reusables.dependabot.enterprise-enable-dependabot %}
 
-## 依存関係の更新のカスタマイズについて
+{% data reusables.dependabot.beta-security-and-version-updates %}
+{% data reusables.dependabot.enterprise-enable-dependabot %}
 
-バージョン アップデートを有効にすると、*dependabot.yml* ファイルにその他のオプションを追加することで、{% data variables.product.prodname_dependabot %} を使って依存関係を維持する方法をカスタマイズできます。 たとえば、次のことが可能です。
+## About customizing dependency updates
 
-- バージョン アップデートの pull request をオープンする曜日を指定する (`schedule.day`)
-- レビュー担当者、担当者、各パッケージ マネージャーのラベルを設定する (`reviewers`、`assignees`、`labels`)
-- 各マニフェスト ファイルの変更に対するバージョン管理戦略を定義する (`versioning-strategy`)
-- バージョン アップデートの pull requests オープンする回数を、既定の 5 回から最大の回数に変更する (`open-pull-requests-limit`)
-- バージョン アップデートの pull request をオープンして、既定のブランチの代わりに特定のブランチをターゲットにする (`target-branch`)
+After you've enabled version updates, you can customize how {% data variables.product.prodname_dependabot %} maintains your dependencies by adding further options to the *dependabot.yml* file. For example, you could:
 
-構成オプションの詳しい情報については、「[dependabot.yml ファイルの構成オプション](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/configuration-options-for-dependency-updates)」を参照してください。
+- Specify which day of the week to open pull requests for version updates: `schedule.day`
+- Set reviewers, assignees, and labels for each package manager: `reviewers`, `assignees`, and `labels`
+- Define a versioning strategy for changes to each manifest file: `versioning-strategy`
+- Change the maximum number of open pull requests for version updates from the default of 5: `open-pull-requests-limit`
+- Open pull requests for version updates to target a specific branch, instead of the default branch: `target-branch`
 
-リポジトリ内の *dependabot.yml* ファイルを更新すると、{% data variables.product.prodname_dependabot %} によって、新しい構成で、すぐにチェックが実行されます。 数分以内に、 **[{% data variables.product.prodname_dependabot %}]** タブに依存関係の更新済みリストが表示されます。リポジトリにある依存関係が多い場合は、時間がかかることがあります。 バージョン更新に関する新しいプルリクエストが表示されることもあります。 詳しい情報については、「[バージョン更新用に設定された依存関係を一覧表示する](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/listing-dependencies-configured-for-version-updates)」を参照してください。
+For more information about the configuration options, see "[Configuration options for the dependabot.yml file](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/configuration-options-for-dependency-updates)."
 
-## 設定変更によるセキュリティアップデートへの影響
+When you update the *dependabot.yml* file in your repository, {% data variables.product.prodname_dependabot %} runs an immediate check with the new configuration. Within minutes you will see an updated list of dependencies on the **{% data variables.product.prodname_dependabot %}** tab, this may take longer if the repository has many dependencies. You may also see new pull requests for version updates. For more information, see "[Listing dependencies configured for version updates](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/listing-dependencies-configured-for-version-updates)."
 
-*dependabot.yml* ファイルをカスタマイズしていると、セキュリティ アップデートに対して発行された pull request の変更点に気づくかもしれません。 これらのプルリクエストは、{% data variables.product.prodname_dependabot %} スケジュールではなく、常に依存関係のセキュリティアドバイザリによってトリガーされます。 ただし、バージョン アップデートに別のターゲット ブランチを指定していなければ、関連する構成設定は *dependabot.yml* ファイルから継承されます。
+## Impact of configuration changes on security updates
 
-例については、[カスタム ラベルの設定](#setting-custom-labels)に関する以下のセクションを参照してください。
+If you customize the *dependabot.yml* file, you may notice some changes to the pull requests raised for security updates. These pull requests are always triggered by a security advisory for a dependency, rather than by the {% data variables.product.prodname_dependabot %} schedule. However, they inherit relevant configuration settings from the *dependabot.yml* file unless you specify a different target branch for version updates.
 
-## スケジュールを変更する
+For an example, see "[Setting custom labels](#setting-custom-labels)" below.
 
-アップデート スケジュールを `daily` に設定すると、既定の 05:00 (UTC) に {% data variables.product.prodname_dependabot %} で新しいバージョンのチェックが行われます。 `schedule.time` を使うと、アップデートのチェックを別の時刻に指定できます (`hh:mm` 形式)。
+## Modifying scheduling
 
-次の *dependabot.yml* ファイルの例では、npm 構成を拡張して、{% data variables.product.prodname_dependabot %} で依存関係のバージョン アップデートをチェックするタイミングを指定します。
+When you set a `daily` update schedule, by default, {% data variables.product.prodname_dependabot %} checks for new versions at 05:00 UTC. You can use `schedule.time` to specify an alternative time of day to check for updates (format: `hh:mm`).
+
+The example *dependabot.yml* file below expands the npm configuration to specify when {% data variables.product.prodname_dependabot %} should check for version updates to dependencies.
 
 ```yaml
 # dependabot.yml file with
@@ -70,13 +66,13 @@ updates:
       time: "02:00"
 ```
 
-## レビュー担当者とアサインされた人を設定する
+## Setting reviewers and assignees
 
-デフォルトでは、{% data variables.product.prodname_dependabot %} は、レビュー担当者やアサインされた人なしでプルリクエストを発行します。
+By default, {% data variables.product.prodname_dependabot %} raises pull requests without any reviewers or assignees.
 
-`reviewers` と `assignees` を使うと、パッケージ マネージャーに対して発行されたすべての pull request のレビュー担当者と担当者を指定できます。 Team を指定する場合は、その Team (Organization を含む) を @mentioning していたように、Team のフル ネームを使う必要があります。
+You can use `reviewers` and `assignees`  to specify reviewers and assignees for all pull requests raised for a package manager. When you specify a team, you must use the full team name, as if you were @mentioning the team (including the organization).
 
-次の *dependabot.yml* ファイルの例では、npm のバージョン アップデートとセキュリティ アップデートでオープンしたすべての pull request に 2 人のレビュー担当者と 1 人の担当者が存在するように、npm 構成を変更します。
+The example *dependabot.yml* file below changes the npm configuration so that all pull requests opened with version and security updates for npm will have two reviewers and one assignee.
 
 ```yaml
 # dependabot.yml file with
@@ -88,7 +84,7 @@ updates:
   - package-ecosystem: "npm"
     directory: "/"
     schedule:
-      interval: "daily"
+      interval: "weekly"
     # Raise all npm pull requests with reviewers
     reviewers:
       - "my-org/team-name"
@@ -98,17 +94,17 @@ updates:
       - "user-name"
 ```
 
-## カスタムラベルを設定する
+## Setting custom labels
 
 {% data reusables.dependabot.default-labels %}
 
-`labels` を使うと、既定のラベルを上書きして、パッケージ マネージャーに対して発行されたすべての pull request に代替ラベルを指定できます。 *dependabot.yml* ファイルでは新しいラベルを作成できないため、リポジトリ内に代替ラベルが既に存在している必要があります。
+You can use `labels` to override the default labels and specify alternative labels for all pull requests raised for a package manager. You can't create new labels in the *dependabot.yml* file, so the alternative labels must already exist in the repository.
 
-次の *dependabot.yml* ファイルの例では、npm のバージョン アップデートとセキュリティ アップデートでオープンしたすべての pull request にカスタム ラベルが存在するように、npm 構成を変更します。 また、Docker 設定を変更して、カスタムブランチに対するバージョン更新を確認し、そのカスタムブランチに対するカスタムラベルを使用してプルリクエストを発行します。 セキュリティアップデートは常にデフォルトのブランチに対して行われるため、Docker への変更はセキュリティアップデートのプルリクエストには影響しません。
+The example *dependabot.yml* file below changes the npm configuration so that all pull requests opened with version and security updates for npm will have custom labels. It also changes the Docker configuration to check for version updates against a custom branch and to raise pull requests with custom labels against that custom branch. The changes to Docker will not affect security update pull requests because security updates are always made against the default branch.
 
 {% note %}
 
-**注:** 新しい `target-branch` には、更新する Dockerfile が含まれている必要があります。含まれていない場合、この変更を行うと、Docker のバージョン アップデートが無効になります。
+**Note:** The new `target-branch` must contain a Dockerfile to update, otherwise this change will have the effect of disabling version updates for Docker.
 
 {% endnote %}
 
@@ -122,7 +118,7 @@ updates:
   - package-ecosystem: "npm"
     directory: "/"
     schedule:
-      interval: "daily"
+      interval: "weekly"
     # Raise all npm pull requests with custom labels
     labels:
       - "npm dependencies"
@@ -132,7 +128,7 @@ updates:
   - package-ecosystem: "docker"
     directory: "/"
     schedule:
-      interval: "daily"
+      interval: "weekly"
     # Raise pull requests for Docker version updates
     # against the "develop" branch. The Docker configuration
     # no longer affects security update pull requests.
@@ -143,6 +139,6 @@ updates:
       - "triage-board"
 ```
 
-## その他の例
+## More examples
 
-詳しい情報については、「[dependabot.yml ファイルの設定オプション](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/configuration-options-for-dependency-updates)」を参照してください。
+For more examples, see "[Configuration options for the dependabot.yml file](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/configuration-options-for-dependency-updates)."
diff --git a/translations/ja-JP/content/code-security/dependabot/dependabot-version-updates/index.md b/translations/ja-JP/content/code-security/dependabot/dependabot-version-updates/index.md
index 16fecdf5e9..2f9c0112d5 100644
--- a/translations/ja-JP/content/code-security/dependabot/dependabot-version-updates/index.md
+++ b/translations/ja-JP/content/code-security/dependabot/dependabot-version-updates/index.md
@@ -8,7 +8,7 @@ redirect_from:
 versions:
   fpt: '*'
   ghec: '*'
-  ghes: '>3.2'
+  ghes: '*'
 topics:
   - Repositories
   - Dependabot
@@ -22,11 +22,11 @@ children:
   - /customizing-dependency-updates
   - /configuration-options-for-the-dependabot.yml-file
 shortTitle: Dependabot version updates
-ms.openlocfilehash: 7eec75884da9fed388c7f882fe870d993606cb00
-ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.openlocfilehash: 7d926dd11d8d97511a66109273e30aa018f2707a
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: ja-JP
-ms.lasthandoff: 09/11/2022
-ms.locfileid: '145124841'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148109805'
 ---
 
diff --git a/translations/ja-JP/content/code-security/dependabot/dependabot-version-updates/listing-dependencies-configured-for-version-updates.md b/translations/ja-JP/content/code-security/dependabot/dependabot-version-updates/listing-dependencies-configured-for-version-updates.md
index 4d234695d1..e44e45c3e1 100644
--- a/translations/ja-JP/content/code-security/dependabot/dependabot-version-updates/listing-dependencies-configured-for-version-updates.md
+++ b/translations/ja-JP/content/code-security/dependabot/dependabot-version-updates/listing-dependencies-configured-for-version-updates.md
@@ -1,6 +1,6 @@
 ---
-title: バージョン更新用に設定された依存関係を一覧表示する
-intro: '{% data variables.product.prodname_dependabot %} が更新を監視している依存関係を表示できます。'
+title: Listing dependencies configured for version updates
+intro: 'You can view the dependencies that {% data variables.product.prodname_dependabot %} monitors for updates.'
 redirect_from:
   - /github/administering-a-repository/listing-dependencies-configured-for-version-updates
   - /code-security/supply-chain-security/listing-dependencies-configured-for-version-updates
@@ -8,7 +8,7 @@ redirect_from:
 versions:
   fpt: '*'
   ghec: '*'
-  ghes: '>3.2'
+  ghes: '*'
 type: how_to
 topics:
   - Repositories
@@ -16,28 +16,27 @@ topics:
   - Version updates
   - Dependencies
 shortTitle: List configured dependencies
-ms.openlocfilehash: 8028c10c39d4b045206954fc38ed805b5432e553
-ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
-ms.translationtype: HT
-ms.contentlocale: ja-JP
-ms.lasthandoff: 09/10/2022
-ms.locfileid: '145124836'
 ---
-{% data reusables.dependabot.beta-security-and-version-updates %} {% data reusables.dependabot.enterprise-enable-dependabot %}
 
-## {% data variables.product.prodname_dependabot %} によって監視されている依存関係を表示する
+{% data reusables.dependabot.beta-security-and-version-updates %}
+{% data reusables.dependabot.enterprise-enable-dependabot %}
 
-バージョン更新を有効にした後、リポジトリの依存関係グラフの **[{% data variables.product.prodname_dependabot %}]** タブで、設定が正しいかどうかを確認できます。 詳細については、「[{% data variables.product.prodname_dependabot %} バージョンの更新の構成](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/enabling-and-disabling-dependabot-version-updates)」を参照してください。
+## Viewing dependencies monitored by {% data variables.product.prodname_dependabot %}
 
-{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.accessing-repository-graphs %} {% data reusables.repositories.click-dependency-graph %} {% data reusables.dependabot.click-dependabot-tab %}
-1. 必要に応じて、パッケージ マネージャーで監視されているファイルを表示するには、関連する {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} をクリックします。
-  ![監視対象の依存関係ファイル](/assets/images/help/dependabot/monitored-dependency-files.png)
+After you've enabled version updates, you can confirm that your configuration is correct using the **{% data variables.product.prodname_dependabot %}** tab in the dependency graph for the repository. For more information, see "[Configuring {% data variables.product.prodname_dependabot %} version updates](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/enabling-and-disabling-dependabot-version-updates)."
 
-依存関係が見つからない場合は、ログファイルでエラーを確認します。 パッケージマネージャーが見つからない場合は、設定ファイルを確認してください。
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.accessing-repository-graphs %}
+{% data reusables.repositories.click-dependency-graph %}
+{% data reusables.dependabot.click-dependabot-tab %}
+1. Optionally, to view the files monitored for a package manager, click the associated {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}.
+  ![Monitored dependency files](/assets/images/help/dependabot/monitored-dependency-files.png)
 
-## Viewing {% data variables.product.prodname_dependabot %} のログファイルを表示する
+If any dependencies are missing, check the log files for errors. If any package managers are missing, review the configuration file.
 
-1. **[{% data variables.product.prodname_dependabot %}]** タブで、 **[最後のチェックは *時間* 前]** をクリックして、{% data variables.product.prodname_dependabot %} で最後のバージョン更新チェック時に生成されたログファイルを表示します。
-  ![[ログ ファイルの表示]](/assets/images/help/dependabot/last-checked-link.png)
-2. 必要に応じて、バージョン チェックを再実行するには、 **[更新プログラムをチェックする]** をクリックします。
-  ![更新プログラムをチェックする](/assets/images/help/dependabot/check-for-updates.png)
+## Viewing {% data variables.product.prodname_dependabot %} log files
+
+1. On the **{% data variables.product.prodname_dependabot %}** tab, click **Last checked *TIME* ago** to see the log file that {% data variables.product.prodname_dependabot %} generated during the last check for version updates.
+  ![View log file](/assets/images/help/dependabot/last-checked-link.png)
+2. Optionally, to rerun the version check, click **Check for updates**.
+  ![Check for updates](/assets/images/help/dependabot/check-for-updates.png)
diff --git a/translations/ja-JP/content/code-security/dependabot/index.md b/translations/ja-JP/content/code-security/dependabot/index.md
index c349d32515..757cd057ed 100644
--- a/translations/ja-JP/content/code-security/dependabot/index.md
+++ b/translations/ja-JP/content/code-security/dependabot/index.md
@@ -1,7 +1,7 @@
 ---
-title: Dependabot を使用してサプライ チェーンを安全に保つ
+title: Keeping your supply chain secure with Dependabot
 shortTitle: Dependabot
-intro: '{% data variables.product.prodname_dependabot %} を使って、プロジェクトで使用される依存関係の脆弱性を監視し{% ifversion fpt or ghec or ghes > 3.2 %}、依存関係を最新の状態に保ちます{% endif %}。'
+intro: 'Monitor vulnerabilities in dependencies used in your project{% ifversion fpt or ghec or ghes %} and keep your dependencies up-to-date{% endif %} with {% data variables.product.prodname_dependabot %}.'
 allowTitleToDifferFromFilename: true
 versions:
   fpt: '*'
@@ -19,11 +19,5 @@ children:
   - /dependabot-security-updates
   - /dependabot-version-updates
   - /working-with-dependabot
-ms.openlocfilehash: 82b385ab7177adfe568344c0dc04357ffafeb0b3
-ms.sourcegitcommit: 80842b4e4c500daa051eff0ccd7cde91c2d4bb36
-ms.translationtype: HT
-ms.contentlocale: ja-JP
-ms.lasthandoff: 09/12/2022
-ms.locfileid: '145124835'
 ---
 
diff --git a/translations/ja-JP/content/code-security/dependabot/working-with-dependabot/automating-dependabot-with-github-actions.md b/translations/ja-JP/content/code-security/dependabot/working-with-dependabot/automating-dependabot-with-github-actions.md
index 4d727384fd..05fcb40b26 100644
--- a/translations/ja-JP/content/code-security/dependabot/working-with-dependabot/automating-dependabot-with-github-actions.md
+++ b/translations/ja-JP/content/code-security/dependabot/working-with-dependabot/automating-dependabot-with-github-actions.md
@@ -6,7 +6,7 @@ miniTocMaxHeadingLevel: 3
 versions:
   fpt: '*'
   ghec: '*'
-  ghes: '>3.2'
+  ghes: '*'
   ghae: '*'
 type: how_to
 topics:
diff --git a/translations/ja-JP/content/code-security/dependabot/working-with-dependabot/index.md b/translations/ja-JP/content/code-security/dependabot/working-with-dependabot/index.md
index 75d9b73043..8216cae4a2 100644
--- a/translations/ja-JP/content/code-security/dependabot/working-with-dependabot/index.md
+++ b/translations/ja-JP/content/code-security/dependabot/working-with-dependabot/index.md
@@ -5,7 +5,7 @@ intro: '{% data variables.product.prodname_dependabot %} で発生した pull re
 versions:
   fpt: '*'
   ghec: '*'
-  ghes: '>3.2'
+  ghes: '*'
 topics:
   - Repositories
   - Dependabot
@@ -20,11 +20,11 @@ children:
   - /managing-encrypted-secrets-for-dependabot
   - /troubleshooting-the-detection-of-vulnerable-dependencies
   - /troubleshooting-dependabot-errors
-ms.openlocfilehash: ae4f4cd7f4f748487420c2804eae67d561455099
-ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.openlocfilehash: efab6caf0c9384c9e72cc5ed1fe64bd500cede45
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: ja-JP
-ms.lasthandoff: 09/10/2022
-ms.locfileid: '145125910'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148108959'
 ---
 
diff --git a/translations/ja-JP/content/code-security/dependabot/working-with-dependabot/keeping-your-actions-up-to-date-with-dependabot.md b/translations/ja-JP/content/code-security/dependabot/working-with-dependabot/keeping-your-actions-up-to-date-with-dependabot.md
index 2185172d64..d6ffb64685 100644
--- a/translations/ja-JP/content/code-security/dependabot/working-with-dependabot/keeping-your-actions-up-to-date-with-dependabot.md
+++ b/translations/ja-JP/content/code-security/dependabot/working-with-dependabot/keeping-your-actions-up-to-date-with-dependabot.md
@@ -1,6 +1,6 @@
 ---
-title: Dependabot でアクションを最新に保つ
-intro: '{% data variables.product.prodname_dependabot %} を使用して、使用するアクションを最新バージョンに更新しておくことができます。'
+title: Keeping your actions up to date with Dependabot
+intro: 'You can use {% data variables.product.prodname_dependabot %} to keep the actions you use updated to the latest versions.'
 redirect_from:
   - /github/administering-a-repository/keeping-your-actions-up-to-date-with-github-dependabot
   - /github/administering-a-repository/keeping-your-actions-up-to-date-with-dependabot
@@ -9,7 +9,7 @@ redirect_from:
 versions:
   fpt: '*'
   ghec: '*'
-  ghes: '>3.2'
+  ghes: '*'
 type: how_to
 topics:
   - Repositories
@@ -17,38 +17,33 @@ topics:
   - Version updates
   - Actions
 shortTitle: Auto-update actions
-ms.openlocfilehash: b7de2100ad191dbcb66f4853779e5f048ca33a84
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
-ms.translationtype: HT
-ms.contentlocale: ja-JP
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '146027964'
 ---
+
 {% data reusables.dependabot.beta-security-and-version-updates %}
 
 {% data reusables.dependabot.enterprise-enable-dependabot %}
 
-## {% data variables.product.prodname_dependabot_version_updates %} のアクションについて
+## About {% data variables.product.prodname_dependabot_version_updates %} for actions
 
-多くの場合、アクションはバグ修正と新機能で更新され、自動プロセスの信頼性、速度、安全性が向上しています。 {% data variables.product.prodname_actions %} に対して {% data variables.product.prodname_dependabot_version_updates %} を有効にすると、{% data variables.product.prodname_dependabot %} では、リポジトリの *workflow.yml* ファイル内のアクションへのリファレンスが最新の状態に保たれるようにします。 {% data variables.product.prodname_dependabot %} では、ファイル内のアクションごとに、アクションのリファレンス (通常、アクションに関連付けられているバージョン番号またはコミット ID) が最新バージョンと参照されます。 より新しいバージョンのアクションが使用可能な場合、{% data variables.product.prodname_dependabot %} によって、ワークフロー ファイル内のリファレンスを最新バージョンに更新する pull request が送信されます。 {% data variables.product.prodname_dependabot_version_updates %} について詳しくは、「[{% data variables.product.prodname_dependabot_version_updates %} について](/github/administering-a-repository/about-dependabot-version-updates)」を参照してください。 {% data variables.product.prodname_actions %} のワークフロー構成について詳しくは、「[{% data variables.product.prodname_actions %} を学ぶ](/actions/learn-github-actions)」を参照してください。
+Actions are often updated with bug fixes and new features to make automated processes more reliable, faster, and safer. When you enable {% data variables.product.prodname_dependabot_version_updates %} for {% data variables.product.prodname_actions %}, {% data variables.product.prodname_dependabot %} will help ensure that references to actions in a repository's *workflow.yml* file are kept up to date. For each action in the file, {% data variables.product.prodname_dependabot %} checks the action's reference (typically a version number or commit identifier associated with the action) against the latest version. If a more recent version of the action is available, {% data variables.product.prodname_dependabot %} will send you a pull request that updates the reference in the workflow file to the latest version. For more information about {% data variables.product.prodname_dependabot_version_updates %}, see "[About {% data variables.product.prodname_dependabot_version_updates %}](/github/administering-a-repository/about-dependabot-version-updates)." For more information about configuring workflows for {% data variables.product.prodname_actions %}, see "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)."
   
 {% data reusables.actions.workflow-runs-dependabot-note %}
 
-## {% data variables.product.prodname_dependabot_version_updates %} のアクションを有効化する
+## Enabling {% data variables.product.prodname_dependabot_version_updates %} for actions
 
-自分のアクションと、依存するライブラリとパッケージを維持するように {% data variables.product.prodname_dependabot_version_updates %} を構成できます。 
+You can configure {% data variables.product.prodname_dependabot_version_updates %} to maintain your actions as well as the libraries and packages you depend on. 
 
-1. 他のエコシステムまたはパッケージ マネージャーで既に {% data variables.product.prodname_dependabot_version_updates %} を有効にしている場合は、既存の *dependabot.yml* ファイルを開くだけです。 それ以外の場合、リポジトリの `.github` ディレクトリに *dependabot.yml* 構成ファイルを作成します。 詳しくは、「[Dependabot のバージョン アップデートの設定](/code-security/dependabot/dependabot-version-updates/configuring-dependabot-version-updates#enabling-dependabot-version-updates)」をご覧ください。
-1. `"github-actions"` を `package-ecosystem` として指定して監視します。
-1. `directory` を `"/"` に設定して、`.github/workflows` でワークフロー ファイルを確認します。
-1. `schedule.interval` を設定して、新しいバージョンを確認する頻度を指定します。
-{% data reusables.dependabot.check-in-dependabot-yml %} 既存のファイルを編集した場合は、変更を保存します。
+1. If you have already enabled {% data variables.product.prodname_dependabot_version_updates %} for other ecosystems or package managers, simply open the existing *dependabot.yml* file. Otherwise, create a *dependabot.yml* configuration file in the `.github` directory of your repository. For more information, see "[Configuring Dependabot version updates](/code-security/dependabot/dependabot-version-updates/configuring-dependabot-version-updates#enabling-dependabot-version-updates)."
+1. Specify `"github-actions"` as a `package-ecosystem` to monitor.
+1. Set the `directory` to `"/"` to check for workflow files in `.github/workflows`.
+1. Set a `schedule.interval` to specify how often to check for new versions.
+{% data reusables.dependabot.check-in-dependabot-yml %} If you have edited an existing file, save your changes.
 
-フォークで {% data variables.product.prodname_dependabot_version_updates %} を有効化することもできます。 詳細については、「[{% data variables.product.prodname_dependabot %} バージョンの更新の構成](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/enabling-and-disabling-dependabot-version-updates#enabling-version-updates-on-forks)」を参照してください。
+You can also enable {% data variables.product.prodname_dependabot_version_updates %} on forks. For more information, see "[Configuring {% data variables.product.prodname_dependabot %} version updates](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/enabling-and-disabling-dependabot-version-updates#enabling-version-updates-on-forks)."
 
-### {% data variables.product.prodname_actions %} の *dependabot.yml* ファイルの例
+### Example *dependabot.yml* file for {% data variables.product.prodname_actions %}
 
-次の *dependabot.yml* ファイルの例では、{% data variables.product.prodname_actions %} のバージョン更新を設定しています。 `.github/workflows` でワークフロー ファイルを確認するために、`directory` は `"/"` に設定する必要があります。 `schedule.interval` に `"daily"` が設定されています。 このファイルがチェックインまたは更新されると、{% data variables.product.prodname_dependabot %} はアクションの新しいバージョンをチェックします。 {% data variables.product.prodname_dependabot %} では、検出した期限切れのアクションに対してバージョン更新の pull request が生成されます。 初期バージョンの更新後、{% data variables.product.prodname_dependabot %} では 1 日 1 回、期限切れのバージョンのアクションを引き続き確認します。
+The example *dependabot.yml* file below configures version updates for {% data variables.product.prodname_actions %}. The `directory` must be set to `"/"` to check for workflow files in `.github/workflows`. The `schedule.interval` is set to `"weekly"`. After this file has been checked in or updated, {% data variables.product.prodname_dependabot %} checks for new versions of your actions. {% data variables.product.prodname_dependabot %} will raise pull requests for version updates for any outdated actions that it finds. After the initial version updates, {% data variables.product.prodname_dependabot %} will continue to check for outdated versions of actions once a week.
 
 ```yaml
 # Set update schedule for GitHub Actions
@@ -59,14 +54,14 @@ updates:
   - package-ecosystem: "github-actions"
     directory: "/"
     schedule:
-      # Check for updates to GitHub Actions every weekday
-      interval: "daily"
+      # Check for updates to GitHub Actions every week
+      interval: "weekly"
 ```
 
-## {% data variables.product.prodname_dependabot_version_updates %} のアクションを設定する
+## Configuring {% data variables.product.prodname_dependabot_version_updates %} for actions
 
-アクションに対して {% data variables.product.prodname_dependabot_version_updates %} を有効にする場合は、`package-ecosystem`、`directory`、`schedule.interval` の値を指定する必要があります。 バージョン更新をさらにカスタマイズするための設定オプションのプロパティは他にもたくさんあります。 詳細については、「[dependabot.yml ファイルの構成オプション](/github/administering-a-repository/configuration-options-for-dependency-updates)」を参照してください。
+When enabling {% data variables.product.prodname_dependabot_version_updates %} for actions, you must specify values for `package-ecosystem`, `directory`, and `schedule.interval`. There are many more optional properties that you can set to further customize your version updates. For more information, see "[Configuration options for the dependabot.yml file](/github/administering-a-repository/configuration-options-for-dependency-updates)."
 
-## 参考資料
+## Further reading
 
-- 「[GitHub Actions について](/actions/getting-started-with-github-actions/about-github-actions)」
+- "[About GitHub Actions](/actions/getting-started-with-github-actions/about-github-actions)"
diff --git a/translations/ja-JP/content/code-security/dependabot/working-with-dependabot/managing-encrypted-secrets-for-dependabot.md b/translations/ja-JP/content/code-security/dependabot/working-with-dependabot/managing-encrypted-secrets-for-dependabot.md
index 7b75165e76..d3c87a52e1 100644
--- a/translations/ja-JP/content/code-security/dependabot/working-with-dependabot/managing-encrypted-secrets-for-dependabot.md
+++ b/translations/ja-JP/content/code-security/dependabot/working-with-dependabot/managing-encrypted-secrets-for-dependabot.md
@@ -8,7 +8,7 @@ redirect_from:
 versions:
   fpt: '*'
   ghec: '*'
-  ghes: '>3.2'
+  ghes: '*'
 type: how_to
 topics:
   - Dependabot
diff --git a/translations/ja-JP/content/code-security/dependabot/working-with-dependabot/troubleshooting-dependabot-errors.md b/translations/ja-JP/content/code-security/dependabot/working-with-dependabot/troubleshooting-dependabot-errors.md
index 6e58e7a836..2c35207247 100644
--- a/translations/ja-JP/content/code-security/dependabot/working-with-dependabot/troubleshooting-dependabot-errors.md
+++ b/translations/ja-JP/content/code-security/dependabot/working-with-dependabot/troubleshooting-dependabot-errors.md
@@ -11,7 +11,7 @@ redirect_from:
 versions:
   fpt: '*'
   ghec: '*'
-  ghes: '>3.2'
+  ghes: '*'
 type: how_to
 topics:
   - Dependabot
diff --git a/translations/ja-JP/content/code-security/dependabot/working-with-dependabot/troubleshooting-the-detection-of-vulnerable-dependencies.md b/translations/ja-JP/content/code-security/dependabot/working-with-dependabot/troubleshooting-the-detection-of-vulnerable-dependencies.md
index 7974d9e6ee..725554270a 100644
--- a/translations/ja-JP/content/code-security/dependabot/working-with-dependabot/troubleshooting-the-detection-of-vulnerable-dependencies.md
+++ b/translations/ja-JP/content/code-security/dependabot/working-with-dependabot/troubleshooting-the-detection-of-vulnerable-dependencies.md
@@ -34,13 +34,13 @@ topics:
 *   {% data variables.product.prodname_advisory_database %} is one of the data sources that {% data variables.product.prodname_dotcom %} uses to identify vulnerable dependencies{% ifversion GH-advisory-db-supports-malware %} and malware{% endif %}. It's a free, curated database of security advisories for common package ecosystems on {% data variables.product.prodname_dotcom %}. It includes both data reported directly to {% data variables.product.prodname_dotcom %} from {% data variables.product.prodname_security_advisories %}, as well as official feeds and community sources. This data is reviewed and curated by {% data variables.product.prodname_dotcom %} to ensure that false or unactionable information is not shared with the development community. {% data reusables.security-advisory.link-browsing-advisory-db %}
 *   The dependency graph parses all known package manifest files in a user’s repository. For example, for npm it will parse the _package-lock.json_ file. It constructs a graph of all of the repository’s dependencies and public dependents. This happens when you enable the dependency graph and when anyone pushes to the default branch, and it includes commits that makes changes to a supported manifest format. For more information, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)" and "[Troubleshooting the dependency graph](/code-security/supply-chain-security/understanding-your-software-supply-chain/troubleshooting-the-dependency-graph)."
 *   {% data variables.product.prodname_dependabot %} scans any push, to the default branch, that contains a manifest file. When a new advisory is added, it scans all existing repositories and generates an alert for each repository that is affected. {% data variables.product.prodname_dependabot_alerts %} are aggregated at the repository level, rather than creating one alert per advisory. For more information, see "[About {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)."
-*   {% ifversion fpt or ghec or ghes > 3.2 %}{% data variables.product.prodname_dependabot_security_updates %} are triggered when you receive an alert about a vulnerable dependency in your repository. Where possible, {% data variables.product.prodname_dependabot %} creates a pull request in your repository to upgrade the vulnerable dependency to the minimum possible secure version needed to avoid the vulnerability. For more information, see "[About {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)" and "[Troubleshooting {% data variables.product.prodname_dependabot %} errors](/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors)."
+*   {% ifversion fpt or ghec or ghes %}{% data variables.product.prodname_dependabot_security_updates %} are triggered when you receive an alert about a vulnerable dependency in your repository. Where possible, {% data variables.product.prodname_dependabot %} creates a pull request in your repository to upgrade the vulnerable dependency to the minimum possible secure version needed to avoid the vulnerability. For more information, see "[About {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)" and "[Troubleshooting {% data variables.product.prodname_dependabot %} errors](/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors)."
   
     {% endif %}{% data variables.product.prodname_dependabot %} doesn't scan repositories on a schedule, but rather when something changes. For example, a scan is triggered when a new dependency is added ({% data variables.product.prodname_dotcom %} checks for this on every push), or when a new advisory is added to the database{% ifversion ghes or ghae %} and synchronized to {% data variables.location.product_location %}{% endif %}. For more information, see "[About {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies#detection-of-insecure-dependencies)."
 
 ## Do {% data variables.product.prodname_dependabot_alerts %} only relate to insecure dependencies in manifests and lockfiles?
 
-{% data variables.product.prodname_dependabot_alerts %} advise you about dependencies you should update, including transitive dependencies, where the version can be determined from a manifest or a lockfile. {% ifversion fpt or ghec or ghes > 3.2 %}{% data variables.product.prodname_dependabot_security_updates %} only suggest a change where {% data variables.product.prodname_dependabot %} can directly "fix" the dependency, that is, when these are:
+{% data variables.product.prodname_dependabot_alerts %} advise you about dependencies you should update, including transitive dependencies, where the version can be determined from a manifest or a lockfile. {% ifversion fpt or ghec or ghes %}{% data variables.product.prodname_dependabot_security_updates %} only suggest a change where {% data variables.product.prodname_dependabot %} can directly "fix" the dependency, that is, when these are:
 * Direct dependencies explicitly declared in a manifest or lockfile
 * Transitive dependencies declared in a lockfile{% endif %}
 
@@ -84,7 +84,7 @@ The {% data variables.product.prodname_dependabot_alerts %} count in {% data var
 **Check**: If there is a discrepancy in the totals you are seeing, check that you are not comparing alert numbers with dependency numbers. Also check that you are viewing all alerts and not a subset of filtered alerts.
 {% endif %}
 
-{% ifversion fpt or ghec or ghes > 3.2 %}
+{% ifversion fpt or ghec or ghes %}
 ## Can Dependabot ignore specific dependencies?
 
 You can configure {% data variables.product.prodname_dependabot %} to ignore specific dependencies in the configuration file, which will prevent security and version updates for those dependencies. If you only wish to use security updates, you will need to override the default behavior with a configuration file. For more information, see "[Overriding the default behavior with a configuration file](/code-security/dependabot/dependabot-security-updates/configuring-dependabot-security-updates#overriding-the-default-behavior-with-a-configuration-file)" to prevent version updates from being activated. For information about ignoring dependencies, see "[`ignore`](/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#ignore)."
@@ -95,5 +95,5 @@ You can configure {% data variables.product.prodname_dependabot %} to ignore spe
 - "[About {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)"
 - "[Viewing and updating {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts)"
 - "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)"
-- "[Troubleshooting the dependency graph](/code-security/supply-chain-security/understanding-your-software-supply-chain/troubleshooting-the-dependency-graph)"{% ifversion fpt or ghec or ghes > 3.2 %}
+- "[Troubleshooting the dependency graph](/code-security/supply-chain-security/understanding-your-software-supply-chain/troubleshooting-the-dependency-graph)"{% ifversion fpt or ghec or ghes %}
 - "[Troubleshooting {% data variables.product.prodname_dependabot %} errors](/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors)"{% endif %}
diff --git a/translations/ja-JP/content/code-security/getting-started/adding-a-security-policy-to-your-repository.md b/translations/ja-JP/content/code-security/getting-started/adding-a-security-policy-to-your-repository.md
index 0894245232..9c14fe91d4 100644
--- a/translations/ja-JP/content/code-security/getting-started/adding-a-security-policy-to-your-repository.md
+++ b/translations/ja-JP/content/code-security/getting-started/adding-a-security-policy-to-your-repository.md
@@ -1,6 +1,6 @@
 ---
-title: リポジトリへのセキュリティ ポリシーの追加
-intro: セキュリティポリシーをリポジトリに追加することによって、プロジェクト内のセキュリティ脆弱性を報告する方法の手順を示すことができます。
+title: Adding a security policy to your repository
+intro: You can give instructions for how to report a security vulnerability in your project by adding a security policy to your repository.
 redirect_from:
   - /articles/adding-a-security-policy-to-your-repository
   - /github/managing-security-vulnerabilities/adding-a-security-policy-to-your-repository
@@ -17,47 +17,49 @@ topics:
   - Repositories
   - Health
 shortTitle: Add a security policy
-ms.openlocfilehash: f081d6e6bd99f604e7e86bc094f76de9041adf4b
-ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
-ms.translationtype: HT
-ms.contentlocale: ja-JP
-ms.lasthandoff: 09/10/2022
-ms.locfileid: '145087630'
 ---
-## セキュリティポリシーについて
 
-プロジェクトのセキュリティ脆弱性を報告する手順をユーザーに示すには、{% ifversion fpt or ghes or ghec %} _SECURITY.md_ ファイルを、リポジトリのルート、`docs` フォルダー、または `.github` フォルダーに追加します。{% else %}_SECURITY.md_ ファイルを、リポジトリのルート、または `docs` フォルダーに追加します。{% endif %} だれかがリポジトリに Issue を作成すると、プロジェクトのセキュリティ ポリシーへのリンクが表示されます。
+## About security policies
+
+To give people instructions for reporting security vulnerabilities in your project,{% ifversion fpt or ghes or ghec %} you can add a _SECURITY.md_ file to your repository's root, `docs`, or `.github` folder.{% else %} you can add a _SECURITY.md_ file to your repository's root, or `docs` folder.{% endif %} When someone creates an issue in your repository, they will see a link to your project's security policy.
 
 {% ifversion not ghae %}
 <!-- no public repos in GHAE -->
-所属する Organization または個人アカウントにデフォルトのセキュリティ ポリシーを作成できます。 詳細については、「[既定のコミュニティ正常性ファイルの作成](/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file)」を参照してください。
+You can create a default security policy for your organization or personal account. For more information, see "[Creating a default community health file](/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file)."
 {% endif %}
 
 {% tip %}
 
-**ヒント:** セキュリティ ポリシーを検索しやすくするには、README ファイルなど、リポジトリ内の他の場所から _SECURITY.md_ にリンクします。 詳細については、「[README について](/articles/about-readmes)」を参照してください。
+**Tip:** To help people find your security policy, you can link to your _SECURITY.md_ file from other places in your repository, such as your README file. For more information, see "[About READMEs](/articles/about-readmes)."
 
 {% endtip %}
 
-{% ifversion fpt or ghec %} プロジェクトのセキュリティの脆弱性が報告された後は、{% data variables.product.prodname_security_advisories %} を使用して、脆弱性に関する情報を開示、修正、公開できます。 {% data variables.product.prodname_dotcom %} での脆弱性の報告と開示のプロセスに関する詳細については、「[セキュリティ脆弱性の調整された開示について](/code-security/security-advisories/about-coordinated-disclosure-of-security-vulnerabilities#about-reporting-and-disclosing-vulnerabilities-in-projects-on-github)」を参照してください。 {% data variables.product.prodname_security_advisories %} の詳細については、「[{% data variables.product.prodname_security_advisories %} について](/github/managing-security-vulnerabilities/about-github-security-advisories)」を参照してください。
+{% ifversion fpt or ghec %}
+After someone reports a security vulnerability in your project, you can use {% data variables.product.prodname_security_advisories %} to disclose, fix, and publish information about the vulnerability. For more information about the process of reporting and disclosing vulnerabilities in {% data variables.product.prodname_dotcom %}, see "[About coordinated disclosure of security vulnerabilities](/code-security/security-advisories/about-coordinated-disclosure-of-security-vulnerabilities#about-reporting-and-disclosing-vulnerabilities-in-projects-on-github)." For more information about repository security advisories, see "[About repository security advisories](/github/managing-security-vulnerabilities/about-github-security-advisories)."
 
-{% data reusables.repositories.github-security-lab %} {% endif %} {% ifversion ghes or ghae %}
+{% data reusables.repositories.github-security-lab %}
+{% endif %}
+{% ifversion ghes or ghae %}
 <!-- alternative to the content about GitHub Security Advisories in the dotcom article -->
-セキュリティの報告の指示を明確に利用できる要することで、ユーザがあなたの好むコミュニケーションチャンネルを使ってリポジトリで見つけたセキュリティ脆弱性を報告することを容易にできます。
+By making security reporting instructions clearly available, you make it easy for your users to report any security vulnerabilities they find in your repository using your preferred communication channel.
 {% endif %}
 
-## リポジトリへのセキュリティ ポリシーの追加
+## Adding a security policy to your repository
 
-{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %}
-3. 左側のサイドバーで、 **[セキュリティ ポリシー]** をクリックします。
-  ![[セキュリティ ポリシー] タブ](/assets/images/help/security/security-policy-tab.png)
-4. **[Start setup] (セットアップの開始)** をクリックします。
-  ![[セットアップの開始] ボタン](/assets/images/help/security/start-setup-security-policy-button.png)
-5. 新しい _SECURITY.md_ ファイルに、サポートされているバージョンのプロジェクトに関する情報と、脆弱性を報告する方法を追加します。
-{% data reusables.files.write_commit_message %} {% data reusables.files.choose-commit-email %} {% data reusables.files.choose_commit_branch %} {% data reusables.files.propose_file_change %}
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.sidebar-security %}
+3. In the left sidebar, click **Security policy**.
+  ![Security policy tab](/assets/images/help/security/security-policy-tab.png)
+4. Click **Start setup**.
+  ![Start setup button](/assets/images/help/security/start-setup-security-policy-button.png)
+5. In the new _SECURITY.md_ file, add information about supported versions of your project and how to report a vulnerability.
+{% data reusables.files.write_commit_message %}
+{% data reusables.files.choose-commit-email %}
+{% data reusables.files.choose_commit_branch %}
+{% data reusables.files.propose_file_change %}
 
-## 参考資料
+## Further reading
 
-- 「[リポジトリの保護](/code-security/getting-started/securing-your-repository)」{% ifversion not ghae %}
-- 「[健全なコントリビューションを促すプロジェクトをセットアップする](/communities/setting-up-your-project-for-healthy-contributions)」{% endif %}{% ifversion fpt or ghec %}
+- "[Securing your repository](/code-security/getting-started/securing-your-repository)"{% ifversion not ghae %}
+- "[Setting up your project for healthy contributions](/communities/setting-up-your-project-for-healthy-contributions)"{% endif %}{% ifversion fpt or ghec %}
 - [{% data variables.product.prodname_security %}]({% data variables.product.prodname_security_link %}){% endif %}
diff --git a/translations/ja-JP/content/code-security/getting-started/github-security-features.md b/translations/ja-JP/content/code-security/getting-started/github-security-features.md
index 5e7ed85861..081272149c 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
@@ -28,10 +28,10 @@ Make it easy for your users to confidentially report security vulnerabilities th
 {% ifversion fpt or ghec %}
 ### Security advisories
 
-Privately discuss and fix security vulnerabilities in your repository's code. You can then publish a security advisory to alert your community to the vulnerability and encourage community members to upgrade. For more information, see "[About {% data variables.product.prodname_security_advisories %}](/github/managing-security-vulnerabilities/about-github-security-advisories)."
+Privately discuss and fix security vulnerabilities in your repository's code. You can then publish a security advisory to alert your community to the vulnerability and encourage community members to upgrade. For more information, see "[About repository security advisories](/github/managing-security-vulnerabilities/about-github-security-advisories)."
 
 {% endif %}
-{% ifversion fpt or ghec or ghes > 3.2 %}
+{% ifversion fpt or ghec or ghes %}
 
 ### {% data variables.product.prodname_dependabot_alerts %} and security updates
 
@@ -39,7 +39,7 @@ View alerts about dependencies that are known to contain security vulnerabilitie
 and "[About {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)."
 {% endif %}
 
-{% ifversion ghes < 3.3 or ghae %}
+{% ifversion ghae %}
 ### {% data variables.product.prodname_dependabot_alerts %}
 
 {% data reusables.dependabot.dependabot-alerts-beta %}
@@ -47,7 +47,7 @@ and "[About {% data variables.product.prodname_dependabot_security_updates %}](/
 View alerts about dependencies that are known to contain security vulnerabilities, and manage these alerts. For more information, see "[About {% data variables.product.prodname_dependabot_alerts %}](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)."
 {% endif %}
 
-{% ifversion fpt or ghec or ghes > 3.2 %}
+{% ifversion fpt or ghec or ghes %}
 ### {% data variables.product.prodname_dependabot %} version updates
 
 Use {% data variables.product.prodname_dependabot %} to automatically raise pull requests to keep your dependencies up-to-date. This helps reduce your exposure to older versions of dependencies. Using newer versions makes it easier to apply patches if security vulnerabilities are discovered, and also makes it easier for {% data variables.product.prodname_dependabot_security_updates %} to successfully raise pull requests to upgrade vulnerable dependencies. For more information, see "[About {% data variables.product.prodname_dependabot_version_updates %}](/github/administering-a-repository/about-dependabot-version-updates)."
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 e00a81e612..63cff8ac9b 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
@@ -56,7 +56,7 @@ Dependency review is an {% data variables.product.prodname_advanced_security %}
 {% 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.location.product_location %} and you enable {% data variables.product.prodname_advanced_security %} for the organization (see below).{% endif %}
 
-{% ifversion fpt or ghec or ghes > 3.2 %}
+{% ifversion fpt or ghec or ghes %}
 ## Managing {% data variables.product.prodname_dependabot_security_updates %}
 
 For any repository that uses {% data variables.product.prodname_dependabot_alerts %}, you can enable {% data variables.product.prodname_dependabot_security_updates %} to raise pull requests with security updates when vulnerabilities are detected. You can also enable or disable {% data variables.product.prodname_dependabot_security_updates %} for all repositories across your organization.
@@ -123,9 +123,9 @@ For more information, see "[Managing security and analysis settings for your org
 {% 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
-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 {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts),"{% 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)."
+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 {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts),"{% endif %} {% ifversion fpt or ghec or ghes %}"[Managing pull requests for dependency updates](/code-security/supply-chain-security/managing-pull-requests-for-dependency-updates)," {% endif %}"[Managing {% data variables.product.prodname_code_scanning %} for your repository](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository)," and "[Managing alerts from {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/managing-alerts-from-secret-scanning)."
 
-{% ifversion fpt or ghec %}If you have a security vulnerability, you can create a security advisory to privately discuss and fix the vulnerability. For more information, see "[About {% data variables.product.prodname_security_advisories %}](/code-security/security-advisories/about-github-security-advisories)" and "[Creating a security advisory](/code-security/security-advisories/creating-a-security-advisory)."
+{% 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 repository security advisories](/code-security/security-advisories/about-github-security-advisories)" and "[Creating a security advisory](/code-security/security-advisories/creating-a-security-advisory)."
 {% endif %}
 
 {% ifversion ghes or ghec or ghae %}You{% elsif fpt %}Organizations that use {% data variables.product.prodname_ghe_cloud %}{% endif %} can view, filter, and sort security alerts for repositories owned by {% ifversion ghes or ghec or ghae %}your{% elsif fpt %}their{% endif %} organization in the security overview. For more information, see{% ifversion ghes or ghec or ghae %} "[About the security overview](/code-security/security-overview/about-the-security-overview)."{% elsif fpt %} "[About the security overview](/enterprise-cloud@latest/code-security/security-overview/about-the-security-overview)" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% 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 919f1b2fdd..3e84f7c163 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
@@ -86,8 +86,7 @@ Dependency review is a {% data variables.product.prodname_GH_advanced_security %
 
 {% endif %}
 
-
-{% ifversion fpt or ghec or ghes > 3.2 %}
+{% ifversion fpt or ghec or ghes %}
 
 ## Managing {% data variables.product.prodname_dependabot_security_updates %}
 
@@ -132,7 +131,7 @@ You can set up {% data variables.product.prodname_code_scanning %} to automatica
 {% 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 {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts),"{% 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)."
+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 {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts),"{% endif %} {% ifversion fpt or ghec or ghes %}"[Managing pull requests for dependency updates](/code-security/supply-chain-security/managing-pull-requests-for-dependency-updates)," {% endif %}"[Managing {% data variables.product.prodname_code_scanning %} for your repository](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository)," and "[Managing alerts from {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/managing-alerts-from-secret-scanning)."
 
-{% ifversion fpt or ghec %}If you have a security vulnerability, you can create a security advisory to privately discuss and fix the vulnerability. For more information, see "[About {% data variables.product.prodname_security_advisories %}](/code-security/security-advisories/about-github-security-advisories)" and "[Creating a security advisory](/code-security/security-advisories/creating-a-security-advisory)."
+{% 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 repository 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/ja-JP/content/code-security/index.md b/translations/ja-JP/content/code-security/index.md
index 7dc0f1030b..e9d02c2953 100644
--- a/translations/ja-JP/content/code-security/index.md
+++ b/translations/ja-JP/content/code-security/index.md
@@ -1,7 +1,7 @@
 ---
-title: コードセキュリティ
+title: Code security
 shortTitle: Code security
-intro: 'コードベースからシークレットや脆弱性を排除{% ifversion not ghae %}し、ソフトウェアサプライチェーンを管理{% endif %}する機能で、{% data variables.product.prodname_dotcom %}ワークフローにセキュリティを組み込んでください。'
+intro: 'Build security into your {% data variables.product.prodname_dotcom %} workflow with features to keep secrets and vulnerabilities out of your codebase{% ifversion not ghae %}, and to maintain your software supply chain{% endif %}.'
 introLinks:
   overview: /code-security/getting-started/github-security-features
 featuredLinks:
@@ -53,16 +53,10 @@ children:
   - /adopting-github-advanced-security-at-scale
   - /secret-scanning
   - /code-scanning
-  - /repository-security-advisories
+  - /security-advisories
   - /supply-chain-security
   - /dependabot
   - /security-overview
   - /guides
-ms.openlocfilehash: 90d3ad046a6531849edd8e783db265866f118d90
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
-ms.translationtype: HT
-ms.contentlocale: ja-JP
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147145240'
 ---
 
diff --git a/translations/ja-JP/content/code-security/repository-security-advisories/about-coordinated-disclosure-of-security-vulnerabilities.md b/translations/ja-JP/content/code-security/repository-security-advisories/about-coordinated-disclosure-of-security-vulnerabilities.md
deleted file mode 100644
index 722f0088cd..0000000000
--- a/translations/ja-JP/content/code-security/repository-security-advisories/about-coordinated-disclosure-of-security-vulnerabilities.md
+++ /dev/null
@@ -1,76 +0,0 @@
----
-title: セキュリティ脆弱性の調整された開示について
-intro: 脆弱性の開示は、セキュリティの報告者とリポジトリメンテナの調整された取り組みです。
-redirect_from:
-  - /code-security/security-advisories/about-coordinated-disclosure-of-security-vulnerabilities
-miniTocMaxHeadingLevel: 3
-versions:
-  fpt: '*'
-  ghec: '*'
-type: overview
-topics:
-  - Security advisories
-  - Vulnerabilities
-shortTitle: Coordinated disclosure
-ms.openlocfilehash: a5d4445525b46536cbfd3301cccb78140589de22
-ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
-ms.translationtype: HT
-ms.contentlocale: ja-JP
-ms.lasthandoff: 09/11/2022
-ms.locfileid: '145087581'
----
-## 業界における脆弱性の開示について
-
-{% data reusables.security-advisory.disclosing-vulnerabilities %}
-
-脆弱性の初期の報告は非公開で行われ、完全な詳細はメンテナが問題を認め、理想的には対策もしくはパッチが利用可能になり、場合によってはパッチがインストールできるようさらに時間をおいてから公開されます。 詳細については、OWASP Cheat Sheet Series (OWASP チート シート シリーズ) の Web サイトの [「OWASP Cheat Sheet Series」 (OWASP チート シート シリーズ) の「Vulnerability Disclosure」 (脆弱性の開示) ](https://cheatsheetseries.owasp.org/cheatsheets/Vulnerability_Disclosure_Cheat_Sheet.html#commercial-and-open-source-software)を参照してください。
-
-### 脆弱性報告者のためのベストプラクティス
-
-脆弱性をメンテナに非公開で報告するのは良いやり方です。 可能なら、脆弱性報告者は以下を避けることをおすすめします。
-- メンテナに対策の機会を与えることなく脆弱性を公開してしまうこと。
-- メンテナをバイパスしてしまうこと。
-- コードの修正バージョンが利用可能になる前に脆弱性を公開してしまうこと。
-- パブリックなバウンティプログラムが存在しない場合に、問題の報告に補償がなされると期待すること。
-
-メンテナに連絡を取ろうとしてレスポンスがなかったり、連絡は取れたものの公開をあまりに長く待つよう頼まれたなら、一定期間後に脆弱性報告者が脆弱性を公開することは許容できます。 
-
-脆弱性の報告者は、報告のプロセスの一部として、開示ポリシーの条件を明確に述べることをおすすめします。 脆弱性報告者が厳密なポリシーに従っていないばあいでも、意図的な脆弱性の開示の時期についてメンテナが明確な期待を持てるようにするのは良い考えです。 開示ポリシーの例については、GitHub Security Lab の Web サイトの「[Security Lab's disclosure policy](https://securitylab.github.com/advisories#policy)」 (Security Lab の開示ポリシー) を参照してください。
-
-### メンテナのためのベストプラクティス
-
-メンテナは、脆弱性の報告をいつどのように受けたいかを明確に示しておくのが良いでしょう。 この情報が明確に利用できない場合、脆弱性報告者はどのように連絡をすればいいか分からず、gitのコミット履歴から開発者のメールアドレスを取り出して適切なセキュリティに関する連絡先を見つけようとするかもしれません。 これは、不和、報告の喪失、未解決の報告の公開につながるかもしれません。
-
-メンテナは、適時に脆弱性を開示すべきです。 リポジトリにセキュリティ脆弱性があるなら、以下のようにすることをおすすめします。
-- 脆弱性は、レスポンスにおいても開示においても単純なバグとしてよりもセキュリティの問題として対処してください。 たとえば、リリースノートではその問題をセキュリティ脆弱性として明示的に言及する必要があります。
-- 脆弱性報告を受け取ったことは、たとえすぐに調査するためのリソースがない場合でも、できるだけ早く認めてください。 これはあなたが迅速に対応して行動するというメッセージを送ることになり、あなたと脆弱性報告者との間のそれ以外のやりとりに肯定的なトーンが設定されます。
-- 報告のインパクトと正確性を検証する際には、脆弱性報告者にも関わってもらってください。 おそらく脆弱性の報告者は、すでにその脆弱性を様々なシナリオの中で考慮するのに時間をかけているでしょう。その中には、あなたが自分では考えていなかったものがあるかもしれません。
-- 脆弱性の報告者が提供してくれた懸念点とアドバイスを慎重に考慮に入れて、適切と思われる方法で問題に対処してください。 脆弱性の報告者は、しばしば特定のコーナーケースや対処のバイパスに関する知識を持っており、それらはセキュリティ研究のバックグラウンドなしでは簡単に見逃してしまうものです。
-- 発見されたことを評価する際には、常に脆弱性の報告者に感謝を示してください。
-- できるかぎり早い修正の公開を目指してください。
-- 脆弱性を開示する際には、広汎なエコシステムがその問題と対策を認識するようにしてください。 認識されたセキュリティの問題がプロジェクトの現在の開発ブランチで修正されながら、そのコミットあるいはそれ以降のリリースがセキュリティ修正あるいはリリースとして明示的に示されていない場合が珍しくありません。 これによって、下流の利用者に問題が生じることがあります。
-
-セキュリティ脆弱性の詳細を開会しても、メンテナが悪く見えることはありません。 セキュリティ脆弱性はソフトウェアのあらゆるところに存在し、ユーザはコード中のセキュリティ脆弱性を開示するための明確な確立されたプロセスを持つメンテナを信頼します。
-
-## {% data variables.product.prodname_dotcom %}上のプロジェクトの脆弱性の報告と開示について
-
-{% data variables.product.prodname_dotcom_the_website %}上のプロジェクトの脆弱性の報告と開示のプロセスは以下のようになります。
-
- あなたが脆弱性の報告したいと考えている人（たとえばセキュリティ研究者）なら、まず関連するリポジトリにセキュリティポリシーがあるかをチェックしてください。 詳細については、「[セキュリティ ポリシーについて](/code-security/getting-started/adding-a-security-policy-to-your-repository#about-security-policies)」を参照してください。 セキュリティポリシーがあるなら、そのリポジトリのセキュリティチームに連絡する前に、それに従ってプロセスを理解してください。 
- 
- セキュリティポリシーがないなら、メンテナへの非公開のコミュニケーション方法を確立するための最も効率的な方法は、望ましいセキュリティの連絡先を尋ねるIssueを作成することです。 そのIssueはすぐに公に見ることができるようになるので、そこにはバグに関する情報は含めないようにするべきであることには注意してください。 コミュニケーションが確立できたら、将来的に利用できるよう、セキュリティポリシーを規定してもらうメンテナに提案できます。
-
-{% note %}
-
-**注**: _npm のみ_ - npm パッケージのマルウェアに関する報告を受けた場合は、お客様個人にご連絡させていただきます。 あなたが適時問題に対応しない場合、私たちはその問題を開示します。 詳細については、npm Docs の Web サイトの「[eporting malware in an npm package](https://docs.npmjs.com/reporting-malware-in-an-npm-package)」 (npm パッケージ内のマルウェアの報告) を参照してください。
-
-{% endnote %}
-
- {% data variables.product.prodname_dotcom_the_website %}でセキュリティ脆弱性を発見したら、私たちの調整された開示プロセスを通じてその脆弱性を報告してください。 詳細については、「[{% data variables.product.prodname_dotcom %} セキュリティ アドバイザリの概要](https://bounty.github.com/)」を参照してください。
-
- あなたがメンテナなら、リポジトリのセキュリティポリシーを設定するか、たとえばプロジェクトのREADMEファイルでセキュリティの報告方法を明確にしておくことによって、このパイプラインの開始時点からプロセスの所有権を取ることができます。 セキュリティ ポリシーの追加の詳細については、「[セキュリティ ポリシーについて](/code-security/getting-started/adding-a-security-policy-to-your-repository#about-security-policies)」を参照してください。 セキュリティポリシーがない場合、セキュリティの報告者はおそらくあなたにメールするか、非公開であなたに連絡しようとするでしょう。 あるいは、誰かがセキュリティの問題の詳細を含む（パブリックな）Issueをオープンするかもしれません。
-
- メンテナとしてコード中の脆弱性を開示するために、まずは{% data variables.product.prodname_dotcom %}でパッケージのリポジトリにドラフトのセキュリティアドバイザリを作成します。 {% data reusables.security-advisory.security-advisory-overview %} 詳細については、「[リポジトリの {% data variables.product.prodname_security_advisories %}について](/code-security/repository-security-advisories/about-github-security-advisories-for-repositories)」を参照してください。
-
-
- 開始するには、「[リポジトリ セキュリティ アドバイザリの作成](/code-security/repository-security-advisories/creating-a-repository-security-advisory)」を参照してください。
diff --git a/translations/ja-JP/content/code-security/repository-security-advisories/about-github-security-advisories-for-repositories.md b/translations/ja-JP/content/code-security/repository-security-advisories/about-github-security-advisories-for-repositories.md
deleted file mode 100644
index 5d7e7d4087..0000000000
--- a/translations/ja-JP/content/code-security/repository-security-advisories/about-github-security-advisories-for-repositories.md
+++ /dev/null
@@ -1,66 +0,0 @@
----
-title: リポジトリの GitHub セキュリティ アドバイザリについて
-intro: '{% data variables.product.prodname_security_advisories %} を使用して、リポジトリにおけるセキュリティの脆弱性に関する情報を非公開で議論、修正、公開できます。'
-redirect_from:
-  - /articles/about-maintainer-security-advisories
-  - /github/managing-security-vulnerabilities/about-maintainer-security-advisories
-  - /github/managing-security-vulnerabilities/about-github-security-advisories
-  - /code-security/security-advisories/about-github-security-advisories
-versions:
-  fpt: '*'
-  ghec: '*'
-type: overview
-topics:
-  - Security advisories
-  - Vulnerabilities
-  - CVEs
-shortTitle: Repository security advisories
-ms.openlocfilehash: 5c8ad99a2bee30f52a185fa15421bc6b23429fbf
-ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
-ms.translationtype: HT
-ms.contentlocale: ja-JP
-ms.lasthandoff: 09/10/2022
-ms.locfileid: '145087576'
----
-{% data reusables.repositories.security-advisory-admin-permissions %}
-
-{% data reusables.security-advisory.security-researcher-cannot-create-advisory %}
-
-## {% data variables.product.prodname_security_advisories %} について
-
-{% data reusables.security-advisory.disclosing-vulnerabilities %} 詳細については、「[セキュリティ脆弱性の調整された開示について](/code-security/repository-security-advisories/about-coordinated-disclosure-of-security-vulnerabilities)」を参照してください。
-
-{% data reusables.security-advisory.security-advisory-overview %}
-
-{% data variables.product.prodname_security_advisories %} では、次のことができます。
-
-1. セキュリティアドバイザリのドラフトを作成し、そのドラフトを用いて、プロジェクトに対する脆弱性の影響について非公開で議論します。 詳細については、「[リポジトリ セキュリティ アドバイザリの作成](/code-security/repository-security-advisories/creating-a-repository-security-advisory)」を参照してください。
-2. 一時的なプライベートフォークで、脆弱性を修正するため非公式でコラボレートします。
-3. パッチがリリースされたら、脆弱性のコミュニティに警告するため、セキュリティアドバイザリを公開してください。 詳細については、「[リポジトリ セキュリティ アドバイザリの公開](/code-security/repository-security-advisories/publishing-a-repository-security-advisory)」を参照してください。
-
-{% data reusables.repositories.security-advisories-republishing %}
-
-セキュリティアドバイザリに貢献した個人にクレジットを付与することができます。 詳細については、「[リポジトリ セキュリティ アドバイザリの編集](/code-security/repository-security-advisories/editing-a-repository-security-advisory#about-credits-for-security-advisories)」を参照してください。
-
-{% data reusables.repositories.security-guidelines %}
-
-セキュリティアドバイザリをリポジトリ中で作成した場合、そのセキュリティアドバイザリはリポジトリに残ります。 依存関係グラフによってサポートされる任意のエコシステムのセキュリティ アドバイザリを、[github.com/advisories](https://github.com/advisories) の {% data variables.product.prodname_advisory_database %} に公開しています。 {% data variables.product.prodname_advisory_database %} に公開されているアドバイザリに、だれでも変更を送信することができます。 詳細については、「[{% data variables.product.prodname_advisory_database %} のセキュリティ アドバイザリの編集](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/editing-security-advisories-in-the-github-advisory-database)」を参照してください。
-
-特にnpmに対するものであるセキュリティアドバイザリについては、npmセキュリティアドバイザリにも公開します。 詳細については、[npmjs.com/advisories](https://www.npmjs.com/advisories) を確認してください。
-
-{% data reusables.repositories.github-security-lab %}
-
-## CVE 識別番号
-
-{% data variables.product.prodname_security_advisories %} は、共通脆弱性識別子(CVE) リストに基づいています。 {% data variables.product.prodname_dotcom %}上のセキュリティアドバイザリフォームは、CVEの記述フォーマットにマッチする標準化されたフォームです。 
-
-{% data variables.product.prodname_dotcom %} は CVE Numbering Authority (CNA) であり、CVE 識別番号を割り当てる権限があります。 詳細については、CVE の Web サイトで、「[About CVE](https://www.cve.org/About/Overview)」 (CVE の概要)、および「[CVE Numbering Authorities](https://www.cve.org/ProgramOrganization/CNAs)」 (CVE の番号付け機関) を参照してください。
-
-{% data variables.product.prodname_dotcom %} でパブリックリポジトリのセキュリティアドバイザリを作成する場合、セキュリティの脆弱性に対する既存の CVE 識別番号を提供するオプションがあります。 {% data reusables.repositories.request-security-advisory-cve-id %}
-
-セキュリティアドバイザリを公開し、{% data variables.product.prodname_dotcom %} が CVE 識別番号を脆弱性に割り当てたら、{% data variables.product.prodname_dotcom %} は CVE を MITER データベースに公開します。
-詳細については、「[リポジトリ セキュリティ アドバイザリの公開](/code-security/repository-security-advisories/publishing-a-repository-security-advisory)」を参照してください。
-
-## 公開されたセキュリティアドバイザリの {% data variables.product.prodname_dependabot_alerts %}
-
-{% data reusables.repositories.github-reviews-security-advisories %}
diff --git a/translations/ja-JP/content/code-security/repository-security-advisories/adding-a-collaborator-to-a-repository-security-advisory.md b/translations/ja-JP/content/code-security/repository-security-advisories/adding-a-collaborator-to-a-repository-security-advisory.md
deleted file mode 100644
index c0a2741b68..0000000000
--- a/translations/ja-JP/content/code-security/repository-security-advisories/adding-a-collaborator-to-a-repository-security-advisory.md
+++ /dev/null
@@ -1,50 +0,0 @@
----
-title: リポジトリ セキュリティ アドバイザリへのコラボレータの追加
-intro: あなたと協力するセキュリティアドバイザリとして、ユーザや Team を追加できます。
-redirect_from:
-  - /articles/adding-a-collaborator-to-a-maintainer-security-advisory
-  - /github/managing-security-vulnerabilities/adding-a-collaborator-to-a-maintainer-security-advisory
-  - /github/managing-security-vulnerabilities/adding-a-collaborator-to-a-security-advisory
-  - /code-security/security-advisories/adding-a-collaborator-to-a-security-advisory
-versions:
-  fpt: '*'
-  ghec: '*'
-type: how_to
-topics:
-  - Security advisories
-  - Vulnerabilities
-  - Collaboration
-shortTitle: Add collaborators
-ms.openlocfilehash: 6fa4062fab8e4ffc59724ceb0ba3b6b536871df9
-ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
-ms.translationtype: HT
-ms.contentlocale: ja-JP
-ms.lasthandoff: 09/10/2022
-ms.locfileid: '147879136'
----
-セキュリティアドバイザリの管理者権限を持つユーザは、セキュリティアドバイザリにコラボレータを追加できます。
-
-{% data reusables.security-advisory.repository-level-advisory-note %}
-
-## セキュリティアドバイザリにコラボレータを追加する
-
-コラボレータは、セキュリティアドバイザリへの書き込み権限を持ちます。 詳細については、「[リポジトリ セキュリティ アドバイザリの権限レベル](/code-security/repository-security-advisories/permission-levels-for-repository-security-advisories)」を参照してください。
-
-{% note %}
-
-{% data reusables.repositories.security-advisory-collaborators-public-repositories %} セキュリティ アドバイザリのコラボレーターの削除に関する詳細については、「[リポジトリ セキュリティ アドバイザリからのコラボレータの削除](/code-security/repository-security-advisories/removing-a-collaborator-from-a-repository-security-advisory)」を参照してください。
-
-{% endnote %}
-
-{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %} {% data reusables.repositories.sidebar-advisories %}
-4. [Security Advisories] のリストから、コラボレータとして追加するセキュリティアドバイザリをクリックします。
-5. ページの右側にある、[Collaborators] の下で、セキュリティアドバイザリとして追加するユーザまたは Team の名前を入力します。
-  ![ユーザ名または Team 名を入力するフィールド](/assets/images/help/security/add-collaborator-field.png)
-6. **[追加]** をクリックします。
-  ![[追加] ボタン](/assets/images/help/security/security-advisory-add-collaborator-button.png)
-
-## 参考資料
-
-- 「[リポジトリ セキュリティ アドバイザリの権限レベル](/code-security/repository-security-advisories/permission-levels-for-repository-security-advisories)」
-- 「[一時的なプライベート フォークで、リポジトリのセキュリティ脆弱性を解決するためにコラボレートする](/code-security/repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability)」
-- 「[リポジトリ セキュリティ アドバイザリからのコラボレータの削除](/code-security/repository-security-advisories/removing-a-collaborator-from-a-repository-security-advisory)」。
diff --git a/translations/ja-JP/content/code-security/repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability.md b/translations/ja-JP/content/code-security/repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability.md
deleted file mode 100644
index 04f3744848..0000000000
--- a/translations/ja-JP/content/code-security/repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability.md
+++ /dev/null
@@ -1,90 +0,0 @@
----
-title: 一時的なプライベート フォークで、リポジトリのセキュリティ脆弱性を解決するためにコラボレートする
-intro: リポジトリにおけるセキュリティ脆弱性の修正について非公開でコラボレートするため、一時的なプライベートフォークを作成できます。
-redirect_from:
-  - /articles/collaborating-in-a-temporary-private-fork-to-resolve-a-security-vulnerability
-  - /github/managing-security-vulnerabilities/collaborating-in-a-temporary-private-fork-to-resolve-a-security-vulnerability
-  - /code-security/security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-security-vulnerability
-versions:
-  fpt: '*'
-  ghec: '*'
-type: how_to
-topics:
-  - Security advisories
-  - Vulnerabilities
-  - Collaboration
-  - Forks
-shortTitle: Temporary private forks
-ms.openlocfilehash: c03892c3ad1bd7345a7a066c9a9564858db4b84d
-ms.sourcegitcommit: ac00e2afa6160341c5b258d73539869720b395a4
-ms.translationtype: HT
-ms.contentlocale: ja-JP
-ms.lasthandoff: 09/09/2022
-ms.locfileid: '147878543'
----
-{% data reusables.security-advisory.repository-level-advisory-note %}
-
-## 前提条件
-
-一時的なプライベートフォークでコラボレートする前に、ドラフトのセキュリティアドバイザリを作成する必要があります。 詳細については、「[リポジトリ セキュリティ アドバイザリの作成](/code-security/repository-security-advisories/creating-a-repository-security-advisory)」を参照してください。
-
-## 一時的なプライベートフォークを作成する
-
-セキュリティアドバイザリに対する管理者権限があるユーザなら誰でも、一時的なプライベートフォークを作成できます。
-
-脆弱性についての情報を保護するため、CI を含むインテグレーションは、一時的なプライベートフォークにアクセスできません。
-
-{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %} {% data reusables.repositories.sidebar-advisories %}
-4. [Security Advisories] のリストから、一時的なプライベートフォークを作成するセキュリティアドバイザリをクリックします。
-  ![リスト内のセキュリティ アドバイザリ](/assets/images/help/security/security-advisory-in-list.png)
-5. **[新しい一時的なプライベートフォーク]** をクリックします。
-  ![[新しい一時的なプライベートフォーク] ボタン](/assets/images/help/security/new-temporary-private-fork-button.png)
-
-## 一時的なプライベートフォークにコラボレータを追加する
-
-セキュリティアドバイザリの管理者権限を持つユーザは、セキュリティアドバイザリにコラボレータを追加でき、セキュリティアドバイザリのコラボレータは一時的なプライベートフォークにアクセスできます。 詳細については、「[リポジトリ セキュリティ アドバイザリへのコラボレータの追加](/code-security/repository-security-advisories/adding-a-collaborator-to-a-repository-security-advisory)」を参照してください。
-
-## 一時的なプライベートフォークに変更を追加する
-
-セキュリティアドバイザリに対する管理者権限があるユーザなら誰でも、一時的なプライベートフォークに変更を追加できます。
-
-{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %} {% data reusables.repositories.sidebar-advisories %}
-4. [Security Advisories] のリストから、変更を追加するセキュリティアドバイザリをクリックします。
-  ![リスト内のセキュリティ アドバイザリ](/assets/images/help/security/security-advisory-in-list.png)
-5. {% data variables.product.product_name %} またはローカルに変更を追加します:
-   - {% data variables.product.product_name %} に変更を追加するには、[このアドバイザリに変更を追加する] で、 **[一時的なプライベート フォーク]** をクリックします。 そして、新しいブランチを作成し、ファイルを編集します。 詳細については、「[リポジトリ内でブランチを作成および削除する](/articles/creating-and-deleting-branches-within-your-repository)」および「[ファイルの編集](/repositories/working-with-files/managing-files/editing-files)」を参照してください。
-   - ローカルで変更を追加するには、「クローンを作成して新しいブランチを作成する」および「変更を加えてからプッシュする」の手順に従ってください。
-   ![[このアドバイザリに変更を追加する] ボックス](/assets/images/help/security/add-changes-to-this-advisory-box.png)
-
-## 一時的なプライベートフォークからプルリクエストを作成する
-
-セキュリティアドバイザリに対する書き込み権限があるユーザなら誰でも、一時的なプライベートフォークからプルリクエストを作成できます。
-
-{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %} {% data reusables.repositories.sidebar-advisories %}
-4. [Security Advisories] のリストから、セキュリティアドバイザリを作成するプルリクエストをクリックします。
-  ![リスト内のセキュリティ アドバイザリ](/assets/images/help/security/security-advisory-in-list.png)
-5. ブランチ名の右側にある **[比較と pull request]** をクリックします。
-  ![[比較と pull request] ボタン](/assets/images/help/security/security-advisory-compare-and-pr.png) {% data reusables.repositories.pr-title-description %} {% data reusables.repositories.create-pull-request %}
-
-{% data reusables.repositories.merge-all-pulls-together %} 詳細については、「[変更をセキュリティ アドバイザリにマージする](#merging-changes-in-a-security-advisory)」を参照してください。
-
-## 変更をセキュリティアドバイザリにマージする
-
-セキュリティアドバイザリに対する管理者権限があるユーザなら誰でも、セキュリティアドバイザリに変更をマージできます。
-
-{% data reusables.repositories.merge-all-pulls-together %}
-
-セキュリティアドバイザリの変更をマージするには、一時的なプライベートフォークにあるすべてのオープンされたプルリクエストがマージできる必要があります。 マージコンフリクトは許容されません。また、ブランチ保護の要件を満たす必要があります。 脆弱性についての情報を保護するため、一時的なプライベートフォークにあるプルリクエストに対しては、ステータスチェックは実行されません。 詳細については、「[保護されたブランチについて](/articles/about-protected-branches)」を参照してください。
-
-{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %} {% data reusables.repositories.sidebar-advisories %}
-4. [Security Advisories] のリストから、変更をマージするセキュリティアドバイザリをクリックします。
-  ![リスト内のセキュリティ アドバイザリ](/assets/images/help/security/security-advisory-in-list.png)
-5. 一時的なプライベート フォーク内にあるすべてのオープンされた pull request をマージするには、 **[pull requests をマージする]** をクリックします。
-  ![[pull request のマージ] ボタン](/assets/images/help/security/merge-pull-requests-button.png)
-
-セキュリティアドバイザリの変更をマージした後は、プロジェクトの以前のバージョンにある脆弱性についてコミュニティにアラートするため、セキュリティアドバイザリを公開できます。 詳細については、「[リポジトリ セキュリティ アドバイザリの公開](/code-security/repository-security-advisories/publishing-a-repository-security-advisory)」を参照してください。
-
-## 参考資料
-
-- 「[リポジトリ セキュリティ アドバイザリの権限レベル](/code-security/repository-security-advisories/permission-levels-for-repository-security-advisories)」
-- 「[リポジトリ セキュリティ アドバイザリの公開](/code-security/repository-security-advisories/publishing-a-repository-security-advisory)」
diff --git a/translations/ja-JP/content/code-security/repository-security-advisories/creating-a-repository-security-advisory.md b/translations/ja-JP/content/code-security/repository-security-advisories/creating-a-repository-security-advisory.md
deleted file mode 100644
index 187072360a..0000000000
--- a/translations/ja-JP/content/code-security/repository-security-advisories/creating-a-repository-security-advisory.md
+++ /dev/null
@@ -1,44 +0,0 @@
----
-title: リポジトリ セキュリティ アドバイザリの作成
-intro: セキュリティアドバイザリのドラフトを作成して、オープンソースプロジェクトのセキュリティ脆弱性について非公開で議論して修正することができます。
-redirect_from:
-  - /articles/creating-a-maintainer-security-advisory
-  - /github/managing-security-vulnerabilities/creating-a-maintainer-security-advisory
-  - /github/managing-security-vulnerabilities/creating-a-security-advisory
-  - /code-security/security-advisories/creating-a-security-advisory
-versions:
-  fpt: '*'
-  ghec: '*'
-type: how_to
-topics:
-  - Security advisories
-  - Vulnerabilities
-shortTitle: Create repository advisories
-ms.openlocfilehash: d4b47f84b20873e97b18106448b768288fff3039
-ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
-ms.translationtype: HT
-ms.contentlocale: ja-JP
-ms.lasthandoff: 09/10/2022
-ms.locfileid: '145119397'
----
-リポジトリに対する管理者権限があるユーザなら誰でも、セキュリティアドバイザリを作成できます。
-
-{% data reusables.security-advisory.security-researcher-cannot-create-advisory %}
-
-## セキュリティ アドバイザリの作成
-
-{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %} {% data reusables.repositories.sidebar-advisories %}
-4. **[セキュリティ アドバイザリの新しいドラフト]** をクリックします。
-  ![[アドバイザリのドラフトを開く] ボタン](/assets/images/help/security/security-advisory-new-draft-security-advisory-button.png)
-5. セキュリティアドバイザリのタイトルを入力します。
-{% data reusables.repositories.security-advisory-edit-details %} {% data reusables.repositories.security-advisory-edit-severity %} {% data reusables.repositories.security-advisory-edit-cwe-cve %} {% data reusables.repositories.security-advisory-edit-description %}
-11. **[セキュリティ アドバイザリのドラフトの作成]** をクリックします。
-  ![[セキュリティ アドバイザリの作成] ボタン](/assets/images/help/security/security-advisory-create-security-advisory-button.png)
-
-## 次の手順
-
-- セキュリティアドバイザリのドラフトにコメントして、チームと脆弱性について話し合います。
-- セキュリティアドバイザリにコラボレータを追加します。 詳細については、「[リポジトリ セキュリティ アドバイザリへのコラボレータの追加](/code-security/repository-security-advisories/adding-a-collaborator-to-a-repository-security-advisory)」を参照してください。
-- 一時的なプライベートフォークで、脆弱性を修正するため非公式でコラボレートします。 詳細については、「[一時的なプライベート フォークで、リポジトリのセキュリティ脆弱性を解決するためにコラボレートする](/code-security/repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability)」を参照してください。
-- セキュリティアドバイザリへの貢献に対してクレジットを受け取る必要がある個人を追加します。 詳細については、「[リポジトリ セキュリティ アドバイザリの編集](/code-security/repository-security-advisories/editing-a-repository-security-advisory#about-credits-for-security-advisories)」を参照してください。
-- コミュニティにセキュリティの脆弱性を知らせるため、セキュリティアドバイザリを公開します。 詳細については、「[リポジトリ セキュリティ アドバイザリの公開](/code-security/repository-security-advisories/publishing-a-repository-security-advisory)」を参照してください。
diff --git a/translations/ja-JP/content/code-security/repository-security-advisories/editing-a-repository-security-advisory.md b/translations/ja-JP/content/code-security/repository-security-advisories/editing-a-repository-security-advisory.md
deleted file mode 100644
index faa02ee4fd..0000000000
--- a/translations/ja-JP/content/code-security/repository-security-advisories/editing-a-repository-security-advisory.md
+++ /dev/null
@@ -1,48 +0,0 @@
----
-title: リポジトリ セキュリティ アドバイザリの編集
-intro: 詳細を更新したりエラーを修正したりする必要がある場合は、リポジトリ セキュリティ アドバイザリのメタデータと説明を編集できます。
-redirect_from:
-  - /github/managing-security-vulnerabilities/editing-a-security-advisory
-  - /code-security/security-advisories/editing-a-security-advisory
-versions:
-  fpt: '*'
-  ghec: '*'
-type: how_to
-topics:
-  - Security advisories
-  - Vulnerabilities
-shortTitle: Edit repository advisories
-ms.openlocfilehash: 2ea2f588374d83be677589b4f3bf4e74a7fc6e91
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
-ms.translationtype: HT
-ms.contentlocale: ja-JP
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '145119389'
----
-リポジトリ セキュリティ アドバイザリの管理者権限を持つユーザーは、セキュリティ アドバイザリを編集することができます。
-
-{% data reusables.security-advisory.repository-level-advisory-note %}
-
-## セキュリティアドバイザリのクレジットについて
-
-セキュリティの脆弱性の発見、報告、修正を支援してくれたユーザにクレジットを付与することができます。 ユーザにクレジットを付与すると、相手はそのクレジットを受け入れるか拒否するかを選択できます。
-
-相手がクレジットを受け入れると、そのユーザのユーザ名がセキュリティアドバイザリの [Credits] セクションに表示されます。 リポジトリへの読み取りアクセスを持つユーザは、アドバイザリとそれに対するクレジットを受け入れたユーザを確認することができます。
-
-セキュリティアドバイザリに自分がクレジットされるべきだと信じるなら、そのアドバイザリを作成した人物に連絡し、そのアドバイザリを編集してあなたへのクレジットを含めてもらうように頼んでください。 あなたをクレジットできるのはアドバイザリの作者だけなので、セキュリティアドバイザリでのクレジットについてはGitHub Supportに問い合わせないでください。
-
-## セキュリティアドバイザリを編集する
-
-{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %} {% data reusables.repositories.sidebar-advisories %}
-4. [Security Advisories] のリストから、編集するセキュリティアドバイザリをクリックします。
-5. セキュリティ アドバイザリの詳細の右上隅で、{% octicon "pencil" aria-label="The edit icon" %} をクリックします。
-  ![セキュリティ アドバイザリの [編集] ボタン](/assets/images/help/security/security-advisory-edit-button.png) {% data reusables.repositories.security-advisory-edit-details %} {% data reusables.repositories.security-advisory-edit-severity %} {% data reusables.repositories.security-advisory-edit-cwe-cve %} {% data reusables.repositories.security-advisory-edit-description %}
-11. 必要に応じて、セキュリティアドバイザリの [Credits] を編集します。
-  ![セキュリティ アドバイザリのクレジット](/assets/images/help/security/security-advisory-credits.png)
-12. **[セキュリティ アドバイザリの更新]** をクリックします。
-  ![[セキュリティ アドバイザリの更新] ボタン](/assets/images/help/security/update-advisory-button.png)
-13. [Credits] セクションに記載されているユーザは、クレジットを受け入れるように勧めるメールまたは Web 通知を受信します。 受け入れた場合、セキュリティアドバイザリが公開されると、そのユーザ名が公開されます。
-
-## 参考資料
-
-- 「[リポジトリ セキュリティ アドバイザリの撤回](/code-security/repository-security-advisories/withdrawing-a-repository-security-advisory)」
diff --git a/translations/ja-JP/content/code-security/repository-security-advisories/index.md b/translations/ja-JP/content/code-security/repository-security-advisories/index.md
deleted file mode 100644
index 04b515a465..0000000000
--- a/translations/ja-JP/content/code-security/repository-security-advisories/index.md
+++ /dev/null
@@ -1,36 +0,0 @@
----
-title: プロジェクトの脆弱性に関するリポジトリ セキュリティ アドバイザリの管理
-shortTitle: Repository security advisories
-intro: リポジトリ セキュリティ アドバイザリを利用したリポジトリ内のセキュリティ脆弱性に関する話し合い、修正、開示を行います。
-redirect_from:
-  - /articles/managing-security-vulnerabilities-in-your-project
-  - /github/managing-security-vulnerabilities/managing-security-vulnerabilities-in-your-project
-  - /code-security/security-advisories
-versions:
-  fpt: '*'
-  ghec: '*'
-topics:
-  - Security advisories
-  - Vulnerabilities
-  - Repositories
-  - CVEs
-children:
-  - /about-coordinated-disclosure-of-security-vulnerabilities
-  - /about-github-security-advisories-for-repositories
-  - /permission-levels-for-repository-security-advisories
-  - /creating-a-repository-security-advisory
-  - /adding-a-collaborator-to-a-repository-security-advisory
-  - /removing-a-collaborator-from-a-repository-security-advisory
-  - /collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability
-  - /publishing-a-repository-security-advisory
-  - /editing-a-repository-security-advisory
-  - /withdrawing-a-repository-security-advisory
-  - /best-practices-for-writing-repository-security-advisories
-ms.openlocfilehash: 43efe7ceaf307da4a8a7c02c45f744a4967b05b0
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
-ms.translationtype: HT
-ms.contentlocale: ja-JP
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '145119382'
----
-
diff --git a/translations/ja-JP/content/code-security/repository-security-advisories/permission-levels-for-repository-security-advisories.md b/translations/ja-JP/content/code-security/repository-security-advisories/permission-levels-for-repository-security-advisories.md
deleted file mode 100644
index c2431ee59d..0000000000
--- a/translations/ja-JP/content/code-security/repository-security-advisories/permission-levels-for-repository-security-advisories.md
+++ /dev/null
@@ -1,50 +0,0 @@
----
-title: リポジトリ セキュリティ アドバイザリの権限レベル
-intro: リポジトリ セキュリティ アドバイザリで実行できるアクションは、セキュリティ アドバイザリに対する管理者や書き込みの権限を持っているかどうかによって変わります。
-redirect_from:
-  - /articles/permission-levels-for-maintainer-security-advisories
-  - /github/managing-security-vulnerabilities/permission-levels-for-maintainer-security-advisories
-  - /github/managing-security-vulnerabilities/permission-levels-for-security-advisories
-  - /code-security/security-advisories/permission-levels-for-security-advisories
-versions:
-  fpt: '*'
-  ghec: '*'
-type: reference
-topics:
-  - Security advisories
-  - Vulnerabilities
-  - Permissions
-shortTitle: Permission levels
-ms.openlocfilehash: 9c2ad0d30b98b79786df09a224766bd826cb84f6
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
-ms.translationtype: HT
-ms.contentlocale: ja-JP
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '145119390'
----
-この記事は、リポジトリ レベルのセキュリティ アドバイザリのみを対象としています。 あらゆるユーザーは、[github.com/advisories](https://github.com/advisories) で、{% data variables.product.prodname_advisory_database %} のグローバル セキュリティ アドバイザリに貢献できます。 グローバル アドバイザリを編集しても、リポジトリでのアドバイザリの表示方法が変更されたり、影響を受けたりすることはありません。  詳細については、「[{% data variables.product.prodname_advisory_database %} のセキュリティ アドバイザリの編集](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/editing-security-advisories-in-the-github-advisory-database)」を参照してください。
-
-## アクセス許可の概要
-
-{% data reusables.repositories.security-advisory-admin-permissions %} セキュリティ アドバイザリへのコラボレーターの追加に関する詳細については、「[リポジトリ セキュリティ アドバイザリへのコラボレータの追加](/code-security/repository-security-advisories/adding-a-collaborator-to-a-repository-security-advisory)」を参照してください。
-
-アクション | Write 権限 | 管理者のアクセス許可 |
------- | ----------------- | ----------------- |
-セキュリティアドバイザリのドラフトを表示する | X | X |
-コラボレーターをセキュリティ アドバイザリに追加する (「[リポジトリ セキュリティ アドバイザリへのコラボレータの追加](/code-security/repository-security-advisories/adding-a-collaborator-to-a-repository-security-advisory)」を参照してください) | | X |
-セキュリティアドバイザリでコメントを編集および削除する | X | X |
-セキュリティ アドバイザリに一時的なプライベート フォークを作成する (「[一時的なプライベート フォークで、リポジトリのセキュリティ脆弱性を解決するためにコラボレートする](/code-security/repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability)」を参照してください) | | X |
-セキュリティ アドバイザリの一時的なプライベート フォークに変更を追加する (「[一時的なプライベート フォークで、リポジトリのセキュリティ脆弱性を解決するためにコラボレートする](/code-security/repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability)」を参照してください) | X | X |
-一時的なプライベート フォークに pull request を作成する (「[一時的なプライベート フォークで、リポジトリのセキュリティ脆弱性を解決するためにコラボレートする](/code-security/repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability)」を参照してください) | X | X |
-セキュリティ アドバイザリに変更をマージする (「[一時的なプライベート フォークで、リポジトリのセキュリティ脆弱性を解決するためにコラボレートする](/code-security/repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability)」を参照してください) | | X |
-メタデータをセキュリティ アドバイザリに追加して編集する (「[リポジトリ セキュリティ アドバイザリの公開](/code-security/repository-security-advisories/publishing-a-repository-security-advisory)」を参照してください) | X | X |
-セキュリティ アドバイザリのクレジットを追加および削除する (「[リポジトリ セキュリティ アドバイザリの編集](/code-security/repository-security-advisories/editing-a-repository-security-advisory)」を参照してください) | X | X |
-セキュリティアドバイザリのドラフトをクローズする | | X |
-セキュリティ アドバイザリを公開する (「[リポジトリ セキュリティ アドバイザリの公開](/code-security/repository-security-advisories/publishing-a-repository-security-advisory)」を参照してください) | | X |
-
-## 参考資料
-
-- 「[リポジトリ セキュリティ アドバイザリへのコラボレータの追加](/code-security/repository-security-advisories/adding-a-collaborator-to-a-repository-security-advisory)」
-- 「[一時的なプライベート フォークで、リポジトリのセキュリティ脆弱性を解決するためにコラボレートする](/code-security/repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability)」
-- 「[リポジトリ セキュリティ アドバイザリからのコラボレータの削除](/code-security/repository-security-advisories/removing-a-collaborator-from-a-repository-security-advisory)」
-- 「[リポジトリ セキュリティ アドバイザリの撤回](/code-security/repository-security-advisories/withdrawing-a-repository-security-advisory)」
diff --git a/translations/ja-JP/content/code-security/repository-security-advisories/publishing-a-repository-security-advisory.md b/translations/ja-JP/content/code-security/repository-security-advisories/publishing-a-repository-security-advisory.md
deleted file mode 100644
index 786ddf7660..0000000000
--- a/translations/ja-JP/content/code-security/repository-security-advisories/publishing-a-repository-security-advisory.md
+++ /dev/null
@@ -1,101 +0,0 @@
----
-title: リポジトリ セキュリティ アドバイザリの公開
-intro: プロジェクト内のセキュリティ脆弱性についてコミュニティにアラートするため、セキュリティアドバイザリを公開できます。
-redirect_from:
-  - /articles/publishing-a-maintainer-security-advisory
-  - /github/managing-security-vulnerabilities/publishing-a-maintainer-security-advisory
-  - /github/managing-security-vulnerabilities/publishing-a-security-advisory
-  - /code-security/security-advisories/publishing-a-security-advisory
-versions:
-  fpt: '*'
-  ghec: '*'
-type: how_to
-topics:
-  - Security advisories
-  - Vulnerabilities
-  - CVEs
-  - Repositories
-shortTitle: Publish repository advisories
-ms.openlocfilehash: f3e3bfdb6b44ec1c86bb903c66271b854f4fb041
-ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
-ms.translationtype: HT
-ms.contentlocale: ja-JP
-ms.lasthandoff: 09/10/2022
-ms.locfileid: '145119381'
----
-<!--Marketing-LINK: From /features/security/software-supply-chain page "Publishing a security advisory".-->
-
-セキュリティアドバイザリの管理者権限を持つユーザは、セキュリティアドバイザリを公開できます。
-
-{% data reusables.security-advisory.repository-level-advisory-note %}
-
-## 前提条件
-
-セキュリティアドバイザリを公開したり、CVE の ID 番号をリクエストしたりする前に、セキュリティアドバイザリのドラフトを作成し、セキュリティの脆弱性の影響を受けるプロジェクトのバージョンに関する情報を提供する必要があります。 詳細については、「[リポジトリ セキュリティ アドバイザリの作成](/code-security/repository-security-advisories/creating-a-repository-security-advisory)」を参照してください。
-
-セキュリティアドバイザリを作成したが、セキュリティの脆弱性が影響を与えるプロジェクトのバージョンに関する詳細をまだ入力していない場合は、セキュリティアドバイザリを編集できます。 詳細については、「[リポジトリ セキュリティ アドバイザリの編集](/code-security/repository-security-advisories/editing-a-repository-security-advisory)」を参照してください。
-
-## セキュリティアドバイザリの公開について
-
-セキュリティアドバイザリを公開すると、セキュリティアドバイザリが指定するセキュリティの脆弱性についてコミュニティに通知します。 セキュリティアドバイザリを公開すると、コミュニティがパッケージの依存関係を更新し、セキュリティの脆弱性の影響を調査しやすくなります。
-
-{% data reusables.repositories.security-advisories-republishing %}
-
-セキュリティアドバイザリを公開する前に、一時的なプライベートフォークで、脆弱性を修正するため非公式でコラボレートできます。 詳細については、「[一時的なプライベート フォークで、リポジトリのセキュリティ脆弱性を解決するためにコラボレートする](/code-security/repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability)」を参照してください。
-
-{% warning %}
-
-**警告**: 可能な限り、アドバイザリを公開する前に、セキュリティ アドバイザリに修正バージョンを追加する必要があります。 そうしない場合、アドバイザリは修正バージョンなしで公開され、{% data variables.product.prodname_dependabot %} は、更新する安全なバージョンを提供することなく、問題についてユーザに警告します。
-
-このような状況では、次のステップを行うことをお勧めします。
-
-- 修正バージョンが利用可能な場合、可能であれば、修正の準備ができたときに問題を開示するのを待ちます。
-- 修正バージョンが開発中でまだ利用できない場合は、アドバイザリにその旨を記載し、公開後にアドバイザリを編集します。
-- 問題を修正する予定がない場合は、ユーザが修正時期を問い合わせることがないよう、アドバイザリに明示します。 この場合、ユーザが問題を軽減するときに使えるステップを含めると便利です。
-
-{% endwarning %}
-
-パブリックリポジトリからドラフトアドバイザリを公開すると、すべてのユーザが次のことを確認できます。
-
-- アドバイザリデータの現在のバージョン。
-- クレジットされたユーザが受け入れたアドバイザリクレジット。
-  
-{% note %}
-
-**注**: 一般ユーザーは、アドバイザリの編集履歴にアクセスすることはできず、公開されたバージョンのみを見ることができます。
-
-{% endnote %}
-
-セキュリティアドバイザリの URL は、セキュリティアドバイザリの公開後も公開前と同じままです。 リポジトリへの読み取りアクセス権を持つユーザは、セキュリティアドバイザリを閲覧することができます。 セキュリティアドバイザリのコラボレータは、管理者権限を持つユーザがコラボレータをセキュリティアドバイザリから削除しない限り、セキュリティアドバイザリでコメントストリーム全体を含む過去の会話を引き続き表示できます。 
-
-公開したセキュリティアドバイザリの情報をアップデートまたは修正する必要がある場合は、セキュリティアドバイザリを編集できます。 詳細については、「[リポジトリ セキュリティ アドバイザリの編集](/code-security/repository-security-advisories/editing-a-repository-security-advisory)」を参照してください。
-
-## セキュリティアドバイザリを公開する
-
-セキュリティアドバイザリを公開すると、セキュリティアドバイザリの一時的なプライベートフォークが削除されます。
-
-{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %} {% data reusables.repositories.sidebar-advisories %}
-4. [Security Advisories] のリストから、公開するセキュリティアドバイザリをクリックします。
-  ![リスト内のセキュリティ アドバイザリ](/assets/images/help/security/security-advisory-in-list.png)
-5. ページの下部にある **[アドバイザリの公開]** をクリックします。
-  ![[アドバイザリの公開] ボタン](/assets/images/help/security/publish-advisory-button.png)
-  
-## 公開されたセキュリティアドバイザリの {% data variables.product.prodname_dependabot_alerts %}
-
-{% data reusables.repositories.github-reviews-security-advisories %}
-
-## CVE 識別番号をリクエストする (省略可能)
-
-{% data reusables.repositories.request-security-advisory-cve-id %} 詳細については、「[リポジトリの {% data variables.product.prodname_security_advisories %} について](/code-security/repository-security-advisories/about-github-security-advisories-for-repositories#cve-identification-numbers)」を参照してください。
-
-{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %} {% data reusables.repositories.sidebar-advisories %}
-4. [Security Advisories] のリストから、CVE 識別番号をリクエストするセキュリティアドバイザリをクリックします。
-  ![リスト内のセキュリティ アドバイザリ](/assets/images/help/security/security-advisory-in-list.png)
-5. **[アドバイザリの公開]** ドロップダウン メニューを使用して、 **[CVE の要求]** をクリックします。
-  ![ドロップダウンの [CVE の要求]](/assets/images/help/security/security-advisory-drop-down-request-cve.png)
-6. **[CVE の要求]** をクリックします。
-  ![[CVE の要求] ボタン](/assets/images/help/security/security-advisory-request-cve-button.png)
-
-## 参考資料
-
-- 「[リポジトリ セキュリティ アドバイザリの撤回](/code-security/repository-security-advisories/withdrawing-a-repository-security-advisory)」
diff --git a/translations/ja-JP/content/code-security/repository-security-advisories/removing-a-collaborator-from-a-repository-security-advisory.md b/translations/ja-JP/content/code-security/repository-security-advisories/removing-a-collaborator-from-a-repository-security-advisory.md
deleted file mode 100644
index db0429345e..0000000000
--- a/translations/ja-JP/content/code-security/repository-security-advisories/removing-a-collaborator-from-a-repository-security-advisory.md
+++ /dev/null
@@ -1,42 +0,0 @@
----
-title: リポジトリ セキュリティ アドバイザリからのコラボレータの削除
-intro: リポジトリ セキュリティ アドバイザリからコラボレーターを削除すると、そのコラボレーターはセキュリティ アドバイザリのディスカッションとメタデータへの読み取りおよび書き込みアクセス権を失います。
-redirect_from:
-  - /github/managing-security-vulnerabilities/removing-a-collaborator-from-a-security-advisory
-  - /code-security/security-advisories/removing-a-collaborator-from-a-security-advisory
-versions:
-  fpt: '*'
-  ghec: '*'
-type: how_to
-topics:
-  - Security advisories
-  - Vulnerabilities
-  - Collaboration
-shortTitle: Remove collaborators
-ms.openlocfilehash: ced0edd0614304c0d33ddd40dce3c6a24a9ffcfd
-ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
-ms.translationtype: HT
-ms.contentlocale: ja-JP
-ms.lasthandoff: 09/10/2022
-ms.locfileid: '145119358'
----
-セキュリティアドバイザリの管理者権限を持つユーザは、セキュリティアドバイザリからコラボレータを削除できます。
-
-{% data reusables.security-advisory.repository-level-advisory-note %}
-
-## セキュリティアドバイザリからコラボレータを削除する
-
-{% data reusables.repositories.security-advisory-collaborators-public-repositories %}
-
-{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %} {% data reusables.repositories.sidebar-advisories %}
-4. [Security Advisories] のリストから、コラボレータを削除するセキュリティアドバイザリをクリックします。
-  ![リスト内のセキュリティ アドバイザリ](/assets/images/help/security/security-advisory-in-list.png)
-5. ページの右側にある、[Collaborators] の下で、セキュリティアドバイザリから削除するユーザまたは Team の名前を探します。
-  ![セキュリティ アドバイザリのコラボレータ](/assets/images/help/security/security-advisory-collaborator.png)
-6. 削除するコラボレーターの横にある **[X]** アイコンをクリックします。
-  ![セキュリティ アドバイザリからコラボレータを削除する [X] アイコン](/assets/images/help/security/security-advisory-remove-collaborator-x.png)
-
-## 参考資料
-
-- 「[リポジトリ セキュリティ アドバイザリの権限レベル](/code-security/repository-security-advisories/permission-levels-for-repository-security-advisories)」
-- 「[リポジトリ セキュリティ アドバイザリへのコラボレータの追加](/code-security/repository-security-advisories/adding-a-collaborator-to-a-repository-security-advisory)」
diff --git a/translations/ja-JP/content/code-security/repository-security-advisories/withdrawing-a-repository-security-advisory.md b/translations/ja-JP/content/code-security/repository-security-advisories/withdrawing-a-repository-security-advisory.md
deleted file mode 100644
index 2c3377b904..0000000000
--- a/translations/ja-JP/content/code-security/repository-security-advisories/withdrawing-a-repository-security-advisory.md
+++ /dev/null
@@ -1,28 +0,0 @@
----
-title: リポジトリ セキュリティ アドバイザリの撤回
-intro: 公開したリポジトリ セキュリティ アドバイザリを撤回できます。
-redirect_from:
-  - /github/managing-security-vulnerabilities/withdrawing-a-security-advisory
-  - /code-security/security-advisories/withdrawing-a-security-advisory
-versions:
-  fpt: '*'
-  ghec: '*'
-type: how_to
-topics:
-  - Security advisories
-  - Vulnerabilities
-shortTitle: Withdraw repository advisories
-ms.openlocfilehash: 1d85afddaadbd25c5b24ab945dac998b7842ae23
-ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
-ms.translationtype: HT
-ms.contentlocale: ja-JP
-ms.lasthandoff: 09/10/2022
-ms.locfileid: '145119326'
----
-{% data reusables.security-advisory.repository-level-advisory-note %}
-
-誤ってセキュリティアドバイザリを公開した場合は、{% data variables.contact.contact_support %} に連絡するとセキュリティアドバイザリを撤回できます。
-
-## 参考資料
-
-- 「[リポジトリ セキュリティ アドバイザリの編集](/code-security/repository-security-advisories/editing-a-repository-security-advisory)」
diff --git a/translations/ja-JP/content/code-security/secret-scanning/about-secret-scanning.md b/translations/ja-JP/content/code-security/secret-scanning/about-secret-scanning.md
index b9dce9457c..f1c959c882 100644
--- a/translations/ja-JP/content/code-security/secret-scanning/about-secret-scanning.md
+++ b/translations/ja-JP/content/code-security/secret-scanning/about-secret-scanning.md
@@ -110,6 +110,6 @@ monitor results from {% data variables.product.prodname_secret_scanning %} acros
 - "[Keeping your account and data secure](/github/authenticating-to-github/keeping-your-account-and-data-secure)"
 {%- ifversion fpt or ghec %}
 - "[Managing encrypted secrets for your codespaces](/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces)"{% endif %}
-{%- ifversion fpt or ghec or ghes > 3.2 %}
+{%- ifversion fpt or ghec or ghes %}
 - "[Managing encrypted secrets for Dependabot](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/managing-encrypted-secrets-for-dependabot)"{% endif %}
 - "[Encrypted secrets](/actions/security-guides/encrypted-secrets)"
diff --git a/translations/ja-JP/content/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning.md b/translations/ja-JP/content/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning.md
index 03bf9dd95a..3b0a2bf172 100644
--- a/translations/ja-JP/content/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning.md
+++ b/translations/ja-JP/content/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning.md
@@ -15,35 +15,12 @@ topics:
   - Secret scanning
 ---
 
-{% ifversion ghes < 3.3 %}
-{% note %}
-
-**Note:** Custom patterns for {% data variables.product.prodname_secret_scanning %} is currently in beta and is subject to change.
-
-{% endnote %}
-{% endif %}
 
 ## About custom patterns for {% data variables.product.prodname_secret_scanning %}
 
 You can define custom patterns to identify secrets that are not detected by the default patterns supported by {% data variables.product.prodname_secret_scanning %}. For example, you might have a secret pattern that is internal to your organization. For details of the supported secrets and service providers, see "[{% data variables.product.prodname_secret_scanning_caps %} patterns](/code-security/secret-scanning/secret-scanning-patterns)."
 
-You can define custom patterns for your enterprise, organization, or repository. {% data variables.product.prodname_secret_scanning_caps %} supports up to 
-{%- ifversion fpt or ghec or ghes > 3.3 or ghae > 3.3 %} 500 custom patterns for each organization or enterprise account, and up to 100 custom patterns per repository.
-{%- elsif ghes = 3.2 %} 20 custom patterns for each organization or enterprise account, and per repository.
-{%- else %} 100 custom patterns for each organization or enterprise account, and 20 per repository.
-{%- endif %}
-
-{% ifversion ghes < 3.3 %}
-{% note %}
-
-**Note:** During the beta, there are some limitations when using custom patterns for {% data variables.product.prodname_secret_scanning %}:
-
-* There is no dry-run functionality.
-* You cannot edit custom patterns after they're created. To change a pattern, you must delete it and recreate it.
-* There is no API for creating, editing, or deleting custom patterns. However, results for custom patterns are returned in the [secret scanning alerts API](/rest/reference/secret-scanning).
-
-{% endnote %}
-{% endif %}
+You can define custom patterns for your enterprise, organization, or repository. {% data variables.product.prodname_secret_scanning_caps %} supports up to 500 custom patterns for each organization or enterprise account, and up to 100 custom patterns per repository.
 
 ## Regular expression syntax for custom patterns
 
@@ -160,7 +137,7 @@ Before defining a custom pattern, you must ensure that you enable secret scannin
 1. Under "Code security and analysis", click **Security features**.{% else %}
 {% data reusables.enterprise-accounts.advanced-security-policies %}
 {% data reusables.enterprise-accounts.advanced-security-security-features %}{% endif %}
-1. Under "Secret scanning custom patterns", click {% ifversion ghes = 3.2 %}**New custom pattern**{% else %}**New pattern**{% endif %}.
+1. Under "Secret scanning custom patterns", click **New pattern**.
 {% data reusables.advanced-security.secret-scanning-add-custom-pattern-details %}
 {%- ifversion secret-scanning-custom-enterprise-36 or custom-pattern-dry-run-ga %}
 1. When you're ready to test your new custom pattern, to identify matches in the enterprise without creating alerts, click **Save and dry run**.
@@ -172,7 +149,6 @@ Before defining a custom pattern, you must ensure that you enable secret scannin
 
 After your pattern is created, {% data variables.product.prodname_secret_scanning %} scans for any secrets in repositories within your enterprise's organizations with {% data variables.product.prodname_GH_advanced_security %} enabled, including their entire Git history on all branches. Organization owners and repository administrators will be alerted to any secrets found, and can review the alert in the repository where the secret is found. For more information on viewing {% data variables.product.prodname_secret_scanning %} alerts, see "[Managing alerts from {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/managing-alerts-from-secret-scanning)."
 
-{% ifversion fpt or ghes > 3.2 or ghec or ghae %}
 ## Editing a custom pattern
 
 When you save a change to a custom pattern, this closes all the {% data variables.product.prodname_secret_scanning %} alerts that were created using the previous version of the pattern.
@@ -184,7 +160,6 @@ When you save a change to a custom pattern, this closes all the {% data variable
 3. When you're ready to test your edited custom pattern, to identify matches without creating alerts, click **Save and dry run**.
 {%- endif %}
 4. When you have reviewed and tested your changes, click **Save changes**.
-{% endif %}
 
 ## Removing a custom pattern
 
@@ -192,13 +167,8 @@ When you save a change to a custom pattern, this closes all the {% data variable
 
    * For a repository or organization, display the "Security & analysis" settings for the repository or organization where the custom pattern was created. For more information, see "[Defining a custom pattern for a repository](#defining-a-custom-pattern-for-a-repository)" or "[Defining a custom pattern for an organization](#defining-a-custom-pattern-for-an-organization)" above.
    * For an enterprise, under "Policies" display the "Advanced Security" area, and then click **Security features**.  For more information, see "[Defining a custom pattern for an enterprise account](#defining-a-custom-pattern-for-an-enterprise-account)" above.
-{%- ifversion ghec or ghes > 3.2 or ghae %}
 1. To the right of the custom pattern you want to remove, click {% octicon "trash" aria-label="The trash icon" %}.
 1. Review the confirmation, and select a method for dealing with any open alerts relating to the custom pattern.
 1. Click **Yes, delete this pattern**.
 
-   ![Confirming deletion of a custom {% data variables.product.prodname_secret_scanning %} pattern ](/assets/images/help/repository/secret-scanning-confirm-deletion-custom-pattern.png)
-{%- elsif ghes = 3.2 %}
-1. To the right of the custom pattern you want to remove, click **Remove**.
-1. Review the confirmation, and click **Remove custom pattern**.
-{%- endif %}
+   ![Confirming deletion of a custom {% data variables.product.prodname_secret_scanning %} pattern ](/assets/images/help/repository/secret-scanning-confirm-deletion-custom-pattern.png)
\ No newline at end of file
diff --git a/translations/ja-JP/content/code-security/secret-scanning/protecting-pushes-with-secret-scanning.md b/translations/ja-JP/content/code-security/secret-scanning/protecting-pushes-with-secret-scanning.md
index e7ef382b5d..78b23e2fe1 100644
--- a/translations/ja-JP/content/code-security/secret-scanning/protecting-pushes-with-secret-scanning.md
+++ b/translations/ja-JP/content/code-security/secret-scanning/protecting-pushes-with-secret-scanning.md
@@ -137,4 +137,4 @@ If you confirm a secret is real and that you intend to fix it later, you should
 
 1. Click **Allow secret**.
 
-{% endif %}
\ No newline at end of file
+{% endif %}
diff --git a/translations/ja-JP/content/code-security/security-overview/about-the-security-overview.md b/translations/ja-JP/content/code-security/security-overview/about-the-security-overview.md
index 69e55a8adc..c763b80753 100644
--- a/translations/ja-JP/content/code-security/security-overview/about-the-security-overview.md
+++ b/translations/ja-JP/content/code-security/security-overview/about-the-security-overview.md
@@ -67,17 +67,23 @@ The security overview displays active alerts raised by security features. If the
 
 At the organization-level, the security overview displays aggregate and repository-specific security information for repositories owned by your organization. You can filter information by security features at the organization-level.
 
+Organization owners and security managers for organizations have access to the organization-level security overview. {% ifversion ghec or ghes > 3.6 or ghae > 3.6 %}Organization members can access the organization-level security overview to view results for repositories where they have admin privileges or have been granted access to security alerts. For more information on managing security alert access, see "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)".{% endif %}
+
 {% ifversion ghec or ghes > 3.4 or ghae > 3.4 %}
 ### About the enterprise-level security overview
 At the enterprise-level, the security overview displays aggregate and repository-specific security information for your enterprise. You can view repositories owned by your enterprise that have security alerts, view all security alerts, or security feature-specific alerts from across your enterprise.
 
-Organization owners and security managers for organizations in your enterprise also have limited access to the enterprise-level security overview. They can only view repositories and alerts for the organizations that they have full access to.
+Organization owners and security managers for organizations in your enterprise have access to the enterprise-level security overview. They can view repositories and alerts for the organizations that they have full access to.
+
+Enterprise owners can only see alerts for organizations that they are an owner or a security manager of.{% ifversion ghec or ghes > 3.5 or ghae > 3.5 %} Enterprise owners can join an organization as an organization owner to see all of its alerts in the enterprise-level security overview. For more information, see "[Managing your role in an organization owned by your enterprise](/admin/user-management/managing-organizations-in-your-enterprise/managing-your-role-in-an-organization-owned-by-your-enterprise)."{% endif %}
 
 {% elsif fpt %}
 ### About the enterprise-level security overview
 At the enterprise-level, the security overview displays aggregate and repository-specific information for an enterprise. For more information, see "[About the enterprise-level security overview](/enterprise-cloud@latest/code-security/security-overview/about-the-security-overview#about-the-enterprise-level-security-overview)" in the {% data variables.product.prodname_ghe_cloud %} documentation.
 {% endif %}
 
+{% ifversion ghes < 3.7 or ghae < 3.7 %}
 ### About the team-level security overview
 At the team-level, the security overview displays repository-specific security information for repositories that the team has admin privileges for. For more information, see "[Managing team access to an organization repository](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository)."
 {% endif %}
+{% endif %}
diff --git a/translations/ja-JP/content/code-security/supply-chain-security/end-to-end-supply-chain/securing-code.md b/translations/ja-JP/content/code-security/supply-chain-security/end-to-end-supply-chain/securing-code.md
index 882ad462dc..28d368418f 100644
--- a/translations/ja-JP/content/code-security/supply-chain-security/end-to-end-supply-chain/securing-code.md
+++ b/translations/ja-JP/content/code-security/supply-chain-security/end-to-end-supply-chain/securing-code.md
@@ -47,7 +47,7 @@ As a first step, you want to make a complete inventory of your dependencies. The
 
 ### Automatic detection of vulnerabilities in dependencies
 
-{% data variables.product.prodname_dependabot %} can help you by monitoring your dependencies and notifying you when they contain a known vulnerability. {% ifversion fpt or ghec or ghes > 3.2 %}You can even enable {% data variables.product.prodname_dependabot %} to automatically raise pull requests that update the dependency to a secure version.{% endif %} For more information, see "[About {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)"{% ifversion fpt or ghec or ghes > 3.2 %} and "[About Dependabot security updates](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-dependabot-security-updates)"{% endif %}.
+{% data variables.product.prodname_dependabot %} can help you by monitoring your dependencies and notifying you when they contain a known vulnerability. {% ifversion fpt or ghec or ghes %}You can even enable {% data variables.product.prodname_dependabot %} to automatically raise pull requests that update the dependency to a secure version.{% endif %} For more information, see "[About {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)"{% ifversion fpt or ghec or ghes %} and "[About Dependabot security updates](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-dependabot-security-updates)"{% endif %}.
 
 ### Assessment of exposure to risk from a vulnerable dependency
 
@@ -81,15 +81,13 @@ If your organization uses {% data variables.product.prodname_GH_advanced_securit
 You can configure {% data variables.product.prodname_secret_scanning %} to check for secrets issued by many service providers and to notify you when any are detected. You can also define custom patterns to detect additional secrets at the repository, organization, or enterprise level. For more information, see "[About secret scanning](/code-security/secret-scanning/about-secret-scanning)" and "[Secret scanning patterns](/code-security/secret-scanning/secret-scanning-patterns)."
 {% endif %}
 
-{% ifversion fpt or ghec or ghes > 3.2 or ghae %}
 ### Secure storage of secrets you use in {% data variables.product.product_name %}
-{% endif %}
 
 {% ifversion fpt or ghec %}
 Besides your code, you probably need to use secrets in other places. For example, to allow {% data variables.product.prodname_actions %} workflows, {% data variables.product.prodname_dependabot %}, or your {% data variables.product.prodname_github_codespaces %} development environment to communicate with other systems. For more information on how to securely store and use secrets, see "[Encrypted secrets in Actions](/actions/security-guides/encrypted-secrets)," "[Managing encrypted secrets for Dependabot](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/managing-encrypted-secrets-for-dependabot)," and "[Managing encrypted secrets for your codespaces](/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces)."
 {% endif %}
 
-{% ifversion ghes > 3.2 or ghae %}
+{% ifversion ghes or ghae %}
 Besides your code, you probably need to use secrets in other places. For example, to allow {% data variables.product.prodname_actions %} workflows{% ifversion ghes %} or {% data variables.product.prodname_dependabot %}{% endif %} to communicate with other systems. For more information on how to securely store and use secrets, see "[Encrypted secrets in Actions](/actions/security-guides/encrypted-secrets){% ifversion ghes %}" and "[Managing encrypted secrets for Dependabot](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/managing-encrypted-secrets-for-dependabot)."{% else %}."{% endif %}
 {% endif %}
 
diff --git a/translations/ja-JP/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review.md b/translations/ja-JP/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review.md
index 7a13366bbb..3e83d7902b 100644
--- a/translations/ja-JP/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review.md
+++ b/translations/ja-JP/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review.md
@@ -19,8 +19,6 @@ redirect_from:
   - /code-security/supply-chain-security/about-dependency-review
 ---
 
-{% data reusables.dependency-review.beta %}
-
 ## About dependency review
 
 {% data reusables.dependency-review.feature-overview %}  
diff --git a/translations/ja-JP/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-supply-chain-security.md b/translations/ja-JP/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-supply-chain-security.md
index 33e8c19950..8e83dd646e 100644
--- a/translations/ja-JP/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-supply-chain-security.md
+++ b/translations/ja-JP/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-supply-chain-security.md
@@ -1,6 +1,6 @@
 ---
 title: About supply chain security
-intro: '{% data variables.product.product_name %} helps you secure your supply chain, from understanding the dependencies in your environment, to knowing about vulnerabilities in those dependencies{% ifversion fpt or ghec or ghes > 3.2 %}, and patching them{% endif %}.'
+intro: '{% data variables.product.product_name %} helps you secure your supply chain, from understanding the dependencies in your environment, to knowing about vulnerabilities in those dependencies{% ifversion fpt or ghec or ghes %}, and patching them{% endif %}.'
 miniTocMaxHeadingLevel: 3
 shortTitle: Supply chain security
 redirect_from:
@@ -27,13 +27,13 @@ With the accelerated use of open source, most projects depend on hundreds of ope
 
 You add dependencies directly to your supply chain when you specify them in a manifest file or a lockfile. Dependencies can also be included transitively, that is, even if you don’t specify a particular dependency, but a dependency of yours uses it, then you’re also dependent on that dependency.
 
-{% data variables.product.product_name %} offers a range of features to help you understand the dependencies in your environment{% ifversion ghes < 3.3 or ghae %} and know about vulnerabilities in those dependencies{% endif %}{% ifversion fpt or ghec or ghes > 3.2 %}, know about vulnerabilities in those dependencies, and patch them{% endif %}. 
+{% data variables.product.product_name %} offers a range of features to help you understand the dependencies in your environment{% ifversion ghae %} and know about vulnerabilities in those dependencies{% endif %}{% ifversion fpt or ghec or ghes %}, know about vulnerabilities in those dependencies, and patch them{% endif %}. 
 
 The supply chain features on {% data variables.product.product_name %} are:
 - **Dependency graph**
 - **Dependency review**
 - **{% data variables.product.prodname_dependabot_alerts %} **
-{% ifversion fpt or ghec or ghes > 3.2 %}- **{% data variables.product.prodname_dependabot_updates %}**
+{% ifversion fpt or ghec or ghes %}- **{% data variables.product.prodname_dependabot_updates %}**
   - **{% data variables.product.prodname_dependabot_security_updates %}**
   - **{% data variables.product.prodname_dependabot_version_updates %}**{% endif %}
 
@@ -43,7 +43,7 @@ Other supply chain features on {% data variables.product.prodname_dotcom %} rely
 
 - Dependency review uses the dependency graph to identify dependency changes and help you understand the security impact of these changes when you review pull requests.
 - {% data variables.product.prodname_dependabot %} cross-references dependency data provided by the dependency graph with the list of advisories published in the {% data variables.product.prodname_advisory_database %}, scans your dependencies and generates {% data variables.product.prodname_dependabot_alerts %} when a potential vulnerability {% ifversion GH-advisory-db-supports-malware %}or malware{% endif %} is detected.
-{% ifversion fpt or ghec or ghes > 3.2 %}- {% data variables.product.prodname_dependabot_security_updates %} use the dependency graph and  {% data variables.product.prodname_dependabot_alerts %} to help you update dependencies with known vulnerabilities in your repository.
+{% ifversion fpt or ghec or ghes %}- {% data variables.product.prodname_dependabot_security_updates %} use the dependency graph and  {% data variables.product.prodname_dependabot_alerts %} to help you update dependencies with known vulnerabilities in your repository.
 
 {% data variables.product.prodname_dependabot_version_updates %} don't use the dependency graph and rely on the semantic versioning of dependencies instead. {% data variables.product.prodname_dependabot_version_updates %} help you keep your dependencies updated, even when they don’t have any vulnerabilities.
 {% endif %}
@@ -79,9 +79,9 @@ For more information about dependency review, see "[About dependency review](/co
 
 ### What is Dependabot
 
-{% data variables.product.prodname_dependabot %} keeps your dependencies up to date by informing you of any security vulnerabilities in your dependencies{% ifversion fpt or ghec or ghes > 3.2 %}, and automatically opens pull requests to upgrade your dependencies to the next available secure version when a {% data variables.product.prodname_dependabot %} alert is triggered, or to the latest version when a release is published{% else %} so that you can update that dependency{% endif %}.
+{% data variables.product.prodname_dependabot %} keeps your dependencies up to date by informing you of any security vulnerabilities in your dependencies{% ifversion fpt or ghec or ghes %}, and automatically opens pull requests to upgrade your dependencies to the next available secure version when a {% data variables.product.prodname_dependabot %} alert is triggered, or to the latest version when a release is published{% else %} so that you can update that dependency{% endif %}.
 
-{% ifversion fpt or ghec or ghes > 3.2 %}
+{% ifversion fpt or ghec or ghes %}
 The term "{% data variables.product.prodname_dependabot %}" encompasses the following features:
 - {% data variables.product.prodname_dependabot_alerts %}—Displayed notification on the **Security** tab for the repository, and in the repository's dependency graph. The alert includes a link to the affected file in the project, and information about a fixed version.
 - {% data variables.product.prodname_dependabot_updates %}:
@@ -117,7 +117,7 @@ The term "{% data variables.product.prodname_dependabot %}" encompasses the foll
 
 For more information, see "[About {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-alerts-for-vulnerable-dependencies)."
 
-{% ifversion fpt or ghec or ghes > 3.2 %}
+{% ifversion fpt or ghec or ghes %}
 #### What are Dependabot updates
 
 There are two types of {% data variables.product.prodname_dependabot_updates %}: {% data variables.product.prodname_dependabot %} _security_ updates and _version_ updates. {% data variables.product.prodname_dependabot %} generates automatic pull requests to update your dependencies in both cases, but there are several differences.
@@ -166,7 +166,7 @@ Any repository type:
 - **Dependency graph** and **{% data variables.product.prodname_dependabot_alerts %}**—not enabled by default. Both features are configured at an enterprise level by the enterprise owner. For more information, see {% ifversion ghes %}"[Enabling the dependency graph for your enterprise](/admin/code-security/managing-supply-chain-security-for-your-enterprise/enabling-the-dependency-graph-for-your-enterprise)" and {% endif %}"[Enabling {% data variables.product.prodname_dependabot %} for your enterprise](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise)."
 - **Dependency review**—available when dependency graph is enabled for {% data variables.location.product_location %} and {% data variables.product.prodname_advanced_security %} is enabled for the organization or repository. For more information, see "[About {% data variables.product.prodname_GH_advanced_security %}](/get-started/learning-about-github/about-github-advanced-security)."
 {% endif %}
-{% ifversion ghes > 3.2 %}
+{% ifversion ghes %}
 - **{% data variables.product.prodname_dependabot_security_updates %}**—not enabled by default. You can enable {% data variables.product.prodname_dependabot_security_updates %} for any repository that uses {% data variables.product.prodname_dependabot_alerts %} and the dependency graph. For information about enabling security updates, see "[Configuring {% data variables.product.prodname_dependabot_security_updates %}](/code-security/dependabot/dependabot-security-updates/configuring-dependabot-security-updates)."
 - **{% data variables.product.prodname_dependabot_version_updates %}**—not enabled by default. People with write permissions to a repository can enable {% data variables.product.prodname_dependabot_version_updates %}. For information about enabling version updates, see "[Configuring {% data variables.product.prodname_dependabot_version_updates %}](/code-security/dependabot/dependabot-version-updates/configuring-dependabot-version-updates)."
 {% endif %}
diff --git a/translations/ja-JP/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph.md b/translations/ja-JP/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph.md
index 15849448f0..42541c3ef9 100644
--- a/translations/ja-JP/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph.md
+++ b/translations/ja-JP/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph.md
@@ -79,11 +79,7 @@ The recommended formats explicitly define which versions are used for all direct
 {%- ifversion github-actions-in-dependency-graph %}
 | {% data variables.product.prodname_actions %} workflows<sup>[†]</sup> | YAML | `.yml`, `.yaml` | `.yml`, `.yaml` |
 {%- endif %}
-{%- ifversion fpt or ghec or ghes > 3.2 or ghae %}
 | Go modules | Go | `go.sum` | `go.mod`, `go.sum` |
-{%- elsif ghes = 3.2 %}
-| Go modules | Go | `go.mod` | `go.mod` |
-{%- endif %}
 | Maven | Java, Scala |  `pom.xml`  | `pom.xml`  |
 | npm | JavaScript |            `package-lock.json` | `package-lock.json`, `package.json`|
 | pip             | Python                    | `requirements.txt`, `pipfile.lock` | `requirements.txt`, `pipfile`, `pipfile.lock`, `setup.py`<sup>[‡]</sup> |
diff --git a/translations/ja-JP/content/code-security/supply-chain-security/understanding-your-software-supply-chain/configuring-dependency-review.md b/translations/ja-JP/content/code-security/supply-chain-security/understanding-your-software-supply-chain/configuring-dependency-review.md
index 06bb91f769..460c0bb236 100644
--- a/translations/ja-JP/content/code-security/supply-chain-security/understanding-your-software-supply-chain/configuring-dependency-review.md
+++ b/translations/ja-JP/content/code-security/supply-chain-security/understanding-your-software-supply-chain/configuring-dependency-review.md
@@ -4,7 +4,7 @@ intro: You can use dependency review to catch vulnerabilities before they are ad
 shortTitle: Configure dependency review
 versions:
   fpt: '*'
-  ghes: '>= 3.2'
+  ghes: '*'
   ghae: '*'
   ghec: '*'
 type: how_to
@@ -16,8 +16,6 @@ topics:
   - Pull requests
 ---
 
-{% data reusables.dependency-review.beta %}
-
 ## About dependency review
 
 {% data reusables.dependency-review.feature-overview %}   
@@ -46,8 +44,7 @@ Dependency review is available when dependency graph is enabled for {% data vari
 {% data reusables.repositories.sidebar-settings %}
 {% data reusables.repositories.navigate-to-code-security-and-analysis %}
 1. Under "Configure security and analysis features", check if the dependency graph is enabled. 
-1. If dependency graph is enabled, click **Enable** next to "{% data variables.product.prodname_GH_advanced_security %}" to enable {% data variables.product.prodname_advanced_security %}, including dependency review. The enable button is disabled if your enterprise has no available licenses for {% data variables.product.prodname_advanced_security %}.{% ifversion ghes < 3.3 %}
-  ![Screenshot of "Code security and analysis" features"](/assets/images/enterprise/3.2/repository/code-security-and-analysis-enable-ghas-3.2.png){% endif %}{% ifversion ghes > 3.2 %}
+1. If dependency graph is enabled, click **Enable** next to "{% data variables.product.prodname_GH_advanced_security %}" to enable {% data variables.product.prodname_advanced_security %}, including dependency review. The enable button is disabled if your enterprise has no available licenses for {% data variables.product.prodname_advanced_security %}.{% ifversion ghes %}
     ![Screenshot of "Code security and analysis" features"](/assets/images/enterprise/3.4/repository/code-security-and-analysis-enable-ghas-3.4.png){% endif %}
 
 {% endif %}
diff --git a/translations/ja-JP/content/code-security/supply-chain-security/understanding-your-software-supply-chain/troubleshooting-the-dependency-graph.md b/translations/ja-JP/content/code-security/supply-chain-security/understanding-your-software-supply-chain/troubleshooting-the-dependency-graph.md
index 299550e2af..c1879f3d31 100644
--- a/translations/ja-JP/content/code-security/supply-chain-security/understanding-your-software-supply-chain/troubleshooting-the-dependency-graph.md
+++ b/translations/ja-JP/content/code-security/supply-chain-security/understanding-your-software-supply-chain/troubleshooting-the-dependency-graph.md
@@ -1,6 +1,6 @@
 ---
-title: 依存関係グラフのトラブルシューティング
-intro: 依存関係グラフによって報告された依存関係の情報が期待したものと異なる場合、いくつかの考慮するポイントと、さまざまな確認項目があります。
+title: Troubleshooting the dependency graph
+intro: 'If the dependency information reported by the dependency graph is not what you expected, there are a number of points to consider, and various things you can check.'
 shortTitle: Troubleshoot dependency graph
 versions:
   fpt: '*'
@@ -16,56 +16,51 @@ topics:
   - Dependency graph
   - CVEs
   - Repositories
-ms.openlocfilehash: 51a1da4eff062263aeca52de02b764385e7e1184
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
-ms.translationtype: HT
-ms.contentlocale: ja-JP
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '146458245'
 ---
+
 {% data reusables.dependabot.result-discrepancy %}
 
-## 依存関係グラフは、マニフェストとロックファイルの依存関係のみを検索しますか？
+## Does the dependency graph only find dependencies in manifests and lockfiles?
 
-依存関係グラフには、環境で明示的に宣言されている依存関係に関する情報が{% ifversion dependency-submission-api %}自動的に{% endif %}含まれます。 つまり、マニフェストまたはロックファイルで指定されている依存関係です。 依存関係グラフには、通常、マニフェストファイル内の依存関係の依存関係を調べることにより、ロックファイルで指定されていない場合でも、推移的な依存関係も含まれます。
+The dependency graph {% ifversion dependency-submission-api %}automatically{% endif %} includes information on dependencies that are explicitly declared in your environment. That is, dependencies that are specified in a manifest or a lockfile. The dependency graph generally also includes transitive dependencies, even when they aren't specified in a lockfile, by looking at the dependencies of the dependencies in a manifest file.
 
-"ゆるい" 依存関係が依存関係グラフに{% ifversion dependency-submission-api %}自動的に{% endif %}含まれることはありません。 「ゆるい」依存関係は、パッケージマネージャーのマニフェストまたはロックファイルで参照されるのではなく、あるソースからコピーされ、リポジトリに直接またはアーカイブ (ZIP ファイルや JAR ファイルなど) に含まれてチェックインされる個々のファイルです。 
+The dependency graph doesn't {% ifversion dependency-submission-api %}automatically{% endif %} include "loose" dependencies. "Loose" dependencies are individual files that are copied from another source and checked into the repository directly or within an archive (such as a ZIP or JAR file), rather than being referenced by in a package manager’s manifest or lockfile. 
 
-{% ifversion dependency-submission-api %}ただし、プロジェクトのビルド時に解決される依存関係など、依存関係がマニフェストまたはロック ファイルで宣言されていない場合でも、Dependency submission API (ベータ) を使用して、依存関係をプロジェクトの依存関係グラフに追加できます。 依存関係グラフには、送信された依存関係がエコシステム別にグループ化されて表示されますが、マニフェストまたはロック ファイルから解析された依存関係とは別になっています。 Dependency submission API について詳しくは、「[Dependency submission API の利用](/code-security/supply-chain-security/understanding-your-software-supply-chain/using-the-dependency-submission-api)」を参照してください。{% endif %}
+{% ifversion dependency-submission-api %}However, you can use the Dependency submission API (beta) to add dependencies to a project's dependency graph, even if the dependencies are not declared in a manifest or lock file, such as dependencies resolved when a project is built. The dependency graph will display the submitted dependencies grouped by ecosystem, but separately from the dependencies parsed from manifest or lock files. For more information on the Dependency submission API, see "[Using the Dependency submission API](/code-security/supply-chain-security/understanding-your-software-supply-chain/using-the-dependency-submission-api)."{% endif %}
 
-**チェック**: リポジトリのマニフェストまたはロックファイル内で指定されていない、コンポーネントに対する見落とされている依存関係はありますか?
+**Check**: Is the missing dependency for a component that's not specified in the repository's manifest or lockfile?
 
-## 依存関係グラフは、変数を使用して指定された依存関係を検出しますか？
+## Does the dependency graph detect dependencies specified using variables?
 
-依存関係グラフは、マニフェストが {% data variables.product.prodname_dotcom %} にプッシュされるときにマニフェストを分析します。 したがって、依存関係グラフはプロジェクトのビルド環境にアクセスできないため、マニフェスト内で使用される変数を解決できません。 マニフェスト内で変数を使用して名前、またはより一般的には依存関係のバージョンを指定する場合、その依存関係は依存関係グラフに{% ifversion dependency-submission-api %}自動的には{% endif %}含まれません。
+The dependency graph analyzes manifests as they’re pushed to {% data variables.product.prodname_dotcom %}. The dependency graph doesn't, therefore, have access to the build environment of the project, so it can't resolve variables used within manifests. If you use variables within a manifest to specify the name, or more commonly the version of a dependency, then that dependency will not {% ifversion dependency-submission-api %}automatically{% endif %} be included in the dependency graph.
 
-{% ifversion dependency-submission-api %}ただし、依存関係がプロジェクトのビルド時にのみ解決される場合でも、Dependency submission API (ベータ) を使用して、依存関係をプロジェクトの依存関係グラフに追加できます。 Dependency submission API について詳しくは、「[Dependency submission API の利用](/code-security/supply-chain-security/understanding-your-software-supply-chain/using-the-dependency-submission-api)」を参照してください。{% endif %}
+{% ifversion dependency-submission-api %}However, you can use the Dependency submission API (beta) to add dependencies to a project's dependency graph, even if the dependencies are only resolved when a project is built. For more information on the Dependency submission API, see "[Using the Dependency submission API](/code-security/supply-chain-security/understanding-your-software-supply-chain/using-the-dependency-submission-api)."{% endif %}
 
-**チェック**: マニフェストで、名前またはバージョンに変数を使用して、見落とされている依存関係が宣言されていますか?
+**Check**: Is the missing dependency declared in the manifest by using a variable for its name or version?
 
-## 依存関係グラフのデータに影響する制限はありますか？
+## Are there limits which affect the dependency graph data?
 
-はい、依存関係グラフの制限には 2 つのカテゴリがあります。
+Yes, the dependency graph has two categories of limits:
 
-1. **処理制限**
+1. **Processing limits**
 
-    これらは {% data variables.product.prodname_dotcom %} 内に表示される依存関係グラフに影響を与え、{% data variables.product.prodname_dependabot_alerts %} が作成されないようにします。
+    These affect the dependency graph displayed within {% data variables.product.prodname_dotcom %} and also prevent {% data variables.product.prodname_dependabot_alerts %} being created.
 
-    サイズが 0.5 MB を超えるマニフェストは、Enterprise アカウントに対してのみ処理されます。 他のアカウントの場合、0.5 MB を超えるマニフェストは無視され、{% data variables.product.prodname_dependabot_alerts %} は作成されません。
+    Manifests over 0.5 MB in size are only processed for enterprise accounts. For other accounts, manifests over 0.5 MB are ignored and will not create {% data variables.product.prodname_dependabot_alerts %}.
 
-    デフォルト設定では、{% data variables.product.prodname_dotcom %} はリポジトリごとに 20 個を超えるマニフェストを処理しません。 {% data variables.product.prodname_dependabot_alerts %} は、この制限を超えるマニフェストに対しては作成されません。 制限を増やす必要がある場合は、{% data variables.contact.contact_support %} にお問い合わせください。 
+    By default, {% data variables.product.prodname_dotcom %} will not process more than 20 manifests per repository. {% data variables.product.prodname_dependabot_alerts %} are not created for manifests beyond this limit. If you need to increase the limit, contact {% data variables.contact.contact_support %}. 
 
-2. **視覚化の制限**
+2. **Visualization limits**
 
-    これらは、{% data variables.product.prodname_dotcom %} 内の依存関係グラフに表示される内容に影響します。 ただし、作成された {% data variables.product.prodname_dependabot_alerts %} には影響しません。
+    These affect what's displayed in the dependency graph within {% data variables.product.prodname_dotcom %}. However, they don't affect the {% data variables.product.prodname_dependabot_alerts %} that are created.
 
-    リポジトリの依存関係グラフの依存関係ビューには、100 個のマニフェストのみが表示されます。 通常、これは上記の処理制限よりも大幅に高いので十分です。 処理制限が100 個を超える状況でも、{% data variables.product.prodname_dotcom %} 内に表示されていないマニフェストに対して {% data variables.product.prodname_dependabot_alerts %} が作成されます。
+    The Dependencies view of the dependency graph for a repository only displays 100 manifests. Typically this is adequate as it is significantly higher than the processing limit described above. In situations where the processing limit is over 100, {% data variables.product.prodname_dependabot_alerts %} are still created for any manifests that are not shown within {% data variables.product.prodname_dotcom %}.
 
-**チェック**: 0.5 MB を超えるマニフェスト ファイル、または多数のマニフェストがあるリポジトリに見落とされている依存関係はありませんか?
+**Check**: Is the missing dependency in a manifest file that's over 0.5 MB, or in a repository with a large number of manifests?
 
-## 参考資料
+## Further reading
 
-- "[依存関係グラフについて](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph)"
-- 「[リポジトリのセキュリティと分析設定を管理する](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)」
-- 「[Troubleshooting the detection of vulnerable dependencies](/code-security/dependabot/working-with-dependabot/troubleshooting-the-detection-of-vulnerable-dependencies)」(脆弱な依存関係の検出に関するトラブルシューティング){% ifversion fpt or ghec or ghes > 3.2 %}
-- 「[{% data variables.product.prodname_dependabot %} エラーのトラブルシューティング](/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors)」{% endif %}
+- "[About the dependency graph](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph)"
+- "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)"
+- "[Troubleshooting the detection of vulnerable dependencies](/code-security/dependabot/working-with-dependabot/troubleshooting-the-detection-of-vulnerable-dependencies)"{% ifversion fpt or ghec or ghes %}
+- "[Troubleshooting {% data variables.product.prodname_dependabot %} errors](/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors)"{% endif %}
diff --git a/translations/ja-JP/content/codespaces/codespaces-reference/allowing-your-codespace-to-access-a-private-image-registry.md b/translations/ja-JP/content/codespaces/codespaces-reference/allowing-your-codespace-to-access-a-private-image-registry.md
index 40094b5db2..fe7c29fd82 100644
--- a/translations/ja-JP/content/codespaces/codespaces-reference/allowing-your-codespace-to-access-a-private-image-registry.md
+++ b/translations/ja-JP/content/codespaces/codespaces-reference/allowing-your-codespace-to-access-a-private-image-registry.md
@@ -30,7 +30,7 @@ If you publish a container image to {% data variables.packages.prodname_ghcr_or_
 
 By default, when you publish a container image to {% data variables.packages.prodname_ghcr_or_npm_registry %}, the image inherits the access setting of the repository from which the image was published. For example, if the repository is public, the image is also public. If the repository is private, the image is also private, but is accessible from the repository.
 
-This behavior is controlled by the **Inherit access from repo** option. **Inherit access from repo** is selected by default when publishing via {% data variables.product.prodname_actions %}, but not when publishing directly to {% data variables.packages.prodname_ghcr_or_npm_registry %} using a % data variables.product.pat_generic %}.
+This behavior is controlled by the **Inherit access from repo** option. **Inherit access from repo** is selected by default when publishing via {% data variables.product.prodname_actions %}, but not when publishing directly to {% data variables.packages.prodname_ghcr_or_npm_registry %} using a {% data variables.product.pat_generic %}.
 
 If the **Inherit access from repo** option was not selected when the image was published, you can manually add the repository to the published container image's access controls. For more information, see "[Configuring a package's access control and visibility](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility#inheriting-access-for-a-container-image-from-a-repository)."
 
diff --git a/translations/ja-JP/content/codespaces/customizing-your-codespace/changing-the-machine-type-for-your-codespace.md b/translations/ja-JP/content/codespaces/customizing-your-codespace/changing-the-machine-type-for-your-codespace.md
index 5aca361ee0..f985434f1b 100644
--- a/translations/ja-JP/content/codespaces/customizing-your-codespace/changing-the-machine-type-for-your-codespace.md
+++ b/translations/ja-JP/content/codespaces/customizing-your-codespace/changing-the-machine-type-for-your-codespace.md
@@ -105,4 +105,4 @@ You can use the `gh codespace edit --machine MACHINE-TYPE-NAME` {% data variable
 - "[Codespaces machines](/rest/codespaces/machines)" in the REST API documentation
 - [`gh codespace edit`](https://cli.github.com/manual/gh_codespace_edit) in the {% data variables.product.prodname_cli %} manual
 
-{% endcli %}
\ No newline at end of file
+{% endcli %}
diff --git a/translations/ja-JP/content/codespaces/developing-in-codespaces/creating-a-codespace.md b/translations/ja-JP/content/codespaces/developing-in-codespaces/creating-a-codespace.md
index 559ed6dc38..f0e477786b 100644
--- a/translations/ja-JP/content/codespaces/developing-in-codespaces/creating-a-codespace.md
+++ b/translations/ja-JP/content/codespaces/developing-in-codespaces/creating-a-codespace.md
@@ -153,4 +153,4 @@ For full details of the options for this command, see [the {% data variables.pro
 
 ## Further reading
 - "[Opening an existing codespace](/codespaces/developing-in-codespaces/opening-an-existing-codespace)"
-- "[Adding an 'Open in GitHub Codespaces' badge](/codespaces/setting-up-your-project-for-codespaces/adding-a-codespaces-badge)"
\ No newline at end of file
+- "[Adding an 'Open in GitHub Codespaces' badge](/codespaces/setting-up-your-project-for-codespaces/adding-a-codespaces-badge)"
diff --git a/translations/ja-JP/content/codespaces/developing-in-codespaces/deleting-a-codespace.md b/translations/ja-JP/content/codespaces/developing-in-codespaces/deleting-a-codespace.md
index 5a9bb4271a..92bf5d8295 100644
--- a/translations/ja-JP/content/codespaces/developing-in-codespaces/deleting-a-codespace.md
+++ b/translations/ja-JP/content/codespaces/developing-in-codespaces/deleting-a-codespace.md
@@ -124,4 +124,4 @@ You can also use the REST API to delete codespaces for your organization. For mo
 
 ## Further reading
 - "[Codespaces lifecycle](/codespaces/developing-in-codespaces/codespaces-lifecycle)"
-- "[Configuring automatic deletion of your codespaces](/codespaces/customizing-your-codespace/configuring-automatic-deletion-of-your-codespaces)"
\ No newline at end of file
+- "[Configuring automatic deletion of your codespaces](/codespaces/customizing-your-codespace/configuring-automatic-deletion-of-your-codespaces)"
diff --git a/translations/ja-JP/content/codespaces/developing-in-codespaces/developing-in-a-codespace.md b/translations/ja-JP/content/codespaces/developing-in-codespaces/developing-in-a-codespace.md
index 680e4301c4..ed9f3b5c99 100644
--- a/translations/ja-JP/content/codespaces/developing-in-codespaces/developing-in-a-codespace.md
+++ b/translations/ja-JP/content/codespaces/developing-in-codespaces/developing-in-a-codespace.md
@@ -53,4 +53,4 @@ For more information on using {% data variables.product.prodname_vscode_shortnam
 
 ### Using the {% data variables.product.prodname_vscode_command_palette %}
 
-The {% data variables.product.prodname_vscode_command_palette %} allows you to access and manage many features for {% data variables.product.prodname_github_codespaces %} and {% data variables.product.prodname_vscode_shortname %}. For more information, see "[Using the {% data variables.product.prodname_vscode_command_palette_shortname %} in {% data variables.product.prodname_github_codespaces %}](/codespaces/codespaces-reference/using-the-vs-code-command-palette-in-codespaces)."
\ No newline at end of file
+The {% data variables.product.prodname_vscode_command_palette %} allows you to access and manage many features for {% data variables.product.prodname_github_codespaces %} and {% data variables.product.prodname_vscode_shortname %}. For more information, see "[Using the {% data variables.product.prodname_vscode_command_palette_shortname %} in {% data variables.product.prodname_github_codespaces %}](/codespaces/codespaces-reference/using-the-vs-code-command-palette-in-codespaces)."
diff --git a/translations/ja-JP/content/codespaces/guides.md b/translations/ja-JP/content/codespaces/guides.md
index 670ce75cde..70587a4b81 100644
--- a/translations/ja-JP/content/codespaces/guides.md
+++ b/translations/ja-JP/content/codespaces/guides.md
@@ -15,6 +15,8 @@ includeGuides:
   - /codespaces/setting-up-your-project-for-codespaces/setting-up-your-python-project-for-codespaces
   - /codespaces/setting-up-your-project-for-codespaces/setting-up-your-dotnet-project-for-codespaces
   - /codespaces/setting-up-your-project-for-codespaces/setting-up-your-java-project-for-codespaces
+  - /codespaces/setting-up-your-project-for-codespaces/setting-a-minimum-specification-for-codespace-machines
+  - /codespaces/setting-up-your-project-for-codespaces/automatically-opening-files-in-the-codespaces-for-a-repository
   - /codespaces/setting-up-your-project-for-codespaces/adding-a-codespaces-badge
   - /codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project
   - /codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account
diff --git a/translations/ja-JP/content/codespaces/managing-codespaces-for-your-organization/listing-the-codespaces-in-your-organization.md b/translations/ja-JP/content/codespaces/managing-codespaces-for-your-organization/listing-the-codespaces-in-your-organization.md
index 68ef8f119d..996b22f228 100644
--- a/translations/ja-JP/content/codespaces/managing-codespaces-for-your-organization/listing-the-codespaces-in-your-organization.md
+++ b/translations/ja-JP/content/codespaces/managing-codespaces-for-your-organization/listing-the-codespaces-in-your-organization.md
@@ -1,7 +1,7 @@
 ---
 title: Listing the codespaces in your organization
 shortTitle: List organization codespaces
-intro: 'You can list all of the currently active or stopped codespaces for your organization.'
+intro: You can list all of the currently active or stopped codespaces for your organization.
 product: '{% data reusables.gated-features.codespaces %}'
 permissions: 'To list all of the current codespaces for your organization, you must be an organization owner.'
 versions:
@@ -51,4 +51,4 @@ gh codespace list --org ORGANIZATION --user USER
 
 You can use the `/orgs/{org}/codespaces` API endpoint as an alternative method of listing the current codespaces for an organization. This returns more information than {% data variables.product.prodname_cli %}; for example, the machine type details.
 
-For more information about this endpoint, see "[Codespaces organizations](/rest/codespaces/organizations#list-codespaces-for-the-organization)."
\ No newline at end of file
+For more information about this endpoint, see "[Codespaces organizations](/rest/codespaces/organizations#list-codespaces-for-the-organization)."
diff --git a/translations/ja-JP/content/codespaces/overview.md b/translations/ja-JP/content/codespaces/overview.md
index b193cde66d..e0494d19cb 100644
--- a/translations/ja-JP/content/codespaces/overview.md
+++ b/translations/ja-JP/content/codespaces/overview.md
@@ -44,4 +44,4 @@ For information on pricing, storage, and usage for {% data variables.product.pro
 
 {% data reusables.codespaces.codespaces-monthly-billing %} For information on how organizations owners and billing managers can manage the spending limit for {% data variables.product.prodname_github_codespaces %} for an organization, see "[Managing spending limits for {% data variables.product.prodname_github_codespaces %}](/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-github-codespaces)."
 
-You can see who will pay for a codespace before you create it. For more information, see "[Creating a codespace](/codespaces/developing-in-codespaces/creating-a-codespace#creating-a-codespace)."
\ No newline at end of file
+You can see who will pay for a codespace before you create it. For more information, see "[Creating a codespace](/codespaces/developing-in-codespaces/creating-a-codespace#creating-a-codespace)."
diff --git a/translations/ja-JP/content/codespaces/prebuilding-your-codespaces/allowing-a-prebuild-to-access-other-repositories.md b/translations/ja-JP/content/codespaces/prebuilding-your-codespaces/allowing-a-prebuild-to-access-other-repositories.md
index f9f02988d3..0ef2d0b210 100644
--- a/translations/ja-JP/content/codespaces/prebuilding-your-codespaces/allowing-a-prebuild-to-access-other-repositories.md
+++ b/translations/ja-JP/content/codespaces/prebuilding-your-codespaces/allowing-a-prebuild-to-access-other-repositories.md
@@ -1,7 +1,7 @@
 ---
 title: Allowing a prebuild to access other repositories
 shortTitle: Allow external repo access
-intro: You can permit your prebuild to access other {% data variables.product.prodname_dotcom %} repositories so that it can be built successfully.
+intro: 'You can permit your prebuild to access other {% data variables.product.prodname_dotcom %} repositories so that it can be built successfully.'
 versions:
   fpt: '*'
   ghec: '*'
diff --git a/translations/ja-JP/content/codespaces/setting-up-your-project-for-codespaces/adding-a-codespaces-badge.md b/translations/ja-JP/content/codespaces/setting-up-your-project-for-codespaces/adding-a-codespaces-badge.md
index 2f135dcff2..17f055bb42 100644
--- a/translations/ja-JP/content/codespaces/setting-up-your-project-for-codespaces/adding-a-codespaces-badge.md
+++ b/translations/ja-JP/content/codespaces/setting-up-your-project-for-codespaces/adding-a-codespaces-badge.md
@@ -11,12 +11,12 @@ topics:
   - Codespaces
   - Set up
 product: '{% data reusables.gated-features.codespaces %}'
-ms.openlocfilehash: 4a45c11adc5d09888e6bb65b49b9f997f5233fea
-ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794
+ms.openlocfilehash: d2ed02a205a4a8c3e55deb0b52fdc9ffdb855dc4
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: ja-JP
-ms.lasthandoff: 09/09/2022
-ms.locfileid: '147783131'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148108947'
 ---
 ## 概要
 
@@ -26,7 +26,7 @@ Markdown ファイルに [{% data variables.product.prodname_github_codespaces %
 
 バッジを作成するときに、そのバッジで作成される codespace に対して特定の構成オプションを選ぶことができます。
 
-ユーザーがバッジをクリックすると、codespace の作成用の [詳細オプション] ページに移動します。選んだオプションは事前に選択されています。 詳細オプション ページについて詳しくは、「[codespace の作成](https://docs-internal-30445-bfc9ce.preview.ghdocs.com/en/codespaces/developing-in-codespaces/creating-a-codespace#creating-a-codespace)」を参照してください。
+ユーザーがバッジをクリックすると、codespace の作成用の [詳細オプション] ページに移動します。選んだオプションは事前に選択されています。 詳細オプション ページについて詳しくは、「[codespace の作成](/codespaces/developing-in-codespaces/creating-a-codespace#creating-a-codespace)」を参照してください。
 
 [詳細オプション] ページから、ユーザーは必要に応じて事前に選択された設定を変更し、 **[codespace の作成]** をクリックできます。
 
diff --git a/translations/ja-JP/content/codespaces/setting-up-your-project-for-codespaces/index.md b/translations/ja-JP/content/codespaces/setting-up-your-project-for-codespaces/index.md
index f0ae6ea87c..2219a57e3b 100644
--- a/translations/ja-JP/content/codespaces/setting-up-your-project-for-codespaces/index.md
+++ b/translations/ja-JP/content/codespaces/setting-up-your-project-for-codespaces/index.md
@@ -17,6 +17,7 @@ children:
   - /setting-up-your-java-project-for-codespaces
   - /setting-up-your-python-project-for-codespaces
   - /setting-a-minimum-specification-for-codespace-machines
+  - /automatically-opening-files-in-the-codespaces-for-a-repository
   - /adding-a-codespaces-badge
 ms.openlocfilehash: 1e172243dc351f0a173c8624b66914e1c3795495
 ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794
diff --git a/translations/ja-JP/content/codespaces/setting-up-your-project-for-codespaces/setting-a-minimum-specification-for-codespace-machines.md b/translations/ja-JP/content/codespaces/setting-up-your-project-for-codespaces/setting-a-minimum-specification-for-codespace-machines.md
index 9bb7455d6a..9bd36a5a2a 100644
--- a/translations/ja-JP/content/codespaces/setting-up-your-project-for-codespaces/setting-a-minimum-specification-for-codespace-machines.md
+++ b/translations/ja-JP/content/codespaces/setting-up-your-project-for-codespaces/setting-a-minimum-specification-for-codespace-machines.md
@@ -1,7 +1,7 @@
 ---
-title: codespace コンピューターに対して最小仕様を設定する
+title: Setting a minimum specification for codespace machines
 shortTitle: Set a minimum machine spec
-intro: 'リソース不足のコンピューターの種類が、リポジトリの {% data variables.product.prodname_github_codespaces %} に使用されないようにすることができます。'
+intro: 'You can avoid under-resourced machine types being used for {% data variables.product.prodname_github_codespaces %} for your repository.'
 permissions: People with write permissions to a repository can create or edit the codespace configuration.
 versions:
   fpt: '*'
@@ -11,29 +11,24 @@ topics:
   - Codespaces
   - Set up
 product: '{% data reusables.gated-features.codespaces %}'
-ms.openlocfilehash: 368b7c73d13bb0624c9d838ac2d7bb18a2b050e3
-ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
-ms.translationtype: HT
-ms.contentlocale: ja-JP
-ms.lasthandoff: 09/10/2022
-ms.locfileid: '147880807'
 ---
-## 概要
 
-作成する各 codespace は個別の仮想マシンでホストされ、通常はさまざまな種類の仮想マシンから選択できます。 マシンの種類ごとにリソース (CPU、メモリ、ストレージ) が異なり、既定では、リソースが最も少ないコンピューターの種類が使用されます。 詳細については、「[codespace に合わせたコンピューターの種類の変更](/codespaces/customizing-your-codespace/changing-the-machine-type-for-your-codespace#about-machine-types)」を参照してください。
+## Overview
 
-プロジェクトで特定のレベルのコンピューティング能力が必要な場合は、それらの要件を満たすコンピューターの種類のみを、既定で使用、またはユーザーが選択できるように、{% data variables.product.prodname_github_codespaces %} を構成することができます。 `devcontainer.json` ファイル内でこれを構成します。
+Each codespace that you create is hosted on a separate virtual machine, and you can usually choose from different types of virtual machines. Each machine type has different resources (processor cores, memory, storage) and, by default, the machine type with the least resources is used. For more information, see "[Changing the machine type for your codespace](/codespaces/customizing-your-codespace/changing-the-machine-type-for-your-codespace#about-machine-types)."
+
+If your project needs a certain level of compute power, you can configure {% data variables.product.prodname_github_codespaces %} so that only machine types that meet these requirements can be used by default, or selected by users. You configure this in a `devcontainer.json` file.
 
 {% note %}
 
-**重要:** 一部のコンピューターの種類へのアクセスは、組織レベルで制限される場合があります。 通常、これは、より高いレートで課金される、よりリソースの多いコンピューターをユーザーが選択することを防ぐために行われます。 リポジトリがコンピューターの種類に関する組織レベルのポリシーの影響を受ける場合は、ユーザーが選択できるコンピューターの種類がなくなるような最小仕様を設定しないようにする必要があります。 詳細については、「[コンピューターの種類へのアクセスの制限](/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types)」を参照してください。
+**Important:** Access to some machine types may be restricted at the organization level. Typically this is done to prevent people choosing higher resourced machines that are billed at a higher rate. If your repository is affected by an organization-level policy for machine types you should make sure you don't set a minimum specification that would leave no available machine types for people to choose. For more information, see "[Restricting access to machine types](/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types)."
 
 {% endnote %}
 
-## コンピューターの最小仕様の設定
+## Setting a minimum machine specification
 
-1. ご利用のリポジトリの {% data variables.product.prodname_github_codespaces %} は、`devcontainer.json` ファイル内で構成されます。 リポジトリに `devcontainer.json` ファイルがまだ含まれていない場合は、今すぐ追加します。 「[開発コンテナー構成をリポジトリに追加する](/free-pro-team@latest/codespaces/setting-up-your-project-for-codespaces/setting-up-your-project-for-codespaces)」を参照してください。
-1. `devcontainer.json` ファイルを編集し、次のような `hostRequirements` プロパティを追加します。
+{% data reusables.codespaces.edit-devcontainer-json %}
+1. Edit the `devcontainer.json` file, adding the `hostRequirements` property at the top level of the file, within the enclosing JSON object. For example:
 
    ```json{:copy}
    "hostRequirements": {
@@ -43,16 +38,16 @@ ms.locfileid: '147880807'
    }
    ```
 
-   次のいずれかの、またはすべてのオプションを指定できます: `cpus`、`memory`、`storage`。
+   You can specify any or all of the options: `cpus`, `memory`, and `storage`.
    
-   リポジトリで現在使用可能な、{% data variables.product.prodname_github_codespaces %} のコンピューターの種類の仕様を確認するには、コンピューターの種類の選択肢が表示されるまで、codespace の作成プロセスをステップ実行します。 詳細については、「[codespace を作成する](/codespaces/developing-in-codespaces/creating-a-codespace#creating-a-codespace)」を参照してください。
+   To check the specifications of the {% data variables.product.prodname_github_codespaces %} machine types that are currently available for your repository, step through the process of creating a codespace until you see the choice of machine types. For more information, see "[Creating a codespace](/codespaces/developing-in-codespaces/creating-a-codespace#creating-a-codespace)."
    
-1. ファイルを保存し、リポジトリの必要なブランチに加えた変更をコミットします。
+1. Save the file and commit your changes to the required branch of the repository.
 
-   ここで、リポジトリのそのブランチ用に codespace を作成し、作成設定オプションに進むと、指定したリソースと一致するか、またはそれを超えるコンピューターの種類のみを選択できるようになります。
+   Now when you create a codespace for that branch of the repository, and you go to the creation configuration options, you will only be able to select machine types that match or exceed the resources you've specified.
 
-   ![コンピューターの種類の選択が制限されているダイアログ ボックス](/assets/images/help/codespaces/machine-types-limited-choice.png)
+   ![Dialog box showing a limited choice of machine types](/assets/images/help/codespaces/machine-types-limited-choice.png)
 
-## 参考資料
+## Further reading
 
-- "[開発コンテナーの概要](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers)"
+- "[Introduction to dev containers](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers)"
diff --git a/translations/ja-JP/content/codespaces/the-githubdev-web-based-editor.md b/translations/ja-JP/content/codespaces/the-githubdev-web-based-editor.md
index 3944c4fa55..5b85af4092 100644
--- a/translations/ja-JP/content/codespaces/the-githubdev-web-based-editor.md
+++ b/translations/ja-JP/content/codespaces/the-githubdev-web-based-editor.md
@@ -2,7 +2,7 @@
 title: The github.dev web-based editor
 intro: 'Use the github.dev {% data variables.product.prodname_serverless %} from your repository or pull request to create and commit changes.'
 versions:
-  feature: 'githubdev-editor'
+  feature: githubdev-editor
 type: how_to
 miniTocMaxHeadingLevel: 3
 topics:
diff --git a/translations/ja-JP/content/codespaces/troubleshooting/troubleshooting-dotfiles-for-codespaces.md b/translations/ja-JP/content/codespaces/troubleshooting/troubleshooting-dotfiles-for-codespaces.md
index ec51c0bd71..476e7fe0ae 100644
--- a/translations/ja-JP/content/codespaces/troubleshooting/troubleshooting-dotfiles-for-codespaces.md
+++ b/translations/ja-JP/content/codespaces/troubleshooting/troubleshooting-dotfiles-for-codespaces.md
@@ -1,5 +1,5 @@
 ---
-title: Troubleshooting dotfiles for GitHub Codespaces 
+title: Troubleshooting dotfiles for GitHub Codespaces
 allowTitleToDifferFromFilename: true
 intro: Troubleshooting steps for common dotfiles issues.
 product: '{% data reusables.gated-features.codespaces %}'
@@ -23,4 +23,4 @@ If your codespace fails to pick up configuration settings from dotfiles, you sho
    - If your dotfiles were not cloned, check `/workspaces/.codespaces/.persistedshare/EnvironmentLog.txt` to see if there was a problem cloning them.
 1. Check `/workspaces/.codespaces/.persistedshare/creation.log` for possible issues. For more information, see [Creation logs](/codespaces/troubleshooting/codespaces-logs#creation-logs).
 
-If the configuration from your dotfiles is correctly picked up, but part of the configuration is incompatible with codespaces, use the `$CODESPACES` environment variable to add conditional logic for codespace-specific configuration settings.
\ No newline at end of file
+If the configuration from your dotfiles is correctly picked up, but part of the configuration is incompatible with codespaces, use the `$CODESPACES` environment variable to add conditional logic for codespace-specific configuration settings.
diff --git a/translations/ja-JP/content/copilot/configuring-github-copilot/configuring-github-copilot-settings-on-githubcom.md b/translations/ja-JP/content/copilot/configuring-github-copilot/configuring-github-copilot-settings-on-githubcom.md
index bf4bfa7870..181734a513 100644
--- a/translations/ja-JP/content/copilot/configuring-github-copilot/configuring-github-copilot-settings-on-githubcom.md
+++ b/translations/ja-JP/content/copilot/configuring-github-copilot/configuring-github-copilot-settings-on-githubcom.md
@@ -11,12 +11,12 @@ redirect_from:
   - /github/copilot/about-github-copilot-telemetry
   - /github/copilot/github-copilot-telemetry-terms
 shortTitle: GitHub.com
-ms.openlocfilehash: 139a2c93c76155eff092ca168129f8ef52ce69ae
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: cc87328504e3d9eb5e2bce83d981098b7f989ae0
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: ja-JP
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147080107'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148108838'
 ---
 ## {% data variables.product.prodname_dotcom_the_website %} での {% data variables.product.prodname_copilot %} の設定について
 
diff --git a/translations/ja-JP/content/developers/apps/building-oauth-apps/authorizing-oauth-apps.md b/translations/ja-JP/content/developers/apps/building-oauth-apps/authorizing-oauth-apps.md
index 9ed610b338..557287e15b 100644
--- a/translations/ja-JP/content/developers/apps/building-oauth-apps/authorizing-oauth-apps.md
+++ b/translations/ja-JP/content/developers/apps/building-oauth-apps/authorizing-oauth-apps.md
@@ -341,8 +341,8 @@ To build this link, you'll need your OAuth Apps `client_id` that you received fr
 
 * "[Troubleshooting authorization request errors](/apps/managing-oauth-apps/troubleshooting-authorization-request-errors)"
 * "[Troubleshooting OAuth App access token request errors](/apps/managing-oauth-apps/troubleshooting-oauth-app-access-token-request-errors)"
-* "[Device flow errors](#error-codes-for-the-device-flow)"{% ifversion fpt or ghae or ghes > 3.2 or ghec %}
-* "[Token expiration and revocation](/github/authenticating-to-github/keeping-your-account-and-data-secure/token-expiration-and-revocation)"{% endif %}
+* "[Device flow errors](#error-codes-for-the-device-flow)"
+* "[Token expiration and revocation](/github/authenticating-to-github/keeping-your-account-and-data-secure/token-expiration-and-revocation)"
 
 ## Further reading
 
diff --git a/translations/ja-JP/content/developers/apps/getting-started-with-apps/about-apps.md b/translations/ja-JP/content/developers/apps/getting-started-with-apps/about-apps.md
index 166ace7868..db0162551d 100644
--- a/translations/ja-JP/content/developers/apps/getting-started-with-apps/about-apps.md
+++ b/translations/ja-JP/content/developers/apps/getting-started-with-apps/about-apps.md
@@ -84,9 +84,9 @@ Keep these ideas in mind when using {% data variables.product.pat_generic %}s:
 * You can perform one-off cURL requests.
 * You can run personal scripts.
 * Don't set up a script for your whole team or company to use.
-* Don't set up a shared personal account to act as a bot user.{% ifversion fpt or ghes > 3.2 or ghae or ghec %}
+* Don't set up a shared personal account to act as a bot user.
 * Grant your token the minimal privileges it needs.
-* Set an expiration for your {% data variables.product.pat_generic %}s, to help keep your information secure.{% endif %}
+* Set an expiration for your {% data variables.product.pat_generic %}s, to help keep your information secure.
 
 ## Determining which integration to build
 
diff --git a/translations/ja-JP/content/developers/index.md b/translations/ja-JP/content/developers/index.md
index 1cbd15dda1..913d3a3de9 100644
--- a/translations/ja-JP/content/developers/index.md
+++ b/translations/ja-JP/content/developers/index.md
@@ -34,11 +34,11 @@ children:
   - /webhooks-and-events
   - /apps
   - /github-marketplace
-ms.openlocfilehash: 00e920befd903527d2928d7ddf6b0b76ab448341
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: dea95cbf3a90b14441c8bd09692c27dd3798d8e5
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: ja-JP
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147643982'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148109276'
 ---
 
diff --git a/translations/ja-JP/content/developers/webhooks-and-events/webhooks/webhook-events-and-payloads.md b/translations/ja-JP/content/developers/webhooks-and-events/webhooks/webhook-events-and-payloads.md
index 0caacccdd8..7f68a7bb88 100644
--- a/translations/ja-JP/content/developers/webhooks-and-events/webhooks/webhook-events-and-payloads.md
+++ b/translations/ja-JP/content/developers/webhooks-and-events/webhooks/webhook-events-and-payloads.md
@@ -734,7 +734,6 @@ For a detailed description of this payload and the payload for each type of `act
 
 Activity related to merge groups in a merge queue. The type of activity is specified in the action property of the payload object.
 
-
 ### Availability
 
 - Repository webhooks
@@ -1621,8 +1620,6 @@ This event occurs when someone triggers a workflow run on GitHub or sends a `POS
 {{ webhookPayloadsForCurrentVersion.workflow_dispatch }}
 {% endif %}
 
-{% ifversion fpt or ghes > 3.2 or ghec or ghae %}
-
 ## workflow_job
 
 {% data reusables.webhooks.workflow_job_short_desc %}
@@ -1644,7 +1641,6 @@ This event occurs when someone triggers a workflow run on GitHub or sends a `POS
 
 {{ webhookPayloadsForCurrentVersion.workflow_job }}
 
-{% endif %}
 {% ifversion fpt or ghes or ghec %}
 ## workflow_run
 
diff --git a/translations/ja-JP/content/education/contribute-with-github-community-exchange/getting-started-with-github-community-exchange.md b/translations/ja-JP/content/education/contribute-with-github-community-exchange/getting-started-with-github-community-exchange.md
index 2357d70f1d..96de480aa8 100644
--- a/translations/ja-JP/content/education/contribute-with-github-community-exchange/getting-started-with-github-community-exchange.md
+++ b/translations/ja-JP/content/education/contribute-with-github-community-exchange/getting-started-with-github-community-exchange.md
@@ -4,12 +4,12 @@ shortTitle: Get started
 intro: '{% data variables.product.prodname_community_exchange %} にアクセスし、リポジトリを送信する方法について説明します。'
 versions:
   fpt: '*'
-ms.openlocfilehash: f9280e380b251c52d2b582aadb55eb319d5c342d
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: b9c866ef33c321b70b87d8bcd3682d0c02737bfe
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: ja-JP
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147574005'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148109507'
 ---
 ## はじめに
 
diff --git a/translations/ja-JP/content/education/contribute-with-github-community-exchange/index.md b/translations/ja-JP/content/education/contribute-with-github-community-exchange/index.md
index 121b3489d6..23467d9a59 100644
--- a/translations/ja-JP/content/education/contribute-with-github-community-exchange/index.md
+++ b/translations/ja-JP/content/education/contribute-with-github-community-exchange/index.md
@@ -8,11 +8,11 @@ children:
   - /getting-started-with-github-community-exchange
   - /submitting-your-repository-to-github-community-exchange
   - /managing-your-submissions-to-github-community-exchange
-ms.openlocfilehash: 420db797ef8e913a597647f2a20fad8cea2c5861
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: fe002b4cff8bbecaac9ea4611ff69ab366df240f
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: ja-JP
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147409801'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148109500'
 ---
 
diff --git a/translations/ja-JP/content/education/contribute-with-github-community-exchange/managing-your-submissions-to-github-community-exchange.md b/translations/ja-JP/content/education/contribute-with-github-community-exchange/managing-your-submissions-to-github-community-exchange.md
index ee911e2c74..a9949ecf65 100644
--- a/translations/ja-JP/content/education/contribute-with-github-community-exchange/managing-your-submissions-to-github-community-exchange.md
+++ b/translations/ja-JP/content/education/contribute-with-github-community-exchange/managing-your-submissions-to-github-community-exchange.md
@@ -4,12 +4,12 @@ shortTitle: Manage your submissions
 intro: '{% data variables.product.prodname_community_exchange %} ギャラリー内の各リポジトリに割り当てられている目的、トピック、オファーを管理したり、リポジトリの送信を削除したりできます。'
 versions:
   fpt: '*'
-ms.openlocfilehash: 70dc65ccb387817d5b4a78c1fc27085f67dcfc6e
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: a7da6f3bede47700658fe81a1f0ec3e4e33ef316
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: ja-JP
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147409789'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148109476'
 ---
 ## 送信について
 
diff --git a/translations/ja-JP/content/education/contribute-with-github-community-exchange/submitting-your-repository-to-github-community-exchange.md b/translations/ja-JP/content/education/contribute-with-github-community-exchange/submitting-your-repository-to-github-community-exchange.md
index a0efcd57ad..0cc96fab46 100644
--- a/translations/ja-JP/content/education/contribute-with-github-community-exchange/submitting-your-repository-to-github-community-exchange.md
+++ b/translations/ja-JP/content/education/contribute-with-github-community-exchange/submitting-your-repository-to-github-community-exchange.md
@@ -4,12 +4,12 @@ shortTitle: Submit your repository
 intro: '他のユーザーが閲覧または投稿できるように、リポジトリを {% data variables.product.prodname_community_exchange %} に送信できます。'
 versions:
   fpt: '*'
-ms.openlocfilehash: d520f303bf368c9230f26580ba2de9bd744b21e7
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: 07198c74937470a591b30702bd027036d91d3ec7
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: ja-JP
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147409783'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148109475'
 ---
 ## リポジトリの送信について
 
diff --git a/translations/ja-JP/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-students/about-github-global-campus-for-students.md b/translations/ja-JP/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-students/about-github-global-campus-for-students.md
index ea2bbcdb07..872af6c9e9 100644
--- a/translations/ja-JP/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-students/about-github-global-campus-for-students.md
+++ b/translations/ja-JP/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-students/about-github-global-campus-for-students.md
@@ -10,12 +10,12 @@ redirect_from:
 versions:
   fpt: '*'
 shortTitle: For students
-ms.openlocfilehash: a34da8bd0f37646bfaad0dbff3b09c6f2df440e4
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: 9012b473399905e60b04a8876a3d4e6afd10a6ba
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: ja-JP
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147574231'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148109468'
 ---
 学校のプロジェクトで{% data variables.product.prodname_dotcom %}を利用することは、他者とコラボレーションして実世界の体験を見てもらうためのポートフォリオを構築するための実際的な方法です。
 
diff --git a/translations/ja-JP/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-students/apply-to-github-global-campus-as-a-student.md b/translations/ja-JP/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-students/apply-to-github-global-campus-as-a-student.md
index ecb7b10994..7b76fa9471 100644
--- a/translations/ja-JP/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-students/apply-to-github-global-campus-as-a-student.md
+++ b/translations/ja-JP/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-students/apply-to-github-global-campus-as-a-student.md
@@ -1,5 +1,5 @@
 ---
-title: 'Apply to GitHub Global Campus as a student'
+title: Apply to GitHub Global Campus as a student
 intro: 'As a student, you can apply to join {% data variables.product.prodname_global_campus %} and receive access to the student resources and benefits offered by {% data variables.product.prodname_education %}'
 redirect_from:
   - /education/teach-and-learn-with-github-education/apply-for-a-student-developer-pack
diff --git a/translations/ja-JP/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-students/index.md b/translations/ja-JP/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-students/index.md
index 5f4e6a1daf..068c2e4caa 100644
--- a/translations/ja-JP/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-students/index.md
+++ b/translations/ja-JP/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-students/index.md
@@ -14,11 +14,11 @@ children:
   - /why-wasnt-my-application-to-global-campus-for-students-approved
   - /about-github-community-exchange
 shortTitle: About Global Campus for students
-ms.openlocfilehash: 2ee0b90dc4cc25bbd3ac253e22c516ec3984b94a
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: 3f61867f7d7365635a8b2d3bd53a19b0180d0604
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: ja-JP
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147574261'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148109467'
 ---
 
diff --git a/translations/ja-JP/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-teachers/about-github-global-campus-for-teachers.md b/translations/ja-JP/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-teachers/about-github-global-campus-for-teachers.md
index 6d9fb98eb5..6a66913540 100644
--- a/translations/ja-JP/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-teachers/about-github-global-campus-for-teachers.md
+++ b/translations/ja-JP/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-teachers/about-github-global-campus-for-teachers.md
@@ -10,12 +10,12 @@ redirect_from:
 versions:
   fpt: '*'
 shortTitle: For teachers
-ms.openlocfilehash: d4e823cc97b9c75f264b856c39021e30ca0e4fed
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: 6a0e8b7ba27060b4f48438b515786256d93d6d0c
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: ja-JP
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147574219'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148108892'
 ---
 認定教育機関の学生または教職員は、{% data variables.product.prodname_education %} 特典とリソースが含まれている {% data variables.product.prodname_global_campus %} を申し込むことができます。 詳しくは、「[教師として {% data variables.product.prodname_global_campus %} に応募する](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-teachers/apply-to-github-global-campus-as-a-teacher)」を参照してください。
 
diff --git a/translations/ja-JP/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-teachers/index.md b/translations/ja-JP/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-teachers/index.md
index e558dece7e..f3409cc320 100644
--- a/translations/ja-JP/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-teachers/index.md
+++ b/translations/ja-JP/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-teachers/index.md
@@ -13,11 +13,11 @@ children:
   - /apply-to-github-global-campus-as-a-teacher
   - why-wasnt-my-application-to-global-campus-for-teachers-approved
 shortTitle: About Global Campus for teachers
-ms.openlocfilehash: f257ff9da81c99c87caf8f864e621cb7e382974d
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: b29cc4c76f0eb407dafb4080061f7f8a4c9cf62b
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: ja-JP
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147574252'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148108898'
 ---
 
diff --git a/translations/ja-JP/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-teachers/why-wasnt-my-application-to-global-campus-for-teachers-approved.md b/translations/ja-JP/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-teachers/why-wasnt-my-application-to-global-campus-for-teachers-approved.md
index 3ba439a70c..9ab2352573 100644
--- a/translations/ja-JP/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-teachers/why-wasnt-my-application-to-global-campus-for-teachers-approved.md
+++ b/translations/ja-JP/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-teachers/why-wasnt-my-application-to-global-campus-for-teachers-approved.md
@@ -12,12 +12,12 @@ redirect_from:
 versions:
   fpt: '*'
 shortTitle: Application not approved
-ms.openlocfilehash: 86d1f0c3bc1bfe451be611ce47cc3f715fd8ba92
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: 68fe0a970c94a73293505849425bc78ec78b265e
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: ja-JP
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147574245'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148108893'
 ---
 {% tip %}
 
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 401194125d..7f2ad08c68 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
@@ -51,7 +51,7 @@ For information about {% data variables.product.prodname_advanced_security %} fe
 {% 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. {% 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 %}
 
-{% ifversion ghes > 3.1 or ghec or ghae %}
+{% ifversion ghes or ghec or ghae %}
 ## 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 and to review the rollout phases we recommended, see "[Adopting {% data variables.product.prodname_GH_advanced_security %} at scale](/code-security/adopting-github-advanced-security-at-scale)."
diff --git a/translations/ja-JP/content/get-started/quickstart/communicating-on-github.md b/translations/ja-JP/content/get-started/quickstart/communicating-on-github.md
index 746d67c59d..4681320f39 100644
--- a/translations/ja-JP/content/get-started/quickstart/communicating-on-github.md
+++ b/translations/ja-JP/content/get-started/quickstart/communicating-on-github.md
@@ -151,4 +151,4 @@ For {% data variables.product.prodname_discussions %}, you can{% ifversion fpt o
 
 For team discussions, you can edit or delete discussions on a team's page, and you can configure notifications for team discussions. For more information, see "[About team discussions](/organizations/collaborating-with-your-team/about-team-discussions)."
 
-To learn some advanced formatting features that will help you communicate, see "[Quickstart for writing on {% data variables.product.prodname_dotcom %}](/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/quickstart-for-writing-on-github)."
\ No newline at end of file
+To learn some advanced formatting features that will help you communicate, see "[Quickstart for writing on {% data variables.product.prodname_dotcom %}](/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/quickstart-for-writing-on-github)."
diff --git a/translations/ja-JP/content/get-started/quickstart/contributing-to-projects.md b/translations/ja-JP/content/get-started/quickstart/contributing-to-projects.md
index b90de8630e..4bd5001966 100644
--- a/translations/ja-JP/content/get-started/quickstart/contributing-to-projects.md
+++ b/translations/ja-JP/content/get-started/quickstart/contributing-to-projects.md
@@ -26,7 +26,7 @@ This tutorial uses [the Spoon-Knife project](https://github.com/octocat/Spoon-Kn
 
 1. Navigate to the `Spoon-Knife` project at https://github.com/octocat/Spoon-Knife.
 2. Click **Fork**.
-   ![Fork button](/assets/images/help/repository/fork_button.png)
+   ![Fork button](/assets/images/help/repository/fork_button.png){% ifversion fpt or ghec or ghes > 3.5 or ghae > 3.5 %}
 3. Select an owner for the forked repository.
    ![Create a new fork page with owner dropdown emphasized](/assets/images/help/repository/fork-choose-owner.png)
 4. By default, forks are named the same as their parent repositories. You can change the name of the fork to distinguish it further. 
@@ -43,6 +43,7 @@ This tutorial uses [the Spoon-Knife project](https://github.com/octocat/Spoon-Kn
 **Note:** If you want to copy additional branches from the parent repository, you can do so from the **Branches** page. For more information, see "[Creating and deleting branches within your repository](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository)."
 
 {% endnote %}
+{% endif %}
 
 ## Cloning a fork
 
diff --git a/translations/ja-JP/content/get-started/quickstart/fork-a-repo.md b/translations/ja-JP/content/get-started/quickstart/fork-a-repo.md
index ad5ed4621b..a8107f1dd2 100644
--- a/translations/ja-JP/content/get-started/quickstart/fork-a-repo.md
+++ b/translations/ja-JP/content/get-started/quickstart/fork-a-repo.md
@@ -57,7 +57,7 @@ You might fork a project to propose changes to the upstream, or original, reposi
 
 1. On {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom_the_website %}{% else %}{% data variables.location.product_location %}{% endif %}, navigate to the [octocat/Spoon-Knife](https://github.com/octocat/Spoon-Knife) repository.
 2. In the top-right corner of the page, click **Fork**.
-   ![Fork button](/assets/images/help/repository/fork_button.png)
+   ![Fork button](/assets/images/help/repository/fork_button.png){% ifversion fpt or ghec or ghes > 3.5 or ghae > 3.5 %}
 3. Select an owner for the forked repository.
    ![Create a new fork page with owner dropdown emphasized](/assets/images/help/repository/fork-choose-owner.png)
 4. By default, forks are named the same as their parent repositories. You can change the name of the fork to distinguish it further. 
@@ -72,7 +72,7 @@ You might fork a project to propose changes to the upstream, or original, reposi
 
 {% note %}
 
-**Note:** If you want to copy additional branches from the parent repository, you can do so from the **Branches** page. For more information, see "[Creating and deleting branches within your repository](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository)."{% endnote %}
+**Note:** If you want to copy additional branches from the parent repository, you can do so from the **Branches** page. For more information, see "[Creating and deleting branches within your repository](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository)."{% endnote %}{% endif %}
 
 {% endwebui %}
 
diff --git a/translations/ja-JP/content/get-started/using-github/keyboard-shortcuts.md b/translations/ja-JP/content/get-started/using-github/keyboard-shortcuts.md
index 63db7352b5..416cf4f6d1 100644
--- a/translations/ja-JP/content/get-started/using-github/keyboard-shortcuts.md
+++ b/translations/ja-JP/content/get-started/using-github/keyboard-shortcuts.md
@@ -94,13 +94,13 @@ For more keyboard shortcuts, see the [CodeMirror documentation](https://codemirr
 |<kbd>Command</kbd>+<kbd>K</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>K</kbd> (Windows/Linux) | Inserts Markdown formatting for creating a link{% endif %}{% ifversion fpt or ghae > 3.5 or ghes > 3.5 or ghec %}
 |<kbd>Command</kbd>+<kbd>V</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>V</kbd> (Windows/Linux) | Creates a Markdown link when applied over highlighted text{% endif %}
 |<kbd>Command</kbd>+<kbd>Shift</kbd>+<kbd>P</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>P</kbd> (Windows/Linux) | Toggles between the **Write** and **Preview** comment tabs{% ifversion fpt or ghae or ghes > 3.4 or ghec %}
-|<kbd>Command</kbd>+<kbd>Shift</kbd>+<kbd>V</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>V</kbd> (Windows/Linux) | Pastes HTML link as plain text{% endif %}{% ifversion fpt or ghae or ghes > 3.2 or ghec %}
-|<kbd>Command</kbd>+<kbd>Shift</kbd>+<kbd>Option</kbd>+<kbd>V</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>Alt</kbd>+<kbd>V</kbd> (Windows/Linux) | Pastes HTML link as plain text{% endif %}{% ifversion fpt or ghae or ghes > 3.2 or ghec %}
+|<kbd>Command</kbd>+<kbd>Shift</kbd>+<kbd>V</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>V</kbd> (Windows/Linux) | Pastes HTML link as plain text{% endif %}
+|<kbd>Command</kbd>+<kbd>Shift</kbd>+<kbd>Option</kbd>+<kbd>V</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>Alt</kbd>+<kbd>V</kbd> (Windows/Linux) | Pastes HTML link as plain text
 |<kbd>Command</kbd>+<kbd>Shift</kbd>+<kbd>7</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>7</kbd> (Windows/Linux) | Inserts Markdown formatting for an ordered list
-|<kbd>Command</kbd>+<kbd>Shift</kbd>+<kbd>8</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>8</kbd> (Windows/Linux) | Inserts Markdown formatting for an unordered list{% endif %}
+|<kbd>Command</kbd>+<kbd>Shift</kbd>+<kbd>8</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>8</kbd> (Windows/Linux) | Inserts Markdown formatting for an unordered list
 |<kbd>Command</kbd>+<kbd>Enter</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>Enter</kbd> (Windows/Linux) | Submits a comment
-|<kbd>Ctrl</kbd>+<kbd>.</kbd> and then <kbd>Ctrl</kbd>+<kbd>[saved reply number]</kbd> | Opens saved replies menu and then autofills comment field with a saved reply. For more information, see "[About saved replies](/articles/about-saved-replies)."{% ifversion fpt or ghae or ghes > 3.2 or ghec %}
-|<kbd>Command</kbd>+<kbd>Shift</kbd>+<kbd>.</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>.</kbd> (Windows/Linux) | Inserts Markdown formatting for a quote{% endif %}{% ifversion fpt or ghec %}
+|<kbd>Ctrl</kbd>+<kbd>.</kbd> and then <kbd>Ctrl</kbd>+<kbd>[saved reply number]</kbd> | Opens saved replies menu and then autofills comment field with a saved reply. For more information, see "[About saved replies](/articles/about-saved-replies)."
+|<kbd>Command</kbd>+<kbd>Shift</kbd>+<kbd>.</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>.</kbd> (Windows/Linux) | Inserts Markdown formatting for a quote{% ifversion fpt or ghec %}
 |<kbd>Command</kbd>+<kbd>G</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>G</kbd> (Windows/Linux) | Insert a suggestion. For more information, see "[Reviewing proposed changes in a pull request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request)." |{% endif %}
 |<kbd>R</kbd> | Quote the selected text in your reply. For more information, see "[Basic writing and formatting syntax](/articles/basic-writing-and-formatting-syntax#quoting-text)." |
 
diff --git a/translations/ja-JP/content/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax.md b/translations/ja-JP/content/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax.md
index b229b71ca3..5047a0f091 100644
--- a/translations/ja-JP/content/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax.md
+++ b/translations/ja-JP/content/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax.md
@@ -324,7 +324,6 @@ For a full list of available emoji and codes, check out [the Emoji-Cheat-Sheet](
 
 You can create a new paragraph by leaving a blank line between lines of text.
 
-{% ifversion fpt or ghae or ghes > 3.2 or ghec %}
 ## Footnotes
 
 You can add footnotes to your content by using this bracket syntax:
@@ -355,7 +354,6 @@ The footnote will render like this:
 Footnotes are not supported in wikis.
 
 {% endtip %}
-{% endif %}
 
 ## Hiding content with comments
 
@@ -375,14 +373,10 @@ You can tell {% data variables.product.product_name %} to ignore (or escape) Mar
 
 For more information, see Daring Fireball's "[Markdown Syntax](https://daringfireball.net/projects/markdown/syntax#backslash)."
 
-{% ifversion fpt or ghes > 3.2 or ghae or ghec %}
-
 ## Disabling Markdown rendering
 
 {% data reusables.repositories.disabling-markdown-rendering %}
 
-{% endif %}
-
 ## Further reading
 
 - [{% data variables.product.prodname_dotcom %} Flavored Markdown Spec](https://github.github.com/gfm/)
diff --git a/translations/ja-JP/content/graphql/guides/managing-enterprise-accounts.md b/translations/ja-JP/content/graphql/guides/managing-enterprise-accounts.md
index 6c5a8fa020..354bd50661 100644
--- a/translations/ja-JP/content/graphql/guides/managing-enterprise-accounts.md
+++ b/translations/ja-JP/content/graphql/guides/managing-enterprise-accounts.md
@@ -60,8 +60,8 @@ For some example queries, see "[An example query using the Enterprise Accounts A
     - `admin:enterprise`
 
   The enterprise account specific scopes are:
-    - `admin:enterprise`: Gives full control of enterprises (includes {% ifversion ghes > 3.2 or ghae or ghec %}`manage_runners:enterprise`, {% endif %}`manage_billing:enterprise` and `read:enterprise`)
-    - `manage_billing:enterprise`: Read and write enterprise billing data.{% ifversion ghes > 3.2 or ghae  %}
+    - `admin:enterprise`: Gives full control of enterprises (includes `manage_runners:enterprise`, `manage_billing:enterprise` and `read:enterprise`)
+    - `manage_billing:enterprise`: Read and write enterprise billing data.{% ifversion ghes or ghae %}
     - `manage_runners:enterprise`: Access to manage GitHub Actions enterprise runners and runner-groups.{% endif %}
     - `read:enterprise`: Read enterprise profile data.
 
diff --git a/translations/ja-JP/content/graphql/overview/breaking-changes.md b/translations/ja-JP/content/graphql/overview/breaking-changes.md
index 5bce1f800b..bfa41e837e 100644
--- a/translations/ja-JP/content/graphql/overview/breaking-changes.md
+++ b/translations/ja-JP/content/graphql/overview/breaking-changes.md
@@ -10,12 +10,12 @@ versions:
   ghae: '*'
 topics:
   - API
-ms.openlocfilehash: ee38f60dfd12d00688e46c739fc41f328203daf5
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: c76520b1f9dc806659373771b42501e072319937
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: ja-JP
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147496653'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148109499'
 ---
 ## 破壊的変更について
 
diff --git a/translations/ja-JP/content/graphql/overview/changelog.md b/translations/ja-JP/content/graphql/overview/changelog.md
index ad79081118..81821a41f8 100644
--- a/translations/ja-JP/content/graphql/overview/changelog.md
+++ b/translations/ja-JP/content/graphql/overview/changelog.md
@@ -10,11 +10,11 @@ versions:
   ghae: '*'
 topics:
   - API
-ms.openlocfilehash: e5e1fc0708f46759837f29f0eadcaf8abce15220
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: 34f0baed8b75614c939281ed6a2393d7c809c82f
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: ja-JP
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147496549'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148109055'
 ---
 破壊的変更には、既存のクエリを損なったり、クライアントの実行時の振る舞いに影響するかもしれない変更が含まれます。 破壊的変更とそれらが行われる時期のリストについては、「[破壊的変更の履歴](/graphql/overview/breaking-changes)」を参照してください。
diff --git a/translations/ja-JP/content/graphql/overview/schema-previews.md b/translations/ja-JP/content/graphql/overview/schema-previews.md
index 32d9c085ad..c2e29a1c24 100644
--- a/translations/ja-JP/content/graphql/overview/schema-previews.md
+++ b/translations/ja-JP/content/graphql/overview/schema-previews.md
@@ -10,12 +10,12 @@ versions:
   ghae: '*'
 topics:
   - API
-ms.openlocfilehash: a4097cd792931fe33363229b24f0043b9b99a1cd
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: 038afd8cbdd60863213eae385ec9a26f707f62d8
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: ja-JP
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147496597'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148109054'
 ---
 ## スキーマプレビューについて
 
diff --git a/translations/ja-JP/content/graphql/reference/enums.md b/translations/ja-JP/content/graphql/reference/enums.md
index ad20e7b08e..5c5a96f34d 100644
--- a/translations/ja-JP/content/graphql/reference/enums.md
+++ b/translations/ja-JP/content/graphql/reference/enums.md
@@ -4,10 +4,10 @@ redirect_from:
   - /v4/enum
   - /v4/reference/enum
 versions:
-  fpt: "*"
-  ghec: "*"
-  ghes: "*"
-  ghae: "*"
+  fpt: '*'
+  ghec: '*'
+  ghes: '*'
+  ghae: '*'
 topics:
   - API
 ---
diff --git a/translations/ja-JP/content/graphql/reference/input-objects.md b/translations/ja-JP/content/graphql/reference/input-objects.md
index 2e2b6f22a9..c2fac85996 100644
--- a/translations/ja-JP/content/graphql/reference/input-objects.md
+++ b/translations/ja-JP/content/graphql/reference/input-objects.md
@@ -4,10 +4,10 @@ redirect_from:
   - /v4/input_object
   - /v4/reference/input_object
 versions:
-  fpt: "*"
-  ghec: "*"
-  ghes: "*"
-  ghae: "*"
+  fpt: '*'
+  ghec: '*'
+  ghes: '*'
+  ghae: '*'
 topics:
   - API
 ---
diff --git a/translations/ja-JP/content/graphql/reference/interfaces.md b/translations/ja-JP/content/graphql/reference/interfaces.md
index 6575e382f5..7834a90307 100644
--- a/translations/ja-JP/content/graphql/reference/interfaces.md
+++ b/translations/ja-JP/content/graphql/reference/interfaces.md
@@ -4,10 +4,10 @@ redirect_from:
   - /v4/interface
   - /v4/reference/interface
 versions:
-  fpt: "*"
-  ghec: "*"
-  ghes: "*"
-  ghae: "*"
+  fpt: '*'
+  ghec: '*'
+  ghes: '*'
+  ghae: '*'
 topics:
   - API
 ---
diff --git a/translations/ja-JP/content/graphql/reference/mutations.md b/translations/ja-JP/content/graphql/reference/mutations.md
index 4fdac19d7f..d92aac569f 100644
--- a/translations/ja-JP/content/graphql/reference/mutations.md
+++ b/translations/ja-JP/content/graphql/reference/mutations.md
@@ -4,10 +4,10 @@ redirect_from:
   - /v4/mutation
   - /v4/reference/mutation
 versions:
-  fpt: "*"
-  ghec: "*"
-  ghes: "*"
-  ghae: "*"
+  fpt: '*'
+  ghec: '*'
+  ghes: '*'
+  ghae: '*'
 topics:
   - API
 ---
diff --git a/translations/ja-JP/content/graphql/reference/objects.md b/translations/ja-JP/content/graphql/reference/objects.md
index 0fd065294c..a843b57912 100644
--- a/translations/ja-JP/content/graphql/reference/objects.md
+++ b/translations/ja-JP/content/graphql/reference/objects.md
@@ -4,10 +4,10 @@ redirect_from:
   - /v4/object
   - /v4/reference/object
 versions:
-  fpt: "*"
-  ghec: "*"
-  ghes: "*"
-  ghae: "*"
+  fpt: '*'
+  ghec: '*'
+  ghes: '*'
+  ghae: '*'
 topics:
   - API
 ---
diff --git a/translations/ja-JP/content/graphql/reference/queries.md b/translations/ja-JP/content/graphql/reference/queries.md
index 971960270b..394cfc85e2 100644
--- a/translations/ja-JP/content/graphql/reference/queries.md
+++ b/translations/ja-JP/content/graphql/reference/queries.md
@@ -11,12 +11,12 @@ versions:
   ghae: '*'
 topics:
   - API
-ms.openlocfilehash: 2e4f855c4140193b2d814b937341665e13a535de
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: d5c31e8e00788d2e75f27b0bb161249f01fcfb1d
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: ja-JP
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147496525'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148109043'
 ---
 ## クエリについて
 
diff --git a/translations/ja-JP/content/graphql/reference/scalars.md b/translations/ja-JP/content/graphql/reference/scalars.md
index fa1909884b..197191569b 100644
--- a/translations/ja-JP/content/graphql/reference/scalars.md
+++ b/translations/ja-JP/content/graphql/reference/scalars.md
@@ -10,12 +10,12 @@ versions:
   ghae: '*'
 topics:
   - API
-ms.openlocfilehash: f52c697c5b9659ff387102756e34cd9a332e882c
-ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.openlocfilehash: 731b2085e9b207298b39b99b4b37907c517b5814
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: ja-JP
-ms.lasthandoff: 09/10/2022
-ms.locfileid: '147879112'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148109704'
 ---
 ## スカラについて
 
diff --git a/translations/ja-JP/content/graphql/reference/unions.md b/translations/ja-JP/content/graphql/reference/unions.md
index 08cac387e2..f0e4e92119 100644
--- a/translations/ja-JP/content/graphql/reference/unions.md
+++ b/translations/ja-JP/content/graphql/reference/unions.md
@@ -4,10 +4,10 @@ redirect_from:
   - /v4/union
   - /v4/reference/union
 versions:
-  fpt: "*"
-  ghec: "*"
-  ghes: "*"
-  ghae: "*"
+  fpt: '*'
+  ghec: '*'
+  ghes: '*'
+  ghae: '*'
 topics:
   - API
 ---
diff --git a/translations/ja-JP/content/index.md b/translations/ja-JP/content/index.md
index 91ea171895..967cb422fb 100644
--- a/translations/ja-JP/content/index.md
+++ b/translations/ja-JP/content/index.md
@@ -128,11 +128,11 @@ externalProducts:
     name: npm
     href: 'https://docs.npmjs.com/'
     external: true
-ms.openlocfilehash: dfd88a0c13da67bf929a5f5334e73319c04ad394
-ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794
+ms.openlocfilehash: 09ad193360503125adce9c659a465cfae32dd54e
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: ja-JP
-ms.lasthandoff: 09/09/2022
-ms.locfileid: '147643846'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148107630'
 ---
 
diff --git a/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/index.md b/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/index.md
index 78808d8231..f269ee99ac 100644
--- a/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/index.md
+++ b/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/index.md
@@ -17,11 +17,11 @@ redirect_from:
   - /tracking-progress-on-your-project-board
   - /filtering-cards-on-a-project-board
   - /archiving-cards-on-a-project-board
-ms.openlocfilehash: c498a1e93008276aebe022dcc53a66086b86def7
-ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d
+ms.openlocfilehash: 5827065f7fe316f4ec8ea41b56be61b1e01943dd
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: ja-JP
-ms.lasthandoff: 09/11/2022
-ms.locfileid: '147422989'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148109042'
 ---
 {% data reusables.projects.project_boards_old %}
diff --git a/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/managing-project-boards/about-automation-for-project-boards.md b/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/managing-project-boards/about-automation-for-project-boards.md
index 10255228be..c963d25a3a 100644
--- a/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/managing-project-boards/about-automation-for-project-boards.md
+++ b/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/managing-project-boards/about-automation-for-project-boards.md
@@ -11,12 +11,12 @@ topics:
   - Pull requests
 shortTitle: 'Automation for {% data variables.product.prodname_projects_v1 %}'
 allowTitleToDifferFromFilename: true
-ms.openlocfilehash: 76cea8f38d7470bd7b6212ae1f93601b5e8c923b
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: 28c4719cca14dff54d971b9a081837c172f4da76
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: ja-JP
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147423341'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148108982'
 ---
 {% data reusables.projects.project_boards_old %}
 
diff --git a/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards.md b/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards.md
index aa83f058df..1ef5d0831c 100644
--- a/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards.md
+++ b/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards.md
@@ -1,5 +1,5 @@
 ---
-title: About {% data variables.product.prodname_projects_v1 %}
+title: 'About {% data variables.product.prodname_projects_v1 %}'
 intro: '{% data variables.product.prodname_projects_v1_caps %} on {% data variables.product.product_name %} help you organize and prioritize your work. You can create {% data variables.projects.projects_v1_boards %} for specific feature work, comprehensive roadmaps, or even release checklists. With {% data variables.product.prodname_projects_v1 %}, you have the flexibility to create customized workflows that suit your needs.'
 redirect_from:
   - /github/managing-your-work-on-github/managing-project-boards/about-project-boards
@@ -7,7 +7,7 @@ redirect_from:
   - /articles/about-project-boards
   - /github/managing-your-work-on-github/about-project-boards
 versions:
-  feature: "projects-v1"
+  feature: projects-v1
 topics:
   - Pull requests
 allowTitleToDifferFromFilename: true
diff --git a/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/managing-project-boards/changing-project-board-visibility.md b/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/managing-project-boards/changing-project-board-visibility.md
index 6ec3216396..03e1987e4d 100644
--- a/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/managing-project-boards/changing-project-board-visibility.md
+++ b/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/managing-project-boards/changing-project-board-visibility.md
@@ -1,6 +1,6 @@
 ---
-title: '{% data variables.product.prodname_project_v1 %}の可視性の変更'
-intro: '組織の所有者または{% data variables.projects.projects_v1_board %}管理者は、{% data variables.projects.projects_v1_board %}を{% ifversion ghae %}内部{% else %}パブリック{% endif %}またはプライベートにすることができます。'
+title: 'Changing {% data variables.product.prodname_project_v1 %} visibility'
+intro: 'As an organization owner or {% data variables.projects.projects_v1_board %} admin, you can make a {% data variables.projects.projects_v1_board %} {% ifversion ghae %}internal{% else %}public{% endif %} or private.'
 redirect_from:
   - /github/managing-your-work-on-github/managing-project-boards/changing-project-board-visibility
   - /articles/changing-project-board-visibility
@@ -11,12 +11,6 @@ topics:
   - Pull requests
 shortTitle: Change visibility
 allowTitleToDifferFromFilename: true
-ms.openlocfilehash: c288e72dccb5c1212e6e01d24197289cc77c18ce
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
-ms.translationtype: HT
-ms.contentlocale: ja-JP
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147614480'
 ---
 {% data reusables.projects.project_boards_old %}
 
@@ -24,13 +18,15 @@ ms.locfileid: '147614480'
 
 {% note %}
 
-**{% ifversion classic-project-visibility-permissions %}注{% else %}注{% endif %}:** {% ifversion classic-project-visibility-permissions %}
+**{% ifversion classic-project-visibility-permissions %}Notes{% else %}Note{% endif %}:** {% ifversion classic-project-visibility-permissions %}
 
 * {% data reusables.projects.owners-can-limit-visibility-permissions %}
-* {% endif %}{% data variables.projects.projects_v1_board %} を{% ifversion ghae %}内部{% else %}パブリック{% endif %}にすると、Organization のメンバーには既定で読み取りアクセス権が付与されます。 特定の Organization メンバーに書き込みまたは管理者権限を付与するには、参加しているチームへのアクセス権限を与えるか、{% data variables.projects.projects_v1_board %}にコラボレーターとして追加します。 詳しくは、「[Organization の{% data variables.product.prodname_project_v1_caps %}のアクセス許可](/articles/project-board-permissions-for-an-organization)」を参照してください。
+* {% endif %}When you make your {% data variables.projects.projects_v1_board %} {% ifversion ghae %}internal{% else %}public{% endif %}, organization members are given read access by default. You can give specific organization members write or admin permissions by giving access to teams they're on or by adding them to the {% data variables.projects.projects_v1_board %} as a collaborator. For more information, see "[{% data variables.product.prodname_project_v1_caps %} permissions for an organization](/articles/project-board-permissions-for-an-organization)."
 
 {% endnote %}
 
-1. {% ifversion ghae %}インターナル{% else %}パブリック{% endif %}もしくはプライベートにしたいプロジェクトボードにアクセスしてください。
-{% data reusables.project-management.click-menu %} {% data reusables.project-management.access-collaboration-settings %} {% data reusables.project-management.choose-visibility %}
-1. **[保存]** をクリックします。
+1. Navigate to the project board you want to make {% ifversion ghae %}internal{% else %}public{% endif %} or private.
+{% data reusables.project-management.click-menu %}
+{% data reusables.project-management.access-collaboration-settings %}
+{% data reusables.project-management.choose-visibility %}
+1. Click **Save**.
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 f83625c8c4..7896a33f2d 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
@@ -11,12 +11,12 @@ versions:
 topics:
   - Pull requests
 allowTitleToDifferFromFilename: true
-ms.openlocfilehash: fb62345b404e94ddd5a6a22995b9481c9855914d
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: 21dfb0c6837f97d567f19168cd7f343aac06a4c0
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: ja-JP
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147422709'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148109703'
 ---
 {% data reusables.projects.project_boards_old %}
 
diff --git a/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/managing-project-boards/configuring-automation-for-project-boards.md b/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/managing-project-boards/configuring-automation-for-project-boards.md
index d306081d2c..8dc6a0a663 100644
--- a/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/managing-project-boards/configuring-automation-for-project-boards.md
+++ b/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/managing-project-boards/configuring-automation-for-project-boards.md
@@ -15,12 +15,12 @@ topics:
 shortTitle: Configure automation
 type: how_to
 allowTitleToDifferFromFilename: true
-ms.openlocfilehash: 67294015021ef97a8210bff8bbe6c95e352dc26e
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: faf559c3423178b43f3b524bbf3cdc41acd18a92
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: ja-JP
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147422685'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148109698'
 ---
 {% data reusables.projects.project_boards_old %}
 
diff --git a/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/managing-project-boards/copying-a-project-board.md b/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/managing-project-boards/copying-a-project-board.md
index 2c589a5ac7..2e1aef5aab 100644
--- a/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/managing-project-boards/copying-a-project-board.md
+++ b/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/managing-project-boards/copying-a-project-board.md
@@ -1,6 +1,6 @@
 ---
-title: '{% data variables.product.prodname_project_v1 %}のコピー'
-intro: '{% data variables.projects.projects_v1_board %}をコピーして、新しいプロジェクトをすばやく作成できます。 頻繁に使用される、または高度にカスタマイズされた{% data variables.projects.projects_v1_boards %}をコピーすると、ワークフローの標準化に役立ちます。'
+title: 'Copying a {% data variables.product.prodname_project_v1 %}'
+intro: 'You can copy a {% data variables.projects.projects_v1_board %} to quickly create a new project. Copying frequently used or highly customized {% data variables.projects.projects_v1_boards %} helps standardize your workflow.'
 redirect_from:
   - /github/managing-your-work-on-github/managing-project-boards/copying-a-project-board
   - /articles/copying-a-project-board
@@ -11,34 +11,29 @@ versions:
 topics:
   - Pull requests
 allowTitleToDifferFromFilename: true
-ms.openlocfilehash: 055e697d2bb5c7aa1ad4667d24bbe919ede87a99
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
-ms.translationtype: HT
-ms.contentlocale: ja-JP
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147423605'
 ---
 {% data reusables.projects.project_boards_old %}
 
-{% data variables.projects.projects_v1_board %}をコピーすると、{% data variables.projects.projects_v1_board %}のタイトル、説明、および自動化構成を再利用できます。 {% data variables.projects.projects_v1_boards %}をコピーすると、同様のワークフローで新しい{% data variables.projects.projects_v1_boards %}を作成する手動プロセスを排除できます。
+Copying a {% data variables.projects.projects_v1_board %} allows you to reuse a {% data variables.projects.projects_v1_board %}'s title, description, and automation configuration. You can copy {% data variables.projects.projects_v1_boards %} to eliminate the manual process of creating new {% data variables.projects.projects_v1_boards %} for similar workflows.
 
-{% data variables.projects.projects_v1_board %}を書き込みアクセスがあるリポジトリまたは Organization にコピーするには、読み取りアクセスが必要です。
+You must have read access to a {% data variables.projects.projects_v1_board %} to copy it to a repository or organization where you have write access.
 
-{% data variables.projects.projects_v1_board %}を Organization にコピーすると、{% data variables.projects.projects_v1_board %}の可視性は既定で非公開になり、可視性を変更するオプションが設定されます。 詳しくは、「[{% data variables.product.prodname_project_v1 %}の可視性の変更](/articles/changing-project-board-visibility/)」を参照してください。
+When you copy a {% data variables.projects.projects_v1_board %} to an organization, the {% data variables.projects.projects_v1_board %}'s visibility will default to private, with an option to change the visibility. For more information, see "[Changing {% data variables.product.prodname_project_v1 %} visibility](/articles/changing-project-board-visibility/)."
 
-既定では、{% data variables.projects.projects_v1_board %}の自動化も有効になっています。 詳しくは、「[{% data variables.product.prodname_projects_v1 %}の自動化について](/articles/about-automation-for-project-boards/)」を参照してください。
+A {% data variables.projects.projects_v1_board %}'s automation is also enabled by default. For more information, see "[About automation for {% data variables.product.prodname_projects_v1 %}](/articles/about-automation-for-project-boards/)."
 
-1. コピーする{% data variables.projects.projects_v1_board %}に移動します。
+1. Navigate to the {% data variables.projects.projects_v1_board %} you want to copy.
 {% data reusables.project-management.click-menu %}
-3. {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} をクリックし、 **[コピー]** をクリックします。
-![プロジェクトボードのサイドバーにある、ドロップダウンメニューの [Copy] オプション](/assets/images/help/projects/project-board-copy-setting.png)
-4. [Owner] の下にあるドロップダウンメニューで、プロジェクトボードのコピー先にするリポジトリまたは Organization をクリックします。
-![ドロップダウンメニューから、コピーしたプロジェクトボードのオーナーを選択](/assets/images/help/projects/copied-project-board-owner.png)
-5. 必要に応じて、[プロジェクト ボード名] に、コピーした{% data variables.projects.projects_v1_board %}の名前を入力します。
-![コピーされたプロジェクトボードの名前を入力するフィールド](/assets/images/help/projects/copied-project-board-name.png)
-6. 必要に応じて、他の人に読んでもらうために、[Description] の下に、コピーしたプロジェクトボードについての説明を入力します。
-![コピーしたプロジェクトボードの説明を入力するフィールド](/assets/images/help/projects/copied-project-board-description.png)
-7. 必要に応じて、[Automation settings] の下で、設定済みの自動化されたワークフローをコピーするかどうかを選択します。 既定では、このオプションは有効になっています。 詳しくは、「[プロジェクトボードの自動化について](/articles/about-automation-for-project-boards/)」を参照してください。
-![コピーされたプロジェクトボードの自動化設定を選ぶ](/assets/images/help/projects/copied-project-board-automation-settings.png) {% data reusables.project-management.choose-visibility %}
-9. **[プロジェクトのコピー]** をクリックします。
-![[コピーを確定する] ボタン](/assets/images/help/projects/confirm-copy-project-board.png)
+3. Click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, then click **Copy**.
+![Copy option in drop-down menu from project board sidebar](/assets/images/help/projects/project-board-copy-setting.png)
+4. Under "Owner", use the drop-down menu and click the repository or organization where you want to copy the project board.
+![Select owner of copied project board from drop-down menu](/assets/images/help/projects/copied-project-board-owner.png)
+5. Optionally, under "Project board name", type the name of the copied {% data variables.projects.projects_v1_board %}.
+![Field to type a name for the copied project board](/assets/images/help/projects/copied-project-board-name.png)
+6. Optionally, under "Description", type a description of the copied project board that other people will see.
+![Field to type a description for the copied project board](/assets/images/help/projects/copied-project-board-description.png)
+7. Optionally, under "Automation settings", select whether you want to copy the configured automatic workflows. This option is enabled by default. For more information, see "[About automation for project boards](/articles/about-automation-for-project-boards/)."
+![Select automation settings for copied project board](/assets/images/help/projects/copied-project-board-automation-settings.png)
+{% data reusables.project-management.choose-visibility %}
+9. Click **Copy project**.
+![Confirm Copy button](/assets/images/help/projects/confirm-copy-project-board.png)
diff --git a/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/managing-project-boards/creating-a-project-board.md b/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/managing-project-boards/creating-a-project-board.md
index d180658a19..8c2e267000 100644
--- a/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/managing-project-boards/creating-a-project-board.md
+++ b/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/managing-project-boards/creating-a-project-board.md
@@ -1,6 +1,6 @@
 ---
-title: '{% data variables.product.prodname_project_v1 %} の作成'
-intro: '{% data variables.projects.projects_v1_boards_caps %} は、特定機能の作業の追跡と優先度付け、総合的なロードマップ、さらにはリリース チェックリストなど、ニーズを満たすカスタマイズ ワークフローを作成するために使用できます。'
+title: 'Creating a {% data variables.product.prodname_project_v1 %}'
+intro: '{% data variables.projects.projects_v1_boards_caps %} can be used to create customized workflows to suit your needs, like tracking and prioritizing specific feature work, comprehensive roadmaps, or even release checklists.'
 redirect_from:
   - /github/managing-your-work-on-github/managing-project-boards/creating-a-project-board
   - /articles/creating-a-project
@@ -15,12 +15,6 @@ topics:
   - Project management
 type: how_to
 allowTitleToDifferFromFilename: true
-ms.openlocfilehash: 9c55be9ea212cf9a09147267fc62da8f6f89fbbc
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
-ms.translationtype: HT
-ms.contentlocale: ja-JP
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147614256'
 ---
 {% data reusables.projects.project_boards_old %}
 
@@ -28,55 +22,94 @@ ms.locfileid: '147614256'
 
 {% data reusables.project-management.copy-project-boards %}
 
-{% data reusables.project-management.link-repos-to-project-board %} 詳しい情報については、「[{% data variables.product.prodname_project_v1 %} へのリポジトリのリンク](/articles/linking-a-repository-to-a-project-board)」を参照してください。
+{% data reusables.project-management.link-repos-to-project-board %} For more information, see "[Linking a repository to a {% data variables.product.prodname_project_v1 %}
+](/articles/linking-a-repository-to-a-project-board)."
 
-{% data variables.projects.projects_v1_board %} を作成したら、issue、pull request、ノートを追加できます。 詳しい情報については、「[{% data variables.product.prodname_project_v1 %} への issue と pull request の追加](/articles/adding-issues-and-pull-requests-to-a-project-board)」および「[{% data variables.product.prodname_project_v1 %} へのノートの追加](/articles/adding-notes-to-a-project-board)」を参照してください。
+Once you've created your {% data variables.projects.projects_v1_board %}, you can add issues, pull requests, and notes to it. For more information, see "[Adding issues and pull requests to a {% data variables.product.prodname_project_v1 %}](/articles/adding-issues-and-pull-requests-to-a-project-board)" and "[Adding notes to a {% data variables.product.prodname_project_v1 %}](/articles/adding-notes-to-a-project-board)."
 
-{% data variables.projects.projects_v1_board %} を issue や pull request の状態と常に同期させるようにワークフローの自動化を構成することもできます。 詳しい情報については、「[{% data variables.product.prodname_projects_v1 %} の自動化について](/articles/about-automation-for-project-boards)」を参照してください。
+You can also configure workflow automations to keep your {% data variables.projects.projects_v1_board %} in sync with the status of issues and pull requests. For more information, see "[About automation for {% data variables.product.prodname_projects_v1 %}](/articles/about-automation-for-project-boards)."
 
 {% data reusables.project-management.project-board-import-with-api %}
 
-## ユーザー所有の {% data variables.projects.projects_v1_board %} の作成
+## Creating a user-owned {% data variables.projects.projects_v1_board %}
 
 {% data reusables.projects.classic-project-creation %}
 
 {% data reusables.profile.access_profile %}
-2. プロファイル ページの上部のメイン ナビゲーションにある {% octicon "project" aria-label="The project board icon" %} **[プロジェクト]** をクリックします。
-![[プロジェクト] タブ](/assets/images/help/projects/user-projects-tab.png){% ifversion projects-v2 %}
-1. **[Project (classic)]** をクリックします{% endif %} {% data reusables.project-management.click-new-project %} {% data reusables.project-management.create-project-name-description %} {% data reusables.project-management.choose-template %} {% data reusables.project-management.choose-visibility %} {% data reusables.project-management.linked-repositories %} {% data reusables.project-management.create-project-button %} {% data reusables.project-management.add-column-new-project %} {% data reusables.project-management.name-project-board-column %} {% data reusables.project-management.select-column-preset %} {% data reusables.project-management.select-automation-options-new-column %} {% data reusables.project-management.click-create-column %} {% data reusables.project-management.add-more-columns %}
+2. On the top of your profile page, in the main navigation, click {% octicon "project" aria-label="The project board icon" %} **Projects**.
+![Project tab](/assets/images/help/projects/user-projects-tab.png){% ifversion projects-v2 %}
+1. Click **Projects (classic)**{% endif %}
+{% data reusables.project-management.click-new-project %}
+{% data reusables.project-management.create-project-name-description %}
+{% data reusables.project-management.choose-template %}
+{% data reusables.project-management.choose-visibility %}
+{% data reusables.project-management.linked-repositories %}
+{% data reusables.project-management.create-project-button %}
+{% data reusables.project-management.add-column-new-project %}
+{% data reusables.project-management.name-project-board-column %}
+{% data reusables.project-management.select-column-preset %}
+{% data reusables.project-management.select-automation-options-new-column %}
+{% data reusables.project-management.click-create-column %}
+{% data reusables.project-management.add-more-columns %}
 
 {% data reusables.project-management.edit-project-columns %}
 
-## Organization 全体の {% data variables.projects.projects_v1_board %} の作成
+## Creating an organization-wide {% data variables.projects.projects_v1_board %}
 
 {% data reusables.projects.classic-project-creation %}
 
-{% ifversion classic-project-visibility-permissions %} {% note %}
+{% ifversion classic-project-visibility-permissions %}
+{% note %}
 
-**注:** {% data reusables.projects.owners-can-limit-visibility-permissions %}
+**Note:** {% data reusables.projects.owners-can-limit-visibility-permissions %}
 
-{% endnote %} {% endif %}
+{% endnote %}
+{% endif %}
 
-{% data reusables.profile.access_org %} {% data reusables.user-settings.access_org %} {% data reusables.organizations.organization-wide-project %}{% ifversion projects-v2 %}
-1. **[Project (classic)]** をクリックします{% endif %} {% data reusables.project-management.click-new-project %} {% data reusables.project-management.create-project-name-description %} {% data reusables.project-management.choose-template %} {% data reusables.project-management.choose-visibility %} {% data reusables.project-management.linked-repositories %} {% data reusables.project-management.create-project-button %} {% data reusables.project-management.add-column-new-project %} {% data reusables.project-management.name-project-board-column %} {% data reusables.project-management.select-column-preset %} {% data reusables.project-management.select-automation-options-new-column %} {% data reusables.project-management.click-create-column %} {% data reusables.project-management.add-more-columns %}
+{% data reusables.profile.access_org %}
+{% data reusables.user-settings.access_org %}
+{% data reusables.organizations.organization-wide-project %}{% ifversion projects-v2 %}
+1. Click **Projects (classic)**{% endif %}
+{% data reusables.project-management.click-new-project %}
+{% data reusables.project-management.create-project-name-description %}
+{% data reusables.project-management.choose-template %}
+{% data reusables.project-management.choose-visibility %}
+{% data reusables.project-management.linked-repositories %}
+{% data reusables.project-management.create-project-button %}
+{% data reusables.project-management.add-column-new-project %}
+{% data reusables.project-management.name-project-board-column %}
+{% data reusables.project-management.select-column-preset %}
+{% data reusables.project-management.select-automation-options-new-column %}
+{% data reusables.project-management.click-create-column %}
+{% data reusables.project-management.add-more-columns %}
 
 {% data reusables.project-management.edit-project-columns %}
 
-## リポジトリの {% data variables.projects.projects_v1_board %} の作成
+## Creating a repository {% data variables.projects.projects_v1_board %}
 
 {% data reusables.projects.classic-project-creation %}
 
 {% data reusables.repositories.navigate-to-repo %}
-2. リポジトリ名の下にある {% octicon "project" aria-label="The project board icon" %} **[プロジェクト]** をクリックします。
-![[プロジェクト] タブ](/assets/images/help/projects/repo-tabs-projects.png){% ifversion projects-v2 %}
-1. **[Project (classic)]** をクリックします{% endif %} {% data reusables.project-management.click-new-project %} {% data reusables.project-management.create-project-name-description %} {% data reusables.project-management.choose-template %} {% data reusables.project-management.create-project-button %} {% data reusables.project-management.add-column-new-project %} {% data reusables.project-management.name-project-board-column %} {% data reusables.project-management.select-column-preset %} {% data reusables.project-management.select-automation-options-new-column %} {% data reusables.project-management.click-create-column %} {% data reusables.project-management.add-more-columns %}
+2. Under your repository name, click {% octicon "project" aria-label="The project board icon" %} **Projects**.
+![Project tab](/assets/images/help/projects/repo-tabs-projects.png){% ifversion projects-v2 %}
+1. Click **Projects (classic)**{% endif %}
+{% data reusables.project-management.click-new-project %}
+{% data reusables.project-management.create-project-name-description %}
+{% data reusables.project-management.choose-template %}
+{% data reusables.project-management.create-project-button %}
+{% data reusables.project-management.add-column-new-project %}
+{% data reusables.project-management.name-project-board-column %}
+{% data reusables.project-management.select-column-preset %}
+{% data reusables.project-management.select-automation-options-new-column %}
+{% data reusables.project-management.click-create-column %}
+{% data reusables.project-management.add-more-columns %}
 
 {% data reusables.project-management.edit-project-columns %}
 
-## 参考資料
+## Further reading
 
-- 「[プロジェクトボードについて](/articles/about-project-boards)」
-- 「[プロジェクトボードの編集](/articles/editing-a-project-board)」{% ifversion fpt or ghec %}
-- 「[プロジェクトボードをコピーする](/articles/copying-a-project-board)」{% endif %}
-- 「[プロジェクト ボードを閉じる](/articles/closing-a-project-board)」
-- 「[プロジェクトボードの自動化について](/articles/about-automation-for-project-boards)」
+- "[About projects boards](/articles/about-project-boards)"
+- "[Editing a project board](/articles/editing-a-project-board)"{% ifversion fpt or ghec %}
+- "[Copying a project board](/articles/copying-a-project-board)"{% endif %}
+- "[Closing a project board](/articles/closing-a-project-board)"
+- "[About automation for project boards](/articles/about-automation-for-project-boards)"
diff --git a/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/managing-project-boards/deleting-a-project-board.md b/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/managing-project-boards/deleting-a-project-board.md
index e86b20e254..05eb5e1acd 100644
--- a/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/managing-project-boards/deleting-a-project-board.md
+++ b/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/managing-project-boards/deleting-a-project-board.md
@@ -11,12 +11,12 @@ versions:
 topics:
   - Pull requests
 allowTitleToDifferFromFilename: true
-ms.openlocfilehash: 13de993715fa8e16f8cbce4555214e7940fb4917
-ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d
+ms.openlocfilehash: fb68b796fa41a565ab2e196f878c17c94ec44a06
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: ja-JP
-ms.lasthandoff: 09/11/2022
-ms.locfileid: '147422973'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148108940'
 ---
 {% data reusables.projects.project_boards_old %}
 
diff --git a/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/managing-project-boards/editing-a-project-board.md b/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/managing-project-boards/editing-a-project-board.md
index fb5cf085e0..61f1a571d6 100644
--- a/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/managing-project-boards/editing-a-project-board.md
+++ b/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/managing-project-boards/editing-a-project-board.md
@@ -12,12 +12,12 @@ versions:
 topics:
   - Pull requests
 allowTitleToDifferFromFilename: true
-ms.openlocfilehash: 23e4958654bd58de323e401ab4b47d1205aaa4ce
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: 9b3811bcd472d44be809681064476e7e4f5bef08
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: ja-JP
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147422957'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148109564'
 ---
 {% data reusables.projects.project_boards_old %}
 
diff --git a/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/managing-project-boards/index.md b/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/managing-project-boards/index.md
index ce33454c75..8f7087dfd5 100644
--- a/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/managing-project-boards/index.md
+++ b/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/managing-project-boards/index.md
@@ -22,11 +22,11 @@ children:
 redirect_from:
   - /github/managing-your-work-on-github/managing-project-boards
 allowTitleToDifferFromFilename: true
-ms.openlocfilehash: a480750b4c44c7934efa6a0a554c1cf7040629de
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: b4034bc9c9ffd29709ac491c6729787c958dd50b
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: ja-JP
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147422941'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148109571'
 ---
 {% data reusables.projects.project_boards_old %}
diff --git a/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/managing-project-boards/linking-a-repository-to-a-project-board.md b/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/managing-project-boards/linking-a-repository-to-a-project-board.md
index 84e2ed7155..4417ce54eb 100644
--- a/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/managing-project-boards/linking-a-repository-to-a-project-board.md
+++ b/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/managing-project-boards/linking-a-repository-to-a-project-board.md
@@ -11,12 +11,12 @@ topics:
   - Pull requests
 shortTitle: Link repository to board
 allowTitleToDifferFromFilename: true
-ms.openlocfilehash: 939266bff35928f5b0ae33fe1cce1b380698ee85
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: d0893b64551be80577547b9791e7a7ed6a432de0
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: ja-JP
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147423261'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148109697'
 ---
 {% data reusables.projects.project_boards_old %}
 
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 0b13cd155e..b5fabfbc82 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
@@ -11,12 +11,12 @@ topics:
   - Pull requests
 shortTitle: 'Reopen {% data variables.product.prodname_project_v1 %}'
 allowTitleToDifferFromFilename: true
-ms.openlocfilehash: d865d4b61000857c943276c45a9ec02163e9f59b
-ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.openlocfilehash: e0101378c0b7049f7cba5e04dd28231a1237d0c5
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: ja-JP
-ms.lasthandoff: 09/11/2022
-ms.locfileid: '147882200'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148109572'
 ---
 {% data reusables.projects.project_boards_old %}
 
diff --git a/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/adding-issues-and-pull-requests-to-a-project-board.md b/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/adding-issues-and-pull-requests-to-a-project-board.md
index 32b9e379be..45a23052ee 100644
--- a/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/adding-issues-and-pull-requests-to-a-project-board.md
+++ b/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/adding-issues-and-pull-requests-to-a-project-board.md
@@ -12,12 +12,12 @@ topics:
   - Pull requests
 shortTitle: 'Add issues & PRs to {% data variables.product.prodname_project_v1 %}'
 allowTitleToDifferFromFilename: true
-ms.openlocfilehash: 36897518283fa085c37363157fb44cbd8e1a75c6
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: 3adfb2c337a417b8e4f932ab9ae9860939217c6c
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: ja-JP
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147422773'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148109692'
 ---
 {% data reusables.projects.project_boards_old %}
 
diff --git a/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/adding-notes-to-a-project-board.md b/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/adding-notes-to-a-project-board.md
index d7ae97a085..c2a8923ccf 100644
--- a/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/adding-notes-to-a-project-board.md
+++ b/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/adding-notes-to-a-project-board.md
@@ -12,12 +12,12 @@ topics:
   - Pull requests
 shortTitle: 'Add notes to {% data variables.product.prodname_project_v1 %}'
 allowTitleToDifferFromFilename: true
-ms.openlocfilehash: 46068bb6de081043b05c78e731a09e7dbaa47c78
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: fc9df02b211056a08ed608a6c98b9d2f0b78c5b7
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: ja-JP
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147422749'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148109788'
 ---
 {% data reusables.projects.project_boards_old %}
 
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 1d1148345a..14a1977859 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
@@ -11,12 +11,12 @@ topics:
   - Pull requests
 shortTitle: 'Archive cards on {% data variables.product.prodname_project_v1 %}'
 allowTitleToDifferFromFilename: true
-ms.openlocfilehash: de1d0a4981a46c4ceddd73b5d1f49b74f111601f
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: bef90f56a55d6d087c21603586def91ec2f1c9ed
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: ja-JP
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147423589'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148109691'
 ---
 {% data reusables.projects.project_boards_old %}
 
diff --git a/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/filtering-cards-on-a-project-board.md b/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/filtering-cards-on-a-project-board.md
index f897fec764..da73054b12 100644
--- a/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/filtering-cards-on-a-project-board.md
+++ b/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/filtering-cards-on-a-project-board.md
@@ -11,12 +11,12 @@ topics:
   - Pull requests
 shortTitle: 'Filter cards on {% data variables.product.prodname_project_v1 %}'
 allowTitleToDifferFromFilename: true
-ms.openlocfilehash: 337c84415fefad0c542c6b46706de716e71c29b9
-ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d
+ms.openlocfilehash: f203785a6fc18dc5f67b2ae62934aa10c2f6e8b8
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: ja-JP
-ms.lasthandoff: 09/11/2022
-ms.locfileid: '147882312'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148109556'
 ---
 {% data reusables.projects.project_boards_old %}
 
diff --git a/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/index.md b/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/index.md
index 298e3455f2..be5a9da8aa 100644
--- a/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/index.md
+++ b/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/index.md
@@ -16,11 +16,11 @@ children:
 redirect_from:
   - /github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-project-boards
 allowTitleToDifferFromFilename: true
-ms.openlocfilehash: ba1428a6423198d972abfb6671165b43c4988f94
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: 75699a8c8daa2729de4aaa7389b7e9a0448f09fa
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: ja-JP
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147423621'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148109037'
 ---
 {% data reusables.projects.project_boards_old %}
diff --git a/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/tracking-progress-on-your-project-board.md b/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/tracking-progress-on-your-project-board.md
index f5538eb2e5..c745a9209d 100644
--- a/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/tracking-progress-on-your-project-board.md
+++ b/translations/ja-JP/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/tracking-progress-on-your-project-board.md
@@ -11,12 +11,12 @@ topics:
   - Pull requests
 shortTitle: 'Track progress on {% data variables.product.prodname_project_v1 %}'
 allowTitleToDifferFromFilename: true
-ms.openlocfilehash: 8dae880cb0ef0fbd0a136e16029688c4aaef08ac
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: 5104029ad5225c217697ea89a4bca8ff2d3fa4b5
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: ja-JP
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147422669'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148109036'
 ---
 {% data reusables.projects.project_boards_old %}
 
diff --git a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/automating-your-project/automating-projects-using-actions.md b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/automating-your-project/automating-projects-using-actions.md
index 3b0e137b23..87e7359893 100644
--- a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/automating-your-project/automating-projects-using-actions.md
+++ b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/automating-your-project/automating-projects-using-actions.md
@@ -1,10 +1,10 @@
 ---
 title: 'Automating {% data variables.product.prodname_projects_v2 %} using Actions'
-shortTitle: 'Automating with Actions'
+shortTitle: Automating with Actions
 intro: 'You can use {% data variables.product.prodname_actions %} to automate your projects.'
 miniTocMaxHeadingLevel: 3
 versions:
-  feature: "projects-v2"
+  feature: projects-v2
 redirect_from:
   - /issues/trying-out-the-new-projects-experience/automating-projects
 type: tutorial
diff --git a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/automating-your-project/index.md b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/automating-your-project/index.md
index 2f4dad0c08..93a635bf68 100644
--- a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/automating-your-project/index.md
+++ b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/automating-your-project/index.md
@@ -13,11 +13,11 @@ children:
   - /automating-projects-using-actions
   - /archiving-items-automatically
 allowTitleToDifferFromFilename: true
-ms.openlocfilehash: 6c9777a65125f574e4a2cd05a7177448606f8348
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: 9187012a572af445192343af1b1ba121ae442087
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: ja-JP
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147424008'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148107230'
 ---
 
diff --git a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/automating-your-project/using-the-api-to-manage-projects.md b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/automating-your-project/using-the-api-to-manage-projects.md
index afb973e02b..e2b1241fa3 100644
--- a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/automating-your-project/using-the-api-to-manage-projects.md
+++ b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/automating-your-project/using-the-api-to-manage-projects.md
@@ -1,10 +1,10 @@
 ---
 title: 'Using the API to manage {% data variables.product.prodname_projects_v2 %}'
-shortTitle: 'Automating with the API'
-intro: 'You can use the GraphQL API to automate your projects.'
+shortTitle: Automating with the API
+intro: You can use the GraphQL API to automate your projects.
 miniTocMaxHeadingLevel: 3
 versions:
-  feature: "projects-v2"
+  feature: projects-v2
 redirect_from:
   - /issues/trying-out-the-new-projects-experience/using-the-api-to-manage-projects
 type: tutorial
@@ -511,7 +511,7 @@ The response will contain the node ID of the newly created draft issue.
 ```json
 {
   "data": {
-    "addProjectV2ItemById": {
+    "addProjectV2DraftIssue": {
       "projectItem": {
         "id": "PVTI_lADOANN5s84ACbL0zgBbxFc"
       }
diff --git a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/automating-your-project/using-the-built-in-automations.md b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/automating-your-project/using-the-built-in-automations.md
index 44e12998e2..ec7814330c 100644
--- a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/automating-your-project/using-the-built-in-automations.md
+++ b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/automating-your-project/using-the-built-in-automations.md
@@ -8,12 +8,12 @@ versions:
 type: tutorial
 topics:
   - Projects
-ms.openlocfilehash: 950ad805eaf73361c2c790d9e30c2e1708a871d8
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: 40f82bbe99ff036a70007f38534d401a972516f7
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: ja-JP
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147424878'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148109492'
 ---
 {% note %}
 
diff --git a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/creating-projects/creating-a-project.md b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/creating-projects/creating-a-project.md
index 86baf1ff2f..0b5e8191cc 100644
--- a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/creating-projects/creating-a-project.md
+++ b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/creating-projects/creating-a-project.md
@@ -10,12 +10,12 @@ type: tutorial
 topics:
   - Projects
 allowTitleToDifferFromFilename: true
-ms.openlocfilehash: 0827845ea3dff3a641d99bbac20b8febdfaca885
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: 6cbe9313866c19e8325bdd34e90c6a39863de515
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: ja-JP
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147424120'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148109484'
 ---
 {% data variables.product.prodname_projects_v2 %} は、{% data variables.product.company_short %} データを最新の状態に保つアイテムの適応可能なコレクションです。 プロジェクトでは、issue、pull request、メモしたアイデアを追跡できます。 カスタムフィールドを追加して、特定の目的のためのビューを作成できます。
 
diff --git a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/creating-projects/index.md b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/creating-projects/index.md
index cf5fc06b41..5f7d5c1bcf 100644
--- a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/creating-projects/index.md
+++ b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/creating-projects/index.md
@@ -11,11 +11,11 @@ children:
   - /creating-a-project
   - /migrating-from-projects-classic
 allowTitleToDifferFromFilename: true
-ms.openlocfilehash: 3ad98749a0f404446cab9942b8e10883a31bf3ab
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: 4d982f7f1f5fa66f372bcca74cea084cb2497d9c
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: ja-JP
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147424117'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148109491'
 ---
 
diff --git a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/creating-projects/migrating-from-projects-classic.md b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/creating-projects/migrating-from-projects-classic.md
index 1cff91eeec..3c10aabb59 100644
--- a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/creating-projects/migrating-from-projects-classic.md
+++ b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/creating-projects/migrating-from-projects-classic.md
@@ -1,6 +1,6 @@
 ---
-title: '{% data variables.product.prodname_projects_v1 %} からの移行'
-intro: '{% data variables.projects.projects_v1_board %} を新しい {% data variables.product.prodname_projects_v2 %} エクスペリエンスに移行できます。'
+title: 'Migrating from {% data variables.product.prodname_projects_v1 %}'
+intro: 'You can migrate your {% data variables.projects.projects_v1_board %} to the new {% data variables.product.prodname_projects_v2 %} experience.'
 miniTocMaxHeadingLevel: 3
 versions:
   feature: projects-v2
@@ -10,53 +10,57 @@ type: tutorial
 topics:
   - Projects
 allowTitleToDifferFromFilename: true
-ms.openlocfilehash: b16235e98306e19a8f08dfc04913c6935772b5cc
-ms.sourcegitcommit: 76b840f45ba85fb79a7f0c1eb43bc663b3eadf2b
-ms.translationtype: HT
-ms.contentlocale: ja-JP
-ms.lasthandoff: 09/12/2022
-ms.locfileid: '147424116'
 ---
-{% note %}
 
-**注:**
-
-- 移行するプロジェクトに 1,200 を超える項目が含まれている場合は、未解決の issue が優先され、その後に未解決の pull request、メモが続きます。 残りの領域は、解決された issue、マージされた pull request、および解決された pull request に使用されます。 この制限により移行できない項目は、アーカイブに移動されます。 アーカイブの上限である 10,000 項目に達した場合、追加の項目は移行されません。
-- ノート カードは下書きの issue に変換され、内容は下書きの issue の本文に保存されます。 情報が見つからないように見える場合は、非表示フィールドを表示します。 詳しくは、「[フィールドの表示と非表示](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/customizing-a-view#showing-and-hiding-fields)」を参照してください。
-- 自動化は移行されません。
-- トリアージ、アーカイブ、アクティビティは移行されません。
-- 移行後、新しく移行されたプロジェクトと古いプロジェクトは同期されません。
-
-{% endnote %}
-
-## プロジェクトの移行について
-
-プロジェクト ボードを新しい {% data variables.product.prodname_projects_v2 %} エクスペリエンスに移行し、テーブル、複数のビュー、新しい自動化オプション、強力なフィールドの種類を試すことができます。 詳しくは、「[プロジェクトについて](/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)」を参照してください。
-
-## 組織のプロジェクト ボードの移行
-
-{% data reusables.projects.enable-migration %} {% data reusables.profile.access_org %} {% data reusables.user-settings.access_org %} {% data reusables.organizations.organization-wide-project %}
-1. 左側の **[プロジェクト (クラシック)]** をクリックします。
-  ![[プロジェクト (クラシック)] メニュー オプションを示すスクリーンショット](/assets/images/help/issues/projects-classic-org.png) {% data reusables.projects.migrate-project-steps %}
-
-## ユーザー プロジェクト ボードの移行
-
-{% data reusables.projects.enable-migration %} {% data reusables.profile.access_profile %}
-1. プロファイル ページの上部のメイン ナビゲーションにある {% octicon "project" aria-label="The project board icon" %} **[プロジェクト]** をクリックします。
-![[プロジェクト] タブ](/assets/images/help/projects/user-projects-tab.png)
-1. プロジェクトの一覧の上にある **[プロジェクト (クラシック)]** をクリックします。
-  ![[プロジェクト (クラシック)] メニュー オプションを示すスクリーンショット](/assets/images/help/issues/projects-classic-user.png) {% data reusables.projects.migrate-project-steps %}
-
-## リポジトリのプロジェクトボードの移行
 
 {% note %}
 
-**注:** {% data variables.projects.projects_v2_caps %} では、リポジトリ レベルのプロジェクトはサポートされていません。 リポジトリ プロジェクト ボードを移行すると、リポジトリ プロジェクトを所有する組織または個人アカウントに移行され、移行されたプロジェクトは元のリポジトリにピン留めされます。
+**Notes:**
+
+- If the project you are migrating contains more than 1200 items, open issues will be prioritized followed by open pull requests and then notes. Remaining space will be used for closed issues, merged pull requested, and closed pull requests. Items that cannot be migrated due to this limit will be moved to the archive. If the archive limit of 10,000 items is reached, additional items will not be migrated.
+- Note cards are converted to draft issues, and the contents are saved to the body of the draft issue. If information appears to be missing, make any hidden fields visible. For more information, see "[Showing and hiding fields](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/customizing-a-view#showing-and-hiding-fields)."
+- Automation will not be migrated.
+- Triage, archive, and activity will not be migrated.
+- After migration, the new migrated project and old project will not be kept in sync.
 
 {% endnote %}
 
-{% data reusables.projects.enable-migration %} {% data reusables.repositories.navigate-to-repo %}
-1. リポジトリ名の下にある {% octicon "project" aria-label="The project board icon" %} **[プロジェクト]** をクリックします。
-![[プロジェクト] タブ](/assets/images/help/projects/repo-tabs-projects.png)
-1. **[プロジェクト (クラシック)]** をクリックします。
-  ![[プロジェクト (クラシック)] メニュー オプションを示すスクリーンショット](/assets/images/help/issues/projects-classic-org.png) {% data reusables.projects.migrate-project-steps %}
+## About project migration
+
+You can migrate your project boards to the new {% data variables.product.prodname_projects_v2 %} experience and try out tables, multiple views, new automation options, and powerful field types. For more information, see "[About projects](/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)."
+
+## Migrating an organization project board
+
+{% data reusables.projects.enable-migration %}
+{% data reusables.profile.access_org %}
+{% data reusables.user-settings.access_org %}
+{% data reusables.organizations.organization-wide-project %}
+1. On the left, click **Projects (classic)**.
+  ![Screenshot showing Projects (classic) menu option}](/assets/images/help/issues/projects-classic-org.png)
+{% data reusables.projects.migrate-project-steps %}
+
+## Migrating a user project board
+
+{% data reusables.projects.enable-migration %}
+{% data reusables.profile.access_profile %}
+1. On the top of your profile page, in the main navigation, click {% octicon "project" aria-label="The project board icon" %} **Projects**.
+![Project tab](/assets/images/help/projects/user-projects-tab.png)
+1. Above the list of projects, click **Projects (classic)**.
+  ![Screenshot showing Projects (classic) menu option}](/assets/images/help/issues/projects-classic-user.png)
+{% data reusables.projects.migrate-project-steps %}
+
+## Migrating a repository project board
+
+{% note %}
+
+**Note:** {% data variables.projects.projects_v2_caps %} does not support repository level projects. When you migrate a repository project board, it will migrate to either the organization or personal account that owns the repository project, and the migrated project will be pinned to the original repository.
+
+{% endnote %}
+
+{% data reusables.projects.enable-migration %}
+{% data reusables.repositories.navigate-to-repo %}
+1. Under your repository name, click {% octicon "project" aria-label="The project board icon" %} **Projects**.
+![Project tab](/assets/images/help/projects/repo-tabs-projects.png)
+1. Click **Projects (classic)**.
+  ![Screenshot showing Projects (classic) menu option}](/assets/images/help/issues/projects-classic-org.png)
+{% data reusables.projects.migrate-project-steps %}
diff --git a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/customizing-a-view.md b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/customizing-a-view.md
index 1929b511b2..960ace9738 100644
--- a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/customizing-a-view.md
+++ b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/customizing-a-view.md
@@ -1,9 +1,9 @@
 ---
-title: 'Customizing a view'
+title: Customizing a view
 intro: 'Display the information you need by changing the layout, grouping, sorting in your project.'
 miniTocMaxHeadingLevel: 3
 versions:
-  feature: "projects-v2"
+  feature: projects-v2
 redirect_from:
   - /issues/trying-out-the-new-projects-experience/customizing-your-project-views
 type: tutorial
@@ -147,4 +147,4 @@ In the board layout, you can can choose which columns to display. The available
    
    ![Screenshot showing the list of columns](/assets/images/help/projects-v2/board-select-columns.png)
    
-{% endif %}
\ No newline at end of file
+{% endif %}
diff --git a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/filtering-projects.md b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/filtering-projects.md
index dd1f43e5b5..171c7b065d 100644
--- a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/filtering-projects.md
+++ b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/filtering-projects.md
@@ -10,12 +10,12 @@ type: tutorial
 topics:
   - Projects
 allowTitleToDifferFromFilename: true
-ms.openlocfilehash: 820a9b22deab6ecaf7fa06129e2205267b22812c
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: b1c04738a3c03d892b360c3b23def694d202ee0c
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: ja-JP
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147424183'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148109025'
 ---
 Issueにアサインされた人やラベルといったアイテムのメタデータやプロジェクトのフィールドに対するフィルタを使って、ビューをカスタマイズできます。 フィルタを組み合わせて、ビューとして保存できます。 詳しくは、「[プロジェクトのビューのカスタマイズ](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/customizing-a-view)」をご覧ください。
 
diff --git a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/index.md b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/index.md
index da6bf82a9b..4930d06904 100644
--- a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/index.md
+++ b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/index.md
@@ -12,11 +12,11 @@ children:
   - /filtering-projects
   - /managing-your-views
 allowTitleToDifferFromFilename: true
-ms.openlocfilehash: c5a7f7f8aff5ab61a4711f6fbb30f64cf9fea002
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: 10c4aaf54f90773acb1d7a9ed2a8dc186278010e
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: ja-JP
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147424177'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148109030'
 ---
 
diff --git a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/managing-your-views.md b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/managing-your-views.md
index 1d088d8a7a..4989b89d22 100644
--- a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/managing-your-views.md
+++ b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/managing-your-views.md
@@ -7,12 +7,12 @@ versions:
 type: tutorial
 topics:
   - Projects
-ms.openlocfilehash: d434b4b086c1ec8526c3214161ac00d58dced4fd
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: 9b3d7f4b12210841a0c55f3b0b7356da9b225416
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: ja-JP
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147424162'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148109563'
 ---
 ## プロジェクトビューの作成
 
diff --git a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/index.md b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/index.md
index bf31061a3e..27c380429f 100644
--- a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/index.md
+++ b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/index.md
@@ -19,11 +19,11 @@ children:
 allowTitleToDifferFromFilename: true
 redirect_from:
   - /issues/trying-out-the-new-projects-experience
-ms.openlocfilehash: de9bdc87563e88ac945783bc8e98fd520dfb36ef
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: 80a894cdca5dda3afff3476a8209cb54589c89b5
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: ja-JP
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147425249'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148109555'
 ---
 
diff --git a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects.md b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects.md
index 61e008d2ad..d189455973 100644
--- a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects.md
+++ b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects.md
@@ -10,12 +10,12 @@ redirect_from:
 type: overview
 topics:
   - Projects
-ms.openlocfilehash: f50d54b95862102eafe97dcf1dfcec4daa1d7995
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: 4de4e96b6e445a29377c63188f6529c5b2023a5e
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: ja-JP
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147424156'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148109031'
 ---
 ## {% data variables.product.prodname_projects_v2 %} について
 
diff --git a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/learning-about-projects/best-practices-for-projects.md b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/learning-about-projects/best-practices-for-projects.md
index d427bed2f3..bc5b255031 100644
--- a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/learning-about-projects/best-practices-for-projects.md
+++ b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/learning-about-projects/best-practices-for-projects.md
@@ -1,10 +1,10 @@
 ---
 title: 'Best practices for {% data variables.product.prodname_projects_v2 %}'
-intro: 'Learn tips for managing your projects.'
+intro: Learn tips for managing your projects.
 allowTitleToDifferFromFilename: true
 miniTocMaxHeadingLevel: 3
 versions:
-  feature: "projects-v2"
+  feature: projects-v2
 redirect_from:
   - /issues/trying-out-the-new-projects-experience/best-practices-for-managing-projects
 type: overview
diff --git a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/learning-about-projects/index.md b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/learning-about-projects/index.md
index 32a5d28e69..ad03814aee 100644
--- a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/learning-about-projects/index.md
+++ b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/learning-about-projects/index.md
@@ -11,11 +11,11 @@ children:
   - /quickstart-for-projects
   - /best-practices-for-projects
 allowTitleToDifferFromFilename: true
-ms.openlocfilehash: 3bd91ba9dda01dd1dc567cde62336a86b3968260
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: 3629a25866eb08c704ee857ef78140e356202337
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: ja-JP
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147424153'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148109024'
 ---
 
diff --git a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/learning-about-projects/quickstart-for-projects.md b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/learning-about-projects/quickstart-for-projects.md
index 19ea9a2d17..d61e693b56 100644
--- a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/learning-about-projects/quickstart-for-projects.md
+++ b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/learning-about-projects/quickstart-for-projects.md
@@ -10,12 +10,12 @@ redirect_from:
 type: quick_start
 topics:
   - Projects
-ms.openlocfilehash: 165f12f1f76bcc571a7f7c47c33106bad2d6ff42
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: 39798565419acaa831a996a0c86cc62f367f4bb7
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: ja-JP
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147424053'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148109685'
 ---
 ## はじめに
 
diff --git a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/managing-items-in-your-project/adding-items-to-your-project.md b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/managing-items-in-your-project/adding-items-to-your-project.md
index 7fc55bb88e..25daa92188 100644
--- a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/managing-items-in-your-project/adding-items-to-your-project.md
+++ b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/managing-items-in-your-project/adding-items-to-your-project.md
@@ -1,10 +1,10 @@
 ---
 title: 'Adding items to your {% data variables.projects.project_v2 %}'
-shortTitle: 'Adding items'
+shortTitle: Adding items
 intro: 'Learn how to add pull requests, issues, and draft issues to your projects individually or in bulk.'
 miniTocMaxHeadingLevel: 4
 versions:
-  feature: "projects-v2"
+  feature: projects-v2
 type: tutorial
 topics:
   - Projects
@@ -83,4 +83,4 @@ Draft issues can have a title, text body, assignees, and any custom fields from
 
 **Note**: Users will not receive notifications when they are assigned to or mentioned in a draft issue unless the draft issue is converted to an issue.
 
-{% endnote %}
\ No newline at end of file
+{% endnote %}
diff --git a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/managing-items-in-your-project/archiving-items-from-your-project.md b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/managing-items-in-your-project/archiving-items-from-your-project.md
index d49c64ef7c..05edecb409 100644
--- a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/managing-items-in-your-project/archiving-items-from-your-project.md
+++ b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/managing-items-in-your-project/archiving-items-from-your-project.md
@@ -1,10 +1,10 @@
 ---
 title: 'Archiving items from your {% data variables.projects.project_v2 %}'
-shortTitle: 'Archiving items'
+shortTitle: Archiving items
 intro: 'You can archive items, keeping them available to restore, or permanently delete them.'
 miniTocMaxHeadingLevel: 2
 versions:
-  feature: "projects-v2"
+  feature: projects-v2
 type: tutorial
 topics:
   - Projects
@@ -45,4 +45,4 @@ You can delete an item to remove it from the project entirely.
 1. Click **Delete from project**.
    ![Screenshot showing delete option](/assets/images/help/projects-v2/delete-menu-item.png)
 1. When prompted, confirm your choice by clicking **Delete**.
-   ![Screenshot showing delete prompt](/assets/images/help/projects-v2/delete-item-prompt.png)
\ No newline at end of file
+   ![Screenshot showing delete prompt](/assets/images/help/projects-v2/delete-item-prompt.png)
diff --git a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/managing-items-in-your-project/converting-draft-issues-to-issues.md b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/managing-items-in-your-project/converting-draft-issues-to-issues.md
index 11f90b26a3..fb8c138578 100644
--- a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/managing-items-in-your-project/converting-draft-issues-to-issues.md
+++ b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/managing-items-in-your-project/converting-draft-issues-to-issues.md
@@ -8,12 +8,12 @@ versions:
 type: tutorial
 topics:
   - Projects
-ms.openlocfilehash: 22d80acf06957a3ab617e51d0051c75cf42db988
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: 6c956f5453941bdd6b9fbe89191737b1b7f59cec
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: ja-JP
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147424029'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148109019'
 ---
 ## テーブル レイアウトでのドラフト issue の変換
 
diff --git a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/managing-items-in-your-project/index.md b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/managing-items-in-your-project/index.md
index 872628e18e..09e065fe6e 100644
--- a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/managing-items-in-your-project/index.md
+++ b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/managing-items-in-your-project/index.md
@@ -12,11 +12,11 @@ children:
   - /converting-draft-issues-to-issues
   - /archiving-items-from-your-project
 allowTitleToDifferFromFilename: true
-ms.openlocfilehash: 76a77b3ba3cf61b37aaf2b23ae1117951d5b3105
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: 99f64d6e5f4d9cb39771f1ef9f0fae42c36a8cb7
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: ja-JP
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147424020'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148109680'
 ---
 
diff --git a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/managing-your-project/adding-your-project-to-a-repository.md b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/managing-your-project/adding-your-project-to-a-repository.md
index 07f84290c9..97a7a6a54a 100644
--- a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/managing-your-project/adding-your-project-to-a-repository.md
+++ b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/managing-your-project/adding-your-project-to-a-repository.md
@@ -9,12 +9,12 @@ type: tutorial
 topics:
   - Projects
 allowTitleToDifferFromFilename: true
-ms.openlocfilehash: 58739f4e548985729d01a962e67a12ea0c0b38e9
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: 30486f727a04ccea3b5bfd374a4da3c6367d1cb6
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: ja-JP
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147424152'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148109679'
 ---
 リポジトリ中で、関連するプロジェクトをリストできます。 リストできるのは、リポジトリを所有している同じユーザもしくはOrganizationが所有しているプロジェクトだけです。
 
diff --git a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/managing-your-project/closing-and-deleting-your-projects.md b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/managing-your-project/closing-and-deleting-your-projects.md
index d190afd92d..066978afba 100644
--- a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/managing-your-project/closing-and-deleting-your-projects.md
+++ b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/managing-your-project/closing-and-deleting-your-projects.md
@@ -11,12 +11,12 @@ type: tutorial
 topics:
   - Projects
 allowTitleToDifferFromFilename: true
-ms.openlocfilehash: a37980d4d19ca0392fab51dc7e99987e469d2c9a
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: cfd4db85e8bd046e667b108c5c8d8c23102e0d29
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: ja-JP
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147424071'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148109674'
 ---
 ## プロジェクトの削除
 
diff --git a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/managing-your-project/index.md b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/managing-your-project/index.md
index 0aa855634d..151af578fd 100644
--- a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/managing-your-project/index.md
+++ b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/managing-your-project/index.md
@@ -13,11 +13,11 @@ children:
   - /adding-your-project-to-a-repository
   - /adding-your-project-to-a-team
 allowTitleToDifferFromFilename: true
-ms.openlocfilehash: ca7c42e8dcb3daf477c70248eb79d12ca9670052
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: c7dd1657bae11e0f43895e946b5e20a209666363
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: ja-JP
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147424047'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148109018'
 ---
 
diff --git a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/managing-your-project/managing-access-to-your-projects.md b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/managing-your-project/managing-access-to-your-projects.md
index e5f823f24e..bda406771e 100644
--- a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/managing-your-project/managing-access-to-your-projects.md
+++ b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/managing-your-project/managing-access-to-your-projects.md
@@ -4,7 +4,7 @@ shortTitle: 'Managing {% data variables.projects.project_v2 %} access'
 intro: 'Learn how to manage team and individual access to your {% data variables.projects.project_v2 %}.'
 miniTocMaxHeadingLevel: 3
 versions:
-  feature: "projects-v2"
+  feature: projects-v2
 redirect_from:
   - /issues/trying-out-the-new-projects-experience/managing-access-to-projects
 type: tutorial
diff --git a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/managing-your-project/managing-visibility-of-your-projects.md b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/managing-your-project/managing-visibility-of-your-projects.md
index bd0a4b01d0..9ae363ad33 100644
--- a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/managing-your-project/managing-visibility-of-your-projects.md
+++ b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/managing-your-project/managing-visibility-of-your-projects.md
@@ -12,12 +12,12 @@ topics:
   - Projects
 allowTitleToDifferFromFilename: true
 permissions: Organization owners can manage the visibility of project boards in their organization. Organization owners can also allow collaborators with admin permissions to manage project visibility. Visibility of user projects can be managed by the owner of the project and collaborators with admin permissions.
-ms.openlocfilehash: 0fcd51dc996f28103179835f05fc74941eb1daee
-ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794
+ms.openlocfilehash: fbe4f0943010129b14ace21f6071b99e1160053b
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: ja-JP
-ms.lasthandoff: 09/09/2022
-ms.locfileid: '147854061'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148109787'
 ---
 ## プロジェクトの可視性について
 
diff --git a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/understanding-field-types/about-date-fields.md b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/understanding-field-types/about-date-fields.md
index ad7b151fba..ebc5e9fcd2 100644
--- a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/understanding-field-types/about-date-fields.md
+++ b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/understanding-field-types/about-date-fields.md
@@ -8,12 +8,12 @@ versions:
 type: tutorial
 topics:
   - Projects
-ms.openlocfilehash: e5cdcbdfbc2e51949c22c27fb1071b6e931ee59a
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: 7c3bc45c036e209e0be682c3b13b9dafcba17885
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: ja-JP
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147424101'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148109668'
 ---
 `YYYY-MM-DD` 形式 (`date:2022-07-01` など) を使用して、日付値をフィルター処理できます。 `>`、`>=`、`<`、`<=`、`..` などの演算子を使用することもできます。 たとえば、`date:>2022-07-01` や `date:2022-07-01..2022-07-31`す。 `@today` を指定して、フィルターで現在の日付を表すこともできます。 詳細については、[プロジェクトのフィルター処理](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/filtering-projects)に関するページを参照してください。
 
diff --git a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/understanding-field-types/about-iteration-fields.md b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/understanding-field-types/about-iteration-fields.md
index 1c2290e33a..b13876acda 100644
--- a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/understanding-field-types/about-iteration-fields.md
+++ b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/understanding-field-types/about-iteration-fields.md
@@ -10,12 +10,12 @@ redirect_from:
 type: tutorial
 topics:
   - Projects
-ms.openlocfilehash: fe0b02e356023880b03302de93a44273efd135a5
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: 93039327ab7075e0f79c9d5ae5d6652aa635a500
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: ja-JP
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147424017'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148109781'
 ---
 繰り返しフィールドを作成して、アイテムを特定の繰り返し時間ブロックに関連づけることができます。 繰り返しは任意の長さに設定でき、休憩を含められ、名前と日付の範囲を変更するために個別に編集できます。 プロジェクトでは、繰り返しでグループ化を行い、今後の作業のバランスを視覚化し、フィルタを使って繰り返しの1つに焦点を当て、繰り返しで並べ替えできます。
 
diff --git a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/understanding-field-types/about-single-select-fields.md b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/understanding-field-types/about-single-select-fields.md
index 3bfb878685..ab50d84b6c 100644
--- a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/understanding-field-types/about-single-select-fields.md
+++ b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/understanding-field-types/about-single-select-fields.md
@@ -8,12 +8,12 @@ versions:
 type: tutorial
 topics:
   - Projects
-ms.openlocfilehash: 50251608201f6a5e199c235cb0c715449bc99882
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: 1dfb11e43de04bd55f544a9fb97a0a9346a22d96
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: ja-JP
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147424113'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148109252'
 ---
 オプション (`fieldname:option` など) を指定して、単一選択フィールドでフィルター処理することができます。 オプションのコンマ区切りリスト (`fieldname:option,option` など) を指定して、複数の値をフィルター処理できます。 詳細については、[プロジェクトのフィルター処理](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/filtering-projects)に関するページを参照してください。
 
diff --git a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/understanding-field-types/about-text-and-number-fields.md b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/understanding-field-types/about-text-and-number-fields.md
index 4ae2735fa7..f82adba43e 100644
--- a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/understanding-field-types/about-text-and-number-fields.md
+++ b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/understanding-field-types/about-text-and-number-fields.md
@@ -8,12 +8,12 @@ versions:
 type: tutorial
 topics:
   - Projects
-ms.openlocfilehash: d6ab274812f4f35ff4f6afa9e1e2139abf86dd54
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: 2ef01bbd4ec13e37fdcd95e2a536e73c6da2304d
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: ja-JP
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147424145'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148109267'
 ---
 テキスト フィールドを使用して、プロジェクトに注釈やその他のフリーフォーム テキストを含めることができます。
 
diff --git a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/understanding-field-types/deleting-fields.md b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/understanding-field-types/deleting-fields.md
index b7001731b6..ced1d25304 100644
--- a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/understanding-field-types/deleting-fields.md
+++ b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/understanding-field-types/deleting-fields.md
@@ -7,12 +7,12 @@ versions:
 type: tutorial
 topics:
   - Projects
-ms.openlocfilehash: c0e250a584d596377c5efaa15d06dacf943827a7
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: 2998d4d39a3ec5f59a649fe62fd15c974e1e7ff7
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: ja-JP
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147424132'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148109259'
 ---
 {% data reusables.projects.project-settings %}
 1. 削除するフィールドの名前をクリックします。
diff --git a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/understanding-field-types/index.md b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/understanding-field-types/index.md
index d22b655c23..9a340fb59d 100644
--- a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/understanding-field-types/index.md
+++ b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/understanding-field-types/index.md
@@ -15,11 +15,11 @@ children:
   - /renaming-fields
   - /deleting-fields
 allowTitleToDifferFromFilename: true
-ms.openlocfilehash: 8b4f48ba1d55d81c571256f48334c54ce3a7e71d
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: eaa9fe7d4dbd6b2c43d0ab2ad12faf173d6f571a
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: ja-JP
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147423999'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148109013'
 ---
 
diff --git a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/understanding-field-types/renaming-fields.md b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/understanding-field-types/renaming-fields.md
index 5b8c0001d7..e0d66c9b5b 100644
--- a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/understanding-field-types/renaming-fields.md
+++ b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/understanding-field-types/renaming-fields.md
@@ -7,12 +7,12 @@ versions:
 type: tutorial
 topics:
   - Projects
-ms.openlocfilehash: ab1373e5bea18c01ba97f37a7e77441d0bb70422
-ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794
+ms.openlocfilehash: a8e43cc14edf9dd0c6838d8f75839a2c0624a7a5
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: ja-JP
-ms.lasthandoff: 09/09/2022
-ms.locfileid: '147717550'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148109097'
 ---
 {% data reusables.projects.project-settings %}
 1. 名前を変更するフィールドの名前をクリックします。
diff --git a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/viewing-insights-from-your-project/about-insights-for-projects.md b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/viewing-insights-from-your-project/about-insights-for-projects.md
index 6f7fc9f4ac..96a1e4cb41 100644
--- a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/viewing-insights-from-your-project/about-insights-for-projects.md
+++ b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/viewing-insights-from-your-project/about-insights-for-projects.md
@@ -11,12 +11,12 @@ product: '{% data reusables.gated-features.historical-insights-for-projects %}'
 topics:
   - Projects
 allowTitleToDifferFromFilename: true
-ms.openlocfilehash: a90ec5dfb6aa983b8ffe26c84c4ec6ad01b0471d
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: 89f93ace53547fccd69ffb7e6d7b666a6cb48991
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: ja-JP
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147424014'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148109096'
 ---
 {% ifversion fpt %}
 
diff --git a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/viewing-insights-from-your-project/configuring-charts.md b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/viewing-insights-from-your-project/configuring-charts.md
index ca173e7237..6b25e43565 100644
--- a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/viewing-insights-from-your-project/configuring-charts.md
+++ b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/viewing-insights-from-your-project/configuring-charts.md
@@ -8,12 +8,12 @@ type: tutorial
 product: '{% data reusables.gated-features.historical-insights-for-projects %}'
 topics:
   - Projects
-ms.openlocfilehash: 4fffa6ebd196419dc08de7abaf5d85349bd38737
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: dd8f97ac69beb90a511c36ddd0a51f0e16b2d4b3
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: ja-JP
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147424144'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148109091'
 ---
 {% ifversion fpt %}
 
diff --git a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/viewing-insights-from-your-project/creating-charts.md b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/viewing-insights-from-your-project/creating-charts.md
index 7bcabb1d1a..277d446928 100644
--- a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/viewing-insights-from-your-project/creating-charts.md
+++ b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/viewing-insights-from-your-project/creating-charts.md
@@ -8,12 +8,12 @@ type: tutorial
 product: '{% data reusables.gated-features.historical-insights-for-projects %}'
 topics:
   - Projects
-ms.openlocfilehash: 1f6a072676480b02bcfbd589f5d4e9011e8e8052
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: c708476decfb76086f32d96d8fc1e085030ae37e
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: ja-JP
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147423996'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148108977'
 ---
 {% data reusables.projects.access-insights %}
 3. 左側のメニューで **[新しいグラフ]** をクリックします。
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 adbebde7ee..93e9451968 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
@@ -107,8 +107,8 @@ You can filter a repository's list of pull requests to find:
 - Pull requests that [require a review](/github/administering-a-repository/about-protected-branches#require-pull-request-reviews-before-merging) before they can be merged
 - Pull requests that a reviewer has approved
 - Pull requests in which a reviewer has asked for changes
-- Pull requests that you have reviewed{% ifversion fpt or ghae or ghes > 3.2 or ghec %}
-- Pull requests that someone has asked you directly to review{% endif %}
+- Pull requests that you have reviewed
+- Pull requests that someone has asked you directly to review
 - Pull requests that [someone has asked you, or a team you're a member of, to review](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/requesting-a-pull-request-review)
 
 {% data reusables.repositories.navigate-to-repo %}
@@ -168,7 +168,6 @@ With issue and pull request search terms, you can:
 - Filter issues and pull requests by label: `state:open type:issue label:"bug"`
 - Filter out search terms by using `-` before the term: `state:open type:issue -author:octocat`
 
-{% ifversion fpt or ghes > 3.2 or ghae or ghec %}
 {% tip %}
 
 **Tip:** You can filter issues and pull requests by label using logical OR or using logical AND.
@@ -176,7 +175,6 @@ With issue and pull request search terms, you can:
 - To filter issues using logical AND, use separate label filters: `label:"bug" label:"wip"`.
 
 {% endtip %}
-{% endif %}
 
 For issues, you can also use search to:
 
@@ -190,8 +188,8 @@ For pull requests, you can also use search to:
 - Filter pull requests that a reviewer has approved: `state:open type:pr review:approved`
 - Filter pull requests in which a reviewer has asked for changes: `state:open type:pr review:changes_requested`
 - Filter pull requests by [reviewer](/articles/about-pull-request-reviews/): `state:open type:pr reviewed-by:octocat`
-- Filter pull requests by the specific user [requested for review](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/requesting-a-pull-request-review): `state:open type:pr review-requested:octocat`{% ifversion fpt or ghae or ghes > 3.2 or ghec %}
-- Filter pull requests that someone has asked you directly to review: `state:open type:pr user-review-requested:@me`{% endif %}
+- Filter pull requests by the specific user [requested for review](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/requesting-a-pull-request-review): `state:open type:pr review-requested:octocat`
+- Filter pull requests that someone has asked you directly to review: `state:open type:pr user-review-requested:@me`
 - Filter pull requests by the team requested for review: `state:open type:pr team-review-requested:github/docs`
 - Filter for pull requests that are linked to an issue that the pull request may close: `linked:issue`
 
diff --git a/translations/ja-JP/content/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue.md b/translations/ja-JP/content/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue.md
index 5802070b3c..10b193cadf 100644
--- a/translations/ja-JP/content/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue.md
+++ b/translations/ja-JP/content/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue.md
@@ -1,6 +1,6 @@
 ---
 title: Linking a pull request to an issue
-intro: You can link a pull request {% ifversion link-existing-branches-to-issue %}or branch {% endif %}to an issue to show that a fix is in progress and to automatically close the issue when the pull request {% ifversion link-existing-branches-to-issue %}or branch {% endif %} is merged.
+intro: 'You can link a pull request {% ifversion link-existing-branches-to-issue %}or branch {% endif %}to an issue to show that a fix is in progress and to automatically close the issue when the pull request {% ifversion link-existing-branches-to-issue %}or branch {% endif %} is merged.'
 redirect_from:
   - /github/managing-your-work-on-github/managing-your-work-with-issues-and-pull-requests/linking-a-pull-request-to-an-issue
   - /articles/closing-issues-via-commit-message
diff --git a/translations/ja-JP/content/organizations/collaborating-with-groups-in-organizations/about-organizations.md b/translations/ja-JP/content/organizations/collaborating-with-groups-in-organizations/about-organizations.md
index bbb80dd102..b886081748 100644
--- a/translations/ja-JP/content/organizations/collaborating-with-groups-in-organizations/about-organizations.md
+++ b/translations/ja-JP/content/organizations/collaborating-with-groups-in-organizations/about-organizations.md
@@ -12,12 +12,12 @@ versions:
 topics:
   - Organizations
   - Teams
-ms.openlocfilehash: 3780e309aa149de90a6871fbe236aac752c67d0b
-ms.sourcegitcommit: 5b1461b419dbef60ae9dbdf8e905a4df30fc91b7
+ms.openlocfilehash: 7412c38e647ddec33543bd04d38d813bf6a93c88
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: ja-JP
-ms.lasthandoff: 09/10/2022
-ms.locfileid: '147878795'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148108976'
 ---
 ## Organizationについて
 
diff --git a/translations/ja-JP/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-security-and-analysis-settings-for-your-organization.md b/translations/ja-JP/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-security-and-analysis-settings-for-your-organization.md
index 58f47d8e9d..bb75ec8494 100644
--- a/translations/ja-JP/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-security-and-analysis-settings-for-your-organization.md
+++ b/translations/ja-JP/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-security-and-analysis-settings-for-your-organization.md
@@ -70,12 +70,10 @@ You can enable or disable features for all repositories.
    {% 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 %}
+   {% ifversion ghes %}
    !["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.2 %}
-   !["Enable all" or "Disable all" button for "Configure security and analysis" features](/assets/images/enterprise/3.1/help/organizations/security-and-analysis-disable-or-enable-all-ghas.png)
-   {% endif %}
+   
    
    {% ifversion ghae %}
    !["Enable all" or "Disable all" button for "Configure security and analysis" features](/assets/images/enterprise/github-ae/organizations/security-and-analysis-disable-or-enable-all-ghae.png)
@@ -108,17 +106,15 @@ You can enable or disable features for all repositories.
    {% ifversion fpt or ghec %}
    ![Screenshot of a checkbox for enabling a feature for new repositories](/assets/images/help/organizations/security-and-analysis-enable-or-disable-feature-checkbox.png)
    {% endif %}
-  {% ifversion ghes > 3.2 %}
+  {% ifversion ghes %}
    ![Screenshot of a checkbox for enabling a feature for new repositories](/assets/images/enterprise/3.3/organizations/security-and-analysis-enable-or-disable-feature-checkbox.png)
    {% endif %}
-   {% ifversion ghes = 3.2 %}
-   ![Screenshot of a checkbox for enabling a feature for new repositories](/assets/images/enterprise/3.1/help/organizations/security-and-analysis-enable-or-disable-feature-checkbox.png)
-   {% endif %}
+   
    {% ifversion ghae %}
    ![Screenshot of a checkbox for enabling 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 fpt or ghec or ghes %}
 
 ## Allowing {% data variables.product.prodname_dependabot %} to access private dependencies
 
diff --git a/translations/ja-JP/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization.md b/translations/ja-JP/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization.md
index 8ab11cb17b..704456d6fe 100644
--- a/translations/ja-JP/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization.md
+++ b/translations/ja-JP/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization.md
@@ -42,16 +42,16 @@ To search for specific events, use the `action` qualifier in your query. Actions
 | [`auto_approve_personal_access_token_requests`](#auto_approve_personal_access_token_requests-category-actions) | Contains activities related to your organization's approval policy for {% data variables.product.pat_v2 %}s. For more information, see "[Setting a {% data variables.product.pat_generic %} policy for your organization](/organizations/managing-programmatic-access-to-your-organization/setting-a-personal-access-token-policy-for-your-organization)."{% endif %}{% ifversion fpt or ghec %}
 | [`billing`](#billing-category-actions) | Contains all activities related to your organization's billing.{% endif %}{% ifversion fpt or ghec %}
 | [`business`](#business-category-actions) | Contains activities related to business settings for an enterprise. |{% endif %}{% ifversion fpt or ghec %}
-| [`codespaces`](#codespaces-category-actions) | Contains all activities related to your organization's codespaces. |{% endif %}{% ifversion fpt or ghec or ghes > 3.2 or ghae %}
+| [`codespaces`](#codespaces-category-actions) | Contains all activities related to your organization's codespaces. |{% endif %}
 | [`dependabot_alerts`](#dependabot_alerts-category-actions) | Contains organization-level configuration activities for {% data variables.product.prodname_dependabot_alerts %} in existing repositories. For more information, see "[About {% data variables.product.prodname_dependabot_alerts %}](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)."
-| [`dependabot_alerts_new_repos`](#dependabot_alerts_new_repos-category-actions) | Contains organization-level configuration activities for {% data variables.product.prodname_dependabot_alerts %} in new repositories created in the organization.{% endif %}{% ifversion fpt or ghec or ghes > 3.2 %}
+| [`dependabot_alerts_new_repos`](#dependabot_alerts_new_repos-category-actions) | Contains organization-level configuration activities for {% data variables.product.prodname_dependabot_alerts %} in new repositories created in the organization.{% ifversion fpt or ghec or ghes %}
 | [`dependabot_security_updates`](#dependabot_security_updates-category-actions) | Contains organization-level configuration activities for {% data variables.product.prodname_dependabot_security_updates %} in existing repositories. For more information, see "[Configuring {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/configuring-dependabot-security-updates)."
 | [`dependabot_security_updates_new_repos`](#dependabot_security_updates_new_repos-category-actions) | Contains organization-level configuration activities for {% data variables.product.prodname_dependabot_security_updates %} for new repositories created in the organization.{% endif %}{% ifversion fpt or ghec %}
 | [`dependency_graph`](#dependency_graph-category-actions) | Contains organization-level configuration activities for dependency graphs for repositories. For more information, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)."
 | [`dependency_graph_new_repos`](#dependency_graph_new_repos-category-actions) | Contains organization-level configuration activities for new repositories created in the organization.{% endif %}
 | [`discussion_post`](#discussion_post-category-actions) | Contains all activities related to discussions posted to a team page.
 | [`discussion_post_reply`](#discussion_post_reply-category-actions) | Contains all activities related to replies to discussions posted to a team page.{% ifversion fpt or ghes or ghec %}
-| [`enterprise`](#enterprise-category-actions) | Contains activities related to enterprise settings. | {% endif %}
+| [`enterprise`](#enterprise-category-actions) | Contains activities related to enterprise settings. |{% endif %}
 | [`hook`](#hook-category-actions) | Contains all activities related to webhooks.
 | [`integration_installation`](#integration_installation-category-actions)  | Contains activities related to integrations installed in an account. |
 | [`integration_installation_request`](#integration_installation_request-category-actions) | Contains all activities related to organization member requests for owners to approve integrations for use in the organization. |{% ifversion ghec or ghae %}
@@ -77,8 +77,8 @@ To search for specific events, use the `action` qualifier in your query. Actions
 | [`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 %}{% 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 secret-scanning-audit-log-custom-patterns %}
-| [`repository_secret_scanning_custom_pattern`](#respository_secret_scanning_custom_pattern-category-actions) | Contains repository-level activities related to secret scanning custom patterns. For more information, see "[Defining custom patterns for secret scanning](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning)." {% endif %}{% ifversion secret-scanning-audit-log-custom-patterns %}
-| [`repository_secret_scanning_push_protection`](#respository_secret_scanning_push_protection) | Contains repository-level activities related to secret scanning custom patterns. For more information, see "[Protecting pushes with secert scanning](/code-security/secret-scanning/protecting-pushes-with-secret-scanning)." {% endif %}
+| [`repository_secret_scanning_custom_pattern`](#repository_secret_scanning_custom_pattern-category-actions) | Contains repository-level activities related to secret scanning custom patterns. For more information, see "[Defining custom patterns for secret scanning](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning)." {% endif %}{% ifversion secret-scanning-audit-log-custom-patterns %}
+| [`repository_secret_scanning_push_protection`](#repository_secret_scanning_push_protection-category-actions) | Contains repository-level activities related to secret scanning custom patterns. For more information, see "[Protecting pushes with secret scanning](/code-security/secret-scanning/protecting-pushes-with-secret-scanning)." {% endif %}
 | [`repository_vulnerability_alert`](#repository_vulnerability_alert-category-actions) | Contains all activities related to [{% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/about-dependabot-alerts).{% 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 custom-repository-roles %}
 | [`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 %}
@@ -253,7 +253,6 @@ An overview of some of the most common actions that are recorded as events in th
 | `manage_access_and_security` | Triggered when a user updates [which repositories a codespace can access](/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces).
 {% endif %}
 
-{% ifversion fpt or ghec or ghes > 3.2 or ghae %}
 ### `dependabot_alerts` category actions
 
 | Action | Description
@@ -267,9 +266,8 @@ An overview of some of the most common actions that are recorded as events in th
 |------------------|-------------------
 | `disable` | Triggered when an organization owner disables {% data variables.product.prodname_dependabot_alerts %} for all new {% ifversion fpt or ghec %}private {% endif %}repositories. For more information, see "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)."
 | `enable` | Triggered when an organization owner enables {% data variables.product.prodname_dependabot_alerts %} for all new {% ifversion fpt or ghec %}private {% endif %}repositories.
-{% endif %}
 
-{% ifversion fpt or ghec or ghes > 3.2 %}
+{% ifversion fpt or ghec or ghes %}
 ### `dependabot_security_updates` category actions
 
 | Action | Description
@@ -867,4 +865,4 @@ For more information, see "[Managing the publication of {% data variables.produc
 - "[Keeping your organization secure](/articles/keeping-your-organization-secure)"{% ifversion fpt or ghec or ghes > 3.3 or ghae > 3.3 %}
 {%- ifversion fpt or ghec %}
 - "[Exporting member information for your organization](/organizations/managing-membership-in-your-organization/exporting-member-information-for-your-organization)"{% endif %}
-{%- endif %}
\ No newline at end of file
+{%- endif %}
diff --git a/translations/ja-JP/content/organizations/managing-access-to-your-organizations-project-boards/adding-an-outside-collaborator-to-a-project-board-in-your-organization.md b/translations/ja-JP/content/organizations/managing-access-to-your-organizations-project-boards/adding-an-outside-collaborator-to-a-project-board-in-your-organization.md
index afd77dd2cc..228294ab4c 100644
--- a/translations/ja-JP/content/organizations/managing-access-to-your-organizations-project-boards/adding-an-outside-collaborator-to-a-project-board-in-your-organization.md
+++ b/translations/ja-JP/content/organizations/managing-access-to-your-organizations-project-boards/adding-an-outside-collaborator-to-a-project-board-in-your-organization.md
@@ -1,6 +1,6 @@
 ---
-title: 'Organization の {% data variables.product.prodname_project_v1 %} に外部コラボレーターを追加する'
-intro: 'Organization オーナーまたは {% data variables.projects.projects_v1_board %} 管理者は、{% data variables.projects.projects_v1_board %} に外部コラボレーターを追加し、そのアクセス許可をカスタマイズできます。'
+title: 'Adding an outside collaborator to a {% data variables.product.prodname_project_v1 %} in your organization'
+intro: 'As an organization owner or {% data variables.projects.projects_v1_board %} admin, you can add an outside collaborator and customize their permissions to a {% data variables.projects.projects_v1_board %}.'
 redirect_from:
   - /articles/adding-an-outside-collaborator-to-a-project-board-in-your-organization
   - /github/setting-up-and-managing-organizations-and-teams/adding-an-outside-collaborator-to-a-project-board-in-your-organization
@@ -14,18 +14,21 @@ topics:
   - Teams
 shortTitle: Add a collaborator
 allowTitleToDifferFromFilename: true
-ms.openlocfilehash: 04a8728c1dc38937a00277316e162ead9acb0fef
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
-ms.translationtype: HT
-ms.contentlocale: ja-JP
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147422949'
 ---
+
 {% data reusables.projects.project_boards_old %}
 
-外部コラボレーターは、Organization の明示的なメンバーではありませんが、Organization 内の {% data variables.projects.projects_v1_board %} に対するアクセス許可を持つユーザーです。
+An outside collaborator is a person who isn't explicitly a member of your organization, but who has permissions to a {% data variables.projects.projects_v1_board %} in your organization.
 
-{% data reusables.profile.access_org %} {% data reusables.user-settings.access_org %} {% data reusables.organizations.organization-wide-project %}{% ifversion projects-v2 %}
-1. **[Project (classic)]** をクリックします{% endif %} {% data reusables.project-management.select-project %} {% data reusables.project-management.click-menu %} {% data reusables.project-management.access-collaboration-settings %} {% data reusables.project-management.collaborator-option %}
-9. [Search by username, full name or email address] (ユーザ名、フルネーム、メールアドレスでの検索) の下で、外部のコラボレータの名前、ユーザ名、{% data variables.product.prodname_dotcom %}メールを入力してください。
-   ![Octocat のユーザー名が検索フィールドに入力されている [コラボレーター] セクション](/assets/images/help/projects/org-project-collaborators-find-name.png) {% data reusables.project-management.add-collaborator %} {% data reusables.project-management.collaborator-permissions %}
+{% data reusables.profile.access_org %}
+{% data reusables.user-settings.access_org %}
+{% data reusables.organizations.organization-wide-project %}{% ifversion projects-v2 %}
+1. Click **Projects (classic)**{% endif %}
+{% data reusables.project-management.select-project %}
+{% data reusables.project-management.click-menu %}
+{% data reusables.project-management.access-collaboration-settings %}
+{% data reusables.project-management.collaborator-option %}
+9. Under "Search by username, full name or email address", type the outside collaborator's name, username, or {% data variables.product.prodname_dotcom %} email.
+   ![The Collaborators section with the Octocat's username entered in the search field](/assets/images/help/projects/org-project-collaborators-find-name.png)
+{% data reusables.project-management.add-collaborator %}
+{% data reusables.project-management.collaborator-permissions %}
diff --git a/translations/ja-JP/content/organizations/managing-access-to-your-organizations-project-boards/index.md b/translations/ja-JP/content/organizations/managing-access-to-your-organizations-project-boards/index.md
index 149b54fe0a..1054ec6f24 100644
--- a/translations/ja-JP/content/organizations/managing-access-to-your-organizations-project-boards/index.md
+++ b/translations/ja-JP/content/organizations/managing-access-to-your-organizations-project-boards/index.md
@@ -22,11 +22,11 @@ children:
   - /removing-an-outside-collaborator-from-an-organization-project-board
 shortTitle: 'Manage {% data variables.product.prodname_project_v1 %} access'
 allowTitleToDifferFromFilename: true
-ms.openlocfilehash: bde0cbf48426b968aae6326e3db7a66fe47fda16
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: ec3c6cdaffc23dcb4df631879d17ec1ca6c1d61b
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: ja-JP
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147422933'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148108833'
 ---
 
diff --git a/translations/ja-JP/content/organizations/managing-access-to-your-organizations-project-boards/managing-access-to-a-project-board-for-organization-members.md b/translations/ja-JP/content/organizations/managing-access-to-your-organizations-project-boards/managing-access-to-a-project-board-for-organization-members.md
index cdd3771833..c17aea1352 100644
--- a/translations/ja-JP/content/organizations/managing-access-to-your-organizations-project-boards/managing-access-to-a-project-board-for-organization-members.md
+++ b/translations/ja-JP/content/organizations/managing-access-to-your-organizations-project-boards/managing-access-to-a-project-board-for-organization-members.md
@@ -1,6 +1,6 @@
 ---
-title: 'Organization メンバーの {% data variables.product.prodname_project_v1 %} へのアクセスを管理する'
-intro: 'Organization オーナーまたは {% data variables.projects.projects_v1_board %} 管理者は、すべての Organization メンバーの {% data variables.projects.projects_v1_board %} に対する既定のアクセス許可レベルを設定できます。'
+title: 'Managing access to a {% data variables.product.prodname_project_v1 %} for organization members'
+intro: 'As an organization owner or {% data variables.projects.projects_v1_board %} admin, you can set a default permission level for a {% data variables.projects.projects_v1_board %} for all organization members.'
 redirect_from:
   - /articles/managing-access-to-a-project-board-for-organization-members
   - /github/setting-up-and-managing-organizations-and-teams/managing-access-to-a-project-board-for-organization-members
@@ -14,33 +14,33 @@ topics:
   - Teams
 shortTitle: Manage access for members
 allowTitleToDifferFromFilename: true
-ms.openlocfilehash: fe9d8ebee09d4eb6278545b5561b9691a0468bf5
-ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
-ms.translationtype: HT
-ms.contentlocale: ja-JP
-ms.lasthandoff: 09/10/2022
-ms.locfileid: '147880783'
 ---
+
 {% data reusables.projects.project_boards_old %}
 
-既定では、Organization オーナーまたは {% data variables.projects.projects_v1_board %} 管理者が特定の {% data variables.projects.projects_v1_boards %} に対して別のアクセス許可を設定しない限り、Organization メンバーは、その Organization の {% data variables.projects.projects_v1_boards %} に対する書き込みアクセス権が付与されます。
+By default, organization members have write access to their organization's {% data variables.projects.projects_v1_boards %} unless organization owners or {% data variables.projects.projects_v1_board %} admins set different permissions for specific {% data variables.projects.projects_v1_boards %}.
 
-## Organization のすべてのメンバーに対して標準の権限レベルを設定する
+## Setting a baseline permission level for all organization members
 
 {% tip %}
 
-**ヒント:** Organization メンバーに、{% data variables.projects.projects_v1_board %} に対するより高いアクセス許可を付与できます。 詳細については、「[Organization のプロジェクト ボード権限](/articles/project-board-permissions-for-an-organization)」を参照してください。
+**Tip:** You can give an organization member higher permissions to {% data variables.projects.projects_v1_board %}. For more information, see "[Project board permissions for an organization](/articles/project-board-permissions-for-an-organization)."
 
 {% endtip %}
 
-{% data reusables.profile.access_org %} {% data reusables.user-settings.access_org %} {% data reusables.organizations.organization-wide-project %}{% ifversion projects-v2 %}
-1. **[Project (classic)]** をクリックします{% endif %} {% data reusables.project-management.select-project %} {% data reusables.project-management.click-menu %} {% data reusables.project-management.access-collaboration-settings %}
-8. [Organization メンバーのアクセス許可] で、すべての Organization メンバーの基準の権限レベル (**読み取り**、**書き込み**、**管理者**、**なし** のいずれか) を選択します。
-![Organization のすべてのメンバーのプロジェクト ボードに対する基準の権限オプション](/assets/images/help/projects/baseline-project-permissions-for-organization-members.png)
-9. **[保存]** をクリックします。
+{% data reusables.profile.access_org %}
+{% data reusables.user-settings.access_org %}
+{% data reusables.organizations.organization-wide-project %}{% ifversion projects-v2 %}
+1. Click **Projects (classic)**{% endif %}
+{% data reusables.project-management.select-project %}
+{% data reusables.project-management.click-menu %}
+{% data reusables.project-management.access-collaboration-settings %}
+8. Under "Organization member permission", choose a baseline permission level for all organization members: **Read**, **Write**, **Admin**, or **None**.
+![Baseline project board permission options for all organization members](/assets/images/help/projects/baseline-project-permissions-for-organization-members.png)
+9. Click **Save**.
 
-## 参考資料
+## Further reading
 
-- 「[Organization の {% data variables.product.prodname_project_v1 %} への個人のアクセスを管理する](/articles/managing-an-individual-s-access-to-an-organization-project-board)」
-- 「[Organization の {% data variables.product.prodname_project_v1 %} への Team のアクセスを管理する](/articles/managing-team-access-to-an-organization-project-board)」
-- 「[Organization の {% data variables.product.prodname_project_v1_caps %} へのアクセス許可](/articles/project-board-permissions-for-an-organization)」
+- "[Managing an individual’s access to an organization {% data variables.product.prodname_project_v1 %}](/articles/managing-an-individual-s-access-to-an-organization-project-board)"
+- "[Managing team access to an organization {% data variables.product.prodname_project_v1 %}](/articles/managing-team-access-to-an-organization-project-board)"
+- "[{% data variables.product.prodname_project_v1_caps %} permissions for an organization](/articles/project-board-permissions-for-an-organization)"
diff --git a/translations/ja-JP/content/organizations/managing-access-to-your-organizations-project-boards/managing-an-individuals-access-to-an-organization-project-board.md b/translations/ja-JP/content/organizations/managing-access-to-your-organizations-project-boards/managing-an-individuals-access-to-an-organization-project-board.md
index ca6d14b31b..adaec974e3 100644
--- a/translations/ja-JP/content/organizations/managing-access-to-your-organizations-project-boards/managing-an-individuals-access-to-an-organization-project-board.md
+++ b/translations/ja-JP/content/organizations/managing-access-to-your-organizations-project-boards/managing-an-individuals-access-to-an-organization-project-board.md
@@ -1,6 +1,6 @@
 ---
-title: 'Organization の {% data variables.product.prodname_project_v1 %} への個人のアクセスを管理する'
-intro: 'Organization オーナーまたは {% data variables.projects.projects_v1_board %} 管理者は、Organization が所有する {% data variables.projects.projects_v1_board %} への個々のメンバーのアクセス権を管理できます。'
+title: 'Managing an individual’s access to an organization {% data variables.product.prodname_project_v1 %}'
+intro: 'As an organization owner or {% data variables.projects.projects_v1_board %} admin, you can manage an individual member''s access to a {% data variables.projects.projects_v1_board %} owned by your organization.'
 redirect_from:
   - /articles/managing-an-individual-s-access-to-an-organization-project-board
   - /articles/managing-an-individuals-access-to-an-organization-project-board
@@ -15,40 +15,57 @@ topics:
   - Teams
 shortTitle: Manage individual access
 allowTitleToDifferFromFilename: true
-ms.openlocfilehash: 3fd77225e83df2124e8e026453b539f6961ff473
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
-ms.translationtype: HT
-ms.contentlocale: ja-JP
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147422893'
 ---
+
 {% data reusables.projects.project_boards_old %}
 
 {% note %}
 
-**注:** {% data reusables.project-management.cascading-permissions %} 詳しい情報については、「[Organization の {% data variables.product.prodname_project_v1_caps %} へのアクセス許可](/articles/project-board-permissions-for-an-organization)」を参照してください。 
+**Note:** {% data reusables.project-management.cascading-permissions %} For more information, see "[{% data variables.product.prodname_project_v1_caps %} permissions for an organization](/articles/project-board-permissions-for-an-organization)." 
 
 {% endnote %}
 
-## {% data variables.projects.projects_v1_board %} へのアクセス権を Organization メンバーに付与する
+## Giving an organization member access to a {% data variables.projects.projects_v1_board %}
 
-{% data reusables.profile.access_org %} {% data reusables.user-settings.access_org %} {% data reusables.organizations.organization-wide-project %}{% ifversion projects-v2 %}
-1. **[Project (classic)]** をクリックします{% endif %} {% data reusables.project-management.select-project %} {% data reusables.project-management.click-menu %} {% data reusables.project-management.access-collaboration-settings %} {% data reusables.project-management.collaborator-option %}
-9. [Search by username, full name or email address] で、コラボレーターの名前、ユーザ名、または {% data variables.product.prodname_dotcom %} メールを入力します。
-   ![Octocat のユーザー名が検索フィールドに入力されている [コラボレーター] セクション](/assets/images/help/projects/org-project-collaborators-find-name.png) {% data reusables.project-management.add-collaborator %} {% data reusables.project-management.collaborator-permissions %}
+{% data reusables.profile.access_org %}
+{% data reusables.user-settings.access_org %}
+{% data reusables.organizations.organization-wide-project %}{% ifversion projects-v2 %}
+1. Click **Projects (classic)**{% endif %}
+{% data reusables.project-management.select-project %}
+{% data reusables.project-management.click-menu %}
+{% data reusables.project-management.access-collaboration-settings %}
+{% data reusables.project-management.collaborator-option %}
+9. Under "Search by username, full name or email address", type the collaborator's name, username, or {% data variables.product.prodname_dotcom %} email.
+   ![The Collaborators section with the Octocat's username entered in the search field](/assets/images/help/projects/org-project-collaborators-find-name.png)
+{% data reusables.project-management.add-collaborator %}
+{% data reusables.project-management.collaborator-permissions %}
 
-## {% data variables.projects.projects_v1_board %} への Organization メンバーのアクセス権を変更する
+## Changing an organization member's access to a {% data variables.projects.projects_v1_board %}
 
-{% data reusables.profile.access_org %} {% data reusables.user-settings.access_org %} {% data reusables.organizations.organization-wide-project %}{% ifversion projects-v2 %}
-1. **[Project (classic)]** をクリックします{% endif %} {% data reusables.project-management.select-project %} {% data reusables.project-management.click-menu %} {% data reusables.project-management.access-collaboration-settings %} {% data reusables.project-management.collaborator-option %} {% data reusables.project-management.collaborator-permissions %}
+{% data reusables.profile.access_org %}
+{% data reusables.user-settings.access_org %}
+{% data reusables.organizations.organization-wide-project %}{% ifversion projects-v2 %}
+1. Click **Projects (classic)**{% endif %}
+{% data reusables.project-management.select-project %}
+{% data reusables.project-management.click-menu %}
+{% data reusables.project-management.access-collaboration-settings %}
+{% data reusables.project-management.collaborator-option %}
+{% data reusables.project-management.collaborator-permissions %}
 
-## {% data variables.projects.projects_v1_board %} への Organization メンバーのアクセス権を削除する
+## Removing an organization member's access to a {% data variables.projects.projects_v1_board %}
 
-コラボレーターを {% data variables.projects.projects_v1_board %} から削除しても、コラボレーターは引き続き他のロールに対するアクセス許可に基づいてボードにアクセスできる場合があります。 {% data variables.projects.projects_v1_board %} へのアクセス権を完全に削除するには、そのユーザーが持つ各ロールのアクセス権を削除する必要があります。 たとえば、ユーザーは、Organization メンバーまたは Team メンバーとして {% data variables.projects.projects_v1_board %} にアクセスできます。 詳しい情報については、「[Organization の {% data variables.product.prodname_project_v1_caps %} へのアクセス許可](/articles/project-board-permissions-for-an-organization)」を参照してください。
+When you remove a collaborator from a {% data variables.projects.projects_v1_board %}, they may still retain access to the board based on the permissions they have for other roles. To completely remove access to a {% data variables.projects.projects_v1_board %}, you must remove access for each role the person has. For instance, a person may have access to the {% data variables.projects.projects_v1_board %} as an organization member or team member. For more information, see "[{% data variables.product.prodname_project_v1_caps %} permissions for an organization](/articles/project-board-permissions-for-an-organization)."
 
-{% data reusables.profile.access_org %} {% data reusables.user-settings.access_org %} {% data reusables.organizations.organization-wide-project %}{% ifversion projects-v2 %}
-1. **[Project (classic)]** をクリックします{% endif %} {% data reusables.project-management.select-project %} {% data reusables.project-management.click-menu %} {% data reusables.project-management.access-collaboration-settings %} {% data reusables.project-management.collaborator-option %} {% data reusables.project-management.remove-collaborator %}
+{% data reusables.profile.access_org %}
+{% data reusables.user-settings.access_org %}
+{% data reusables.organizations.organization-wide-project %}{% ifversion projects-v2 %}
+1. Click **Projects (classic)**{% endif %}
+{% data reusables.project-management.select-project %}
+{% data reusables.project-management.click-menu %}
+{% data reusables.project-management.access-collaboration-settings %}
+{% data reusables.project-management.collaborator-option %}
+{% data reusables.project-management.remove-collaborator %}
 
-## 参考資料
+## Further reading
 
-- 「[Organization の {% data variables.product.prodname_project_v1_caps %} へのアクセス許可](/articles/project-board-permissions-for-an-organization)」
+- "[{% data variables.product.prodname_project_v1_caps %} permissions for an organization](/articles/project-board-permissions-for-an-organization)"
diff --git a/translations/ja-JP/content/organizations/managing-access-to-your-organizations-project-boards/managing-team-access-to-an-organization-project-board.md b/translations/ja-JP/content/organizations/managing-access-to-your-organizations-project-boards/managing-team-access-to-an-organization-project-board.md
index 522bc91b7a..30b1dbf759 100644
--- a/translations/ja-JP/content/organizations/managing-access-to-your-organizations-project-boards/managing-team-access-to-an-organization-project-board.md
+++ b/translations/ja-JP/content/organizations/managing-access-to-your-organizations-project-boards/managing-team-access-to-an-organization-project-board.md
@@ -1,5 +1,5 @@
 ---
-title: Managing team access to an organization {% data variables.product.prodname_project_v1 %}
+title: 'Managing team access to an organization {% data variables.product.prodname_project_v1 %}'
 intro: 'As an organization owner or {% data variables.projects.projects_v1_board %} admin, you can give a team access to a {% data variables.projects.projects_v1_board %} owned by your organization.'
 redirect_from:
   - /articles/managing-team-access-to-an-organization-project-board
@@ -68,4 +68,4 @@ If a team's access to a {% data variables.projects.projects_v1_board %} is inher
 - [Adding your project to a team](/issues/planning-and-tracking-with-projects/managing-your-project/adding-your-project-to-a-team)
 
 
-{% endif %}
\ No newline at end of file
+{% endif %}
diff --git a/translations/ja-JP/content/organizations/managing-access-to-your-organizations-project-boards/removing-an-outside-collaborator-from-an-organization-project-board.md b/translations/ja-JP/content/organizations/managing-access-to-your-organizations-project-boards/removing-an-outside-collaborator-from-an-organization-project-board.md
index 09991aca0d..fb33b5a98b 100644
--- a/translations/ja-JP/content/organizations/managing-access-to-your-organizations-project-boards/removing-an-outside-collaborator-from-an-organization-project-board.md
+++ b/translations/ja-JP/content/organizations/managing-access-to-your-organizations-project-boards/removing-an-outside-collaborator-from-an-organization-project-board.md
@@ -1,6 +1,6 @@
 ---
-title: 'Organization の {% data variables.product.prodname_project_v1 %} から外部コラボレーターを削除する'
-intro: 'Organization オーナーまたは {% data variables.projects.projects_v1_board %} 管理者は、{% data variables.projects.projects_v1_board %} への外部コラボレーターのアクセス権を削除できます。'
+title: 'Removing an outside collaborator from an organization {% data variables.product.prodname_project_v1 %}'
+intro: 'As an organization owner or {% data variables.projects.projects_v1_board %} admin, you can remove an outside collaborator''s access to a {% data variables.projects.projects_v1_board %}.'
 redirect_from:
   - /articles/removing-an-outside-collaborator-from-an-organization-project-board
   - /github/setting-up-and-managing-organizations-and-teams/removing-an-outside-collaborator-from-an-organization-project-board
@@ -14,14 +14,16 @@ topics:
   - Teams
 shortTitle: Remove outside collaborator
 allowTitleToDifferFromFilename: true
-ms.openlocfilehash: 2dfcc372565366328820e968d6c6384f97b0e2c1
-ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
-ms.translationtype: HT
-ms.contentlocale: ja-JP
-ms.lasthandoff: 09/11/2022
-ms.locfileid: '147884198'
 ---
+
 {% data reusables.projects.project_boards_old %}
 
-{% data reusables.profile.access_org %} {% data reusables.user-settings.access_org %} {% data reusables.organizations.organization-wide-project %}{% ifversion projects-v2 %}
-1. **[Project (classic)]** をクリックします{% endif %} {% data reusables.project-management.select-project %} {% data reusables.project-management.click-menu %} {% data reusables.project-management.access-collaboration-settings %} {% data reusables.project-management.collaborator-option %} {% data reusables.project-management.remove-collaborator %}
+{% data reusables.profile.access_org %}
+{% data reusables.user-settings.access_org %}
+{% data reusables.organizations.organization-wide-project %}{% ifversion projects-v2 %}
+1. Click **Projects (classic)**{% endif %}
+{% data reusables.project-management.select-project %}
+{% data reusables.project-management.click-menu %}
+{% data reusables.project-management.access-collaboration-settings %}
+{% data reusables.project-management.collaborator-option %}
+{% data reusables.project-management.remove-collaborator %}
diff --git a/translations/ja-JP/content/organizations/managing-organization-settings/allowing-project-visibility-changes-in-your-organization.md b/translations/ja-JP/content/organizations/managing-organization-settings/allowing-project-visibility-changes-in-your-organization.md
index 1054ccf40e..5e485b33cf 100644
--- a/translations/ja-JP/content/organizations/managing-organization-settings/allowing-project-visibility-changes-in-your-organization.md
+++ b/translations/ja-JP/content/organizations/managing-organization-settings/allowing-project-visibility-changes-in-your-organization.md
@@ -9,12 +9,12 @@ topics:
 shortTitle: Project visibility permissions
 allowTitleToDifferFromFilename: true
 permissions: 'Organization owners can allow {% data variables.projects.project_v2_and_v1 %} visibility changes for an organization.'
-ms.openlocfilehash: 784b0f35ff86a1a2620a0c96d4e951a8ca28e136
-ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794
+ms.openlocfilehash: 5f8963e8c03e2c0a62586964b6331ec7b3d945b5
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: ja-JP
-ms.lasthandoff: 09/09/2022
-ms.locfileid: '147854085'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148109539'
 ---
 ## プロジェクトの可視性の変更について
 
diff --git a/translations/ja-JP/content/organizations/managing-organization-settings/disabling-insights-for-projects-in-your-organization.md b/translations/ja-JP/content/organizations/managing-organization-settings/disabling-insights-for-projects-in-your-organization.md
index e0536d2906..60d34b7621 100644
--- a/translations/ja-JP/content/organizations/managing-organization-settings/disabling-insights-for-projects-in-your-organization.md
+++ b/translations/ja-JP/content/organizations/managing-organization-settings/disabling-insights-for-projects-in-your-organization.md
@@ -8,12 +8,12 @@ topics:
   - Projects
 shortTitle: 'Disable {% data variables.product.prodname_projects_v2 %} insights'
 allowTitleToDifferFromFilename: true
-ms.openlocfilehash: 06ab0f550603e3810bf860f01efe9113766c0fb3
-ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.openlocfilehash: 80a35ea28d90b89c39fb7f9207b2ea950a98a8b6
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: ja-JP
-ms.lasthandoff: 09/11/2022
-ms.locfileid: '147424083'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148108832'
 ---
 Organization 内のプロジェクトの分析情報を無効にした後、Organization が所有するプロジェクトの分析情報にアクセスできなくなります。
 
diff --git a/translations/ja-JP/content/organizations/managing-organization-settings/index.md b/translations/ja-JP/content/organizations/managing-organization-settings/index.md
index c3e16e92ab..8996d8f20e 100644
--- a/translations/ja-JP/content/organizations/managing-organization-settings/index.md
+++ b/translations/ja-JP/content/organizations/managing-organization-settings/index.md
@@ -45,11 +45,11 @@ children:
   - /disabling-insights-for-projects-in-your-organization
   - /allowing-project-visibility-changes-in-your-organization
 shortTitle: Manage organization settings
-ms.openlocfilehash: 5e89284314ef4f1125ff4ca0843031326e378b0b
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: d19c515ac3d908df15afd8c5741553f7526a6f99
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: ja-JP
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147424745'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148008712'
 ---
 {% ifversion fpt or ghec %} {% endif %}
diff --git a/translations/ja-JP/content/organizations/managing-organization-settings/managing-the-commit-signoff-policy-for-your-organization.md b/translations/ja-JP/content/organizations/managing-organization-settings/managing-the-commit-signoff-policy-for-your-organization.md
index 3e9cacd22c..25ed41ec30 100644
--- a/translations/ja-JP/content/organizations/managing-organization-settings/managing-the-commit-signoff-policy-for-your-organization.md
+++ b/translations/ja-JP/content/organizations/managing-organization-settings/managing-the-commit-signoff-policy-for-your-organization.md
@@ -1,29 +1,26 @@
 ---
-title: Organization のコミット サインオフ ポリシーの管理
-intro: 'Organization が所有するリポジトリへの {% data variables.product.product_name %} の Web インターフェイスでユーザーが行ったすべてのコミットを、自動的にサインオフするように要求できます。'
+title: Managing the commit signoff policy for your organization
+intro: 'You can require users to automatically sign off all commits they make in {% data variables.product.product_name %}''s web interface to repositories owned by your organization.'
 versions:
   feature: commit-signoffs
 permissions: Organization owners can require all commits to repositories owned by the organization be signed off by the commit author.
 topics:
   - Organizations
 shortTitle: Manage the commit signoff policy
-ms.openlocfilehash: 0d4f2a0fae7db59a7a1f5d8646263e965e9be9ef
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
-ms.translationtype: HT
-ms.contentlocale: ja-JP
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147409825'
 ---
-## コミットのサインオフについて
 
-コミットがリポジトリを管理するルールとライセンスに準拠していることを確認するために、多くの Organization では、開発者がすべてのコミットをサインオフする必要があります。 Organization でコミットのサインオフが必要な場合は、{% data variables.product.product_name %} の Web インターフェイスを介してコミットするユーザーに対して強制コミット サインオフを有効にすることで、コミット プロセスのシームレスな部分をサインオフできます。 Organization の強制コミット サインオフを有効にした後、{% data variables.product.product_name %} の Web インターフェイスを介してその Organization 内のリポジトリに対して行われたすべてのコミットは、コミット作成者によって自動的にサインオフされます。
+## About commit signoffs
 
-リポジトリへの管理者アクセス権を持つユーザーは、リポジトリ レベルで強制コミット サインオフを有効にすることもできます。 詳しくは、「[リポジトリのコミット サインオフ ポリシーの管理](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-the-commit-signoff-policy-for-your-repository)」を参照してください。
+To affirm that a commit complies with the rules and licensing governing a repository, many organizations require developers to sign off on every commit. If your organization requires commit signoffs, you can make signing off a seamless part of the commit process by enabling compulsory commit signoffs for users committing through {% data variables.product.product_name %}'s web interface. After you enable compulsory commit signoffs for an organization, every commit made to repositories in that organization through {% data variables.product.product_name %}'s web interface will automatically be signed off on by the commit author.
+
+People with admin access to a repository can also enable compulsory commit signoffs at the repository level. For more information, see "[Managing the commit signoff policy for your repository](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-the-commit-signoff-policy-for-your-repository)."
 
 {% data reusables.repositories.commit-signoffs %}
 
-## Organization の強制コミット サインオフの管理
+## Managing compulsory commit signoffs for your organization
 
-{% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} {% data reusables.organizations.repository-defaults %}
-1. **[共同作成者に Web ベースのコミットのサインオフを要求する]** を選択または選択解除します。
-  ![[共同作成者に Web ベースのコミットのサインオフを要求する] のスクリーンショット](/assets/images/help/organizations/require-signoffs.png)
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.repository-defaults %}
+1. Select or deselect **Require contributors to sign off on web-based commits**.
+  ![Screenshot of Require contributors to sign off on web-based commits](/assets/images/help/organizations/require-signoffs.png)
diff --git a/translations/ja-JP/content/organizations/managing-organization-settings/setting-permissions-for-adding-outside-collaborators.md b/translations/ja-JP/content/organizations/managing-organization-settings/setting-permissions-for-adding-outside-collaborators.md
index ed25ce1f3e..43c2116721 100644
--- a/translations/ja-JP/content/organizations/managing-organization-settings/setting-permissions-for-adding-outside-collaborators.md
+++ b/translations/ja-JP/content/organizations/managing-organization-settings/setting-permissions-for-adding-outside-collaborators.md
@@ -1,6 +1,6 @@
 ---
-title: 外部のコラボレーターを追加するための権限を設定する
-intro: Organization のデータを保護し、Organization 内で使用されている有料ライセンスの数が無駄遣いされないようにするために、外部コラボレーターを Organization のリポジトリに追加できる人を構成できます。
+title: Setting permissions for adding outside collaborators
+intro: 'To protect your organization''s data and the number of paid licenses used in your organization, you can configure who can add outside collaborators to organization repositories.'
 redirect_from:
   - /articles/restricting-the-ability-to-add-outside-collaborators-to-organization-repositories
   - /articles/setting-permissions-for-adding-outside-collaborators
@@ -13,28 +13,25 @@ topics:
   - Organizations
   - Teams
 shortTitle: Set collaborator policy
-ms.openlocfilehash: eadf4f805775a99f763ec4df211fe6ea9735dabc
-ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
-ms.translationtype: HT
-ms.contentlocale: ja-JP
-ms.lasthandoff: 09/11/2022
-ms.locfileid: '145119245'
 ---
-デフォルトでは、リポジトリへの管理アクセスを持つ人は、そのリポジトリで作業してもらうために外部のコラボレータを招待できます。 外部のコラボレータを追加する機能は、Organizationのオーナーのみに制限することもできます。
 
-{% ifversion ghec %} {% note %}
+By default, anyone with admin access to a repository can invite outside collaborators to work on the repository. You can choose to restrict the ability to add outside collaborators to organization owners only.
 
-**注:** {% data variables.product.prodname_ghe_cloud %} を使う Organization だけが、外部のコラボレータを招待する機能を Organization のオーナーに制限できます。 {% data reusables.enterprise.link-to-ghec-trial %}
+{% ifversion ghec %}
+{% note %}
 
-{% endnote %} {% endif %}
+**Note:** Only organizations that use {% data variables.product.prodname_ghe_cloud %} can restrict the ability to invite outside collaborators to organization owners. {% data reusables.enterprise.link-to-ghec-trial %}
 
-{% ifversion ghec %}Organization がエンタープライズアカウントによって所有されているとき、{% else %}{% endif %}エンタープライズ所有者がエンタープライズレベルでポリシーを設定している場合、Organization にこの設定を構成できないことがあります。 詳しくは、「Enterprise でリポジトリ管理ポリシーを適用する{% ifversion ghec %}(/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-for-inviting-collaborators-to-repositories)"{% else %}(/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-for-inviting-outside-collaborators-to-repositories){% endif %}」を参照してください。
+{% endnote %}
+{% endif %}
+
+{% ifversion ghec %}If your organization is owned by an enterprise account, you{% else %}You{% endif %} may not be able to configure this setting for your organization, if an enterprise owner has set a policy at the enterprise level. For more information, see "[Enforcing repository management policies in your enterprise]{% ifversion ghec %}(/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-for-inviting-collaborators-to-repositories)"{% else %}(/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-for-inviting-outside-collaborators-to-repositories){% endif %}."
 
 {% data reusables.organizations.outside-collaborators-use-seats %}
 
-{% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} {% data reusables.organizations.member-privileges %}{% ifversion ghes < 3.3 %}
-5. [リポジトリ招待] の下で、 **[この Organization のリポジトリに外部コラボレータを招待することをメンバーに許可する]** を選択します。
-   ![外部コラボレータを Organization リポジトリに招待することをメンバーに許可するためのチェックボックス](/assets/images/help/organizations/repo-invitations-checkbox-old.png){% else %}
-5. [リポジトリの外部コラボレータ] で **[この Organization のリポジトリに外部コラボレータを招待することをリポジトリ管理者に許可する]** の選択を解除します。
-  ![外部コラボレータを Organization リポジトリに招待することをリポジトリ管理者に許可するためのチェックボックス](/assets/images/help/organizations/repo-invitations-checkbox-updated.png){% endif %}
-6. **[保存]** をクリックします。
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.member-privileges %}
+5. Under "Repository outside collaborators", deselect **Allow repository administrators to invite outside collaborators to repositories for this organization**.
+  ![Checkbox to allow repository administrators to invite outside collaborators to organization repositories](/assets/images/help/organizations/repo-invitations-checkbox-updated.png)
+6. Click **Save**.
diff --git a/translations/ja-JP/content/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization.md b/translations/ja-JP/content/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization.md
index 52f83adc9b..6e30cf02ec 100644
--- a/translations/ja-JP/content/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization.md
+++ b/translations/ja-JP/content/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization.md
@@ -15,12 +15,12 @@ topics:
   - Organizations
   - Teams
 shortTitle: Roles in an organization
-ms.openlocfilehash: d8d07ff40026de0d12fce2e11479c424b781680a
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: 960f6f701ad524220e9e79ada04fa9e4d30b8e9f
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: ja-JP
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147061739'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148108803'
 ---
 ## ロールについて
 {% data reusables.organizations.about-roles %}
@@ -142,7 +142,7 @@ Organizationでの{% data variables.product.prodname_github_app %}マネージ
 | Team 同期を有効にする (「[Organization の Team 同期を管理する](/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization)」を参照) | **X** |  |  |  |  |{% endif %}
 | Organization での Pull Request のレビューを管理する (「[Organization での Pull Request のレビューの管理](/organizations/managing-organization-settings/managing-pull-request-reviews-in-your-organization)」を参照) | **X** |  |  |  |  |
 
-{% elsif ghes > 3.2 or ghae %}
+{% elsif ghes or ghae %}
 <!-- GHES 3.3+ and eventual GHAE release don't have the extra columns for Moderators and Billing managers. -->
 
 | Organization のアクション | 所有者 | メンバー | セキュリティマネージャー |
@@ -167,7 +167,7 @@ Organizationでの{% data variables.product.prodname_github_app %}マネージ
 | "*チーム メンテナ*" に指定できる | **X** | **X** | **X**  |
 | リポジトリを移譲する | **X** | |  |
 | セキュリティと分析の設定を管理する (「[Organization のセキュリティと分析設定を管理する](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)」を参照) | **X** | | **X** |{% ifversion ghes %}
-| Organization のセキュリティの概要を表示する (「[セキュリティの概要について](/code-security/security-overview/about-the-security-overview)」を参照) | **X** | | **X** |{% endif %}{% ifversion ghes > 3.2 %}
+| Organization のセキュリティの概要を表示する (「[セキュリティの概要について](/code-security/security-overview/about-the-security-overview)」を参照) | **X** | | **X** |{% endif %}{% ifversion ghes %}
 | {% data variables.product.prodname_dependabot_security_updates %} を管理する (「[{% data variables.product.prodname_dependabot_security_updates %} について](/github/managing-security-vulnerabilities/about-dependabot-security-updates)」を参照) | **X** | | **X** |{% endif %}
 | Organization の SSH 認証局を管理する (「[Organization の SSH 認証局を管理する](/articles/managing-your-organizations-ssh-certificate-authorities)」を参照) | **X** |  |  |
 | プロジェクト ボードを作成する (「[Organization のプロジェクト ボード権限](/articles/project-board-permissions-for-an-organization)」を参照) | **X** | **X** | **X** |
diff --git a/translations/ja-JP/content/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on.md b/translations/ja-JP/content/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on.md
index a6056acced..b0a8576c06 100644
--- a/translations/ja-JP/content/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on.md
+++ b/translations/ja-JP/content/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on.md
@@ -20,10 +20,12 @@ shortTitle: IAM with SAML SSO
 
 {% data reusables.saml.saml-accounts %}
 
-Organization owners can enforce SAML SSO for an individual organization, or enterprise owners can enforce SAML SSO for all organizations in an enterprise account. For more information, see "[Configuring SAML single sign-on for your enterprise](/enterprise-cloud@latest/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise)."
+{% data reusables.saml.resources-without-sso %}
 
 {% data reusables.saml.outside-collaborators-exemption %}
 
+Organization owners can enforce SAML SSO for an individual organization, or enterprise owners can enforce SAML SSO for all organizations in an enterprise account. For more information, see "[Configuring SAML single sign-on for your enterprise](/enterprise-cloud@latest/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise)."
+
 Before enabling SAML SSO for your organization, you'll need to connect your IdP to your organization. For more information, see "[Connecting your identity provider to your organization](/organizations/managing-saml-single-sign-on-for-your-organization/connecting-your-identity-provider-to-your-organization)."
 
 For an organization, SAML SSO can be disabled, enabled but not enforced, or enabled and enforced. After you enable SAML SSO for your organization and your organization's members successfully authenticate with your IdP, you can enforce the SAML SSO configuration. For more information about enforcing SAML SSO for your {% data variables.product.prodname_dotcom %} organization, see "[Enforcing SAML single sign-on for your organization](/articles/enforcing-saml-single-sign-on-for-your-organization)."
diff --git a/translations/ja-JP/content/organizations/managing-saml-single-sign-on-for-your-organization/troubleshooting-identity-and-access-management-for-your-organization.md b/translations/ja-JP/content/organizations/managing-saml-single-sign-on-for-your-organization/troubleshooting-identity-and-access-management-for-your-organization.md
index c38eff7ab0..1a08195f35 100644
--- a/translations/ja-JP/content/organizations/managing-saml-single-sign-on-for-your-organization/troubleshooting-identity-and-access-management-for-your-organization.md
+++ b/translations/ja-JP/content/organizations/managing-saml-single-sign-on-for-your-organization/troubleshooting-identity-and-access-management-for-your-organization.md
@@ -9,12 +9,12 @@ topics:
 shortTitle: Troubleshooting access
 redirect_from:
   - /organizations/managing-saml-single-sign-on-for-your-organization/troubleshooting-identity-and-access-management
-ms.openlocfilehash: 41a629c9cff075e06e31d186a4a4edf7eebd96d2
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: d3110d61fb511f55aa840d0911c036dd342fa833
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: ja-JP
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147093201'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148106974'
 ---
 {% data reusables.saml.current-time-earlier-than-notbefore-condition %}
 
@@ -84,7 +84,7 @@ SCIM REST APIは、外部アイデンティティの下でSCIMメタデータが
 ```
 
 ```shell
-curl -X POST -H "Authorization: Bearer <personal access token>" -H "Content-Type: application/json" -d '{ "query": "{ organization(login: \"ORG\") { samlIdentityProvider { externalIdentities(first: 100) { pageInfo { endCursor startCursor hasNextPage } edges { cursor node { samlIdentity { nameId } scimIdentity {username}  user { login } } } } } } }" }'  https://api.github.com/graphql
+curl -X POST -H "Authorization: Bearer YOUR_TOKEN" -H "Content-Type: application/json" -d '{ "query": "{ organization(login: \"ORG\") { samlIdentityProvider { externalIdentities(first: 100) { pageInfo { endCursor startCursor hasNextPage } edges { cursor node { samlIdentity { nameId } scimIdentity {username}  user { login } } } } } } }" }'  https://api.github.com/graphql
 ```
 
 GraphQL APIの利用に関する詳しい情報については、以下を参照してください。 
diff --git a/translations/ja-JP/content/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team.md b/translations/ja-JP/content/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team.md
index afbb13b86e..a577717cf0 100644
--- a/translations/ja-JP/content/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team.md
+++ b/translations/ja-JP/content/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team.md
@@ -86,7 +86,7 @@ Any team members that have set their status to "Busy" will not be selected for r
 {% ifversion ghes < 3.4 %}
 1. Optionally, to only notify the team members chosen by code review assignment for each pull review request, under "Notifications" select **If assigning team members, don't notify the entire team.**
 {%- endif %}
-{% ifversion fpt or ghec or ghae > 3.3 or ghes > 3.2 %}
+{% ifversion fpt or ghec or ghes or ghae > 3.3 %}
 1. Optionally, to include members of child teams as potential reviewers when assigning requests, select **Child team members**.
 1. Optionally, to count any members whose review has already been requested against the total number of members to assign, select **Count existing requests**.
 1. Optionally, to remove the review request from the team when assigning team members, select **Team review request**.
diff --git a/translations/ja-JP/content/packages/working-with-a-github-packages-registry/migrating-to-the-container-registry-from-the-docker-registry.md b/translations/ja-JP/content/packages/working-with-a-github-packages-registry/migrating-to-the-container-registry-from-the-docker-registry.md
index 400f954e6d..0fe78be916 100644
--- a/translations/ja-JP/content/packages/working-with-a-github-packages-registry/migrating-to-the-container-registry-from-the-docker-registry.md
+++ b/translations/ja-JP/content/packages/working-with-a-github-packages-registry/migrating-to-the-container-registry-from-the-docker-registry.md
@@ -9,7 +9,7 @@ redirect_from:
 versions:
   fpt: '*'
   ghec: '*'
-  feature: 'docker-ghcr-enterprise-migration'
+  feature: docker-ghcr-enterprise-migration
 shortTitle: Migration to Container registry
 topics:
   - Containers
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 f17d1a1b94..e687fd7b2b 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
@@ -142,14 +142,14 @@ You can use `publishConfig` element in the *package.json* file to specify the re
   {% endif %}
   ```shell
   "publishConfig": {
-    "registry":"https://{% ifversion fpt or ghec %}npm.pkg.github.com{% else %}npm.HOSTNAME/{% endif %}"
+    "registry": "https://{% ifversion fpt or ghec %}npm.pkg.github.com{% else %}npm.HOSTNAME/{% endif %}"
   },
   ```
   {% ifversion ghes %}
   If your instance has subdomain isolation disabled:
    ```shell
    "publishConfig": {
-     "registry":"https://HOSTNAME/_registry/npm/"
+     "registry": "https://HOSTNAME/_registry/npm/"
    },
   ```
   {% endif %}
diff --git a/translations/ja-JP/content/pages/getting-started-with-github-pages/index.md b/translations/ja-JP/content/pages/getting-started-with-github-pages/index.md
index b1e2bcecad..907b514a06 100644
--- a/translations/ja-JP/content/pages/getting-started-with-github-pages/index.md
+++ b/translations/ja-JP/content/pages/getting-started-with-github-pages/index.md
@@ -24,11 +24,11 @@ children:
   - /using-submodules-with-github-pages
   - /unpublishing-a-github-pages-site
 shortTitle: Get started
-ms.openlocfilehash: 7e9d3b9bb171a596b84b814eac52d4c5d22134de
-ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794
+ms.openlocfilehash: 4945585f635543fefe2f60de2f82b49bf4d10e84
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: ja-JP
-ms.lasthandoff: 09/09/2022
-ms.locfileid: '147643878'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148109268'
 ---
 
diff --git a/translations/ja-JP/content/pages/getting-started-with-github-pages/unpublishing-a-github-pages-site.md b/translations/ja-JP/content/pages/getting-started-with-github-pages/unpublishing-a-github-pages-site.md
index b0e56e98b1..bdaf20e577 100644
--- a/translations/ja-JP/content/pages/getting-started-with-github-pages/unpublishing-a-github-pages-site.md
+++ b/translations/ja-JP/content/pages/getting-started-with-github-pages/unpublishing-a-github-pages-site.md
@@ -1,6 +1,6 @@
 ---
-title: GitHub Pages サイトを取り下げる
-intro: '{% data variables.product.prodname_pages %} サイトを取り下げて、サイトを利用不可にすることができます。'
+title: Unpublishing a GitHub Pages site
+intro: 'You can unpublish your {% data variables.product.prodname_pages %} site so that the site is no longer available.'
 redirect_from:
   - /articles/how-do-i-unpublish-a-project-page
   - /articles/unpublishing-a-project-page
@@ -18,38 +18,35 @@ versions:
 topics:
   - Pages
 shortTitle: Unpublish Pages site
-ms.openlocfilehash: fbfec49ec44c250e5f6cb2da85fda59261c1d0d9
-ms.sourcegitcommit: 76b840f45ba85fb79a7f0c1eb43bc663b3eadf2b
-ms.translationtype: HT
-ms.contentlocale: ja-JP
-ms.lasthandoff: 09/12/2022
-ms.locfileid: '147428349'
 ---
+
 {% ifversion pages-custom-workflow %}
 
-自分のサイトを非公開にすると、そのサイトは利用不可になります。 既存のリポジトリ設定またはコンテンツが、影響を受けることはありません。
+When you unpublish your site, the site will no longer be available. Any existing repository settings or content will not be affected.
 
 {% data reusables.repositories.navigate-to-repo %}
-1. **{% data variables.product.prodname_pages %}** の下で、**サイトがライブになっている場所** に関するメッセージの横にある、[{% octicon "kebab-horizontal" aria-label="the horizontal kebab icon" %}] をクリックします。
-1. 表示されるメニューで、 **[サイトを取り下げる]** を選びます。
+1. Under **{% data variables.product.prodname_pages %}**, next to the **Your site is live at** message, click {% octicon "kebab-horizontal" aria-label="the horizontal kebab icon" %}.
+1. In the menu that appears, select **Unpublish site**.
 
-   ![サイトを取り下げるためのドロップ ダウン メニュー](/assets/images/help/pages/unpublish-site.png)
+   ![Drop down menu to unpublish site](/assets/images/help/pages/unpublish-site.png)
 
 {% else %}
 
-## プロジェクトサイトを取り下げる
+## Unpublishing a project site
 
 {% data reusables.repositories.navigate-to-repo %}
-2. リポジトリに `gh-pages` ブランチが存在する場合は、`gh-pages` ブランチを削除します。 詳細については、「[リポジトリ内でブランチを作成および削除する](/articles/creating-and-deleting-branches-within-your-repository#deleting-a-branch)」を参照してください。
-3. `gh-pages` ブランチが公開ソースの場合、{% ifversion fpt or ghec %}手順 6 に進みます{% else %}サイトは公開されていません。残りの手順はスキップできます{% endif %}。
-{% data reusables.repositories.sidebar-settings %} {% data reusables.pages.sidebar-pages %}
-5. "{% data variables.product.prodname_pages %}" で、 **[Source]\(ソース\)** ドロップダウン メニューを使用し、 **[None]\(なし\)** を選択します。
-  ![公開ソースを選択するためのドロップダウン メニュー](/assets/images/help/pages/publishing-source-drop-down.png) {% data reusables.pages.update_your_dns_settings %}
+2. If a `gh-pages` branch exists in the repository, delete the `gh-pages` branch. For more information, see "[Creating and deleting branches within your repository](/articles/creating-and-deleting-branches-within-your-repository#deleting-a-branch)."
+3. If the `gh-pages` branch was your publishing source, {% ifversion fpt or ghec %}skip to step 6{% else %}your site is now unpublished and you can skip the remaining steps{% endif %}.
+{% data reusables.repositories.sidebar-settings %}
+{% data reusables.pages.sidebar-pages %}
+5. Under "{% data variables.product.prodname_pages %}", use the **Source** drop-down menu and select **None.**
+  ![Drop down menu to select a publishing source](/assets/images/help/pages/publishing-source-drop-down.png)
+{% data reusables.pages.update_your_dns_settings %}
 
-## ユーザまたは Organization サイトを取り下げる
+## Unpublishing a user or organization site
 
 {% data reusables.repositories.navigate-to-repo %}
-2. 公開元として使用しているブランチを削除するか、リポジトリ全体を削除します。 詳細については、「[リポジトリ内でブランチを作成および削除する](/articles/creating-and-deleting-branches-within-your-repository#deleting-a-branch)」と「[リポジトリを削除する](/articles/deleting-a-repository)」を参照してください。
+2. Delete the branch that you're using as a publishing source, or delete the entire repository. For more information, see "[Creating and deleting branches within your repository](/articles/creating-and-deleting-branches-within-your-repository#deleting-a-branch)" and "[Deleting a repository](/articles/deleting-a-repository)."
 {% data reusables.pages.update_your_dns_settings %}
 
 {% endif %}
diff --git a/translations/ja-JP/content/pages/index.md b/translations/ja-JP/content/pages/index.md
index 5c8d0c692f..19adbee123 100644
--- a/translations/ja-JP/content/pages/index.md
+++ b/translations/ja-JP/content/pages/index.md
@@ -50,3 +50,4 @@ children:
   - /setting-up-a-github-pages-site-with-jekyll
   - /configuring-a-custom-domain-for-your-github-pages-site
 ---
+
diff --git a/translations/ja-JP/content/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 5ecd5f08d3..141f27d805 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
@@ -22,8 +22,6 @@ 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 %}
diff --git a/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request.md b/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request.md
index 922f9dbb84..32a3feaa26 100644
--- a/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request.md
+++ b/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request.md
@@ -65,8 +65,6 @@ For more information on reviewing pull requests in {% data variables.product.pro
 {% ifversion fpt or ghes or ghec %}
 ## Reviewing dependency changes
 
-{% data reusables.dependency-review.beta %}
-
 If the pull request contains changes to dependencies you can use the dependency review for a manifest or lock file to see what has changed and check whether the changes introduce security vulnerabilities. For more information, see "[Reviewing dependency changes in a pull request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request)."
 
 {% data reusables.repositories.changed-files %}
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 ae7c873c86..a2808b957d 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
@@ -95,7 +95,7 @@ Optionally, you can require approvals from someone other than the last person to
 
 Required status checks ensure that all required CI tests are passing before collaborators can make changes to a protected branch. Required status checks can be checks or statuses. For more information, see "[About status checks](/github/collaborating-with-issues-and-pull-requests/about-status-checks)."
 
-Before you can enable required status checks, you must configure the repository to use the status API. For more information, see "[Repositories](/rest/reference/commits#commit-statuses)" in the REST documentation.
+Before you can enable required status checks, you must configure the repository to use the commit status API. For more information, see "[Commit statuses](/rest/commits/statuses)" in the REST API documentation.
 
 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.
 
@@ -187,7 +187,7 @@ When you enable branch restrictions, only users, teams, or apps that have been g
 Optionally, you can apply the same restrictions to the creation of branches that match the rule. For example, if you create a rule that only allows a certain team to push to any branches that contain the word `release`, only members of that team would be able to create a new branch that contains the word `release`.
 {% endif %}
 
-You can only give push access to a protected branch, or give permission to create a matching 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 or create a matching branch.
+You can only give push access to a protected branch, or give permission to create a matching 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{% ifversion restrict-pushes-create-branch %} or create a matching branch{% endif %}.
 
 ### Allow force pushes
 
diff --git a/translations/ja-JP/content/repositories/creating-and-managing-repositories/about-repositories.md b/translations/ja-JP/content/repositories/creating-and-managing-repositories/about-repositories.md
index 014c709c08..04007167b4 100644
--- a/translations/ja-JP/content/repositories/creating-and-managing-repositories/about-repositories.md
+++ b/translations/ja-JP/content/repositories/creating-and-managing-repositories/about-repositories.md
@@ -78,6 +78,14 @@ People with admin permissions for a repository can change an existing repository
 
 {% data reusables.repositories.about-internal-repos %} For more information on innersource, see {% data variables.product.prodname_dotcom %}'s whitepaper "[An introduction to innersource](https://resources.github.com/whitepapers/introduction-to-innersource/)."
 
+{% ifversion ghec %}
+{% note %}
+
+**Note:** You can only create internal repositories if you use {% data variables.product.prodname_ghe_cloud %} with an enterprise account. An enterprise account is a separate type of account that allows a central point of management for multiple organizations. For more information, see "[Types of {% data variables.product.prodname_dotcom %} account](/get-started/learning-about-github/types-of-github-accounts)."
+
+{% endnote %}
+{% endif %}
+
 All enterprise members have read permissions to the internal repository, but internal repositories are not visible to people {% ifversion fpt or ghec %}outside of the enterprise{% else %}who are not members of any organization{% endif %}, including outside collaborators on organization repositories. For more information, see "[Roles in an enterprise](/github/setting-up-and-managing-your-enterprise/roles-in-an-enterprise#enterprise-members)" and "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)."
 
 {% ifversion ghes %}
diff --git a/translations/ja-JP/content/repositories/creating-and-managing-repositories/transferring-a-repository.md b/translations/ja-JP/content/repositories/creating-and-managing-repositories/transferring-a-repository.md
index dff4c98d4d..ca7dd28f84 100644
--- a/translations/ja-JP/content/repositories/creating-and-managing-repositories/transferring-a-repository.md
+++ b/translations/ja-JP/content/repositories/creating-and-managing-repositories/transferring-a-repository.md
@@ -51,6 +51,12 @@ When you transfer a repository, its issues, pull requests, wiki, stars, and watc
   $ git remote set-url origin NEW_URL
   ```
 
+  {% warning %}
+
+  **Warning**: If you create a new repository under your account in the future, do not reuse the original name of the transferred repository. If you do, redirects to the transferred repository will no longer work.
+
+  {% endwarning %}
+
 - When you transfer a repository from an organization to a personal account, the repository's read-only collaborators will not be transferred. This is because collaborators can't have read-only access to repositories owned by a personal account. For more information about repository permission levels, see "[Permission levels for a personal account repository](/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository)" and "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)."{% ifversion fpt or ghec %}
 - Sponsors who have access to the repository through a sponsorship tier may be affected. For more information, see "[Adding a repository to a sponsorship tier](/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers#adding-a-repository-to-a-sponsorship-tier)".{% endif %}
 
diff --git a/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-citation-files.md b/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-citation-files.md
index b3a5dbf23b..77460dc0f2 100644
--- a/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-citation-files.md
+++ b/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-citation-files.md
@@ -5,17 +5,17 @@ redirect_from:
   - /github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github/about-citation-files
 versions:
   fpt: '*'
-  ghes: '>=3.3'
+  ghes: '*'
   ghae: '*'
   ghec: '*'
 topics:
   - Repositories
-ms.openlocfilehash: 2f7869e9218679c3c18c3182b15835bcd24e134d
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: 96e5e7308ba5d1877f231dcb454d7b797a63f221
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: ja-JP
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '145193803'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148108971'
 ---
 ## CITATION ファイルについて
 
diff --git a/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners.md b/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners.md
index 343a994c1e..d3212418a8 100644
--- a/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners.md
+++ b/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners.md
@@ -37,13 +37,11 @@ Each CODEOWNERS file assigns the code owners for a single branch in the reposito
 
 For code owners to receive review requests, the CODEOWNERS file must be on the base branch of the pull request. For example, if you assign `@octocat` as the code owner for *.js* files on the `gh-pages` branch of your repository, `@octocat` will receive review requests when a pull request with changes to *.js* files is opened between the head branch and `gh-pages`.
 
-{% ifversion fpt or ghec or ghes > 3.2 or ghae %}
 ## CODEOWNERS file size
 
 CODEOWNERS files must be under 3 MB in size. A CODEOWNERS file over this limit will not be loaded, which means that code owner information is not shown and the appropriate code owners will not be requested to review changes in a pull request.
 
 To reduce the size of your CODEOWNERS file, consider using wildcard patterns to consolidate multiple entries into a single entry.
-{% endif %}
 
 ## CODEOWNERS syntax
 
@@ -129,7 +127,6 @@ apps/ @octocat
 ## CODEOWNERS and branch protection
 Repository owners can add branch protection rules to ensure that changed code is reviewed by the owners of the changed files. For more information, see "[About protected branches](/github/administering-a-repository/defining-the-mergeability-of-pull-requests/about-protected-branches)."
 
-
 ## Further reading
 
 - "[Creating new files](/articles/creating-new-files)"
diff --git a/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-readmes.md b/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-readmes.md
index 03bfb1040b..7de402dfc0 100644
--- a/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-readmes.md
+++ b/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-readmes.md
@@ -17,7 +17,7 @@ topics:
 ---
 ## About READMEs
 
-You can add a README file to a repository to communicate important information about your project. A README, along with a repository license{% ifversion fpt or ghes > 3.2 or ghae or ghec %}, citation file{% endif %}{% ifversion fpt or ghec %}, contribution guidelines, and a code of conduct{% elsif ghes %} and contribution guidelines{% endif %}, communicates expectations for your project and helps you manage contributions.
+You can add a README file to a repository to communicate important information about your project. A README, along with a repository license, citation file{% ifversion fpt or ghec %}, contribution guidelines, and a code of conduct{% elsif ghes %} and contribution guidelines{% endif %}, communicates expectations for your project and helps you manage contributions.
 
 For more information about providing guidelines for your project, see {% ifversion fpt or ghec %}"[Adding a code of conduct to your project](/communities/setting-up-your-project-for-healthy-contributions/adding-a-code-of-conduct-to-your-project)" and {% endif %}"[Setting up your project for healthy contributions](/communities/setting-up-your-project-for-healthy-contributions)."
 
@@ -66,4 +66,4 @@ A README should contain only the necessary information for developers to get sta
 - 18F's "[Making READMEs readable](https://github.com/18F/open-source-guide/blob/18f-pages/pages/making-readmes-readable.md)"
 {%- ifversion fpt or ghec %} 
 - "[Adding an 'Open in GitHub Codespaces' badge](/codespaces/setting-up-your-project-for-codespaces/adding-a-codespaces-badge)"
-{%- endif %}   
\ No newline at end of file
+{%- endif %}   
diff --git a/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/classifying-your-repository-with-topics.md b/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/classifying-your-repository-with-topics.md
index c939fb420e..0227ac595d 100644
--- a/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/classifying-your-repository-with-topics.md
+++ b/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/classifying-your-repository-with-topics.md
@@ -1,6 +1,6 @@
 ---
-title: トピックでリポジトリを分類する
-intro: あなたのプロジェクトを他の人が見つけて貢献しやすくするために、プロジェクトの目的、分野、主催グループなどの、リポジトリに関するトピックを追加できます。
+title: Classifying your repository with topics
+intro: 'To help other people find and contribute to your project, you can add topics to your repository related to your project''s intended purpose, subject area, affinity groups, or other important qualities.'
 redirect_from:
   - /articles/about-topics
   - /articles/classifying-your-repository-with-topics
@@ -14,35 +14,36 @@ versions:
 topics:
   - Repositories
 shortTitle: Classify with topics
-ms.openlocfilehash: 68bd754ac6c50968961c61e533cb6b9de26e4cc4
-ms.sourcegitcommit: 76b840f45ba85fb79a7f0c1eb43bc663b3eadf2b
-ms.translationtype: HT
-ms.contentlocale: ja-JP
-ms.lasthandoff: 09/12/2022
-ms.locfileid: '145132235'
 ---
-## Topics について
 
-Topics を利用すれば、特定の領域に関するリポジトリを調べたり、コントリビュートするプロジェクトを見つけたり、特定の問題に対する新たなソリューションを見つけ出すことができます。 Topics は、リポジトリのメインページに表示されます。 トピック名をクリックして、{% ifversion fpt or ghec %}関連するトピックや、そのトピックに分類される他のリポジトリのリストを見たりすることができます。{% else %}そのトピックの他のリポジトリを検索することができます。{% endif %}
+## About topics
 
-![Topics を表示しているテストリポジトリのメインページ](/assets/images/help/repository/os-repo-with-topics.png)
+With topics, you can explore repositories in a particular subject area, find projects to contribute to, and discover new solutions to a specific problem. Topics appear on the main page of a repository. You can click a topic name to {% ifversion fpt or ghec %}see related topics and a list of other repositories classified with that topic{% else %}search for other repositories with that topic{% endif %}.
 
-最も使われているトピックを参照するには、 https://github.com/topics/ にアクセスします。
+![Main page of the test repository showing topics](/assets/images/help/repository/os-repo-with-topics.png)
 
-{% ifversion fpt or ghec %}[github/explore](https://github.com/github/explore) リポジトリにある {% data variables.product.product_name %} の注目のトピックのセットにコントリビュートできます。 {% endif %}
+To browse the most used topics, go to https://github.com/topics/.
 
-リポジトリの管理者は、リポジトリに好きなトピックを追加できます。 リポジトリを分類するのに役立つトピックには、そのリポジトリの意図する目的、主題の領域、コミュニティ、言語などがあります。{% ifversion fpt or ghec %}加えて、{% data variables.product.product_name %} はパブリックなリポジトリの内容を分析し、推奨されるトピックを生成します。リポジトリの管理者は、これを受諾することも拒否することもできます。 プライベートリポジトリの内容は分析されず、Topics が推奨されることはありません。{% endif %}
+{% ifversion fpt or ghec %}You can contribute to {% data variables.product.product_name %}'s set of featured topics in the [github/explore](https://github.com/github/explore) repository. {% endif %}
 
-{% ifversion fpt %}パブリックとプライベート{% elsif ghec or ghes %}パブリック、プライベート、内部{% elsif ghae %}プライベートと内部{% endif %}のリポジトリにはトピックを含めることができますが、トピック検索結果にはアクセスできるプライベート リポジトリのみが表示されます。
+Repository admins can add any topics they'd like to a repository. Helpful topics to classify a repository include the repository's intended purpose, subject area, community, or language.{% ifversion fpt or ghec %} Additionally, {% data variables.product.product_name %} analyzes public repository content and generates suggested topics that repository admins can accept or reject. Private repository content is not analyzed and does not receive topic suggestions.{% endif %}
 
-特定のトピックに関連付けられているリポジトリを検索できます。 詳細については、「[リポジトリを検索する](/search-github/searching-on-github/searching-for-repositories#search-by-topic)」を参照してください。 また、{% data variables.product.product_name %} 上でトピックのリストを検索することもできます。 詳しくは、「[トピックを検索する](/search-github/searching-on-github/searching-topics)」をご覧ください。
+{% ifversion fpt %}Public and private{% elsif ghec or ghes %}Public, private, and internal{% elsif ghae %}Private and internal{% endif %} repositories can have topics, although you will only see private repositories that you have access to in topic search results.
 
-## Topics をリポジトリに追加する
+You can search for repositories that are associated with a particular topic. For more information, see "[Searching for repositories](/search-github/searching-on-github/searching-for-repositories#search-by-topic)." You can also search for a list of topics on {% data variables.product.product_name %}. For more information, see "[Searching topics](/search-github/searching-on-github/searching-topics)."
+
+## Adding topics to your repository
+
+{% note %}
+
+**Note:** Topic names are always public, even if you create the topic from within a private repository.
+
+{% endnote %}
 
 {% data reusables.repositories.navigate-to-repo %}
-2. [バージョン情報] の右側にある {% octicon "gear" aria-label="The Gear icon" %} をクリックします。
-  ![リポジトリのメイン ページにある歯車アイコン](/assets/images/help/repository/edit-repository-details-gear.png)
-3. [Topics] で、リポジトリに追加するトピックを入力してから、スペースを入力します。
-  ![トピックの入力フォーム](/assets/images/help/repository/add-topic-form.png)
-4. トピックの追加が終わったら、 **[変更の保存]** をクリックします。
-  ![[リポジトリの詳細の編集] の [変更の保存] ボタン](/assets/images/help/repository/edit-repository-details-save-changes-button.png)
+2. To the right of "About", click {% octicon "gear" aria-label="The Gear icon" %}.
+  ![Gear icon on main page of a repository](/assets/images/help/repository/edit-repository-details-gear.png)
+3. Under "Topics", type the topic you want to add to your repository, then type a space.
+  ![Form to enter topics](/assets/images/help/repository/add-topic-form.png)
+4. After you've finished adding topics, click **Save changes**.
+  !["Save changes" button in "Edit repository details"](/assets/images/help/repository/edit-repository-details-save-changes-button.png)
diff --git a/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/disabling-project-boards-in-a-repository.md b/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/disabling-project-boards-in-a-repository.md
index 1d38c1ac93..0b6d9e77db 100644
--- a/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/disabling-project-boards-in-a-repository.md
+++ b/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/disabling-project-boards-in-a-repository.md
@@ -15,12 +15,12 @@ topics:
   - Pull requests
 shortTitle: 'Disable {% data variables.projects.projects_v1_boards %}'
 allowTitleToDifferFromFilename: true
-ms.openlocfilehash: 0407d6df39ae664474aa3fb5c99dc7998df1b951
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: 8c550cd9ebc767327298e39dc0b3a6a11368dc3f
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: ja-JP
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147422661'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148109524'
 ---
 {% data variables.projects.projects_v1_boards %} を無効にすると、タイムラインや[監査ログ](/articles/reviewing-your-security-log/)に {% data variables.projects.projects_v1_board %} の情報が表示されなくなります。
 
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 3bc55f4486..1cbb6dffab 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
@@ -50,8 +50,7 @@ You can manage the security and analysis features for your {% ifversion fpt or g
 {% ifversion fpt or ghes or ghec %}
 4. Under "Code security and analysis", 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 %}
   ![Screenshot of "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 %}
-  ![Screenshot of "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.6 or ghae > 3.6 %}<!--Insert screenshot for GHES 3.7 when available-->{% elsif ghes = 3.2 %}
-  ![Screenshot of "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){% else %}
+  ![Screenshot of "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.6 or ghae > 3.6 %}<!--Insert screenshot for GHES 3.7 when available-->
   ![Screenshot of "Enable" or "Disable" button for "Configure security and analysis" features](/assets/images/enterprise/3.3/repository/security-and-analysis-disable-or-enable-ghes.png){% endif %}
   
   {% ifversion not fpt %}
@@ -81,23 +80,19 @@ Organization owners and repository administrators can only grant access to view
 {% data reusables.repositories.sidebar-settings %}
 {% data reusables.repositories.navigate-to-code-security-and-analysis %}
 4. Under "Access to alerts", in the search field, start typing the name of the person or team you'd like to find, then click a name in the list of matches.
-   {% ifversion fpt or ghec or ghes > 3.2 %}
+   {% ifversion fpt or ghec or ghes %}
    ![Search field for granting people or teams access to security alerts](/assets/images/help/repository/security-and-analysis-security-alerts-person-or-team-search.png)
    {% endif %}
-   {% ifversion ghes < 3.3 %}
-   ![Search field for granting people or teams access to security alerts](/assets/images/enterprise/3.2/repository/security-and-analysis-security-alerts-person-or-team-search.png)
-   {% endif %}
+   
    {% ifversion ghae %}
    ![Search field for granting people or teams access to security alerts](/assets/images/enterprise/github-ae/repository/security-and-analysis-security-alerts-person-or-team-search-ghae.png)
    {% endif %}
    
 5. Click **Save changes**.
-   {% ifversion fpt or ghes > 3.2 or ghec %}
+   {% ifversion fpt or ghes or ghec %}
    !["Save changes" button for changes to security alert settings](/assets/images/help/repository/security-and-analysis-security-alerts-save-changes.png)
    {% endif %}
-   {% ifversion ghes < 3.3 %}
-   !["Save changes" button for changes to security alert settings](/assets/images/enterprise/3.2/repository/security-and-analysis-security-alerts-save-changes.png)
-   {% endif %}
+   
    {% ifversion ghae %}
    !["Save changes" button for changes to security alert settings](/assets/images/enterprise/github-ae/repository/security-and-analysis-security-alerts-save-changes-ghae.png)
    {% endif %}
@@ -108,12 +103,10 @@ Organization owners and repository administrators can only grant access to view
 {% data reusables.repositories.sidebar-settings %}
 {% data reusables.repositories.navigate-to-code-security-and-analysis %}
 4. Under "Access to alerts", to the right of the person or team whose access you'd like to remove, click {% octicon "x" aria-label="X symbol" %}.
-   {% ifversion fpt or ghec or ghes > 3.2 %}  
+   {% ifversion fpt or ghec or ghes %}  
    !["x" button to remove someone's access to security alerts for your repository](/assets/images/help/repository/security-and-analysis-security-alerts-username-x.png)
    {% endif %}
-   {% ifversion ghes < 3.3 %}
-   !["x" button to remove someone's access to security alerts for your repository](/assets/images/enterprise/3.2/repository/security-and-analysis-security-alerts-username-x.png)
-   {% endif %}
+   
    {% ifversion ghae %}
    !["x" button to remove someone's access to security alerts for your repository](/assets/images/enterprise/github-ae/repository/security-and-analysis-security-alerts-username-x-ghae.png)
    {% endif %}
diff --git a/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-the-commit-signoff-policy-for-your-repository.md b/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-the-commit-signoff-policy-for-your-repository.md
index 188b4b10dc..941d10d1b0 100644
--- a/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-the-commit-signoff-policy-for-your-repository.md
+++ b/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-the-commit-signoff-policy-for-your-repository.md
@@ -1,6 +1,6 @@
 ---
 title: Managing the commit signoff policy for your repository
-intro: You can require users to automatically sign off on the commits they make to your repository using {% data variables.product.product_name %}'s web interface.
+intro: 'You can require users to automatically sign off on the commits they make to your repository using {% data variables.product.product_name %}''s web interface.'
 versions:
   feature: commit-signoffs
 permissions: Organization owners and repository administrators can require all commits to a repository to be signed off by the commit author.
@@ -22,4 +22,4 @@ Organization owners can also enable compulsory commit signoffs at the organizati
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
 1. Select **Require contributors to sign off on web-based commits**.
-  ![Screenshot of Require contributors to sign off on web-based commits](/assets/images/help/repository/require-signoffs.png)
\ No newline at end of file
+  ![Screenshot of Require contributors to sign off on web-based commits](/assets/images/help/repository/require-signoffs.png)
diff --git a/translations/ja-JP/content/repositories/releasing-projects-on-github/managing-releases-in-a-repository.md b/translations/ja-JP/content/repositories/releasing-projects-on-github/managing-releases-in-a-repository.md
index d01f6e8e7a..832a7ae04f 100644
--- a/translations/ja-JP/content/repositories/releasing-projects-on-github/managing-releases-in-a-repository.md
+++ b/translations/ja-JP/content/repositories/releasing-projects-on-github/managing-releases-in-a-repository.md
@@ -39,22 +39,19 @@ You can choose whether {% data variables.large_files.product_name_long %} ({% da
 1. Click **Draft a new release**.
 
    {% ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4 %}![Releases draft button](/assets/images/help/releases/draft-release-button-with-search.png){% else %}![Releases draft button](/assets/images/help/releases/draft_release_button.png){% endif %}
-1. {% ifversion fpt or ghec or ghes > 3.2 or ghae %}Click **Choose a tag**, type{% else %}Type{% endif %} a version number for your release{% ifversion fpt or ghec or ghes > 3.2 or ghae %}, and press **Enter**{% endif %}. Alternatively, select an existing tag.
+1. Click **Choose a tag**, type a version number for your release, and press **Enter**. Alternatively, select an existing tag.
 
-   {% ifversion fpt or ghec or ghes > 3.2 or ghae %}![Enter a tag](/assets/images/help/releases/releases-tag-create.png)
+   ![Enter a tag](/assets/images/help/releases/releases-tag-create.png)
 1. If you are creating a new tag, click **Create new tag**.
 
    ![Screenshot of confirming you want to create a new tag](/assets/images/help/releases/releases-tag-create-confirm.png)
-   {% else %}
-   ![Screenshot of the Releases tagged version](/assets/images/enterprise/releases/releases-tag-version.png)
-{% endif %}
+   
 1. If you have created a new tag, use the drop-down menu to select the branch that contains the project you want to release.
 
-   {% ifversion fpt or ghec or ghes > 3.2 or ghae %}
+   
    ![Screenshot of dropdown to choose a branch](/assets/images/help/releases/releases-choose-branch.png)
 
-   {% else %}
-   ![Screenshot of the Releases tagged branch](/assets/images/enterprise/releases/releases-tag-branch.png){% endif %}
+   
 
 {%- data reusables.releases.previous-release-tag %}
 1. Type a title and description for your release.
@@ -90,7 +87,7 @@ You can choose whether {% data variables.large_files.product_name_long %} ({% da
 1. If you're ready to publicize your release, click **Publish release**. To work on the release later, click **Save draft**.
    ![Publish release and Draft release buttons](/assets/images/help/releases/release_buttons.png)
 
-   {%- ifversion fpt or ghec or ghes > 3.2 or ghae > 3.3 %}
+   {%- ifversion fpt or ghec or ghae > 3.3 %}
    You can then view your published or draft releases in the releases feed for your repository. For more information, see "[Screenshot of your repository's releases and tags](/github/administering-a-repository/releasing-projects-on-github/viewing-your-repositorys-releases-and-tags)."
 
    {% ifversion fpt or ghec or ghes > 3.4 or ghae > 3.3 %}
diff --git a/translations/ja-JP/content/repositories/releasing-projects-on-github/searching-a-repositorys-releases.md b/translations/ja-JP/content/repositories/releasing-projects-on-github/searching-a-repositorys-releases.md
index 7fd76aff9f..b910f68b66 100644
--- a/translations/ja-JP/content/repositories/releasing-projects-on-github/searching-a-repositorys-releases.md
+++ b/translations/ja-JP/content/repositories/releasing-projects-on-github/searching-a-repositorys-releases.md
@@ -6,16 +6,16 @@ shortTitle: Searching releases
 versions:
   fpt: '*'
   ghec: '*'
-  ghes: '>3.2'
+  ghes: '*'
   ghae: '>= 3.4'
 topics:
   - Repositories
-ms.openlocfilehash: 193363cc5762db6cb030906a64dacb7bab6f5b7a
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: a61e49521452befdcddf2724cad837062c7d54a1
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: ja-JP
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147066187'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148109652'
 ---
 ## リポジトリ内のリリースの検索
 
diff --git a/translations/ja-JP/content/repositories/working-with-files/using-files/working-with-non-code-files.md b/translations/ja-JP/content/repositories/working-with-files/using-files/working-with-non-code-files.md
index 5dd1df54fe..d8ad87c848 100644
--- a/translations/ja-JP/content/repositories/working-with-files/using-files/working-with-non-code-files.md
+++ b/translations/ja-JP/content/repositories/working-with-files/using-files/working-with-non-code-files.md
@@ -199,14 +199,10 @@ You can click {% octicon "file" aria-label="The paper icon" %} to see the change
 
 ![Rendered Prose changes](/assets/images/help/repository/rendered_prose_changes.png)
 
-{% ifversion fpt or ghes > 3.2 or ghae or ghec %}
-
 ### Disabling Markdown rendering
 
 {% data reusables.repositories.disabling-markdown-rendering %}
 
-{% endif %}
-
 ### Visualizing attribute changes
 
 We provide a tooltip
diff --git a/translations/ja-JP/content/rest/deployments/branch-policies.md b/translations/ja-JP/content/rest/deployments/branch-policies.md
index 77b8636e5d..07177ff285 100644
--- a/translations/ja-JP/content/rest/deployments/branch-policies.md
+++ b/translations/ja-JP/content/rest/deployments/branch-policies.md
@@ -11,12 +11,12 @@ versions:
 topics:
   - API
 miniTocMaxHeadingLevel: 3
-ms.openlocfilehash: 70f5d05f0a28e9fa21bf7bc99abbac6bd4a6509a
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: 109bf81019d62e4c654ba6da4fa71f8fd359ceb4
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: ja-JP
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147549127'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148109595'
 ---
 ## デプロイ ブランチ ポリシー API について
 
diff --git a/translations/ja-JP/content/rest/enterprise-admin/audit-log.md b/translations/ja-JP/content/rest/enterprise-admin/audit-log.md
index 33ca7acbfc..f5f5ec12fb 100644
--- a/translations/ja-JP/content/rest/enterprise-admin/audit-log.md
+++ b/translations/ja-JP/content/rest/enterprise-admin/audit-log.md
@@ -2,7 +2,7 @@
 title: Audit log
 intro: ''
 versions:
-  ghes: '>=3.3'
+  ghes: '*'
   ghec: '*'
   ghae: '*'
 topics:
diff --git a/translations/ja-JP/content/rest/enterprise-admin/scim.md b/translations/ja-JP/content/rest/enterprise-admin/scim.md
index 05b64bf796..5f0be8c0ba 100644
--- a/translations/ja-JP/content/rest/enterprise-admin/scim.md
+++ b/translations/ja-JP/content/rest/enterprise-admin/scim.md
@@ -1,6 +1,6 @@
 ---
 title: SCIM
-intro: 'You can automate user creation and team memberships using the SCIM API.'
+intro: You can automate user creation and team memberships using the SCIM API.
 versions:
   ghes: '>=3.6'
 topics:
diff --git a/translations/ja-JP/content/rest/overview/api-previews.md b/translations/ja-JP/content/rest/overview/api-previews.md
index 6fa7bcc827..9ec7f2ffc9 100644
--- a/translations/ja-JP/content/rest/overview/api-previews.md
+++ b/translations/ja-JP/content/rest/overview/api-previews.md
@@ -1,203 +1,29 @@
 ---
-title: API プレビュー
-intro: API プレビューを使用して新機能を試し、これらの機能が正式なものになる前にフィードバックを提供できます。
+title: API previews
+intro: You can use API previews to try out new features and provide feedback before these features become official.
 redirect_from:
   - /v3/previews
 versions:
   ghes: <3.4
 topics:
   - API
-ms.openlocfilehash: fe00e2ab78881edab8d0f7704f80f2f20163fdeb
-ms.sourcegitcommit: ac00e2afa6160341c5b258d73539869720b395a4
-ms.translationtype: HT
-ms.contentlocale: ja-JP
-ms.lasthandoff: 09/09/2022
-ms.locfileid: '147878439'
 ---
-API プレビューを使用すると、正式に GitHub API の一部になる前に、新しい API や既存の API メソッドへの変更を試すことができます。
 
-プレビュー期間中は、開発者からのフィードバックに基づいて機能を変更することがあります。 変更を行う際には、事前の通知なく[開発者ブログ](https://developer.github.com/changes/)で発表します。
 
-API プレビューにアクセスするには、自分の要求の `Accept` ヘッダーにカスタムの[メディアの種類](/rest/overview/media-types)を指定する必要があります。 各プレビューの機能ドキュメントに、どのカスタムメディアタイプを提供するのかが示されています。
+API previews let you try out new APIs and changes to existing API methods before they become part of the official GitHub API.
 
-{% ifversion ghes < 3.3 %}
+During the preview period, we may change some features based on developer feedback. If we do make changes, we'll announce them on the [developer blog](https://developer.github.com/changes/) without advance notice.
 
-## 強化されたデプロイメント
-
-より多くの情報と細かい粒度で[デプロイ](/rest/reference/repos#deployments)をより細かく制御します。
-
-**カスタムのメディアの種類:** `ant-man-preview`
-**発表日:** [2016-04-06](https://developer.github.com/changes/2016-04-06-deployment-and-deployment-status-enhancements/)
-
-{% endif %}
-
-{% ifversion ghes < 3.3 %}
-
-## リアクション
-
-コミット、問題、コメントの[リアクション](/rest/reference/reactions)を管理します。
-
-**カスタムのメディアの種類:** `squirrel-girl-preview`
-**発表:** [2016-05-12](https://developer.github.com/changes/2016-05-12-reactions-api-preview/)
-**更新:** [2016-06-07](https://developer.github.com/changes/2016-06-07-reactions-api-update/)
-
-{% endif %}
-
-{% ifversion ghes < 3.3 %}
-
-## タイムライン
-
-問題または pull request の[イベントの一覧](/rest/reference/issues#timeline)を取得します。
-
-**カスタムのメディアの種類:** `mockingbird-preview`
-**発表日:** [2016-05-23](https://developer.github.com/changes/2016-05-23-timeline-preview-api/)
-
-{% endif %}
-
-{% ifversion ghes < 3.3 %}
-## プロジェクト
-
-[プロジェクト](/rest/reference/projects)を管理します。
-
-**カスタムのメディアの種類:** `inertia-preview`
-**発表:** [2016-09-14](https://developer.github.com/changes/2016-09-14-projects-api/)
-**更新:** [2016-10-27](https://developer.github.com/changes/2016-10-27-changes-to-projects-api/) {% endif %} {% ifversion ghes < 3.3 %}
-
-## コミット検索
-
-[コミットを検索します](/rest/reference/search)。
-
-**カスタムのメディアの種類:** `cloak-preview`
-**発表:** [2017-01-05](https://developer.github.com/changes/2017-01-05-commit-search-api/) {% endif %} {% ifversion ghes < 3.3 %}
-
-## リポジトリトピック
-
-リポジトリの結果を返す[呼び出し](/articles/about-topics/)で[リポジトリ トピック](/rest/reference/repos)の一覧を表示します。
-
-**カスタムのメディアの種類:** `mercy-preview`
-**発表:** [2017-01-31](https://github.com/blog/2309-introducing-topics) {% endif %} {% ifversion ghes < 3.3 %}
-
-## 行動規範
-
-すべての[行動規範](/rest/reference/codes-of-conduct)を表示するか、リポジトリに現在含まれる行動規範を取得します。
-
-**カスタムのメディアの種類:** `scarlet-witch-preview`
-
-{% endif %}
-
-{% ifversion ghes < 3.3 %}
-
-## グローバル webhook
-
-[組織](/webhooks/event-payloads/#organization)と[ユーザー](/webhooks/event-payloads/#user)のイベントの種類に対して[グローバル Webhook](/rest/reference/enterprise-admin#global-webhooks/) を有効にします。 この API プレビューは {% data variables.product.prodname_ghe_server %} でのみ使用できます。
-
-**カスタムのメディアの種類:** `superpro-preview`
-**発表日:** [2017-12-12](/rest/reference/enterprise-admin#global-webhooks)
-
-{% endif %}
-
-{% ifversion ghes < 3.3 %}
-
-## 署名済みコミットの必須化
-
-これで、API を使用して、[保護されたブランチで署名済みコミットを必須にする](/rest/reference/repos#branches)ための設定を管理できるようになりました。
-
-**カスタムのメディアの種類:** `zzzax-preview`
-**発表:** [2018-02-22](https://developer.github.com/changes/2018-02-22-protected-branches-required-signatures) {% endif %} {% ifversion ghes < 3.3 %}
-
-## 複数の承認レビューの必須化
-
-API を使用することで、pull request に対して[複数の承認レビューを要求](/rest/reference/repos#branches)できるようになりました。
-
-**カスタムのメディアの種類:** `luke-cage-preview`
-**発表日:** [2018-03-16](https://developer.github.com/changes/2018-03-16-protected-branches-required-approving-reviews)
-
-{% endif %}
-
-{% ifversion ghes < 3.3 %}
-
-## プロジェクトカードの詳細
-
-[issue イベント](/rest/reference/issues#events)と [issue タイムライン イベント](/rest/reference/issues#timeline) の REST API 応答から、プロジェクト関連のイベントの `project_card` フィールドが返されるようになりました。
-
-**カスタムのメディアの種類:** `starfox-preview`
-**発表日:** [2018-09-05](https://developer.github.com/changes/2018-09-05-project-card-events)
-
-{% endif %}
-
-{% ifversion ghes < 3.3 %}
-
-## デプロイメントステータス
-
-これで、[デプロイ状態](/rest/reference/deployments#create-a-deployment-status)の `environment` を更新し、`in_progress` と `queued` の状態を使用できるようになりました。 デプロイの状態を作成する際に、`auto_inactive` パラメーターを使用して古い `production` デプロイを `inactive` として使用できるようになりました。
-
-**カスタムのメディアの種類:** `flash-preview`
-**発表日:** [2018-10-16](https://developer.github.com/changes/2018-10-16-deployments-environments-states-and-auto-inactive-updates/)
-
-{% endif %}
-
-{% ifversion ghes < 3.3 %}
-
-## リポジトリの作成権限
-
-Organization メンバーによるリポジトリの作成可否、および作成可能なリポジトリのタイプを設定できるようになりました。 詳細については、[組織の更新](/rest/reference/orgs#update-an-organization)に関するページを参照してください。
-
-**カスタムのメディアの種類:** `surtur-preview`
-**発表:** [2019-12-03](https://developer.github.com/changes/2019-12-03-internal-visibility-changes/)
-
-{% endif %}
+To access an API preview, you'll need to provide a custom [media type](/rest/overview/media-types) in the `Accept` header for your requests. Feature documentation for each preview specifies which custom media type to provide.
 
 {% ifversion ghes < 3.4 %}
-## コンテンツの添付
+## Content attachments
 
-{% data variables.product.prodname_unfurls %} API を使用して、登録されたドメインにリンクする URL の詳細情報を GitHub で提供できるようになりました。 詳細については、「[添付コンテンツを使用する](/apps/using-content-attachments/)」を参照してください。
+You can now provide more information in GitHub for URLs that link to registered domains by using the {% data variables.product.prodname_unfurls %} API. See "[Using content attachments](/apps/using-content-attachments/)" for more details.
 
-**カスタムのメディアの種類:** `corsair-preview`
-**発表:** [2018-12-10](https://developer.github.com/changes/2018-12-10-content-attachments-api/)
-
-{% endif %} {% ifversion ghes < 3.3 %}
-
-## Pages の有効化と無効化
-
-[Pages API](/rest/reference/repos#pages) の新しいエンドポイントを使用して、Pages を有効または無効にすることができます。 Pages の詳細については、[GitHub Pages の基本](/categories/github-pages-basics)に関するページを参照してください。
-
-**カスタムのメディアの種類:** `switcheroo-preview`
-**発表:** [2019-03-14](https://developer.github.com/changes/2019-03-14-enabling-disabling-pages/)
+**Custom media types:** `corsair-preview`
+**Announced:** [2018-12-10](https://developer.github.com/changes/2018-12-10-content-attachments-api/)
 
 {% endif %}
 
-{% ifversion ghes < 3.3 %}
 
-## コミットのブランチまたはプルリクエストの一覧表示
-
-[Commits API](/rest/reference/repos#commits) で 2 つの新しいエンドポイントを使用して、コミットのブランチまたは pull requests を一覧表示できます。
-
-**カスタムのメディアの種類:** `groot-preview`
-**発表:** [2019-04-11](https://developer.github.com/changes/2019-04-11-pulls-branches-for-commit/)
-
-{% endif %}
-
-{% ifversion ghes < 3.3 %}
-
-## プルリクエストブランチの更新
-
-新しいエンドポイントを使用することで、アップストリーム ブランチの HEAD からの変更で [pull request ブランチを更新](/rest/reference/pulls#update-a-pull-request-branch)することができます。
-
-**カスタムのメディアの種類:** `lydian-preview`
-**発表:** [2019-05-29](https://developer.github.com/changes/2019-05-29-update-branch-api/)
-
-{% endif %} {% ifversion ghes < 3.3 %}
-
-## リポジトリテンプレートの作成および使用
-
-新しいエンドポイントを使用すると、[テンプレートを使用してリポジトリを作成](/rest/reference/repos#create-a-repository-using-a-template)したり、`is_template` パラメーターを `true` に設定して[認証済みユーザー用のリポジトリを作成](/rest/reference/repos#create-a-repository-for-the-authenticated-user)したりできます。 [リポジトリを取得](/rest/reference/repos#get-a-repository)することで、`is_template` キーを使用してそれがテンプレート リポジトリとして設定されているかどうかを確認できます。
-
-**カスタムのメディアの種類:** `baptiste-preview`
-**発表:** [2019-07-05](https://developer.github.com/changes/2019-07-16-repository-templates-api/) {% endif %} {% ifversion ghes < 3.3 %}
-
-## Repositories API の新しい可視性パラメータ
-
-[Repositories API](/rest/reference/repos) でリポジトリの可視性を設定および取得できます。
-
-**カスタムのメディアの種類:** `nebula-preview`
-**発表:** [2019-11-25](https://developer.github.com/changes/2019-12-03-internal-visibility-changes/) {% endif %}
diff --git a/translations/ja-JP/content/rest/overview/endpoints-available-for-github-apps.md b/translations/ja-JP/content/rest/overview/endpoints-available-for-github-apps.md
index f3fbea2471..73eb4745e2 100644
--- a/translations/ja-JP/content/rest/overview/endpoints-available-for-github-apps.md
+++ b/translations/ja-JP/content/rest/overview/endpoints-available-for-github-apps.md
@@ -13,11 +13,11 @@ versions:
 topics:
   - API
 shortTitle: GitHub App-enabled endpoints
-ms.openlocfilehash: ab79abe1df9a14f7fdcc73f863e7bce5aa4abd4c
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: d8bb53e1844b8171a1ce742fc38e4c4bb29013e7
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: ja-JP
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147410364'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148109523'
 ---
 <!-- The content of this page is rendered as a NextJS page component. -->
diff --git a/translations/ja-JP/content/rest/overview/permissions-required-for-github-apps.md b/translations/ja-JP/content/rest/overview/permissions-required-for-github-apps.md
index 67ed185aab..3d7ecba758 100644
--- a/translations/ja-JP/content/rest/overview/permissions-required-for-github-apps.md
+++ b/translations/ja-JP/content/rest/overview/permissions-required-for-github-apps.md
@@ -140,6 +140,7 @@ If you set the metadata permission to **No access** and select a permission that
 - [`GET /repos/:owner/:repo/actions/workflows`](/rest/reference/actions#list-repository-workflows) (read)
 - [`GET /repos/:owner/:repo/actions/workflows/:workflow_id`](/rest/reference/actions#get-a-workflow) (read)
 - [`GET /repos/:owner/:repo/actions/workflows/:workflow_id/runs`](/rest/reference/actions#list-workflow-runs) (read)
+- [`POST /repos/:owner/:repo/actions/workflows/:workflow_id/dispatches`](/rest/reference/actions#create-a-workflow-dispatch-event) (write)
 {% endif %}
 
 ## Administration
@@ -284,20 +285,14 @@ If you set the metadata permission to **No access** and select a permission that
 - [`GET /repos/:owner/:repo/code-scanning/alerts`](/rest/reference/code-scanning#list-code-scanning-alerts-for-a-repository) (read)
 - [`GET /repos/:owner/:repo/code-scanning/alerts/:alert_number`](/rest/reference/code-scanning#get-a-code-scanning-alert) (read)
 - [`PATCH /repos/:owner/:repo/code-scanning/alerts/:alert_number`](/rest/reference/code-scanning#update-a-code-scanning-alert) (write)
-{% ifversion fpt or ghec or ghes or ghae -%}
 - [`GET /repos/:owner/:repo/code-scanning/alerts/:alert_number/instances`](/rest/reference/code-scanning#list-instances-of-a-code-scanning-alert) (read)
-{% endif -%}
 - [`GET /repos/:owner/:repo/code-scanning/analyses`](/rest/reference/code-scanning#list-code-scanning-analyses-for-a-repository) (read)
-{% ifversion fpt or ghec or ghes or ghae -%}
 - [`GET /repos/:owner/:repo/code-scanning/analyses/:analysis_id`](/rest/reference/code-scanning#get-a-code-scanning-analysis-for-a-repository) (read)
-{% endif -%}
 {% ifversion fpt or ghec or ghes -%}
 - [`DELETE /repos/:owner/:repo/code-scanning/analyses/:analysis_id`](/rest/reference/code-scanning#delete-a-code-scanning-analysis-from-a-repository) (write)
 {% endif -%}
 - [`POST /repos/:owner/:repo/code-scanning/sarifs`](/rest/reference/code-scanning#upload-an-analysis-as-sarif-data) (write)
-{% ifversion fpt or ghec or ghes or ghae -%}
 - [`GET /repos/:owner/:repo/code-scanning/sarifs/:sarif_id`](/rest/reference/code-scanning#get-information-about-a-sarif-upload) (read)
-{% endif -%}
 {% ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4 -%}
 - [`GET /orgs/:org/code-scanning/alerts`](/rest/reference/code-scanning#list-code-scanning-alerts-by-organization) (read)
 {% endif -%}
diff --git a/translations/ja-JP/content/rest/repos/autolinks.md b/translations/ja-JP/content/rest/repos/autolinks.md
index ea8442f75c..ad8ae892e4 100644
--- a/translations/ja-JP/content/rest/repos/autolinks.md
+++ b/translations/ja-JP/content/rest/repos/autolinks.md
@@ -5,18 +5,18 @@ shortTitle: Autolinks
 intro: ご利用のワークフローをスムーズにするには、API を使って、JIRA の Issue や Zendesk のチケットなど外部リソースへの自動リンクを追加します。
 versions:
   fpt: '*'
-  ghes: '>=3.3'
+  ghes: '*'
   ghae: '*'
   ghec: '*'
 topics:
   - API
 miniTocMaxHeadingLevel: 3
-ms.openlocfilehash: 1a0900a0665675526381987836631c7ff3496a81
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: c35d9232ec43cf9dc19c9559de0e8411fa85e242
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: ja-JP
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147066555'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148109007'
 ---
 ## リポジトリ自動リンク API について
 
diff --git a/translations/ja-JP/content/rest/repos/lfs.md b/translations/ja-JP/content/rest/repos/lfs.md
index a258ba1f75..a402c744c9 100644
--- a/translations/ja-JP/content/rest/repos/lfs.md
+++ b/translations/ja-JP/content/rest/repos/lfs.md
@@ -3,7 +3,7 @@ title: Git LFS
 intro: 'You can enable or disable {% data variables.large_files.product_name_long %} (LFS) for a repository.'
 versions:
   fpt: '*'
-  ghes: '>=3.3'
+  ghes: '*'
   ghae: '*'
   ghec: '*'
 topics:
diff --git a/translations/ja-JP/content/rest/users/ssh-signing-keys.md b/translations/ja-JP/content/rest/users/ssh-signing-keys.md
index df9418c21a..678c0a704c 100644
--- a/translations/ja-JP/content/rest/users/ssh-signing-keys.md
+++ b/translations/ja-JP/content/rest/users/ssh-signing-keys.md
@@ -9,12 +9,12 @@ topics:
   - API
 miniTocMaxHeadingLevel: 3
 allowTitleToDifferFromFilename: true
-ms.openlocfilehash: 758f7897f965323e3675bf6b0ac1d295a3338f05
-ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794
+ms.openlocfilehash: c8b9b71cf14efdd119f759fa36f5baae8e7a9301
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: ja-JP
-ms.lasthandoff: 09/09/2022
-ms.locfileid: '147773905'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148108935'
 ---
 ## ユーザーの SSH 署名キー API について
 
diff --git a/translations/ja-JP/content/search-github/searching-on-github/searching-issues-and-pull-requests.md b/translations/ja-JP/content/search-github/searching-on-github/searching-issues-and-pull-requests.md
index 0054f0a88c..71105cabcd 100644
--- a/translations/ja-JP/content/search-github/searching-on-github/searching-issues-and-pull-requests.md
+++ b/translations/ja-JP/content/search-github/searching-on-github/searching-issues-and-pull-requests.md
@@ -163,8 +163,8 @@ You can narrow your results by labels, using the `label` qualifier. Since issues
 | ------------- | -------------
 | <code>label:<em>LABEL</em></code> | [**label:"help wanted" language:ruby**](https://github.com/search?utf8=%E2%9C%93&q=label%3A%22help+wanted%22+language%3Aruby&type=Issues) matches issues with the label "help wanted" that are in Ruby repositories.
 |  | [**broken in:body -label:bug label:priority**](https://github.com/search?q=broken+in%3Abody+-label%3Abug+label%3Apriority&type=Issues) matches issues with the word "broken" in the body, that lack the label "bug", but *do* have the label "priority."
-| | [**label:bug label:resolved**](https://github.com/search?l=&q=label%3Abug+label%3Aresolved&type=Issues) matches issues with the labels "bug" and "resolved."{% ifversion fpt or ghes > 3.2 or ghae or ghec %}
-| | [**label:bug,resolved**](https://github.com/search?q=label%3Abug%2Cresolved&type=Issues) matches issues with the label "bug" or the label "resolved."{% endif %}
+| | [**label:bug label:resolved**](https://github.com/search?l=&q=label%3Abug+label%3Aresolved&type=Issues) matches issues with the labels "bug" and "resolved."
+| | [**label:bug,resolved**](https://github.com/search?q=label%3Abug%2Cresolved&type=Issues) matches issues with the label "bug" or the label "resolved."
 
 ## Search by milestone
 
@@ -266,8 +266,8 @@ You can filter pull requests based on their [review status](/pull-requests/colla
 | `review:approved` | [**type:pr review:approved**](https://github.com/search?utf8=%E2%9C%93&q=type%3Apr+review%3Aapproved&type=Issues) matches pull requests that a reviewer has approved.
 | `review:changes_requested` | [**type:pr review:changes_requested**](https://github.com/search?utf8=%E2%9C%93&q=type%3Apr+review%3Achanges_requested&type=Issues) matches pull requests in which a reviewer has asked for changes.
 | <code>reviewed-by:<em>USERNAME</em></code> | [**type:pr reviewed-by:gjtorikian**](https://github.com/search?utf8=%E2%9C%93&q=type%3Apr+reviewed-by%3Agjtorikian&type=Issues) matches pull requests reviewed by a particular person.
-| <code>review-requested:<em>USERNAME</em></code> | [**type:pr review-requested:benbalter**](https://github.com/search?utf8=%E2%9C%93&q=type%3Apr+review-requested%3Abenbalter&type=Issues) matches pull requests where a specific person is requested for review. Requested reviewers are no longer listed in the search results after they review a pull request. If the requested person is on a team that is requested for review, then review requests for that team will also appear in the search results.{% ifversion fpt or ghae or ghes > 3.2 or ghec %}
-| <code>user-review-requested:@me</code> | [**type:pr user-review-requested:@me**](https://github.com/search?q=is%3Apr+user-review-requested%3A%40me+) matches pull requests that you have directly been asked to review.{% endif %}
+| <code>review-requested:<em>USERNAME</em></code> | [**type:pr review-requested:benbalter**](https://github.com/search?utf8=%E2%9C%93&q=type%3Apr+review-requested%3Abenbalter&type=Issues) matches pull requests where a specific person is requested for review. Requested reviewers are no longer listed in the search results after they review a pull request. If the requested person is on a team that is requested for review, then review requests for that team will also appear in the search results.
+| <code>user-review-requested:@me</code> | [**type:pr user-review-requested:@me**](https://github.com/search?q=is%3Apr+user-review-requested%3A%40me+) matches pull requests that you have directly been asked to review.
 | <code>team-review-requested:<em>TEAMNAME</em></code> | [**type:pr team-review-requested:github/docs**](https://github.com/search?q=type%3Apr+team-review-requested%3Agithub%2Fdocs&type=pullrequests) matches pull requests that have review requests from the team `github/docs`. Requested reviewers are no longer listed in the search results after they review a pull request.
 
 ## Search by when an issue or pull request was created or last updated
diff --git a/translations/ja-JP/content/search/index.md b/translations/ja-JP/content/search/index.md
index 1d56a86dc2..6d79ce0407 100644
--- a/translations/ja-JP/content/search/index.md
+++ b/translations/ja-JP/content/search/index.md
@@ -6,11 +6,11 @@ versions:
   ghec: '*'
   ghes: '*'
   ghae: '*'
-ms.openlocfilehash: d7e276ed5305ffc8fd9732f6895fdf3b7461fb4c
-ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794
+ms.openlocfilehash: 1a780ae1a9481af58598ac2a37eec1553b08f627
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: ja-JP
-ms.lasthandoff: 09/09/2022
-ms.locfileid: '147648290'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148108826'
 ---
 
diff --git a/translations/ja-JP/content/sponsors/receiving-sponsorships-through-github-sponsors/index.md b/translations/ja-JP/content/sponsors/receiving-sponsorships-through-github-sponsors/index.md
index 56cb561fd3..734faced51 100644
--- a/translations/ja-JP/content/sponsors/receiving-sponsorships-through-github-sponsors/index.md
+++ b/translations/ja-JP/content/sponsors/receiving-sponsorships-through-github-sponsors/index.md
@@ -23,11 +23,11 @@ children:
   - /tax-information-for-github-sponsors
   - /disabling-your-github-sponsors-account
   - /unpublishing-your-github-sponsors-profile
-ms.openlocfilehash: 7f7a6e7a1f46dadaac3cf75b8387bf18dd22e0d0
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: d7d3b8f98e7acf74ee24e7cf705f0ddb3c5d4b26
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: ja-JP
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '145149677'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148108821'
 ---
 
diff --git a/translations/ja-JP/data/glossaries/external.yml b/translations/ja-JP/data/glossaries/external.yml
index ff91db0de1..2fd18cd191 100644
--- a/translations/ja-JP/data/glossaries/external.yml
+++ b/translations/ja-JP/data/glossaries/external.yml
@@ -1,564 +1,788 @@
-- term: '@メンション'
+- term: '@mention'
   description:
-    "GitHub のユーザーに通知するには、ユーザー名の前に \"@\" を付けます。GitHub の Organization のユーザーも、メンションされるチームの一員にすることができます。"
-- term: アクセス トークン
+    To notify a person on GitHub by using `@` before their username. Users in an organization on GitHub can also be a part of a team that can be
+    mentioned.
+- term: access token
   description: >-
-    コマンド ラインと API のどちらで Git を使っても、HTTPS 経由で Git 操作を実行するときにパスワードの代わりに使用されるトークン。個人用アクセス トークンとも呼ばれます。
-- term: API プレビュー
+    A token that is used in place of a password when performing Git operations
+    over HTTPS with Git on the command line or the API. Also called a personal
+    access token.
+- term: API preview
   description: >-
-    新しい API や、既存の API メソッドに対する変更を、公式 GitHub API の一部となる前に試す方法。
-- term: アプライアンス
+    A way to try out new APIs and changes to existing API methods before they
+    become part of the official GitHub API.
+- term: appliance
   description: >-
-    Just Enough Operating System (JeOS) と結合して、業界標準ハードウェア (通常はサーバー) または仮想マシンで最適に動作するソフトウェア アプリケーション。
+    A software application combined with just enough operating system (JeOS) to
+    run optimally on industry-standard hardware (typically a server) or in a
+    virtual machine.
 - term: assignee
-  description: issue に割り当てられたユーザー。
-- term: 認証コード
+  description: The user that is assigned to an issue.
+- term: authentication code
   description: >-
-    ブラウザーから 2FA でサインインするときに、GitHub パスワードの他に入力するコード。このコードは、アプリケーションによって生成されるか、お使いのスマートフォンにテキスト メッセージで送信されます。"2FA 認証コード" とも呼ばれます。
-- term: ベース ブランチ
+    A code you'll supply, in addition to your GitHub password, when signing in
+    with 2FA via the browser. This code is either generated by an application or delivered to
+    your phone via text message. Also called a "2FA authentication code."
+- term: base branch
   description:
-    pull request をマージするときに変更の組み込み先となるブランチ。必要な場合は、pull request を作成するときに、ベース ブランチをリポジトリの既定のブランチから別のブランチに変更できます。
-- term: Basic 認証
+    The branch into which changes are combined when you merge a pull request.
+    When you create a pull request, you can change the base branch from the repository's default branch to another branch if required.
+- term: basic authentication
   description: >-
-    資格情報が暗号化されていないテキストとして送信される場合の認証の方法。
-- term: 略歴
+    A method of authentication where the credentials are sent as
+    unencrypted text.
+- term: bio
   description: >-
-    プロフィールに記載されている、ユーザーが作成した説明 ([プロフィールに略歴を追加する](/articles/adding-a-bio-to-your-profile))
-- term: 支払いサイクル
-  description: 特定の支払いプランの時間間隔。
-- term: 支払い請求先メール アドレス
+    The user-generated description found on a profile:
+    [Adding a bio to your profile](/articles/adding-a-bio-to-your-profile)
+- term: billing cycle
+  description: The interval of time for your specific billing plan.
+- term: billing email
   description: >-
-    領収書や、クレジットカードまたは PayPal の支払いなど、GitHub からの支払い関連の連絡の送信先となる Organization のメール アドレス。
-- term: 支払いマネージャー
-  description: Organization の支払い設定を管理する Organization メンバー。
-- term: お支払いプラン
+    The organization email address where GitHub sends receipts, credit card or
+    PayPal charges, and other billing-related communication.
+- term: billing manager
+  description: The organization member that manages billing settings for an organization.
+- term: billing plan
   description: >-
-    ユーザーと Organization 向けのお支払いプラン。プランの各タイプのセット機能が含まれています。
+    Payment plans for users and organizations that include set features for each
+    type of plan.
 - term: blame
   description: >-
-    Git の "blame" 機能は、ファイルの各行に対して最後に行われた変更を説明するものであり、通常は、リビジョン、作成者、時刻が表示されます。これは、機能が追加された日時や、特定のバグを引き起こしたコミットを追跡する場合などに役立ちます。
+    The "blame" feature in Git describes the last modification to each line of a
+    file, which generally displays the revision, author and time. This is
+    helpful, for example, in tracking down when a feature was added, or which
+    commit led to a particular bug.
 - term: block
   description: >-
-    ユーザーが Organization のリポジトリでコラボレーションできないようにすること。
-- term: 分岐
+    To remove a user's ability to collaborate on an organization's repositories.
+- term: branch
   description: >-
-    ブランチとは、リポジトリのパラレル バージョンです。これは、リポジトリに含まれていますが、プライマリ ブランチや main ブランチに影響を与えることはなく、"ライブ" バージョンに混乱をもたらさずに自由に作業できるものです。必要な変更を行ったら、ブランチを main ブランチにマージし直して、変更を公開できます。
-- term: ブランチ制限
+    A branch is a parallel version of a repository. It is contained within the
+    repository, but does not affect the primary or main branch allowing you to
+    work freely without disrupting the "live" version. When you've made the
+    changes you want to make, you can merge your branch back into the main
+    branch to publish your changes.
+- term: branch restriction
   description: >-
-    特定のユーザーまたはチームのみが、プッシュしたり、ブランチに対して変更を行ったりすることができるように、リポジトリ管理者が有効化できる制限。
-- term: Business プラン
+    A restriction that repository admins can enable so that only certain users
+    or teams can push or make certain changes to the branch.
+- term: Business plan
   description: >-
-    Organization の支払いプラン。無制限のパブリック リポジトリやプライベート リポジトリでコラボレーションしたり、SAML SSO を使った GitHub に対する認証を Organization メンバーに許可または要求したり、SAML または SCIM を使ってアクセスをプロビジョニングまたはプロビジョニング解除したりすることができます。
-- term: CA 証明書
+    An organization billing plan where you can collaborate on unlimited public
+    and private repositories, allow or require organization members to
+    authenticate to GitHub using SAML SSO, and provision and deprovision access
+    with SAML or SCIM.
+- term: CA certificate
   description: >-
-    証明機関 (CA) から発行されるデジタル証明書。これによって、2 つのマシン (ユーザーのコンピューターと GitHub.com など) の間で有効な接続が確保され、サイトの所有権が検証されます。
-- term: カード
-  description: Issue または pull request に関連付けられたプロジェクト ボード内にある移動可能な正方形。
-- term: チェック
+    A digital certificate issued by Certificate Authority (CA) that ensures there are valid connections between two machines, such as a user's computer and GitHub.com and verifies the ownership of a site.
+- term: card
+  description: A movable square within a project board associated with an issue or pull request.
+- term: check
   description: >-
-    チェックは、{% data variables.product.product_name %} でのステータス チェックのタイプの 1 つです。「[ステータス チェック](#status-checks)」を参照してください。
-- term: チェックアウト
+    A check is a type of status check on {% data variables.product.product_name %}. See "[Status checks](#status-checks)."
+- term: checkout
   description: >-
-    "git checkout" は、コマンド ラインで使うと、新しいブランチを作成できます。また、"git checkout" によって、作業中のブランチを、別のブランチに変更するだけではなく、"git checkout [branchname] [path to file]" を指定した別のブランチの別のバージョンのファイルに切り替えることもできます。"checkout" アクションを使うと、オブジェクト データベースのツリー オブジェクトや BLOB でワーキング ツリー全体または一部を更新できます。また、ワーキングツリー全体が新しいブランチをポイントしている場合は、インデックスと HEAD を更新できます。
-- term: チェリーピック
+    You can use `git checkout` on the command line to create a new branch, change your current working branch to a different branch, or even to switch to a different version of a file from a different branch with `git checkout [branchname] [path to file]`. The "checkout" action updates all or part of the working tree with a tree object or
+    blob from the object database, and updates the index and HEAD if the whole
+    working tree is pointing to a new branch.
+- term: cherry-picking
   description: >-
-    変更のサブセットを一連の変更 (通常はコミット) から選び、新しい一連の変更を別の codebase 上に記録すること。Git では、別のブランチの既存のコミットによって導入された変更を抽出したり、それを現在のブランチのヒントに基づいて新しいコミットとして記録したりするために、"git cherry-pick" コマンドを使ってこれを実行します。詳しくは、Git ドキュメントで [git-cherry-pick](https://git-scm.com/docs/git-cherry-pick) に関するページを参照してください。
-- term: 子チーム
+    To choose a subset of changes from a series of changes (typically commits) and record them as a new series of changes on top of a different codebase. In Git, this is performed by the `git cherry-pick` command to extract the change introduced by an existing commit on another branch and to record it based on the tip of the current branch as a new commit. For more information, see [git-cherry-pick](https://git-scm.com/docs/git-cherry-pick) in the Git documentation.
+- term: child team
   description: >-
-    入れ子チーム内で、親チームのアクセス権限と @メンションを継承するサブチーム。
-- term: クリーン
+    Within nested teams, the subteam that inherits the parent team's access
+    permissions and @mentions.
+- term: clean
   description: >-
-    ワーキング ツリーが現在の HEAD によって参照されているリビジョンに対応している場合、そのワーキング ツリーはクリーンです。「ダーティ」も参照してください。
-- term: 複製
+    A working tree is clean if it corresponds to the revision referenced by the
+    current HEAD. Also see "dirty".
+- term: clone
   description: >-
-    クローンとは、Web サイトのサーバー上ではなく、ユーザーのコンピューターに存在するリポジトリのコピーのことです。または、そのコピーを作成する操作を指します。クローンを作成すると、好きなエディターでファイルを編集したり、オンラインでなくても、Git を使って変更を記録したりすることができます。クローンしたリポジトリは、リモート バージョンには接続されたままなので、オンラインになったときに、ローカルで行った変更をリモート バージョンにプッシュすれば同期させることができます。
-- term: クラスターリング
+    A clone is a copy of a repository that lives on your computer instead of on
+    a website's server somewhere, or the act of making that copy. When you make a
+    clone, you can edit the files in your preferred editor and use Git to keep
+    track of your changes without having to be online. The repository you cloned
+    is still connected to the remote version so that you can push your local
+    changes to the remote to keep them synced when you're online.
+- term: clustering
   description: >-
-    複数のノードにわたって、またこれらのノード間の負荷分散リクエストにわたって、GitHub Enterprise サービスを実行する機能。
-- term: コードの更新頻度のグラフ
+    The ability to run GitHub Enterprise services across multiple nodes and load
+    balance requests between them.
+- term: code frequency graph
   description: >-
-    各週のコンテンツの追加と削除の回数をリポジトリの履歴に示すリポジトリ グラフ。
-- term: 行動規範
-  description: コミュニティへの参加方法の基準を定義したドキュメント。
-- term: コード オーナー
+    A repository graph that shows the content additions and deletions for each
+    week in a repository's history.
+- term: code of conduct
+  description: A document that defines standards for how to engage in a community.
+- term: code owner
   description: >-
-    リポジトリのコードがある部分のオーナーに指名されたユーザー。コード オーナーが所有するコードを変更する pull request を他のユーザーが開くと、コード オーナーに対してレビューが自動的にリクエストされます。
-- term: コラボレーター
+    A person who is designated as an owner of a portion of a repository's code. The code owner is automatically requested for review when someone opens a pull request (not in draft mode) that makes changes to code the code owner owns.
+- term: collaborator
   description: >-
-    コラボレーターとは、リポジトリへの読み取りアクセスと書き込みアクセスを持ち、コントリビューションするようにリポジトリ オーナーが招待したユーザーのことです。
-- term: コミット (commit)
+    A collaborator is a person with read and write access to a repository who
+    has been invited to contribute by the repository owner.
+- term: commit
   description: >-
-    コミットは、ファイル (またはファイルのセット) に対する個別の変更のことであり、"リビジョン" とも呼ばれます。コミットして作業内容を保存すると、Git によって一意の ID ("SHA" や "ハッシュ" とも呼ばれます) が作成されます。この ID で、コミットした特定の変更や、作成したユーザーや日時の記録を保持することができます。通常、コミットには、変更の内容について簡潔に記述されたコミット メッセージが含まれています。
-- term: コミット作者
-  description: コミットを行うユーザー。
-- term: コミット グラフ
+    A commit, or "revision", is an individual change to a file (or set of
+    files). When you make a commit to save your work, Git creates a unique ID (a.k.a. the "SHA" or "hash") that allows you to keep record of the specific changes committed along with who made them and when. Commits usually contain a
+    commit message which is a brief description of what changes were made.
+- term: commit author
+  description: The user who makes the commit.
+- term: Commit graph
   description: >-
-    1 つのリポジトリに対して過去 1 年間で行われたすべてのコミットを示すリポジトリ グラフ。
-- term: コミット ID
-  description: SHA とも呼ばれます。コミットを識別する 40 文字のチェックサム ハッシュ。
-- term: コミット メッセージ
+    A repository graph that shows all the commits made to a repository in the
+    past year.
+- term: commit ID
+  description: Also known as SHA. A 40-character checksum hash that identifies the commit.
+- term: commit message
   description: >-
-    コミットに付ける短い説明テキスト。コミットによって行われる変更について伝えます。
-- term: 比較ブランチ
+    Short, descriptive text that accompanies a commit and communicates the change
+    the commit is introducing.
+- term: compare branch
   description: >-
-    pull request の作成に使うブランチ。このブランチは、pull request で選んだベース ブランチと比較されて、変更内容が特定されます。pull request がマージされると、このベース ブランチは、比較ブランチからの変更を使って更新されます。pull request の "ヘッド ブランチ" とも呼ばれます。
-- term: 継続的インテグレーション
+    The branch you use to create a pull request.
+    This branch is compared to the base branch you choose for the pull request, and the changes are identified.
+    When the pull request is merged, the base branch is updated with the changes from the compare branch.
+    Also known as the "head branch" of the pull request.
+- term: continuous integration
   description: >-
-    CI とも呼ばれます。GitHub 上に構成されたリポジトリに対してユーザーが変更をコミットすると、自動化されたビルドとテストを実行するプロセス。CI は、ソフトウェア開発の一般的なベスト プラクティスであり、エラーの検出に役立ちます。
-- term: コントリビューション グラフ
+    Also known as CI. A process that runs automated builds and tests once a person commits a change to a configured repository on GitHub. CI is a common best practice in software development that helps detect errors.
+- term: contribution graph
   description: >-
-    ユーザーのプロファイルの一部であり、過去最大 1 年間の 1 日ごとのコントリビューションを示します。
-- term: コントリビューション ガイドライン
-  description: ユーザーがプロジェクトにコントリビューションする方法を説明したドキュメント。
-- term: コントリビューション
+    The part of a user's profile that shows their contributions over a period of
+    up to one year, day by day.
+- term: contribution guidelines
+  description: A document explaining how people should contribute to your project.
+- term: contributions
   description: >-
-    ユーザーのコントリビューション グラフに正方形を追加 (「[コントリビューションとして何がカウントされるか](/articles/viewing-contributions-on-your-profile/#what-counts-as-a-contribution)」) したり、ユーザーのプロファイルでユーザーのタイムラインにアクティビティを追加 (「[コントリビューション アクティビティ](/articles/viewing-contributions-on-your-profile/#contribution-activity)」) したりする、GitHub での特定のアクティビティ。
-- term: 共同作成者
+    Specific activities on GitHub that will:
+    - Add a square to a user's contribution graph: "[What counts as a contribution](/articles/viewing-contributions-on-your-profile/#what-counts-as-a-contribution)"
+    - Add activities to a user's timeline on their profile: "[Contribution activity](/articles/viewing-contributions-on-your-profile/#contribution-activity)"
+- term: contributor
   description: >-
-    共同作成者とは、リポジトリへのコラボレーター アクセスはないものの、プロジェクトに対してコントリビューションを行い、オープンした pull request をリポジトリにマージさせたユーザーのことです。
-- term: 共同作成者グラフ
-  description: リポジトリの共同作成者上位 100 人を表示するリポジトリ グラフ。
-- term: クーポン
+    A contributor is someone who does not have collaborator access to a repository but has contributed to a project and had a pull request they opened merged into the repository.
+- term: contributors graph
+  description: A repository graph that displays the top 100 contributors to a repository.
+- term: coupon
   description: >-
-    ユーザーや Organization がサブスクリプション全体または一部の支払いに使うことができる、GitHub が指定したコード。
+    A GitHub-provided code that users or organizations can use to pay for all or
+    part of their subscription.
 - term: cron
-  description: Unix のようなコンピューター オペレーティング システムでの、時間ベースのジョブ スケジューラ。
+  description: A time-based job scheduler in Unix-like computer operating systems.
 - term: cURL
-  description: データを転送するためにコマンド ラインまたはスクリプトで使用されます。
+  description: Used in command lines or scripts to transfer data.
 - term: dashboard
   description: >-
-    パーソナル ダッシュボードは、GitHub でのアクティビティのメイン ハブです。パーソナル ダッシュボードでは、フォロー中または作業中の issue や pull request を記録したり、トップ リポジトリやチームのページにアクセスしたり、watch 中または参加中のリポジトリの最近のアクティビティについて把握したりすることができます。また、フォロー中のユーザーや、Star を付けたリポジトリに基づいた、お勧めの新しいリポジトリを見つけることもできます。特定の Organization でのアクティビティのみを表示するには、Organization のダッシュボードにアクセスしてください。詳しくは、「[パーソナル ダッシュボードについて](/articles/about-your-personal-dashboard)」または「[Organization ダッシュボードについて](/articles/about-your-organization-dashboard)」を参照してください。
-- term: 既定のブランチ
+    Your personal dashboard is the main hub of your activity on GitHub. From your personal dashboard, you can keep track of issues and pull requests you're following or working on, navigate to your top repositories and team pages, and learn about recent activity in repositories you're watching or participating in. You can also discover new repositories, which are recommended based on users you're following and repositories you have starred. To only view activity for a specific organization, visit your organization's dashboard. For more information, see "[About your personal dashboard](/articles/about-your-personal-dashboard)" or "[About your organization dashboard](/articles/about-your-organization-dashboard)."
+- term: default branch
   description: >-
-    リポジトリ内の新しい pull request とコードのコミットのためのベース ブランチです。それぞれのリポジトリには、ブランチが 1 つ以上ありますが、これは、リポジトリを初期化すると Git によって作成されるものです。通常、最初のブランチは {% ifversion ghes < 3.2 %}"master"{% else %}"main"{% endif %} という名前のものですが、たいていは既定のブランチです。
-- term: 依存グラフ
+    The base branch for new pull requests and code commits in a repository. Each repository has at least one branch, which Git creates when you initialize the repository. The first branch is usually called {% ifversion ghes < 3.2 %}`master`{% else %}`main`{% endif %}, and is often the default branch.
+- term: dependents graph
   description: >-
-    パブリック リポジトリに依存するパッケージ、プロジェクト、リポジトリを示すリポジトリ グラフ。
-- term: 依存関係グラフ
+    A repository graph that shows the packages, projects, and repositories that depend on a
+    public repository.
+- term: dependency graph
   description: >-
-    リポジトリが依存するパッケージとプロジェクトを示すリポジトリ グラフ。
-- term: デプロイ キー
+    A repository graph that shows the packages and projects that the repository depends on.
+- term: deploy key
   description: >-
-    デプロイ キーは、サーバー上に格納されている SSH キーのことで、単一の GitHub リポジトリへのアクセス権の付与に使います。このキーは、個人用ユーザー アカウントにアタッチされるのではなく、リポジトリに直接アタッチされます。
-- term: デタッチされた HEAD
+    A deploy key is an SSH key that is stored on your server and grants access
+    to a single GitHub repository. This key is attached directly to the
+    repository instead of to a personal user account.
+- term: detached HEAD
   description: >-
-    Git では、デタッチされた HEAD で作業しようとすると、Git によってブランチがポイントされていないという警告や、ユーザーが行ったコミットがコミット履歴に表示されないという警告が表示されます。 たとえば、チェックアウトした任意のコミットが、特定のブランチの最新のコミットではない場合、"デタッチされた HEAD" で作業をしていることになります。
-- term: 診断
-  description: GitHub Enterprise インスタンスの設定と環境の概要。
+    Git will warn you if you're working on a detached HEAD, which means that Git
+    is not pointing to a branch and that any commits you make will not appear in
+    commit history.  For example, when you check out an arbitrary commit that
+    is not the latest commit of any particular branch, you're working on a
+    "detached HEAD."
+- term: diagnostics
+  description: An overview of a GitHub Enterprise instance's settings and environment.
 - term: diff
   description: >-
-    diff とは、2 つのコミットまたは保存された変更間の差異のことです。diff では、最後のコミット以降にファイルに追加されたかファイルから削除されたものを視覚的に説明します。
+    A diff is the difference in changes between two commits, or saved changes.
+    The diff will visually describe what was added or removed from a file since
+    its last commit.
 - term: directory
   description: >-
-    1 つ以上のファイルまたはフォルダーを含むフォルダー。ディレクトリを作成すると、リポジトリの内容を整理できます。
-- term: ダーティ
+    A folder containing one or more files or folders. You can create directories to organize the contents of a repository.
+- term: dirty
   description: >-
-    ワーキング ツリーは、現在のブランチにコミットされていない修正が含まれている場合は、"ダーティ" と見なされます。
-- term: 電子メール通知
-  description: ユーザーのメール アドレスに送信される通知。
-- term: Enterprise アカウント
-  description: "Enterprise アカウントでは、複数の Organization のポリシーと支払いを一元管理できます。{% data reusables.gated-features.enterprise-accounts %}"
-- term: エクスプローラー
+    A working tree is considered "dirty" if it contains modifications that have
+    not been committed to the current branch.
+- term: email notifications
+  description: Notifications sent to a user's email address.
+- term: enterprise account
+  description: Enterprise accounts allow you to centrally manage policy and billing for multiple organizations. {% data reusables.gated-features.enterprise-accounts %}
+- term: Explorer
   description: >-
-    GraphiQL のインスタンスであり、"グラフィカルな対話型ブラウザー内 GraphQL IDE" です。
+    An instance of GraphiQL, which is a "graphical interactive in-browser GraphQL
+    IDE."
 - term: fast-forward
   description: >-
-    fast-forward とは、リビジョンがあり、かつ別のブランチでの変更を "マージしている" が、その変更が偶然にもそのリビジョンの子孫である場合の、特別なタイプのマージのことです。そのような場合は、新しいマージ コミットを行いませんが、代わりに、このリビジョンに対して更新を行います。これは、リモート リポジトリのリモート追跡ブランチで頻繁に起こります。
-- term: 機能ブランチ
+    A fast-forward is a special type of merge where you have a revision and you
+    are "merging" another branch's changes that happen to be a descendant of
+    what you have. In such a case, you do not make a new merge commit but
+    instead just update to this revision. This will happen frequently on a
+    remote-tracking branch of a remote repository.
+- term: feature branch
   description: >-
-    新しい機能の実験や、本番には存在しない issue の修正に使うブランチ。トピック ブランチとも呼ばれます。
-- term: フェンスされたコード ブロック
-  description: "コード ブロックの前後に 3 つのバックティック (\\ \\ \\) を使って、GitHub Flavored Markdown で作成できるコードのインデント付きブロック。こちらの[例](/articles/creating-and-highlighting-code-blocks#fenced-code-blocks)を参照してください。"
+    A branch used to experiment with a new feature or fix an issue that is not in production. Also called a topic branch.
+- term: fenced code block
+  description: An indented block of code you can create with GitHub Flavored Markdown using triple backticks \`\`\` before and after the code block. See this [example](/articles/creating-and-highlighting-code-blocks#fenced-code-blocks).
 - term: fetch
   description: >-
-    "git fetch" は、変更をコミットせずに、リモート リポジトリからローカルで作業中のブランチに追加する場合に使います。"git pull" とは異なり、変更を、ローカル ブランチにコミットする前にレビューできます。
-- term: フォロー (ユーザー)
-  description: 別のユーザーのコントリビューションとアクティビティについて通知を受けること。
-- term: フォース プッシュ
+    When you use `git fetch`, you're adding changes from the remote repository to
+    your local working branch without committing them. Unlike `git pull`, fetching
+    allows you to review changes before committing them to your local branch.
+- term: following (users)
+  description: To get notifications about another user's contributions and activity.
+- term: force push
   description: >-
-    競合を考慮することなく、リモート リポジトリをローカルな変更で上書きする Git プッシュ。
-- term: フォーク
+    A Git push that overwrites the remote repository with local changes without
+    regard for conflicts.
+- term: fork
   description: >-
-    フォークとは、自分のアカウントに存在する別のユーザーのリポジトリの個人用のコピーのことです。フォークすると、元の上流リポジトリに影響を与えることなく、プロジェクトに対して自由に変更を加えることができます。また、上流リポジトリで pull request を開いたり、両方のリポジトリが接続されたままなので、自分が行ったフォークを最新の変更に同期させ続けたりすることもできます。
-- term: Free プラン
+    A fork is a personal copy of another user's repository that lives on your
+    account. Forks allow you to freely make changes to a project without
+    affecting the original upstream repository. You can also open a pull request in
+    the upstream repository and keep your fork synced with the latest changes since
+    both repositories are still connected.
+- term: Free plan
   description: >-
-    無料のユーザー アカウントお支払いプラン。ユーザーは、無制限のパブリック リポジトリで、無制限のコラボレーターと共同作業できます。
+    A user account billing plan that is free. Users can collaborate on unlimited
+    public repositories with unlimited collaborators.
 - term: gist
   description: >-
-    gist とは、共有可能なファイルであり、GitHub 上で編集、クローン、フォークできます。gist を、{% ifversion ghae %}内部{% else %}パブリック{% endif %}またはシークレットの gist にすることができますが、シークレット gist は、URL を持つ{% ifversion ghae %}すべての Enterprise メンバー {% else %}すべてのユーザー{% endif %}が使用できます。
+    A gist is a shareable file that you can edit, clone, and fork on GitHub.
+    You can make a gist {% ifversion ghae %}internal{% else %}public{% endif %} or secret, although secret gists will be
+    available to {% ifversion ghae %}any enterprise member{% else %}anyone{% endif %} with the URL.
 - term: Git
   description: >-
-    Git は、テキスト ファイルの変更を追跡するためのオープン ソース プログラムです。Linux オペレーティング システムの作成者によって記述されたもので、ソーシャルなユーザー インターフェイスである GitHub は、その最上位に構築された中核となるテクノロジです。
+    Git is an open source program for tracking changes in text files. It was
+    written by the author of the Linux operating system, and is the core
+    technology that GitHub, the social and user interface, is built on top of.
 - term: GitHub App
   description: >-
-    GitHub App は、Organization 全体に対してサービスを提供します。また、機能の実行には、独自の ID が使用されます。Organization やユーザー アカウントに直接インストールすることができ、特定のリポジトリへのアクセス権も付与されます。細かな権限が付与されており、Webhook が組み込まれています。
+    GitHub Apps provide a service to an entire organization and use their own
+    identity when performing their function. They can be installed directly on
+    organizations and user accounts and granted access to specific repositories.
+    They come with granular permissions and built-in webhooks.
 - term: GitHub Flavored Markdown
-  description: "GitHub 全体で文章やコードを書式設定するために使用される、GitHub 固有の Markdown。「[GitHub Flavored Markdown の仕様](https://github.github.com/gfm/)」または「[GitHub での記述と書式設定の開始](/articles/getting-started-with-writing-and-formatting-on-github)」を参照してください。"
+  description: GitHub-specific Markdown used to format prose and code across GitHub. See [GitHub Flavored Markdown Spec](https://github.github.com/gfm/) or [Getting started with writing and formatting on GitHub](/articles/getting-started-with-writing-and-formatting-on-github).
 - term: GitHub Importer
   description: >-
-    コミットやリビジョン履歴などのソース コード リポジトリを、ユーザーに代わってすばやく GitHub にインポートするツール。
+    A tool that quickly imports source code repositories, including commits and
+    revision history, to GitHub for users.
 - term: GitHub Jobs
   description: >-
-    GitHub ユーザーが関心を持ちそうな仕事について雇用主が投稿できる GitHub サイト。
+    A GitHub site where employers can post jobs that GitHub users may be
+    interested in.
 - term: GitHub Marketplace
   description: >-
-    GitHub ユーザーや Organization 向けの、ワークフローを拡張して補完するアプリケーションを購入してインストールするためのサブサイト。
-- term: GitHub ページ
+    A subsite for GitHub users and organizations to purchase and install
+    applications that extend and complement their workflow.
+- term: GitHub Pages
   description: >-
-    Pages とも呼ばれます。個人、Organization、またはプロジェクトのページを GitHub リポジトリから直接ホストするように設計された、静的サイト ホスティング サービス。
+    Also referred to as Pages. A static site hosting service designed to host
+    your personal, organization, or project pages directly from a GitHub
+    repository.
 - term: GitHub Wiki
-  description: wiki スタイルのドキュメントを GitHub リポジトリ上でホストするためのセクション。
+  description: A section for hosting wiki style documentation on a GitHub repository.
 - term: gitfile
   description: >-
-    プレーンな ".git" ファイル。常に、ワーキング ツリーのルートに存在し、Git リポジトリ全体とそのメタ データが含まれる Git ディレクトリをポイントしています。このファイルは、リポジトリが実際のリポジトリであれば、コマンド ラインに "git rev-parse --git-dir" が含まれます。
+    A plain `.git` file, which is always at the root of a working tree and points to the Git directory, which has the entire Git repository and its meta data. You can view this file for your repository on the command line with `git rev-parse --git-dir`.
+    that is the real repository.
 - term: GraphQL
   description: >-
-    API のクエリ言語であり、既存のデータを使ってクエリを実行するためのランタイムです。
+    A query language for APIs and a runtime for fulfilling those queries with
+    your existing data.
 - term: HEAD
-  description: ブランチの定義済みコミット。通常は、ブランチの先頭にある最新のコミットです。
-- term: head ブランチ
-  description: "pull request をマージすると、このブランチの変更がベース ブランチに組み込まれます。\"比較ブランチ\" とも呼ばれます。"
+  description: A defined commit of a branch, usually the most recent commit at the tip of the branch.
+- term: head branch
+  description: The branch whose changes are combined into the base branch
+    when you merge a pull request.
+    Also known as the "compare branch."
 - term: 'Hello, World'
   description: >-
-    "Hello, World!" プログラムは、"Hello, World!" をユーザーに対して出力または表示するコンピューター プログラムです。このプログラムは通常、非常に単純なので、プログラミング言語の基本的な構文の例として使用されることが多く、一般的に、新しいプログラミング言語を学習するための最初の演習として使用されます。
+    A "Hello, World!" program is a computer program that outputs or displays
+    "Hello, World!" to a user. Since this program is usually very simple, it is
+    often used as an example of a programming language's basic syntax and
+    serves as a common first exercise for learning a new programming language.
 - term: high-availability
   description: >-
-    長時間継続して稼働させるのが望ましいシステムまたはコンポーネント。
-- term: フック
+    A system or component that is continuously operational for a desirably long
+    length of time.
+- term: hook
   description: >-
-    いくつかの GitHub コマンドでは、コマンドの正常な実行中に、オプションのスクリプトに対してコールアウトが行われるので、開発者は機能やチェックを追加することができます。一般的には、フックすると、コマンドが事前に検証されて終了してしまったり、操作の完了後に事後通知が表示されたりする可能性があります。
+    During the normal execution of several Git commands, call-outs are made to
+    optional scripts that allow a developer to add functionality or checking.
+    Typically, the hooks allow for a command to be pre-verified and potentially
+    aborted, and allow for a post-notification after the operation is done.
 - term: hostname
   description: >-
-    ネットワークに接続されているデバイスのアドレスに対応する、人間が判読可能なニックネーム。
-- term: アイデンティコン
+    Human-readable nicknames that correspond to the address of a device
+    connected to a network.
+- term: identicon
   description: >-
-    ユーザーが GitHub にサインアップするときに既定のプロフィール写真として使用される、自動生成された画像。ユーザーは、アイデンティコンを自分のプロフィール写真に置き換えることができます。
-- term: ID プロバイダー
+    An auto-generated image used as a default profile photo when users sign up for
+    GitHub. Users can replace their identicon with their own profile photo.
+- term: identity provider
   description: >-
-    IdP とも呼ばれます。他の Web サイトへのアクセスに SAML シングル サインオン (SSO) を使うことができる、信頼できるプロバイダー。
+    Also known as an IdP. A trusted provider that lets you use SAML single
+    sign-on (SSO) to access other websites.
 - term: instance
   description: >-
-    Organization の GitHub のプライベートコピー。Organization によって構成され、制御されている仮想マシン内に含まれています。
-- term: 統合
+    An organization's private copy of GitHub contained within a virtual machine
+    that they configure and control.
+- term: integration
   description: >-
-    GitHub と統合されるサードパーティ アプリケーション。これは、GitHub Apps、OAuth Apps、または Webhook である場合があります。
-- term: イシュー
+    A third-party application that integrates with GitHub. These can be GitHub
+    Apps, OAuth Apps, or webhooks.
+- term: issue
   description: >-
-    issue とは、リポジトリに関する改善の提案、タスク、または質問のことです。issue は、あらゆるユーザーが作成することができ (パブリック リポジトリの場合)、リポジトリのコラボレーターによってモデレートされます。各 issue には、独自のディスカッション スレッドが含まれています。また、ラベルを付けて分類したり、他のユーザーに割り当てたりすることもできます。
+    Issues are suggested improvements, tasks or questions related to the
+    repository. Issues can be created by anyone (for public repositories), and
+    are moderated by repository collaborators. Each issue contains its own discussion thread. You can also categorize an issue with labels and assign it to someone.
 - term: Jekyll
-  description: 個人、プロジェクト、または Organization のサイト用の静的サイトジェネレータ。
-- term: Jekyll テーマ選択画面
+  description: A static site generator for personal, project, or organization sites.
+- term: Jekyll Theme Chooser
   description: >-
-    Jekyll サイトで、CSS ファイルを編集したりコピーしたりせずに、ビジュアル テーマを選ぶ自動化された方法。
-- term: キー フィンガープリント
-  description: 長い公開キーを識別するのに使用される、短いバイトのシーケンス。
-- term: キーチェーン
-  description: macOS のパスワード管理システム。
-- term: キーワード (keyword)
-  description: pull request 内で使用される場合、issue をクローズする特定の単語。
+    An automated way to select a visual theme for your Jekyll site without editing or
+    copying CSS files.
+- term: key fingerprint
+  description: A short sequence of bytes used to identify a longer public key.
+- term: keychain
+  description: A password management system in macOS.
+- term: keyword
+  description: A specific word that closes an issue when used within a pull request.
 - term: label
   description: >-
-    issue または pull request に付けるタグ。リポジトリには、既定のラベルがいくつかありますが、ユーザーはカスタム ラベルを作成することができます。
+    A tag on an issue or pull request. Repositories come with a handful of
+    default labels, but users can create custom labels.
 - term: LFS
   description: >-
-    Git Large File Storage。大きいファイルをバージョン管理するためのオープンソース Git 拡張機能。
+    Git Large File Storage. An open source Git extension for versioning large
+    files.
 - term: license
   description: >-
-    ソース コードを使ってできることとできないことをユーザーに知らせるためにプロジェクトに含めることができるドキュメント。
+    A document that you can include with your project to let people know what
+    they can and can't do with your source code.
 - term: Linguist
   description: >-
-    GitHub で使用されるライブラリ。BLOB 言語を検出し、バイナリ ファイルやベンダーされたファイルを無視し、diff で生成されたファイルを非表示にし、言語別グラフを生成します。
-- term: 行コメント
-  description: 特定のコード行についての、pull request 内にあるコメント。
-- term: 行終端
+    A library used on GitHub to detect blob languages, ignore binary or vendored
+    files, suppress generated files in diffs, and generate language breakdown
+    graphs.
+- term: line comment
+  description: A comment within a pull request on a specific line of code.
+- term: line ending
   description: >-
-    テキスト ファイルの行末をシンボル化する、1 つ以上の非表示の文字。
-- term: ロックされた個人用アカウント
+    An invisible character or characters that symbolize the end of a line in a
+    text file.
+- term: locked personal account
   description: >-
-    ユーザーがアクセスできない個人用アカウント。ユーザーが有料アカウントから無料アカウントに変更したり、有料プランの支払い期限を過ぎたりすると、アカウントはロックされます。
-- term: 管理コンソール
+    A personal account that cannot be accessed by the user. Accounts are locked
+    when users downgrade their paid account to a free one, or if their paid plan
+    is past due.
+- term: management console
   description: >-
-    GitHub Enterprise インターフェイス内にある、管理機能を含むセクション。
+    A section within the GitHub Enterprise interface that contains
+    administrative features.
 - term: Markdown
   description: >-
-    Markdown は、非常に簡潔なセマンティック ファイル形式で、.doc、.rtf、.txt にやや近いものです。Markdown は、文章 (リンク、一覧、箇条書きなどを含む) を書いて Web サイトのように表示させるというような Web 発行の経験がないユーザーにとっても取り扱いやすいものです。GitHub では、Markdown をサポートするとともに、GitHub Flavored Markdown という名前の特別な形式の Markdown を使っています。「[GitHub Flavored Markdown の仕様](https://github.github.com/gfm/)」または「[GitHub での記述と書式設定の開始](/articles/getting-started-with-writing-and-formatting-on-github)」を参照してください。
-- term: マークアップ
-  description: ドキュメントの注釈と書式設定を行うためのシステム。
-- term: メイン
+    Markdown is an incredibly simple semantic file format, not too dissimilar
+    from .doc, .rtf and .txt. Markdown makes it easy for even those without a
+    web-publishing background to write prose (including with links, lists,
+    bullets, etc.) and have it displayed like a website. GitHub supports
+    Markdown and uses a particular form of Markdown called GitHub Flavored Markdown. See [GitHub Flavored Markdown Spec](https://github.github.com/gfm/) or [Getting started with writing and formatting on GitHub](/articles/getting-started-with-writing-and-formatting-on-github).
+- term: markup
+  description: A system for annotating and formatting a document.
+- term: main
   description: >-
-    {% ifversion fpt or ghes > 3.1 or ghae %} 既定の開発ブランチ。Git リポジトリを作成するたびに、"main" という名前のブランチが作成され、アクティブなブランチになります。ほとんどの場合、これにはローカル開発が含まれますが、あくまでも規則によるものであり、必須ではありません。{% else %}リポジトリの既定のブランチには、"master" という名前が代わりに選択されることもよくあります。{% endif %}
+    The default development branch. Whenever you create a Git repository,
+    a branch named `main` is created, and becomes the active branch.
+    In most cases, this contains the local development, though that is purely by
+    convention and is not required.
 - term: master
   description: >-
-    多くの Git リポジトリの既定のブランチ。既定では、コマンド ラインで新しい Git リポジトリを作成すると、"master" という名前のブランチが作成されます。多くのツールでは、既定のブランチに別の名前を使うようになってきています。{% ifversion fpt or ghes > 3.1 or ghae %} たとえば、GitHub で新しいリポジトリを作成する場合、既定のブランチは "main" という名前です。{% endif %}
-- term: メンバー グラフ
-  description: リポジトリのすべてのフォークを示すリポジトリ グラフ。
-- term: メンション
+    The default branch in many Git repositories. By default, when you create
+    a new Git repository on the command line, a branch called `master` is created.
+    Many tools now use an alternative name for the default branch. For example,
+    when you create a new repository on GitHub, the default branch is called `main`.
+- term: members graph
+  description: A repository graph that shows all the forks of a repository.
+- term: mention
   description: >-
-    ユーザー名の前に @ 記号を付けることで、そのユーザーに送信される通知。GitHub の Organization のユーザーも、メンションされるチームの一員にすることができます。
+    A notification sent to a user by prefacing their username with the @ symbol.
+    Users in an organization on GitHub can also be a part of a team that can be
+    mentioned.
 - term: merge
   description: >-
-    マージとは、1 つのブランチから (同じリポジトリ内で、またはフォークから) 変更を取得し、その変更を別のブランチに適用することです。これは、多くの場合、"pull request" (マージのリクエストと考えてもよいでしょう) として、またはコマンド ライン経由で行われます。マージは、競合する変更がない場合や、常にコマンド ライン経由で行われる場合は、GitHub.com Web インターフェイス経由で pull request を介して行われます。
-- term: マージの競合
+    Merging takes the changes from one branch (in the same repository or from a
+    fork), and applies them into another. This often happens as a "pull request"
+    (which can be thought of as a request to merge), or via the command line. A
+    merge can be done through a pull request via the GitHub.com web
+    interface if there are no conflicting changes, or can always be done via the
+    command line.
+- term: merge conflict
   description: >-
-    マージされたブランチ間で発生する差異。マージの競合は、複数のユーザーが同じファイルの同じ行に異なる変更を加えた場合や、1 人のユーザーがファイルを編集し、別のユーザーがその同じファイルを削除した場合に発生します。ブランチをマージするには、マージの競合を解決しておく必要があります。
-- term: マイルストーン
+    A difference that occurs between merged branches. Merge conflicts happen
+    when people make different changes to the same line of the same file, or
+    when one person edits a file and another person deletes the same file. The
+    merge conflict must be resolved before you can merge the branches.
+- term: milestone
   description: >-
-    リポジトリ内にある issue や pull request のグループの進行状況を追跡する方法。
-- term: ミラー
-  description: リポジトリの新しいコピー。
-- term: 入れ子チーム
+    A way to track the progress on groups of issues or pull requests in a
+    repository.
+- term: mirror
+  description: A new copy of a repository.
+- term: nested team
   description: >-
-    親チームの子チーム。ユーザーは、複数の子チーム (または入れ子チーム) を持つことができます。
-- term: ネットワーク グラフ
+    A child team of a parent team. You can have multiple children (or nested)
+    teams.
+- term: network graph
   description: >-
-    ルート リポジトリのブランチや、ネットワーク固有のコミットを含むフォークのブランチなど、リポジトリ ネットワーク全体のブランチ履歴を示すリポジトリグラフ。
-- term: ニュース フィード
+    A repository graph that shows the branch history of the entire repository
+    network, including branches of the root repository and branches of forks
+    that contain commits unique to the network.
+- term: news feed
   description: >-
-    Watch しているリポジトリまたはユーザーのアクティビティ ビュー。Organization のニュース フィードには、Organization が所有するリポジトリでのアクティビティが表示されます。
+    An activity view of repositories or people you watch. An organization's News
+    Feed shows activity on repositories owned by the organization.
 - term: non-fast-forward
   description: >-
-    リポジトリのローカル コピーが上流リポジトリと同期されておらず、ローカルの変更をプッシュするには、上流の変更をフェッチする必要がある場合。
-- term: 通知 (notification)
+    When your local copy of a repository is out-of-sync with the upstream
+    repository and you need to fetch the upstream changes before you push your
+    local changes.
+- term: notification
   description: >-
-    関心のあるアクティビティについての情報を提供するアップデート。設定に応じて、Web またはメールで届きます。
+    Updates, delivered by either the web or email depending on your settings,
+    that give you information about the activities you're interested in.
 - term: OAuth App
   description: >-
-    ユーザーに関する情報にアクセスするために、パスワードではなくアクセス トークンが使用されるサードパーティ アプリケーション。
-- term: OAuth トークン
-  description: ユーザーに関する情報にアクセスするために OAuth Apps で使用されるアクセス トークン。
-- term: 外部コラボレーター
+    A third-party application that uses access tokens rather than passwords to
+    access information for users.
+- term: OAuth token
+  description: The access token used in OAuth Apps to access information for users.
+- term: outside collaborator
   description: >-
-    Organization の 1 つ以上のリポジトリへのアクセス権が付与されているが、その Organization への他のアクセス権は付与されておらず、その Organization のメンバーではないユーザー。
-- term: オープン ソース
+    A user who has been given access to one or more of an organization’s
+    repositories, but has no other access to the organization and is not a
+    member of the organization.
+- term: open source
   description: >-
-    オープン ソース ソフトウェアとは、あらゆるユーザーが自由に使い、変更し、共有できるソフトウェアのことです (形式の変更の有無は問いません)。今日の "オープン ソース" の概念は、ソフトウェアの枠を超えて語られることが多く、あらゆるユーザーがオンラインで素材をフォーク、変更、ディスカッション、コントリビューションを行うことができるという意味でのコラボレーションという考え方を表しています。
+    Open source software is software that can be freely used, modified, and
+    shared (in both modified and unmodified form) by anyone. Today the concept
+    of "open source" is often extended beyond software, to represent a
+    philosophy of collaboration in which working materials are made available
+    online for anyone to fork, modify, discuss, and contribute to.
 - term: organization
   description: >-
-    Organization とは、通常、実際の組織を反映する、2 人以上のユーザーのグループのことです。Organization の管理はユーザーが行い、リポジトリとチームの両方を含めることができます。
-- term: Organization オーナー
-  description: 所有する Organization の管理機能へのフル アクセスを持つユーザー。
+    Organizations are a group of two or more users that typically mirror
+    real-world organizations. They are administered by users and can contain
+    both repositories and teams.
+- term: organization owner
+  description: Users who have full administrative access to the organization they own.
 - term: origin
   description: >-
-    既定の上流リポジトリ。ほとんどのプロジェクトには、追跡対象となっている 1 つ以上の上流プロジェクトがあります。既定では、origin がその目的で使用されます。
+    The default upstream repository. Most projects have at least one upstream
+    project that they track. By default, origin is used for that purpose.
 - term: owner
   description: >-
-    Organization のすべての管理機能へのアクセスを持つ Organization メンバー。
-- term: 親チーム
+    Organization members that have complete administrative access to the
+    organization.
+- term: parent team
   description: >-
-    入れ子チーム内で、子チームによるアクセス権限と @メンションの継承元となっているメイン チーム。
-- term: 参加通知
+    Within nested teams, the main team from which child teams inherit access
+    permissions and @mentions.
+- term: participating notifications
   description: >-
-    自分のユーザー名またはチームがメンションされていた、または以前コメント内で返信していた issue や pull request 内の会話のアップデートについての通知。
-- term: パーマリンク
-  description: 特定の Web ページへの永続的な静的ハイパーリンク。
-- term: 個人用アカウント
+    A notification about an update in a conversation in an issue or pull request
+    where your username or team was mentioned or where you have previously replied
+    in a comment.
+- term: permalink
+  description: A permanent static hyperlink to a particular web page.
+- term: personal account
   description: >-
-    個々のユーザーに属している GitHub アカウント。
-- term: プライマリ メール アドレス
+    A GitHub account that belongs to an individual user.
+- term: primary email address
   description: >-
-    領収書や、クレジットカードまたは PayPal の支払いなど、GitHub からの支払い関連の連絡の送信先となる主要なメール アドレス。
-- term: 固定リポジトリ
+    The main email address where GitHub sends receipts, credit card or PayPal
+    charges, and other billing-related communication.
+- term: pinned repository
   description: >-
-    ユーザーがアピールのために自分のプロフィールに表示することにしたリポジトリ。
-- term: pre-receive フック
+    A repository that a user has decided to display prominently on their
+    profile.
+- term: pre-receive hooks
   description: >-
-    GitHub Enterprise サーバー上で実行されるスクリプトで、品質チェックの実装に使うことができます。
-- term: プライベート コントリビューション
-  description: プライベート リポジトリ (パブリック リポジトリではなく) に対して行われるコントリビューション。
-- term: プライベートリポジトリ
+    Scripts that run on the GitHub Enterprise server that you can use to
+    implement quality checks.
+- term: private contributions
+  description: Contributions made to a private (vs. public) repository.
+- term: private repository
   description: >-
-    プライベート リポジトリは、オーナーが指定したリポジトリ オーナーとコラボレーターにのみ表示されます。
-- term: 本番ブランチ
+    Private repositories are only visible to the repository owner and
+    collaborators that the owner specified.
+- term: production branch
   description: >-
-    すぐに使用できる状態になっており、アプリケーションやサイトへのデプロイの準備が完了している、最終変更を含むブランチ。
+    A branch with final changes that are ready to be used or deployed to an application or site.
 - term: profile
-  description: GitHub 上でのユーザーのアクティビティに関する情報を示すページ。
-- term: プロフィール写真
+  description: The page that shows information about a user's activity on GitHub.
+- term: profile photo
   description: >-
-    ユーザーが、自分のアクティビティを特定できるように GitHub にアップロードするカスタム画像。通常は、ユーザー名も記載されます。これは、アバターとも呼ばれます。
-- term: プロジェクト ボード
+    A custom image users upload to GitHub to identify their activity, usually
+    along with their username. This is also referred to as an avatar.
+- term: project board
   description: >-
-    issue、pull request、メモから成る GitHub 内のボード。列内では、カードとして分類されます。
-- term: 保護されたブランチ
+    Boards within GitHub that are made up of issues, pull requests, and notes
+    that are categorized as cards in columns.
+- term: protected branch
   description: >-
-    保護されたブランチを使うと、リポジトリ管理者が保護対象として選んだブランチ上で、Git のいくつかの機能がブロックされます。このブランチに対して強制プッシュや削除はできません。また、必要なチェックに合格していない状態や必要なレビューが承認されていない状態で変更をマージしたり、GitHub Web インターフェイスからファイルをアップロードしたりすることはできません。保護されたブランチは通常、既定のブランチです。
-- term: パブリック コントリビューション
-  description: パブリック リポジトリ (プライベート リポジトリではなく) に対して行われるコントリビューション。
-- term: パブリック リポジトリ
+    Protected branches block several features of Git on a branch that a
+    repository administrator chooses to protect. They can't be force pushed,
+    deleted, have changes merged without required checks passing or required
+    reviews approved, or have files uploaded to it from the GitHub web
+    interface. A protected branch is usually the default branch.
+- term: public contributions
+  description: Contributions made to a public (vs. private) repository.
+- term: public repository
   description: >-
-    パブリック リポジトリは、GitHub ユーザーではないユーザーも含め、すべてのユーザーが見ることができます。
-- term: プル (pull)
+    A public repository can be viewed by anyone, including people who aren't
+    GitHub users.
+- term: pull
   description: >-
-    プルとは、変更をフェッチしてマージすることを指します。たとえば、自分が作業しているファイルを他のユーザーが編集した場合に、その変更を自分のローカル コピーにプルして、最新の状態になるようにすることです。「フェッチ」も参照してください。
-- term: プル アクセス
-  description: 読み取りアクセスの同義語。
+    Pull refers to when you are fetching in changes and merging them. For
+    instance, if someone has edited the remote file you're both working on,
+    you'll want to pull in those changes to your local copy so that it's up to
+    date. See also fetch.
+- term: pull access
+  description: A synonym for read access.
 - term: pull request
   description: >-
-    pull request とは、リポジトリに対して提案された変更のことです。ユーザーがこれを送信すると、リポジトリのコラボレーターはこれを受け入れるか拒否します。issue と同様に、pull request にはそれぞれ独自のディスカッション フォーラムがあります。
-- term: pull request レビュー
+    Pull requests are proposed changes to a repository submitted by a user and
+    accepted or rejected by a repository's collaborators. Like issues, pull
+    requests each have their own discussion forum.
+- term: pull request review
   description: >-
-    コラボレーターからの pull request についてのコメント。pull request がマージされる前に、変更を承認したり、その他の変更を要求したりします。
-- term: パルス グラフ
-  description: リポジトリのアクティビティの概要を示すリポジトリ グラフ。
-- term: パンチ グラフ
+    Comments from collaborators on a pull request that approve the changes or
+    request further changes before the pull request is merged.
+- term: pulse graph
+  description: A repository graph that gives you an overview of a repository's activity.
+- term: punch graph
   description: >-
-    リポジトリのアップデートの頻度を、曜日ごと、または時刻ごとに示すリポジトリ グラフ
+    A repository graph that shows the frequency of updates to a repository based
+    on the day of week and time of day
 - term: push
   description: >-
-    プッシュとは、コミットした変更を GitHub.com 上のリモート リポジトリに送信するという意味です。たとえば、ローカルで何かを変更した場合、その変更をプッシュすると、他のユーザーがアクセスできるようになります。
-- term: ブランチをプッシュする
+    To push means to send your committed changes to a remote repository on
+    GitHub.com. For instance, if you change something locally, you can push those changes so that others may access them.
+- term: push a branch
   description: >-
-    リモート リポジトリへのブランチのプッシュが成功したら、ローカル ブランチからの変更でリモート ブランチを更新します。"ブランチをプッシュする" と、Git では、リモート リポジトリ内にあるブランチの HEAD ref の検索と、それがブランチのローカル HEAD ref の直接の先祖であることの検証が行われます。検証されると、Git によって、すべてのオブジェクト (ローカル HEAD ref から到達可能で、リモート リポジトリにはないもの) がリモート オブジェクト データベースにプルされて、リモート HEAD ref が更新されます。リモート HEAD がローカル HEAD の先祖ではない場合、プッシュは失敗です。
-- term: プッシュ アクセス
-  description: 書き込みアクセスの同義語。
-- term: 読み取りアクセス
+    When you successfully push a branch to a remote repository, you update the remote branch with changes from your local branch. When you "push a branch", Git will search for the branch's HEAD ref in the remote repository and verify that it is a direct ancestor to the branch's local HEAD ref. Once verified, Git pulls all objects (reachable from the local HEAD ref and missing from the remote repository) into the remote object database and then updates the remote HEAD ref. If the remote HEAD is not an ancestor to the local HEAD, the push fails.
+- term: push access
+  description: A synonym for write access.
+- term: read access
   description: >-
-    リポジトリでの権限レベル。これにより、ユーザーは、リポジトリからの情報のプルや読み取りが許可されます。読み取りアクセスは、すべてのパブリック リポジトリによって、すべての GitHub ユーザーに付与されます。プル アクセスの同義語。
+    A permission level on a repository that allows the user to pull, or read,
+    information from the repository. All public repositories give read access to
+    all GitHub users. A synonym for pull access.
 - term: README
-  description: リポジトリ内のファイルに関する情報を含むテキスト ファイル。通常、リポジトリの訪問者に表示される最初のファイルです。README ファイルは、リポジトリ ライセンス、投稿ガイドライン、行動規範とともに、期待値の共有や、プロジェクトへのコントリビューションの管理に役立ちます。
-- term: リベース
+  description: A text file containing information about the files in a repository that is typically the first file a visitor to your repository will see. A README file, along with a repository license, contribution guidelines, and a code of conduct, helps you share expectations and manage contributions to your project.
+- term: rebase
   description: >-
-    ブランチからの複数の変更を別のベースに再適用して、そのブランチの HEAD を結果にリセットすること。
-- term: リカバリー コード
-  description: GitHub アカウントへのアクセスを再取得できるようにするコード。
+    To reapply a series of changes from a branch to a different base, and reset
+    the HEAD of that branch to the result.
+- term: recovery code
+  description: A code that helps you regain access to your GitHub account.
 - term: release
-  description: ソフトウェアをパッケージ化してユーザーに提供する、GitHub での方法。
-- term: リモート
+  description: GitHub's way of packaging and providing software to your users.
+- term: remote
   description: >-
-    これは、サーバー上 (ほとんどの場合 GitHub.com) でホストされるリポジトリまたはブランチのバージョンのことです。リモート バージョンは、ローカルのクローンに接続できるので、変更を同期させることができます。
-- term: リモート リポジトリ
+    This is the version of a repository or branch that is hosted on a server, most likely
+    GitHub.com. Remote versions can be connected to local clones so that changes can be
+    synced.
+- term: remote repository
   description: >-
-    同じプロジェクトの追跡に使用されるが、別の場所にあるリポジトリ。
-- term: リモート URL
+    A repository that is used to track the same project but resides somewhere
+    else.
+- term: remote URL
   description: >-
-    コードが格納されている場所。GitHub 上のリポジトリや別のユーザーのフォークという場合もあれば、別のサーバーという場合もあります。
-- term: レプリカ (replica)
+    The place where your code is stored: a repository on GitHub, another user's
+    fork, or even a different server.
+- term: replica
   description: >-
-    GitHub Enterprise のプライマリ インスタンスに対して冗長性を与える GitHub Enterprise インスタンス。
+    A GitHub Enterprise instance that provides redundancy for the primary GitHub
+    Enterprise instance.
 - term: repository
   description: >-
-    リポジトリは、GitHub の最も基本的な要素です。プロジェクトのフォルダーと考えるのが最もわかりやすいでしょう。1 つのリポジトリには、すべてのプロジェクト ファイル (ドキュメントを含みます) が含まれ、各ファイルのリビジョン履歴が格納されます。リポジトリは、複数のコラボレーターが参加することができ、パブリックとプライベートのどちらにもすることができます。
-- term: リポジトリのキャッシュ
+    A repository is the most basic element of GitHub. They're easiest to imagine
+    as a project's folder. A repository contains all of the project files
+    (including documentation), and stores each file's revision history.
+    Repositories can have multiple collaborators and can be either public or
+    private.
+- term: repository cache
   description: >-
-    分散チームと CI クライアントの近くに配置される、GitHub Enterprise サーバー インスタンスのリポジトリの読み取り専用ミラー。
-- term: リポジトリ グラフ
-  description: リポジトリのデータの視覚的表現。
-- term: リポジトリ メンテナ
+    A read-only mirror of repositories for your GitHub Enterprise server instance, located near
+    distributed teams and CI clients.
+- term: repository graph
+  description: A visual representation of your repository's data.
+- term: repository maintainer
   description: >-
-    リポジトリを管理するユーザー。このユーザーは、リポジトリの作業を管理するために、issue のトリアージや、ラベルなどの機能の使用の支援を行うことができます。また、このユーザーには、README の維持管理や、ファイルを最新の状態に保つ責任もあります。
-- term: pull request レビュー必須
+    Someone who manages a repository. This person may help triage issues and use labels and other features to manage the work of the repository. This person may also be responsible for keeping the README and contributing files updated.
+- term: required pull request review
   description: >-
-    必須レビューを行うと、コラボレーターが保護されたブランチに対して変更を加える前に、pull request 内のレビューが少なくとも 1 つは確実に承認済みになります。
-- term: ステータス チェック必須
+    Required reviews ensure that pull requests have at least one approved review
+    before collaborators can make changes to a protected branch.
+- term: required status check
   description: >-
-    pull request に対するチェック。これを行うと、コラボレーターが保護されたブランチに対して変更を加える前に、すべての必須 CI テストに確実に合格します。
+    Checks on pull requests that ensure all required CI tests are passing before
+    collaborators can make changes to a protected branch.
 - term: resolve
-  description: 失敗した自動マージで実行されなかったものを手動で修正するアクション。
-- term: 打ち消し
+  description: The action of fixing up manually what a failed automatic merge left behind.
+- term: revert
   description: >-
-    GitHub 上で pull request を打ち消すと、新しい pull request が自動的に開きます。これには、マージされた元の pull request からのマージ コミットを打ち消すコミットが 1 つ含まれます。Git では、コミットを打ち消すには "git revert" を使います。
-- term: レビュー
+    When you revert a pull request on GitHub, a new pull request is automatically opened, which has one commit that reverts the merge commit
+    from the original merged pull request. In Git, you can revert commits with `git revert`.
+- term: review
   description: >-
-    レビューでは、リポジトリへのアクセスを持つ他のユーザーが、pull request 内で提案されている変更についてコメントしたり、変更を承認したり、その pull request がマージされる前にさらに変更をリクエストしたりすることができます。
-- term: ルート ディレクトリ
-  description: 階層内の最初のディレクトリ。
-- term: ルート ファイルシステム
-  description: 基本オペレーティング システムと GitHub Enterprise アプリケーション環境。
-- term: 返信テンプレート
+    Reviews allow others with access to your repository to comment on the changes proposed in pull
+    requests, approve the changes, or request further changes before the pull
+    request is merged.
+- term: root directory
+  description: The first directory in a hierarchy.
+- term: root filesystem
+  description: The base operating system and the GitHub Enterprise application environment.
+- term: saved reply
   description: >-
-    自分の GitHub ユーザー アカウントに保存したり追加したりすることで、GitHub のあらゆる場所で、issue や pull request に使うことができるコメント。
+    A comment you can save and add to your GitHub user account so that you can
+    use it across GitHub in issues and pull requests.
 - term: scope
   description: >-
-    OAuth App からリクエストできる、パブリック データと非パブリック データの両方へのアクセスの権限を、グループとして名前を付けたもの。
-- term: シート
+    Named groups of permissions that an OAuth App can request to access both
+    public and non-public data.
+- term: seat
   description: >-
-    GitHub Enterprise の Organization 内のユーザー。これは、"シート数" と呼ばれることがあります。
-- term: シークレット チーム
+    A user within a GitHub Enterprise organization. This may be referred to as
+    "seat count."
+- term: secret team
   description: >-
-    チームの他のユーザーと、オーナー権限を持つユーザーにのみ表示されるチーム。
-- term: セキュリティ ログ
+    A team that is only visible to the other people on the team and people with owner
+    permissions.
+- term: security log
   description: >-
-    最新の 50 個のアクションまたは過去 90 日間に実行されたアクションを一覧表示するログ。
-- term: server-to-server リクエスト
+    A log that lists the last 50 actions or those performed within the last 90
+    days.
+- term: server-to-server request
   description: >-
-    特定のユーザーとは無関係に、ボットとして機能するアプリケーションで使用される API 要求。たとえば、スケジュールどおりに実行され、長時間アクティビティがないと issue をクローズするアプリケーションなどがあります。このタイプの認証を使うアプリケーションでは、ライセンスされた GitHub アカウントを使わないため、特定の数のライセンスの使用が許可されているお支払いプランの Enterprise では、server-to-server ボットに GitHub ライセンスを 1 つも使いません。server-to-server リクエストに使うトークンは、[GitHub API](/rest/reference/apps#create-an-installation-access-token-for-an-app) 経由でプログラムによって取得します。「[user-to-server リクエスト](#user-to-server-request)」も参照してください。
-- term: サービス フック
+    An API request used by an application that acts as a bot, independently of any particular user. For example, an application that runs on a scheduled basis and closes issues where there has been no activity for a long time. Applications that use this type of authentication don't use a licensed GitHub account so, in an enterprise with a billing plan that allows a certain number of licenses to be used, a server-to-server bot is not consuming one of your GitHub licenses. The token used in a server-to-server request is acquired programmatically, via [the GitHub API](/rest/reference/apps#create-an-installation-access-token-for-an-app). See also, "[user-to-server request](#user-to-server-request)."
+- term: service hook
   description: >-
-    "Webhook" とも呼ばれます。 Webhook を使うと、特定のアクションがリポジトリまたは Organization で発生した場合に、外部の Web サーバーへ通知を送信できます。
-- term: シングル サインオン
+    Also called "webhook." Webhooks provide a way for notifications to be
+    delivered to an external web server whenever certain actions occur on a
+    repository or organization.
+- term: single sign-on
   description: >-
-    SSO とも呼ばれます。1 つの場所 (ID プロバイダー (IdP)) へのサインインをユーザーに許可してから、そのユーザーに他のサービス プロバイダーへのアクセス権を付与します。
-- term: スナップショット
-  description: ある時点での仮想マシンのチェックポイント。
+    Also called SSO. Allows users to sign in to a single location - an identity
+    provider (IdP) - that then gives the user access to other service providers.
+- term: snapshot
+  description: A checkpoint of a virtual machine at a point in time.
 - term: squash
-  description: 複数のコミットを結合して 1 つのコミットにすること。Git コマンドとしても使います。
-- term: SSH キー
+  description: To combine multiple commits into a single commit. Also a Git command.
+- term: SSH key
   description: >-
-    SSH キーは、暗号化したメッセージを使って、オンライン サーバーに対して自分自身を識別する方法です。自分のコンピューターに別のサービス用の独自の一意のパスワードが設定されているかのように見えます。{% data variables.product.product_name %} では、SSH キーを使って、コンピューターへの情報の転送が安全に行われます。
-- term: ステージング インスタンス
+    SSH keys are a way to identify yourself to an online server, using an encrypted message. It's as if your computer has its own unique password to another service. {% data variables.product.product_name %} uses SSH keys to securely transfer information to your computer.
+- term: staging instance
   description: >-
-    変更を実際の GitHub Enterprise インスタンスに適用する前にテストする方法。
+    A way to test modifications before they are applied to your actual GitHub
+    Enterprise instance.
 - term: status
   description: >-
-    コミットがコントリビューション先のリポジトリに設定されている条件を満たしていることの、pull request 内での視覚的な表現。
-- term: ステータス チェック
+    A visual representation within a pull request that your commits meet the
+    conditions set for the repository you're contributing to.
+- term: status checks
   description: >-
-    ステータス チェックとは、リポジトリにコミットするたびに実行される継続的インテグレーションのビルドのような、外部のプロセスです。詳しくは、「[ステータス チェックについて](/articles/about-status-checks)」を参照してください。
-- term: 星
+    Status checks are external processes, such as continuous integration builds, which run for each commit you make in a repository. For more information, see "[About status checks](/articles/about-status-checks)."
+- term: star
   description: >-
-    リポジトリのブックマークまたは感謝の表現。星は、プロジェクトの人気をランク付けするための手動の方法です。
+    A bookmark or display of appreciation for a repository. Stars are a manual
+    way to rank the popularity of projects.
 - term: subscription
-  description: ユーザーまたは Organization の GitHub プラン。
-- term: チーム
+  description: A user or organization's GitHub plan.
+- term: team
   description: >-
-    Organization メンバーのグループ。アクセス権限とメンションのカスケードを使って、会社やグループの構造を反映します。
-- term: チーム メンテナ
+    A group of organization members that reflect your company or group's
+    structure with cascading access permissions and mentions.
+- term: team maintainer
   description: >-
-    チームを管理するために Organization オーナーが行使できる権限のサブセットが付与された Organization メンバー。
-- term: Team プラン
+    Organization members that have a subset of permissions available to
+    organization owners to manage teams.
+- term: Team plan
   description: >-
-    パブリック リポジトリとプライベート リポジトリを無制限に利用できる Organization のお支払いプラン。
-- term: タイムライン
-  description: pull request 内またはユーザー プロファイル上の一連のイベント。
-- term: トピック ブランチ
+    An organization billing plan that gives you unlimited public and private
+    repositories.
+- term: timeline
+  description: A series of events in a pull request or on a user profile.
+- term: topic branch
   description: >-
-    開発の分野を概念的に分類したものを識別するために開発者が使う、通常の Git ブランチ。ブランチは非常に簡単で低コストなので、小さなブランチを複数用意して、それぞれのブランチに、明確に定義した概念、小さな増分、関連する変更を含めるのがよいでしょう。機能ブランチとも呼ばれます。
+    A regular Git branch that is used by a developer to identify a conceptual
+    line of development. Since branches are very easy and inexpensive, it is
+    often desirable to have several small branches that each contain very well
+    defined concepts or small incremental yet related changes. Can also be called a feature branch.
 - term: topics
   description: >-
-    Git Hub で、特定の対象分野のリポジトリを探索したり、コントリビューション先となるプロジェクトを見つけたり、特定の問題への新しい解決方法を発見したりするための方法。
-- term: トラフィック グラフ
+    A way to explore repositories in a particular subject area, find projects to
+    contribute to, and discover new solutions to a specific problem on GitHub.
+- term: traffic graph
   description: >-
-    フル クローン (フェッチではなく)、過去 14 日間の訪問者数、参照サイト数、人気のコンテンツなど、リポジトリのトラフィックを示すリポジトリ グラフ。
-- term: 転送
+    A repository graph that shows a repository's traffic, including full clones
+    (not fetches), visitors from the past 14 days, referring sites, and popular
+    content.
+- term: transfer
   description: >-
-    リポジトリの転送には、リポジトリのオーナーの変更という意味があります。新しいオーナーは、リポジトリのコンテンツ、issue、pull request、リリース、設定の管理をすぐに行うことができるようになります。
-- term: 上流
+    To transfer a repository means to change the owner of a repository. The new owner will be able to
+    immediately administer the repository's contents, issues, pull requests,
+    releases, and settings.
+- term: upstream
   description: >-
-    ブランチまたはフォークについて説明する場合、元のリポジトリにあるプライマリ ブランチは、他の変更の主な発生源となるため、"上流" と呼ばれることがよくあります。そのため、ユーザーが作業するブランチやフォークは、"下流" と呼ばれます。origin とも呼ばれます。
-- term: 上流ブランチ
+    When talking about a branch or a fork, the primary branch on the original
+    repository is often referred to as the "upstream", since that is the main
+    place that other changes will come in from. The branch/fork you are working
+    on is then called the "downstream". Also called origin.
+- term: upstream branch
   description: >-
-    あるブランチにマージされる既定のブランチ (または、そのブランチのリベース先のブランチ)。"branch.<name>.remote" と "branch.<name>.merge" を使って構成されます。A の上流ブランチが origin/B だとすると、"A は origin/B を追跡している" という言い方をすることがあります。
+    The default branch that is merged into the branch in question (or the branch
+    in question is rebased onto). It is configured via `branch.<name>.remote` and
+    `branch.<name>.merge`. If the upstream branch of A is origin/B sometimes we
+    say "A is tracking origin/B".
 - term: user
   description: >-
-    ユーザーとは、個人用 GitHub アカウントを持つユーザーのことです。ユーザーはそれぞれ、個人用プロフィールを持っており、リポジトリ (パブリックとプライベートのどちらでも) を複数所有できます。Organization を作成したり、Organization に招待されて参加したり、別のユーザーのリポジトリでコラボレーションしたりすることもできます。
+    Users are people with personal GitHub accounts. Each user has a personal profile, and
+    can own multiple repositories, public or private. They can create or be
+    invited to join organizations or collaborate on another user's repository.
 - term: username
-  description: GitHub 上でのユーザーのハンドル。
-- term: user-to-server リクエスト
+  description: A user's handle on GitHub.
+- term: user-to-server request
   description: >-
-    特定のユーザーの代わりにタスクを実行するアプリケーションで使用される API 要求。user-to-server 認証でタスクが実行された場合、GitHub には、ユーザーによってアプリケーション経由で実行済みとして表示されます。たとえば、サードパーティ アプリケーションから issue を作成すると、GitHub 上では、ユーザーの代わりにそのアプリケーションが issue を作成したことになります。user-to-server リクエストを使った、アプリケーションによる実行が可能なタスクは、アプリとユーザーの両方の権限とアクセスによって範囲が制限されます。user-to-server リクエストで使用されるトークンは、OAuth を介して取得します。詳しくは、「[GitHub アプリのユーザーを特定および認可する](/developers/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps)」を参照してください。 「[server-to-server リクエスト](#server-to-server-request)」も参照してください。
-- term: 参照可能なチーム
-  description: どの Organization メンバーにも表示され、@メンションできるチーム。
+    An API request used by an application that performs a task on behalf of a particular user. Where a task is carried out with user-to-server authentication it's shown on GitHub as having been done by a user via an application. For example, you might choose to create an issue from within a third-party application, and the application would do this on your behalf on GitHub. The scope of tasks an application can perform using a user-to-server request is restricted by both the app's and the user's permissions and access. The token used in a user-to-server request is acquired via OAuth. For more information, see "[Identifying and authorizing users for GitHub Apps](/developers/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps)." See also, "[server-to-server request](#server-to-server-request)."
+- term: visible team
+  description: A team that can be viewed and @mentioned by every organization member.
 - term: watch
   description: >-
-    リポジトリや issue を watch すると、issue や pull request が更新されるたびに通知を受け取ることができます。
-- term: watch 対象の通知
-  description: ユーザーがサブスクライブしているリポジトリでのアクティビティについての通知。
-- term: Web 通知
+    You can watch a repository or issue to receive notifications when updates are made to an issue or pull request.
+- term: watching notifications
+  description: A notification about activity in a repository a user has subscribed to.
+- term: web notifications
   description: >-
-    GitHub の Web インターフェイス (https://github.com/notifications) に表示される通知
+    Notifications displayed in the web interface on GitHub:
+    https://github.com/notifications
 - term: webhooks
   description: >-
-    Webhook を使うと、GitHub.com の特定のイベントをサブスクライブする GitHub Apps をビルドまたはセットアップできます。Webhook を使うと、特定のアクションがリポジトリまたは Organization で発生した場合に、外部の Web サーバーへ通知を送信できます。サービス フックとも呼ばれます。
-- term: 書き込みアクセス
+    Webhooks allow you to build or set up GitHub Apps which subscribe to certain
+    events on GitHub.com. Webhooks provide a way for notifications to be
+    delivered to an external web server whenever certain actions occur on a
+    repository or organization. Also called a service hook.
+- term: write access
   description: >-
-    リポジトリへの変更のプッシュ、書き込み、変更をユーザーに許可する、リポジトリでの権限レベル。
+    A permission level on a repository that allows the user to push, or write,
+    changes to the repository.
diff --git a/translations/ja-JP/data/graphql/ghes-3.2/graphql_previews.enterprise.yml b/translations/ja-JP/data/graphql/ghes-3.2/graphql_previews.enterprise.yml
deleted file mode 100644
index 8820c19067..0000000000
--- a/translations/ja-JP/data/graphql/ghes-3.2/graphql_previews.enterprise.yml
+++ /dev/null
@@ -1,117 +0,0 @@
-- title: パッケージのバージョン削除へのアクセス
-  description: このプレビューは、プライベートパッケージバージョンの削除を有効化する、DeletePackageVersionのミューテーションのサポートを追加します。
-  toggled_by: ':package-deletes-preview'
-  announcement: null
-  updates: null
-  toggled_on:
-    - Mutation.deletePackageVersion
-  owning_teams:
-    - '@github/pe-package-registry'
-- title: デプロイメント
-  description: このプレビューは、デプロイメントのミューテーションと新しいデプロイメントの機能を追加します。
-  toggled_by: ':flash-preview'
-  announcement: null
-  updates: null
-  toggled_on:
-    - DeploymentStatus.environment
-    - Mutation.createDeploymentStatus
-    - CreateDeploymentStatusInput
-    - CreateDeploymentStatusPayload
-    - Mutation.createDeployment
-    - CreateDeploymentInput
-    - CreateDeploymentPayload
-  owning_teams:
-    - '@github/c2c-actions-service'
-- title: MergeInfoPreview - プルリクエストのマージ状態に関する詳細な情報。
-  description: このプレビューは、プルリクエストのマージ状態に関する詳細な情報を提供するフィールドへのアクセスのサポートを追加します。
-  toggled_by: ':merge-info-preview'
-  announcement: null
-  updates: null
-  toggled_on:
-    - PullRequest.canBeRebased
-    - PullRequest.mergeStateStatus
-  owning_teams:
-    - '@github/pe-pull-requests'
-- title: UpdateRefsPreview - 1回の操作で複数の参照を更新します。
-  description: このプレビューは、1回の操作による複数の参照の更新のサポートを追加します。
-  toggled_by: ':update-refs-preview'
-  announcement: null
-  updates: null
-  toggled_on:
-    - Mutation.updateRefs
-    - GitRefname
-    - RefUpdate
-    - UpdateRefsInput
-    - UpdateRefsPayload
-  owning_teams:
-    - '@github/reponauts'
-- title: プロジェクトイベントの詳細
-  description: このプレビューは、プロジェクト関連のIssueイベントに対し、プロジェクト、プロジェクトカード、プロジェクト列の詳細を追加します。
-  toggled_by: ':starfox-preview'
-  announcement: null
-  updates: null
-  toggled_on:
-    - AddedToProjectEvent.project
-    - AddedToProjectEvent.projectCard
-    - AddedToProjectEvent.projectColumnName
-    - ConvertedNoteToIssueEvent.project
-    - ConvertedNoteToIssueEvent.projectCard
-    - ConvertedNoteToIssueEvent.projectColumnName
-    - MovedColumnsInProjectEvent.project
-    - MovedColumnsInProjectEvent.projectCard
-    - MovedColumnsInProjectEvent.projectColumnName
-    - MovedColumnsInProjectEvent.previousProjectColumnName
-    - RemovedFromProjectEvent.project
-    - RemovedFromProjectEvent.projectColumnName
-  owning_teams:
-    - '@github/github-projects'
-- title: コンテンツ添付ファイルの作成
-  description: このプレビューは、コンテンツ添付ファイルの作成のサポートを追加します。
-  toggled_by: ':corsair-preview'
-  announcement: null
-  updates: null
-  toggled_on:
-    - Mutation.createContentAttachment
-  owning_teams:
-    - '@github/feature-lifecycle'
-- title: ラベルのプレビュー
-  description: このプレビューは、ラベルの追加、更新、作成、削除のサポートを追加します。
-  toggled_by: ':bane-preview'
-  announcement: null
-  updates: null
-  toggled_on:
-    - Mutation.createLabel
-    - CreateLabelPayload
-    - CreateLabelInput
-    - Mutation.deleteLabel
-    - DeleteLabelPayload
-    - DeleteLabelInput
-    - Mutation.updateLabel
-    - UpdateLabelPayload
-    - UpdateLabelInput
-  owning_teams:
-    - '@github/pe-pull-requests'
-- title: プロジェクトのインポート
-  description: このプレビューは、プロジェクトのインポートのサポートを追加します。
-  toggled_by: ':slothette-preview'
-  announcement: null
-  updates: null
-  toggled_on:
-    - Mutation.importProject
-  owning_teams:
-    - '@github/pe-issues-projects'
-- title: Teamレビューの割り当てプレビュー
-  description: このプレビューは、Teamレビューの割り当て設定の更新サポートを追加します
-  toggled_by: ':stone-crop-preview'
-  announcement: null
-  updates: null
-  toggled_on:
-    - Mutation.updateTeamReviewAssignment
-    - UpdateTeamReviewAssignmentInput
-    - TeamReviewAssignmentAlgorithm
-    - Team.reviewRequestDelegationEnabled
-    - Team.reviewRequestDelegationAlgorithm
-    - Team.reviewRequestDelegationMemberCount
-    - Team.reviewRequestDelegationNotifyTeam
-  owning_teams:
-    - '@github/pe-pull-requests'
\ No newline at end of file
diff --git a/translations/ja-JP/data/learning-tracks/code-security.yml b/translations/ja-JP/data/learning-tracks/code-security.yml
index e08d0012c2..3b35eb0a73 100644
--- a/translations/ja-JP/data/learning-tracks/code-security.yml
+++ b/translations/ja-JP/data/learning-tracks/code-security.yml
@@ -1,25 +1,29 @@
 # Feature available only on dotcom
 security_advisories:
-  title: 'セキュリティ脆弱性の修正と開示'
-  description: 'リポジトリ セキュリティ アドバイザリを使用して、報告された脆弱性を非公開で修正し、CVE を取得します。'
+  title: 'Fix and disclose a security vulnerability'
+  description: 'Using repository security advisories to privately fix a reported vulnerability and get a CVE.'
   featured_track: '{% ifversion fpt or ghec %}true{% else %}false{% endif %}'
   guides:
-    - /code-security/repository-security-advisories/about-coordinated-disclosure-of-security-vulnerabilities
-    - /code-security/repository-security-advisories/creating-a-repository-security-advisory
-    - /code-security/repository-security-advisories/adding-a-collaborator-to-a-repository-security-advisory
-    - /code-security/repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability
-    - /code-security/repository-security-advisories/publishing-a-repository-security-advisory
-    - /code-security/repository-security-advisories/editing-a-repository-security-advisory
-    - /code-security/repository-security-advisories/withdrawing-a-repository-security-advisory
-    - /code-security/repository-security-advisories/removing-a-collaborator-from-a-repository-security-advisory
+    - /code-security/security-advisories/repository-security-advisories/about-coordinated-disclosure-of-security-vulnerabilities
+    - /code-security/security-advisories/global-security-advisories/about-the-github-advisory-database
+    - /code-security/security-advisories/global-security-advisories/about-global-security-advisories
+    - /code-security/security-advisories/repository-security-advisories/about-repository-security-advisories
+    - /code-security/security-advisories/repository-security-advisories/creating-a-repository-security-advisory
+    - /code-security/security-advisories/repository-security-advisories/adding-a-collaborator-to-a-repository-security-advisory
+    - /code-security/security-advisories/repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability
+    - /code-security/security-advisories/repository-security-advisories/publishing-a-repository-security-advisory
+    - /code-security/security-advisories/repository-security-advisories/editing-a-repository-security-advisory
+    - /code-security/security-advisories/repository-security-advisories/withdrawing-a-repository-security-advisory
+    - /code-security/security-advisories/repository-security-advisories/removing-a-collaborator-from-a-repository-security-advisory
+    - /code-security/security-advisories/guidance-on-reporting-and-writing/best-practices-for-writing-repository-security-advisories
 
 # Feature available on dotcom and GHES 3.3+, so articles available on GHAE and earlier GHES hidden to hide the learning track
 dependabot_alerts:
-  title: 'セキュリティで保護されていない依存関係の通知を受け取る'
-  description: '依存関係に新しい脆弱性{% ifversion GH-advisory-db-supports-malware %}またはマルウェア{% endif %}が見つかった場合に警告するように Dependabot を設定します。'
+  title: 'Get notifications for insecure dependencies'
+  description: 'Set up Dependabot to alert you to new vulnerabilities{% ifversion GH-advisory-db-supports-malware %} or malware{% endif %} in your dependencies.'
   guides:
     - /code-security/dependabot/dependabot-alerts/about-dependabot-alerts
-    - '{% ifversion fpt or ghec or ghes > 3.2 %}/github/administering-a-repository/managing-repository-settings/managing-security-and-analysis-settings-for-your-repository{% endif %}'
+    - '{% ifversion fpt or ghec or ghes %}/github/administering-a-repository/managing-repository-settings/managing-security-and-analysis-settings-for-your-repository{% endif %}'
     - /code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts
     - /code-security/dependabot/dependabot-alerts/configuring-notifications-for-dependabot-alerts
     - /code-security/dependabot/working-with-dependabot/managing-pull-requests-for-dependency-updates
@@ -28,20 +32,20 @@ dependabot_alerts:
 
 # Feature available on dotcom and GHES 3.3+, so articles available on GHAE and earlier GHES hidden to hide the learning track
 dependabot_security_updates:
-  title: '脆弱な依存関係を更新するために pull request を取得する'
-  description: '新しい脆弱性が報告されたときに pull request を作成する Dependabot を設定する'
+  title: 'Get pull requests to update your vulnerable dependencies'
+  description: 'Set up Dependabot to create pull requests when new vulnerabilities are reported.'
   guides:
     - /code-security/dependabot/dependabot-security-updates/about-dependabot-security-updates
     - /code-security/dependabot/dependabot-security-updates/configuring-dependabot-security-updates
-    - '{% ifversion fpt or ghec or ghes > 3.2 %}/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/configuring-notifications-for-vulnerable-dependencies{% endif %}'
-    - '{% ifversion fpt or ghec or ghes > 3.2 %}/github/administering-a-repository/managing-repository-settings/managing-security-and-analysis-settings-for-your-repository{% endif %}'
+    - '{% ifversion fpt or ghec or ghes %}/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/configuring-notifications-for-vulnerable-dependencies{% endif %}'
+    - '{% ifversion fpt or ghec or ghes %}/github/administering-a-repository/managing-repository-settings/managing-security-and-analysis-settings-for-your-repository{% endif %}'
     - /code-security/dependabot/working-with-dependabot/managing-pull-requests-for-dependency-updates
-    - '{% ifversion fpt or ghec or ghes > 3.2 %}/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/troubleshooting-the-detection-of-vulnerable-dependencies{% endif %}'
+    - '{% ifversion fpt or ghec or ghes %}/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/troubleshooting-the-detection-of-vulnerable-dependencies{% endif %}'
 
 # Feature available only on dotcom and GHES 3.3+
 dependency_version_updates:
-  title: '依存関係を最新に保つ'
-  description: 'Dependabot を使って新しいリリースを確認し、依存関係を更新します。'
+  title: 'Keep your dependencies up-to-date'
+  description: 'Use Dependabot to check for new releases and create pull requests to update your dependencies.'
   guides:
     - /code-security/dependabot/dependabot-version-updates/about-dependabot-version-updates
     - /code-security/dependabot/dependabot-version-updates/configuring-dependabot-version-updates
@@ -56,8 +60,8 @@ dependency_version_updates:
 
 # Feature available in GHEC, GHES 3.0 up, and GHAE. Feature limited on FPT so hidden there.
 secret_scanning:
-  title: 'シークレットのスキャン'
-  description: 'トークン、パスワード、その他のシークレットを誤ってリポジトリにチェックインしないように Secret Scanning を設定します。'
+  title: 'Scan for secrets'
+  description: 'Set up secret scanning to guard against accidental check-ins of tokens, passwords, and other secrets to your repository.'
   guides:
     - '{% ifversion not fpt %}/code-security/secret-scanning/about-secret-scanning{% endif %}'
     - '{% ifversion not fpt %}/code-security/secret-scanning/configuring-secret-scanning-for-your-repositories{% endif %}'
@@ -69,20 +73,20 @@ secret_scanning:
 
 # Security overview feature available in GHEC and GHES 3.2+, so other articles hidden to hide the learning path in other versions
 security_alerts:
-  title: 'セキュリティ アラートの調査と管理'
-  description: 'セキュリティ アラートの場所と解決方法について説明します。'
+  title: 'Explore and manage security alerts'
+  description: 'Learn where to find and resolve security alerts.'
   guides:
-    - '{% ifversion ghec or ghes > 3.1 %}/code-security/security-overview/about-the-security-overview {% endif %}'
-    - '{% ifversion ghec or ghes > 3.1 %}/code-security/security-overview/viewing-the-security-overview {% endif %}'
-    - '{% ifversion ghec or ghes > 3.1 %}/code-security/secret-scanning/managing-alerts-from-secret-scanning {% endif %}'
-    - '{% ifversion ghec or ghes > 3.1 %}/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository{% endif %}'
-    - '{% ifversion ghec or ghes > 3.1 %}/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/triaging-code-scanning-alerts-in-pull-requests{% endif %}'
-    - '{% ifversion ghec or ghes > 3.1 %}/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/viewing-and-updating-vulnerable-dependencies-in-your-repository{% endif %}'
+    - '{% ifversion ghec or ghes %}/code-security/security-overview/about-the-security-overview {% endif %}'
+    - '{% ifversion ghec or ghes %}/code-security/security-overview/viewing-the-security-overview {% endif %}'
+    - '{% ifversion ghec or ghes %}/code-security/secret-scanning/managing-alerts-from-secret-scanning {% endif %}'
+    - '{% ifversion ghec or ghes %}/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository{% endif %}'
+    - '{% ifversion ghec or ghes %}/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/triaging-code-scanning-alerts-in-pull-requests{% endif %}'
+    - '{% ifversion ghec or ghes %}/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/viewing-and-updating-vulnerable-dependencies-in-your-repository{% endif %}'
 
 # Feature available in all versions from GHES 2.22 up
 code_security_actions:
-  title: 'GitHub Actions で Code Scanning を実行する'
-  description: '既定のブランチとすべての pull request を確認して、リポジトリに脆弱性とエラーがないようにします。'
+  title: 'Run code scanning with GitHub Actions'
+  description: 'Check your default branch and every pull request to keep vulnerabilities and errors out of your repository.'
   featured_track: '{% ifversion ghae or ghes %}true{% else %}false{% endif %}'
   guides:
     - /code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning
@@ -94,8 +98,8 @@ code_security_actions:
 
 # Feature available in all versions from GHES 2.22 up
 code_security_integration:
-  title: 'Code Scanning と統合する'
-  description: 'SARIF を使ってサードパーティ システムから GitHub にコード分析結果をアップロードします。'
+  title: 'Integrate with code scanning'
+  description: 'Upload code analysis results from third-party systems to GitHub using SARIF.'
   guides:
     - /code-security/code-scanning/integrating-with-code-scanning/about-integration-with-code-scanning
     - /code-security/code-scanning/integrating-with-code-scanning/uploading-a-sarif-file-to-github
@@ -104,8 +108,8 @@ code_security_integration:
 
 # Feature available in all versions from GHES 2.22 up
 code_security_ci:
-  title: 'CI で CodeQL Code Scanning を実行する'
-  description: '既存の CI 内で CodeQL を設定し、結果を GitHub Code Scanning にアップロードします。'
+  title: 'Run CodeQL code scanning in your CI'
+  description: 'Set up CodeQL within your existing CI and upload results to GitHub code scanning.'
   guides:
     - /code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/about-codeql-code-scanning-in-your-ci-system
     - /code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/installing-codeql-cli-in-your-ci-system
@@ -115,8 +119,8 @@ code_security_ci:
 
 # Feature available in all versions
 end_to_end_supply_chain:
-  title: 'エンド ツー エンドのサプライ チェーン'
-  description: 'ユーザー アカウント、コード、ビルド プロセスのセキュリティ保護に関する考え方。'
+  title: 'End-to-end supply chain'
+  description: 'How to think about securing your user accounts, your code, and your build process.'
   guides:
     - /code-security/supply-chain-security/end-to-end-supply-chain/end-to-end-supply-chain-overview
     - /code-security/supply-chain-security/end-to-end-supply-chain/securing-accounts
diff --git a/translations/ja-JP/data/reusables/accounts/create-personal-access-tokens.md b/translations/ja-JP/data/reusables/accounts/create-personal-access-tokens.md
index f68aaad4ba..38f1bde189 100644
--- a/translations/ja-JP/data/reusables/accounts/create-personal-access-tokens.md
+++ b/translations/ja-JP/data/reusables/accounts/create-personal-access-tokens.md
@@ -1 +1 @@
-1. For each of your accounts, create a dedicated {% data variables.product.pat_v1 %} with `repo` scope. {% ifversion pat-v2 %}Or, for each of your accounts and for each organization that you are a member of, create a {% data variables.product.pat_v2 %} that can access the desired repositories and that has read and write permissions on repository contents.{% endif %} For more information, see "[Creating a {% data variables.product.pat_generic %}](/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)."
\ No newline at end of file
+1. For each of your accounts, create a dedicated {% data variables.product.pat_v1 %} with `repo` scope. {% ifversion pat-v2 %}Or, for each of your accounts and for each organization that you are a member of, create a {% data variables.product.pat_v2 %} that can access the desired repositories and that has read and write permissions on repository contents.{% endif %} For more information, see "[Creating a {% data variables.product.pat_generic %}](/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)."
diff --git a/translations/ja-JP/data/reusables/actions/about-runner-groups.md b/translations/ja-JP/data/reusables/actions/about-runner-groups.md
index f3b4dbd192..3df3ae937c 100644
--- a/translations/ja-JP/data/reusables/actions/about-runner-groups.md
+++ b/translations/ja-JP/data/reusables/actions/about-runner-groups.md
@@ -1,10 +1,10 @@
 ---
-ms.openlocfilehash: 98ccaf5f02919ebeb19485e3b2237f7c96ebfc3e
-ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794
+ms.openlocfilehash: 8492ebc0962837c6f748fe30dbca08f529c353fc
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: ja-JP
-ms.lasthandoff: 09/09/2022
-ms.locfileid: "147764012"
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148109090"
 ---
 {% ifversion fpt %} {% note %}
 
@@ -20,4 +20,4 @@ ms.locfileid: "147764012"
 
 新しいランナーが作成されると、それらは自動的にデフォルトグループに割り当てられます。 ランナーは一度に1つのグループにのみ参加できます。 ランナーはデフォルトグループから別のグループに移動できます。 詳しくは、「[ランナーをグループに移動する](#moving-a-runner-to-a-group)」をご覧ください。
 
-{% endif %}
\ No newline at end of file
+{% endif %}
diff --git a/translations/ja-JP/data/reusables/actions/actions-audit-events-workflow.md b/translations/ja-JP/data/reusables/actions/actions-audit-events-workflow.md
index 7f82e808ab..4ebc8f8a39 100644
--- a/translations/ja-JP/data/reusables/actions/actions-audit-events-workflow.md
+++ b/translations/ja-JP/data/reusables/actions/actions-audit-events-workflow.md
@@ -1,12 +1,20 @@
-| Action | Description
+---
+ms.openlocfilehash: 1162ab428d4c20f7f0ca4af8c1ec743b30e42852
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: ja-JP
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148109085"
+---
+| アクション | 説明
 |------------------|-------------------
-| `cancel_workflow_run` | Triggered when a workflow run has been cancelled. For more information, see "[Canceling a workflow](/actions/managing-workflow-runs/canceling-a-workflow)."{% ifversion fpt or ghec or ghes > 3.2 or ghae %}
-| `completed_workflow_run` | Triggered when a workflow status changes to `completed`. Can only be viewed using the REST API; not visible in the UI or the JSON/CSV export. For more information, see "[Viewing workflow run history](/actions/managing-workflow-runs/viewing-workflow-run-history)."{% endif %}{% ifversion fpt or ghec or ghes > 3.2 or ghae %}
-| `created_workflow_run` | Triggered when a workflow run is created. Can only be viewed using the REST API; not visible in the UI or the JSON/CSV export. For more information, see "[Create an example workflow](/actions/learn-github-actions/introduction-to-github-actions#create-an-example-workflow)."{% endif %}
-| `delete_workflow_run` | Triggered when a workflow run is deleted. For more information, see "[Deleting a workflow run](/actions/managing-workflow-runs/deleting-a-workflow-run)."
-| `disable_workflow` | Triggered when a workflow is disabled.
-| `enable_workflow` | Triggered when a workflow is enabled, after previously being disabled by `disable_workflow`.
-| `rerun_workflow_run` | Triggered when a workflow run is re-run. For more information, see "[Re-running a workflow](/actions/managing-workflow-runs/re-running-a-workflow)."{% ifversion fpt or ghec or ghes > 3.2 or ghae %}
-| `prepared_workflow_job` | Triggered when a workflow job is started. Includes the list of secrets that were provided to the job. Can only be viewed using the REST API. It is not visible in the the {% data variables.product.prodname_dotcom %} web interface or included in the JSON/CSV export. For more information, see "[Events that trigger workflows](/actions/reference/events-that-trigger-workflows)."{% endif %}
-| `approve_workflow_job` | Triggered when a workflow job has been approved. For more information, see "[Reviewing deployments](/actions/managing-workflow-runs/reviewing-deployments)."
-| `reject_workflow_job` | Triggered when a workflow job has been rejected. For more information, see "[Reviewing deployments](/actions/managing-workflow-runs/reviewing-deployments)."
+| `cancel_workflow_run` | ワークフローの実行がキャンセルされたときにトリガーされます。 詳細については、「[ワークフローの取り消し](/actions/managing-workflow-runs/canceling-a-workflow)」を参照してください。
+| `completed_workflow_run` | ワークフローの状態が `completed` に変わったときにトリガーされます。 REST APIを通じてのみ見ることができます。UIやJSON/CSVエクスポートでは見ることができません。 詳細については、「[ワークフロー実行の履歴を表示する](/actions/managing-workflow-runs/viewing-workflow-run-history)」を参照してください。
+| `created_workflow_run` | ワークフローの実行が作成されたときにトリガーされます。 REST APIを通じてのみ見ることができます。UIやJSON/CSVエクスポートでは見ることができません。 詳細については、「[ワークフローの例を作成する](/actions/learn-github-actions/introduction-to-github-actions#create-an-example-workflow)」を参照してください。
+| `delete_workflow_run` | ワークフローの実行が削除されたときにトリガーされます。 詳細については、「[ワークフロー実行の削除](/actions/managing-workflow-runs/deleting-a-workflow-run)」を参照してください。
+| `disable_workflow` | ワークフローが無効化されたときにトリガーされます。
+| `enable_workflow` | 以前に `disable_workflow` によって無効にされたワークフローが有効にされたときにトリガーされます。
+| `rerun_workflow_run` | ワークフローの実行が再実行されたときにトリガーされます。 詳細については、[ワークフローの再実行](/actions/managing-workflow-runs/re-running-a-workflow)に関するページを参照してください。
+| `prepared_workflow_job` | ワークフロージョブが開始されたときにトリガーされます。 ジョブに渡されたシークレットのリストを含みます。 REST API を使ってのみ表示できます。 これは、{% data variables.product.prodname_dotcom %} Web インターフェイスでは表示されず、JSON/CSV エクスポートにも含まれません。 詳細については、「[ワークフローをトリガーするイベント](/actions/reference/events-that-trigger-workflows)」を参照してください。
+| `approve_workflow_job` | ワークフロー ジョブが承認されたときにトリガーされます。 詳細については、「[デプロイの確認](/actions/managing-workflow-runs/reviewing-deployments)」を参照してください。
+| `reject_workflow_job` | ワークフロー ジョブが拒否されたときにトリガーされます。 詳細については、「[デプロイの確認](/actions/managing-workflow-runs/reviewing-deployments)」を参照してください。
diff --git a/translations/ja-JP/data/reusables/actions/add-hosted-runner-overview.md b/translations/ja-JP/data/reusables/actions/add-hosted-runner-overview.md
index 94bc82faad..61fdac58ca 100644
--- a/translations/ja-JP/data/reusables/actions/add-hosted-runner-overview.md
+++ b/translations/ja-JP/data/reusables/actions/add-hosted-runner-overview.md
@@ -1,11 +1,11 @@
 ---
-ms.openlocfilehash: 7020f9ed86843200a1b56c9b9142ed238aaf0dd5
-ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794
+ms.openlocfilehash: 955bbcc4f03b8a3a810f282c74230f220908f6b8
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: ja-JP
-ms.lasthandoff: 09/09/2022
-ms.locfileid: "147764016"
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148109084"
 ---
 使用可能なオプションのリストから、オペレーティング システムとハードウェア構成を選ぶことができます。 このランナーの新しいインスタンスが自動スケーリングによってデプロイされると、ここで定義したオペレーティング システムとハードウェア構成が使用されます。
 
-また、ランナーを識別するラベルを定義することもできます。これは、処理のためにワークフローを使ってランナーにジョブを送信する方法です (`runs-on` を使います)。 新しいランナーが既定のグループに自動的に割り当てられるか、ランナー作成プロセス中にランナーを結合する必要があるグループを選ぶことができます。 また、ランナーを登録した後で、ランナーのグループ メンバーシップを変更できます。 詳しくは、「[{% data variables.actions.hosted_runner %}へのアクセスの制御](/actions/using-github-hosted-runners/controlling-access-to-larger-runners)」を参照してください。
\ No newline at end of file
+また、ランナーを識別するラベルを定義することもできます。これは、処理のためにワークフローを使ってランナーにジョブを送信する方法です (`runs-on` を使います)。 新しいランナーが既定のグループに自動的に割り当てられるか、ランナー作成プロセス中にランナーを結合する必要があるグループを選ぶことができます。 また、ランナーを登録した後で、ランナーのグループ メンバーシップを変更できます。 詳しくは、「[{% data variables.actions.hosted_runner %}へのアクセスの制御](/actions/using-github-hosted-runners/controlling-access-to-larger-runners)」を参照してください。
diff --git a/translations/ja-JP/data/reusables/actions/add-hosted-runner.md b/translations/ja-JP/data/reusables/actions/add-hosted-runner.md
index e3d2580d6b..809ed2ad54 100644
--- a/translations/ja-JP/data/reusables/actions/add-hosted-runner.md
+++ b/translations/ja-JP/data/reusables/actions/add-hosted-runner.md
@@ -1,19 +1,11 @@
----
-ms.openlocfilehash: 216386e3e7dc31df99a383af6a335681c72911c2
-ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794
-ms.translationtype: HT
-ms.contentlocale: ja-JP
-ms.lasthandoff: 09/09/2022
-ms.locfileid: "147764046"
----
-1. **[新しいランナー]** をクリックしたら、 **[{% octicon "mark-github" aria-label="New hosted runner" %} 新しい Github ホステッド ランナー]** をクリックします。
-1. 必要な詳細を入力して、新しいランナーを構成します。
+1. Click **New runner**, then click **{% octicon "mark-github" aria-label="New hosted runner" %} New {% data variables.product.prodname_dotcom %}-hosted runner**.
+1. Complete the required details to configure your new runner:
 
-    - **名前**: 新しいランナーの名前を入力します。 識別しやすくするには、ハードウェアとオペレーティング システム (`ubuntu-20.04-16core` など) を示しておくのがよいでしょう。
-    - **ランナー イメージ**: 使用可能なオプションからオペレーティング システムを選びます。 オペレーティング システムを選ぶと、特定のバージョンを選ぶことができるようになります。
-    - **ランナーのサイズ**: 使用可能なオプションのドロップダウン リストからハードウェア構成を選びます。
-    - **自動スケーリング**: いつでもアクティブにすることができるランナーの最大数を選びます。
-    - **ランナー グループ**: ランナーがメンバーとなるグループを選びます。 需要に合わせてスケールアップまたはスケールダウンしながら、このグループによって、ランナーのインスタンスが複数ホストされます。
-    - **ネットワーク**: {% data variables.product.prodname_ghe_cloud %} の場合のみ、静的 IP アドレス範囲を {% data variables.actions.hosted_runner %} のインスタンスに割り当てるかどうかを選びます。 合計で最大 10 個の静的 IP アドレスを使うことができます。
+    - **Name**: Enter a name for your new runner. For easier identification, this should indicate its hardware and operating configuration, such as `ubuntu-20.04-16core`.
+    - **Runner image**: Choose an operating system from the available options. Once you've selected an operating system, you will be able to choose a specific version.
+    - **Runner size**: Choose a hardware configuration from the drop-down list of available options.
+    - **Auto-scaling**: Choose the maximum number of runners that can be active at any time.
+    - **Runner group**: Choose the group that your runner will be a member of. This group will host multiple instances of your runner, as they scale up and down to suit demand.
+    - **Networking**: Only for {% data variables.product.prodname_ghe_cloud %}: Choose whether a static IP address range will be assigned to instances of the {% data variables.actions.hosted_runner %}. You can use up to 10 static IP addresses in total.
 
-1. **[ランナーの作成]** をクリックします。
\ No newline at end of file
+1. Click **Create runner**.
diff --git a/translations/ja-JP/data/reusables/actions/automatically-adding-a-runner-to-a-group.md b/translations/ja-JP/data/reusables/actions/automatically-adding-a-runner-to-a-group.md
index 8a442f263c..79fdada0e7 100644
--- a/translations/ja-JP/data/reusables/actions/automatically-adding-a-runner-to-a-group.md
+++ b/translations/ja-JP/data/reusables/actions/automatically-adding-a-runner-to-a-group.md
@@ -1,10 +1,10 @@
 ---
-ms.openlocfilehash: 39b0767cfd400a12b2fb2d6709e2588dce9be503
-ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794
+ms.openlocfilehash: 4e8c79051e378c800568f0fcf36c783a1bdd8811
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: ja-JP
-ms.lasthandoff: 09/09/2022
-ms.locfileid: "147763997"
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148109078"
 ---
 構成スクリプトを使うと、新しいランナーをグループに自動的に追加できます。 たとえば、このコマンドを実行すると、新しいランナーが登録されて、`--runnergroup` パラメーターを使って `rg-runnergroup` という名前のグループに追加されます。
 
@@ -16,4 +16,4 @@ ms.locfileid: "147763997"
 
 ```
 Could not find any self-hosted runner group named "rg-runnergroup".
-```
\ No newline at end of file
+```
diff --git a/translations/ja-JP/data/reusables/actions/changing-the-access-policy-of-a-runner-group.md b/translations/ja-JP/data/reusables/actions/changing-the-access-policy-of-a-runner-group.md
index cd60712e46..6fe8813540 100644
--- a/translations/ja-JP/data/reusables/actions/changing-the-access-policy-of-a-runner-group.md
+++ b/translations/ja-JP/data/reusables/actions/changing-the-access-policy-of-a-runner-group.md
@@ -35,4 +35,4 @@ You can configure a runner group to run either selected workflows or all workflo
 
 1. Click **Save**.
 
-{% endif %}
\ No newline at end of file
+{% endif %}
diff --git a/translations/ja-JP/data/reusables/actions/changing-the-name-of-a-runner-group.md b/translations/ja-JP/data/reusables/actions/changing-the-name-of-a-runner-group.md
index 7bf82cfc33..3a5df8fce0 100644
--- a/translations/ja-JP/data/reusables/actions/changing-the-name-of-a-runner-group.md
+++ b/translations/ja-JP/data/reusables/actions/changing-the-name-of-a-runner-group.md
@@ -6,4 +6,4 @@
 {% elsif ghae < 3.4 or ghes < 3.4 %}
 {% data reusables.actions.configure-runner-group %}
 1. Change the runner group name.
-{% endif %}
\ No newline at end of file
+{% endif %}
diff --git a/translations/ja-JP/data/reusables/actions/creating-a-runner-group-for-an-organization.md b/translations/ja-JP/data/reusables/actions/creating-a-runner-group-for-an-organization.md
index bb19db9e3b..afe2577607 100644
--- a/translations/ja-JP/data/reusables/actions/creating-a-runner-group-for-an-organization.md
+++ b/translations/ja-JP/data/reusables/actions/creating-a-runner-group-for-an-organization.md
@@ -35,4 +35,4 @@ When creating a group, you must choose a policy that defines which repositories{
    
    ![Add runner group options](/assets/images/help/settings/actions-org-add-runner-group-options.png)
 1. Click **Save group** to create the group and apply the policy.
-{% endif %}
\ No newline at end of file
+{% endif %}
diff --git a/translations/ja-JP/data/reusables/actions/enterprise-http-proxy.md b/translations/ja-JP/data/reusables/actions/enterprise-http-proxy.md
index 6b17543e34..1c7693f8ea 100644
--- a/translations/ja-JP/data/reusables/actions/enterprise-http-proxy.md
+++ b/translations/ja-JP/data/reusables/actions/enterprise-http-proxy.md
@@ -3,4 +3,4 @@ If you have an **HTTP Proxy Server** configured on {% data variables.location.pr
   - You must add `localhost` and `127.0.0.1` to the **HTTP Proxy Exclusion** list.
   - If your external storage location is not routable, then you must also add your external storage URL to the exclusion list.
 
-  For more information on changing your proxy settings, see "[Configuring an outbound web proxy server](/admin/configuration/configuring-an-outbound-web-proxy-server)."
\ No newline at end of file
+  For more information on changing your proxy settings, see "[Configuring an outbound web proxy server](/admin/configuration/configuring-an-outbound-web-proxy-server)."
diff --git a/translations/ja-JP/data/reusables/actions/github_sha_description.md b/translations/ja-JP/data/reusables/actions/github_sha_description.md
index c06ad90ef7..bd4d1f95a3 100644
--- a/translations/ja-JP/data/reusables/actions/github_sha_description.md
+++ b/translations/ja-JP/data/reusables/actions/github_sha_description.md
@@ -1,9 +1,9 @@
 ---
-ms.openlocfilehash: 6d59b7ddcb233704ff06531143d1f2d7126f874b
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: b362ff01387cbd9a70aeeceb51bff2b48f776bb9
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: ja-JP
-ms.lasthandoff: 09/05/2022
-ms.locfileid: "147614570"
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148109763"
 ---
-ワークフローをトリガーしたコミット SHA。 このコミット SHA の値は、ワークフローをトリガーしたイベントによって異なります。 詳細については、「[ワークフローをトリガーするイベント](/actions/using-workflows/events-that-trigger-workflows)」を参照してください。 たとえば、「 `ffac537e6cbbf934b08745a378932722df287a53` 」のように入力します。
\ No newline at end of file
+ワークフローをトリガーしたコミット SHA。 このコミット SHA の値は、ワークフローをトリガーしたイベントによって異なります。 詳細については、「[ワークフローをトリガーするイベント](/actions/using-workflows/events-that-trigger-workflows)」を参照してください。 たとえば、「 `ffac537e6cbbf934b08745a378932722df287a53` 」のように入力します。
diff --git a/translations/ja-JP/data/reusables/actions/hosted-runner-security-admonition.md b/translations/ja-JP/data/reusables/actions/hosted-runner-security-admonition.md
index 7c628b0e8d..e664e58554 100644
--- a/translations/ja-JP/data/reusables/actions/hosted-runner-security-admonition.md
+++ b/translations/ja-JP/data/reusables/actions/hosted-runner-security-admonition.md
@@ -1,13 +1,13 @@
 ---
-ms.openlocfilehash: 7da9bbc78d15f92478a3d67e7bfd195a5635d500
-ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794
+ms.openlocfilehash: 2ce890fe0439b1030ce00041ff72cd98aeca73db
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: ja-JP
-ms.lasthandoff: 09/09/2022
-ms.locfileid: "147763988"
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148109764"
 ---
 {% warning %}
 
 **警告**: {% data reusables.actions.hosted-runner-security %}
 
-{% endwarning %}
\ No newline at end of file
+{% endwarning %}
diff --git a/translations/ja-JP/data/reusables/actions/message-parameters.md b/translations/ja-JP/data/reusables/actions/message-parameters.md
index 3306182ff0..2d37cc50dd 100644
--- a/translations/ja-JP/data/reusables/actions/message-parameters.md
+++ b/translations/ja-JP/data/reusables/actions/message-parameters.md
@@ -1,9 +1,8 @@
----
-ms.openlocfilehash: bbc3a414d8a29780d8df51bd14b9f8a5843a6c4b
-ms.sourcegitcommit: 770ed406ec075528ec9c9695aa4bfdc8c8b25fd3
-ms.translationtype: HT
-ms.contentlocale: ja-JP
-ms.lasthandoff: 09/11/2022
-ms.locfileid: "147885509"
----
-| パラメーター | 値 | | :- | :- |{% ifversion fpt or ghes > 3.2 or ghae or ghec %} | `title` | カスタム タイトル |{% endif %} | `file` | ファイル名 | | `col` | 1 から始まる列番号 |{% ifversion fpt or ghes > 3.2 or ghae or ghec %} | `endColumn` | 終了列番号 |{% endif %} | `line` | 1 から始まる行番号 |{% ifversion fpt or ghes > 3.2 or ghae or ghec %} | `endLine` | 終了行番号 |{% endif %}
+| Parameter | Value |
+| :- | :- |
+| `title` | Custom title |
+| `file` | Filename |
+| `col` | Column number, starting at 1 |
+| `endColumn` | End column number |
+| `line` | Line number, starting at 1 |
+| `endLine` | End line number |
diff --git a/translations/ja-JP/data/reusables/actions/more-resources-for-ghes.md b/translations/ja-JP/data/reusables/actions/more-resources-for-ghes.md
index ec13c86d5d..f3b008579a 100644
--- a/translations/ja-JP/data/reusables/actions/more-resources-for-ghes.md
+++ b/translations/ja-JP/data/reusables/actions/more-resources-for-ghes.md
@@ -1,18 +1,5 @@
----
-ms.openlocfilehash: 0a3393009a2dcd812f5b20e3cdd1b160aee69d5e
-ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
-ms.translationtype: HT
-ms.contentlocale: ja-JP
-ms.lasthandoff: 09/11/2022
-ms.locfileid: "147168309"
----
-インスタンスのユーザーに対して {% data variables.product.prodname_actions %} を有効にする予定の場合は、さらに多くのリソースが必要です。
+If you plan to enable {% data variables.product.prodname_actions %} for the users of your instance, more resources are required.
 
-{%- ifversion ghes = 3.2 %}
-
-{% data reusables.actions.hardware-requirements-3.2 %}
-
-{%- endif %}
 
 {%- ifversion ghes = 3.3 %}
 
@@ -32,4 +19,4 @@ ms.locfileid: "147168309"
 
 {%- endif %}
 
-これらの要件の詳細については、「[{% data variables.product.prodname_ghe_server %} の {% data variables.product.prodname_actions %} の概要](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server#review-hardware-considerations)」を参照してください。
+For more information about these requirements, see "[Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_server %}](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server#review-hardware-considerations)."
diff --git a/translations/ja-JP/data/reusables/actions/moving-a-runner-to-a-group.md b/translations/ja-JP/data/reusables/actions/moving-a-runner-to-a-group.md
index 61a617e79c..f0d634cbeb 100644
--- a/translations/ja-JP/data/reusables/actions/moving-a-runner-to-a-group.md
+++ b/translations/ja-JP/data/reusables/actions/moving-a-runner-to-a-group.md
@@ -12,4 +12,4 @@ If you don't specify a runner group during the registration process, your new ru
     ![Runner group member move](/assets/images/help/settings/actions-org-runner-group-member-move.png)
 3. To move the runner, click on the destination group.
     ![Runner group member move](/assets/images/help/settings/actions-org-runner-group-member-move-destination.png)
-{% endif %}
\ No newline at end of file
+{% endif %}
diff --git a/translations/ja-JP/data/reusables/actions/removing-a-runner-group.md b/translations/ja-JP/data/reusables/actions/removing-a-runner-group.md
index 2f057111e0..2a33557252 100644
--- a/translations/ja-JP/data/reusables/actions/removing-a-runner-group.md
+++ b/translations/ja-JP/data/reusables/actions/removing-a-runner-group.md
@@ -1,10 +1,10 @@
 ---
-ms.openlocfilehash: 62e8c6a4133d8402083e84402453b5fb6820bac3
-ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794
+ms.openlocfilehash: d3eda8a12037f1da8ec915c4652fa658f34fcc6b
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: ja-JP
-ms.lasthandoff: 09/09/2022
-ms.locfileid: "147764049"
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148109751"
 ---
 ランナーは、そのグループが削除されると自動的に既定のグループに戻ります。
 
@@ -13,4 +13,4 @@ ms.locfileid: "147764049"
 2. グループを削除するには、 **[グループの削除]** をクリックします。
 3. 確認プロンプトを確認し、 **[Remove this runner group]\(このランナー グループの削除\)** をクリックします。 このグループのすべてのランナーは、既定のグループに自動的に移動します。ここでは、このグループに割り当てられたアクセス許可を継承します。
 
-{% endif %}
\ No newline at end of file
+{% endif %}
diff --git a/translations/ja-JP/data/reusables/actions/runner-group-enterprise-overview.md b/translations/ja-JP/data/reusables/actions/runner-group-enterprise-overview.md
index 425c274aac..9c38d882bf 100644
--- a/translations/ja-JP/data/reusables/actions/runner-group-enterprise-overview.md
+++ b/translations/ja-JP/data/reusables/actions/runner-group-enterprise-overview.md
@@ -1,11 +1,11 @@
 ---
-ms.openlocfilehash: 3e11d726bb45f2a291ea7fbae4d10770cd505eaf
-ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794
+ms.openlocfilehash: 761cee3710852bda8e1f36d47da475e2c6d6b130
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: ja-JP
-ms.lasthandoff: 09/09/2022
-ms.locfileid: "147763976"
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148109746"
 ---
 ランナー グループは、Organization レベルと Enterprise レベルのランナーへのアクセスを制御するために使用されます。 Enterprise の所有者はアクセス ポリシーを設定して、Enterprise 内のどの Organization {% ifversion restrict-groups-to-workflows %}とワークフロー{% endif %}がランナー グループにアクセスできるかを制御できます。 Organization の所有者はアクセス ポリシーを設定して、Organization 内のどのリポジトリ{% ifversion restrict-groups-to-workflows %}とワークフロー{% endif %}がランナー グループにアクセスできるかを制御できます。
 
-Enterprise の所有者がランナー グループにアクセス権を付与する場合、Organization の所有者には、Organization のランナー設定に一覧表示されているランナー グループが表示されます。 その後、Organization の所有者は、リポジトリ{% ifversion restrict-groups-to-workflows %}とワークフロー{% endif %}の詳細な追加アクセス ポリシーを、Enterprise ランナー グループに割り当てることができます。
\ No newline at end of file
+Enterprise の所有者がランナー グループにアクセス権を付与する場合、Organization の所有者には、Organization のランナー設定に一覧表示されているランナー グループが表示されます。 その後、Organization の所有者は、リポジトリ{% ifversion restrict-groups-to-workflows %}とワークフロー{% endif %}の詳細な追加アクセス ポリシーを、Enterprise ランナー グループに割り当てることができます。
diff --git a/translations/ja-JP/data/reusables/actions/self-hosted-runner-auto-removal.md b/translations/ja-JP/data/reusables/actions/self-hosted-runner-auto-removal.md
index 4800d4e61d..f6fa64f23f 100644
--- a/translations/ja-JP/data/reusables/actions/self-hosted-runner-auto-removal.md
+++ b/translations/ja-JP/data/reusables/actions/self-hosted-runner-auto-removal.md
@@ -1,12 +1,6 @@
----
-ms.openlocfilehash: 80d40b1947f72a35fad5cf4cfb69f7ce68d28eab
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
-ms.translationtype: HT
-ms.contentlocale: ja-JP
-ms.lasthandoff: 09/05/2022
-ms.locfileid: "147558376"
----
-{%- ifversion fpt or ghec or ghes > 3.6 %} セルフホストランナーは、{% data variables.product.prodname_actions %} に 14 日以上接続されないと、{% data variables.product.product_name %} から自動的に削除されます。  
-エフェメラル セルフホストランナーは、{% data variables.product.prodname_actions %} に 1 日以上接続されないと、{% data variables.product.product_name %} から自動的に削除されます。  
-{%- elsif ghae or ghes < 3.7 %} セルフホストランナーは、{% data variables.product.prodname_actions %} に 30 日以上接続されないと、{% data variables.product.product_name %} から自動的に削除されます。  
-{%- endif %}
\ No newline at end of file
+{%- ifversion fpt or ghec or ghes > 3.6 %}
+A self-hosted runner is automatically removed from {% data variables.product.product_name %} if it has not connected to {% data variables.product.prodname_actions %} for more than 14 days.  
+An ephemeral self-hosted runner is automatically removed from {% data variables.product.product_name %} if it has not connected to {% data variables.product.prodname_actions %} for more than 1 day.  
+{%- elsif ghae or ghes < 3.7 %}
+A self-hosted runner is automatically removed from {% data variables.product.product_name %} if it has not connected to {% data variables.product.prodname_actions %} for more than 30 days.  
+{%- endif %}
diff --git a/translations/ja-JP/data/reusables/actions/self-hosted-runner-security-admonition.md b/translations/ja-JP/data/reusables/actions/self-hosted-runner-security-admonition.md
index ed65924082..dfc9f74cbb 100644
--- a/translations/ja-JP/data/reusables/actions/self-hosted-runner-security-admonition.md
+++ b/translations/ja-JP/data/reusables/actions/self-hosted-runner-security-admonition.md
@@ -1,10 +1,10 @@
 ---
-ms.openlocfilehash: bf779905fbb6aa54c5719b4e1046e6e24fc8ad85
-ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794
+ms.openlocfilehash: 8c2084dcfcee3042fd067f1e82138875724c59ac
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: ja-JP
-ms.lasthandoff: 09/09/2022
-ms.locfileid: "147764240"
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148109740"
 ---
 {% warning %}
 
@@ -12,4 +12,4 @@ ms.locfileid: "147764240"
 
 詳細については、[セルフホステッド ランナー](/actions/hosting-your-own-runners/about-self-hosted-runners#self-hosted-runner-security-with-public-repositories)に関する記述をご覧ください。
 
-{% endwarning %}
\ No newline at end of file
+{% endwarning %}
diff --git a/translations/ja-JP/data/reusables/actions/self-hosted-runner-security.md b/translations/ja-JP/data/reusables/actions/self-hosted-runner-security.md
index b2cc85cb56..4a290bd07a 100644
--- a/translations/ja-JP/data/reusables/actions/self-hosted-runner-security.md
+++ b/translations/ja-JP/data/reusables/actions/self-hosted-runner-security.md
@@ -1,9 +1,9 @@
 ---
-ms.openlocfilehash: 61eed0176c65b4e7b691b69b68e32032ea3ee3eb
-ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794
+ms.openlocfilehash: 518c31dffd71180ff4733f98ba7df3d5fe6028d9
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: ja-JP
-ms.lasthandoff: 09/09/2022
-ms.locfileid: "147763797"
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148109739"
 ---
-セルフホストランナーは、プライベートリポジトリでのみ利用することをおすすめします。 これは、ワークフロー内でコードを実行する pull request を作成することで、パブリック リポジトリのフォークによって、セルフホステッド ランナー マシン上で危険なコードが実行される可能性があるからです。
\ No newline at end of file
+セルフホストランナーは、プライベートリポジトリでのみ利用することをおすすめします。 これは、ワークフロー内でコードを実行する pull request を作成することで、パブリック リポジトリのフォークによって、セルフホステッド ランナー マシン上で危険なコードが実行される可能性があるからです。
diff --git a/translations/ja-JP/data/reusables/actions/sidebar-secret.md b/translations/ja-JP/data/reusables/actions/sidebar-secret.md
index 5fa0f6887b..91d60259f5 100644
--- a/translations/ja-JP/data/reusables/actions/sidebar-secret.md
+++ b/translations/ja-JP/data/reusables/actions/sidebar-secret.md
@@ -2,4 +2,4 @@
 1. In the "Security" section of the sidebar, select **{% octicon "key-asterisk" aria-label="The key-asterisk icon" %} Secrets**, then click **Actions**.
 {%- else %}
 1. In the left sidebar, click **Secrets**.
-{%- endif %}
\ No newline at end of file
+{%- endif %}
diff --git a/translations/ja-JP/data/reusables/actions/usage-workflow-run-time.md b/translations/ja-JP/data/reusables/actions/usage-workflow-run-time.md
index e368272fe8..9d41c4d993 100644
--- a/translations/ja-JP/data/reusables/actions/usage-workflow-run-time.md
+++ b/translations/ja-JP/data/reusables/actions/usage-workflow-run-time.md
@@ -1 +1 @@
-- **Workflow run time** - {% ifversion fpt or ghec or ghes > 3.2 or ghae %}Each workflow run is limited to 35 days. If a workflow run reaches this limit, the workflow run is cancelled. This period includes execution duration, and time spent on waiting and approval.{% else %}Each workflow run is limited to 72 hours. If a workflow run reaches this limit, the workflow run is cancelled.{% endif %}
+- **Workflow run time** - Each workflow run is limited to 35 days. If a workflow run reaches this limit, the workflow run is cancelled. This period includes execution duration, and time spent on waiting and approval.
diff --git a/translations/ja-JP/data/reusables/advanced-security/custom-link-beta.md b/translations/ja-JP/data/reusables/advanced-security/custom-link-beta.md
index f4a769e189..71eec7290b 100644
--- a/translations/ja-JP/data/reusables/advanced-security/custom-link-beta.md
+++ b/translations/ja-JP/data/reusables/advanced-security/custom-link-beta.md
@@ -1,13 +1,13 @@
 ---
-ms.openlocfilehash: eca31e7c0c729309568cbf6359a27437ce35fbd2
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: f9f5661230c99fb281c3625972b7e5d0fce98963
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: ja-JP
-ms.lasthandoff: 09/05/2022
-ms.locfileid: "147683812"
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148108815"
 ---
 {% note %}
 
 **メモ:** 現在、ブロックされた push メッセージにリソース リンクを追加する機能はパブリック ベータ版であり、変更される可能性があります。
 
-{% endnote %}
\ No newline at end of file
+{% endnote %}
diff --git a/translations/ja-JP/data/reusables/advanced-security/secret-scanning-create-custom-pattern.md b/translations/ja-JP/data/reusables/advanced-security/secret-scanning-create-custom-pattern.md
index 8b6afe3169..f4fc70a9c2 100644
--- a/translations/ja-JP/data/reusables/advanced-security/secret-scanning-create-custom-pattern.md
+++ b/translations/ja-JP/data/reusables/advanced-security/secret-scanning-create-custom-pattern.md
@@ -1 +1 @@
-1. When you're satisfied with your new custom pattern, click {% ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4 %}**Publish pattern**{% elsif  ghes > 3.2 or ghae %}**Create pattern**{% elsif ghes = 3.2 %}**Create custom pattern**{% endif %}.
+1. When you're satisfied with your new custom pattern, click {% ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4 %}**Publish pattern**{% else %}**Create pattern**.{% endif %}
diff --git a/translations/ja-JP/data/reusables/advanced-security/secret-scanning-new-custom-pattern.md b/translations/ja-JP/data/reusables/advanced-security/secret-scanning-new-custom-pattern.md
index 8aaee97b01..0f675c8f77 100644
--- a/translations/ja-JP/data/reusables/advanced-security/secret-scanning-new-custom-pattern.md
+++ b/translations/ja-JP/data/reusables/advanced-security/secret-scanning-new-custom-pattern.md
@@ -1,9 +1 @@
----
-ms.openlocfilehash: fffcf27ed7d0b6a175d218436989af63172b5d2b
-ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
-ms.translationtype: HT
-ms.contentlocale: ja-JP
-ms.lasthandoff: 09/11/2022
-ms.locfileid: "145113990"
----
-1. [{% data variables.product.prodname_secret_scanning_caps %}] の [カスタム パターン] で、{% ifversion fpt or ghes > 3.2 or ghae or ghec %} **[新しいパターン]** {% elsif ghes = 3.2 %} **[新しいカスタム パターン]** をクリックします{% endif %}。
+1. Under "{% data variables.product.prodname_secret_scanning_caps %}", under "Custom patterns", click **New pattern**.
diff --git a/translations/ja-JP/data/reusables/audit_log/audit-data-retention-tab.md b/translations/ja-JP/data/reusables/audit_log/audit-data-retention-tab.md
index 38de8f9835..5128ffbc03 100644
--- a/translations/ja-JP/data/reusables/audit_log/audit-data-retention-tab.md
+++ b/translations/ja-JP/data/reusables/audit_log/audit-data-retention-tab.md
@@ -1,11 +1,11 @@
 ---
-ms.openlocfilehash: 7b51303370d46101100bc953a25193ea3d14d032
-ms.sourcegitcommit: 770ed406ec075528ec9c9695aa4bfdc8c8b25fd3
+ms.openlocfilehash: ce590bb087145ff4abfb195d7257c614464c2b19
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: ja-JP
-ms.lasthandoff: 09/11/2022
-ms.locfileid: "147884422"
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148109727"
 ---
 1. [監査ログ] で、 **[データ保持の監査]** をクリックします。
 
-   ![[データ保持の監査] タブのスクリーンショット](/assets/images/help/enterprises/audit-data-retention-tab.png)
\ No newline at end of file
+   ![[データ保持の監査] タブのスクリーンショット](/assets/images/help/enterprises/audit-data-retention-tab.png)
diff --git a/translations/ja-JP/data/reusables/audit_log/audit-log-action-categories.md b/translations/ja-JP/data/reusables/audit_log/audit-log-action-categories.md
index a135b85355..f6f3bf77d0 100644
--- a/translations/ja-JP/data/reusables/audit_log/audit-log-action-categories.md
+++ b/translations/ja-JP/data/reusables/audit_log/audit-log-action-categories.md
@@ -33,12 +33,11 @@
 {%- ifversion ghes %}
 | `config_entry` |  Contains activities related to configuration settings. These events are only visible in the site admin audit log.
 {%- endif %}
-{%- ifversion fpt or ghec or ghes > 3.2 or ghae %} |
+|
 | `dependabot_alerts`  | Contains organization-level configuration activities for {% data variables.product.prodname_dependabot_alerts %} in existing repositories. For more information, see "[About {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)."
 | `dependabot_alerts_new_repos`   | Contains organization-level configuration activities for  {% data variables.product.prodname_dependabot_alerts %} in new repositories created in the organization.
 | `dependabot_repository_access` | Contains activities related to which private repositories in an organization {% data variables.product.prodname_dependabot %} is allowed to access.
-{%- endif %}
-{%- ifversion fpt or ghec or ghes > 3.2 %}
+{%- ifversion fpt or ghec or ghes %}
 | `dependabot_security_updates`   | Contains organization-level configuration activities for {% data variables.product.prodname_dependabot_security_updates %} in existing repositories. For more information, see "[Configuring {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/configuring-dependabot-security-updates)."
 | `dependabot_security_updates_new_repos` | Contains organization-level configuration activities for {% data variables.product.prodname_dependabot_security_updates %} for new repositories created in the organization.
 {%- endif %}
diff --git a/translations/ja-JP/data/reusables/audit_log/audit-log-events-workflows.md b/translations/ja-JP/data/reusables/audit_log/audit-log-events-workflows.md
index a41b568841..a5b8769233 100644
--- a/translations/ja-JP/data/reusables/audit_log/audit-log-events-workflows.md
+++ b/translations/ja-JP/data/reusables/audit_log/audit-log-events-workflows.md
@@ -7,8 +7,6 @@
 | `workflows.enable_workflow` | A workflow was enabled, after previously being disabled by `disable_workflow`.
 | `workflows.reject_workflow_job` | A workflow job was rejected. For more information, see "[Reviewing deployments](/actions/managing-workflow-runs/reviewing-deployments)."
 | `workflows.rerun_workflow_run` | A workflow run was re-run. For more information, see "[Re-running a workflow](/actions/managing-workflow-runs/re-running-a-workflow)."
-{%- ifversion fpt or ghec or ghes > 3.2 or ghae %}
 | `workflows.completed_workflow_run` | A workflow status changed to `completed`. Can only be viewed using the REST API; not visible in the UI or the JSON/CSV export. For more information, see "[Viewing workflow run history](/actions/managing-workflow-runs/viewing-workflow-run-history).
 | `workflows.created_workflow_run` | A workflow run was created. Can only be viewed using the REST API; not visible in the UI or the JSON/CSV export. For more information, see "[Create an example workflow](/actions/learn-github-actions/introduction-to-github-actions#create-an-example-workflow)."
 | `workflows.prepared_workflow_job` | A workflow job was started. Includes the list of secrets that were provided to the job. Can only be viewed using the REST API. It is not visible in the the {% data variables.product.prodname_dotcom %} web interface or included in the JSON/CSV export. For more information, see "[Events that trigger workflows](/actions/reference/events-that-trigger-workflows)."
-{%- endif %}
diff --git a/translations/ja-JP/data/reusables/audit_log/git-events-not-in-search-results.md b/translations/ja-JP/data/reusables/audit_log/git-events-not-in-search-results.md
index a3709f54be..11a875bdb9 100644
--- a/translations/ja-JP/data/reusables/audit_log/git-events-not-in-search-results.md
+++ b/translations/ja-JP/data/reusables/audit_log/git-events-not-in-search-results.md
@@ -1,13 +1,13 @@
 ---
-ms.openlocfilehash: a17c50cfb04b759fe451f686129f86bb4b22fcff
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: 6b7d1cd8cae2ecd6688a1a5d41d7bda03d8e8d97
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: ja-JP
-ms.lasthandoff: 09/05/2022
-ms.locfileid: "147424871"
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148109651"
 ---
 {% ifversion git-events-audit-log %} {% note %}
 
 **注:** Git イベントは検索結果に含まれません。
 
-{% endnote %} {% endif %}
\ No newline at end of file
+{% endnote %} {% endif %}
diff --git a/translations/ja-JP/data/reusables/audit_log/streaming-check-s3-endpoint.md b/translations/ja-JP/data/reusables/audit_log/streaming-check-s3-endpoint.md
index 78b626948e..976ff3a514 100644
--- a/translations/ja-JP/data/reusables/audit_log/streaming-check-s3-endpoint.md
+++ b/translations/ja-JP/data/reusables/audit_log/streaming-check-s3-endpoint.md
@@ -1,11 +1,11 @@
 ---
-ms.openlocfilehash: e52e6f55f04b57e1b1f8a8d044b4651b69e2caf5
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: 6e4387a1736c320dbef802ea07c22dfc1fa091a6
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: ja-JP
-ms.lasthandoff: 09/05/2022
-ms.locfileid: "147080077"
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148109275"
 ---
 1. {% data variables.product.prodname_dotcom %} で Amazon S3 エンドポイントに接続して書き込めることを確認するには、 **[Check endpoint]\(エンドポイントのチェック\)** をクリックします。
    
-   ![エンドポイントをチェックする](/assets/images/help/enterprises/audit-stream-check.png)
\ No newline at end of file
+   ![エンドポイントをチェックする](/assets/images/help/enterprises/audit-stream-check.png)
diff --git a/translations/ja-JP/data/reusables/audit_log/streaming-choose-s3.md b/translations/ja-JP/data/reusables/audit_log/streaming-choose-s3.md
index 9de52f7e09..45e69049f0 100644
--- a/translations/ja-JP/data/reusables/audit_log/streaming-choose-s3.md
+++ b/translations/ja-JP/data/reusables/audit_log/streaming-choose-s3.md
@@ -1,11 +1,11 @@
 ---
-ms.openlocfilehash: 67009b930a04da090718919ea104317809515027
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: c8ea836ffb23f1d69d2a42c5204143442480eafa
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: ja-JP
-ms.lasthandoff: 09/05/2022
-ms.locfileid: "147080074"
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148109244"
 ---
 1. **[Configure stream]\(ストリームの構成\)** ドロップダウンを選び、 **[Amazon S3]** をクリックします。
    
-   ![ドロップダウン メニューから [Amazon S3] を選択する](/assets/images/help/enterprises/audit-stream-choice-s3.png)
\ No newline at end of file
+   ![ドロップダウン メニューから [Amazon S3] を選択する](/assets/images/help/enterprises/audit-stream-choice-s3.png)
diff --git a/translations/ja-JP/data/reusables/billing/billing-hosted-runners.md b/translations/ja-JP/data/reusables/billing/billing-hosted-runners.md
index 3dc6aa2725..295a63f256 100644
--- a/translations/ja-JP/data/reusables/billing/billing-hosted-runners.md
+++ b/translations/ja-JP/data/reusables/billing/billing-hosted-runners.md
@@ -1,9 +1,9 @@
 ---
-ms.openlocfilehash: 430ca2e9df62f3bfc869356e5ff58c6170119d77
-ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794
+ms.openlocfilehash: 44593ccc9877d4cb1a224122f7c1dd9695db27f6
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: ja-JP
-ms.lasthandoff: 09/09/2022
-ms.locfileid: "147763996"
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148109243"
 ---
-|  Linux   |   4  |   $0.016   | |  Linux   |   8  |   $0.032   | |  Linux   |  16  |   $0.064   | |  Linux   |  32   |   $0.128   | |  Linux   |   64  |   $0.256   | |  Windows   |   8  |   $0.064   | |  Windows   |  16  |   $0.128   | |  Windows   |  32 |   $0.256   | |  Windows   |  64  |   $0.512   |
\ No newline at end of file
+|  Linux   |   4  |   $0.016   | |  Linux   |   8  |   $0.032   | |  Linux   |  16  |   $0.064   | |  Linux   |  32   |   $0.128   | |  Linux   |   64  |   $0.256   | |  Windows   |   8  |   $0.064   | |  Windows   |  16  |   $0.128   | |  Windows   |  32 |   $0.256   | |  Windows   |  64  |   $0.512   |
diff --git a/translations/ja-JP/data/reusables/code-scanning/alerts-found-in-generated-code.md b/translations/ja-JP/data/reusables/code-scanning/alerts-found-in-generated-code.md
index 242d8e3c1e..7f8f459e7c 100644
--- a/translations/ja-JP/data/reusables/code-scanning/alerts-found-in-generated-code.md
+++ b/translations/ja-JP/data/reusables/code-scanning/alerts-found-in-generated-code.md
@@ -1,11 +1,3 @@
----
-ms.openlocfilehash: 599e48d3a38c855896fac842f5c8b4833488aeae
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
-ms.translationtype: HT
-ms.contentlocale: ja-JP
-ms.lasthandoff: 09/05/2022
-ms.locfileid: "147063737"
----
-Java、C、C++、C# などのコンパイルされた言語の場合、{% data variables.product.prodname_codeql %} はワークフローの実行中に作成されたすべてのコードを分析します。 分析するコードの量を制限するには、`run` ブロックで独自のビルド ステップを指定して、分析するコードのみをビルドします。 独自のビルド ステップの指定と、`pull_request` イベントや `push` イベントでの `paths` フィルターまたは `paths-ignore` フィルターの使用を組み合わせることで、特定のコードが変更されたときにのみワークフローが実行されるようにすることができます。 詳細については、[{% data variables.product.prodname_actions %} のワークフロー構文](/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestpull_request_targetpathspaths-ignore)に関するページを参照してください。
+For compiled languages like Java,{% ifversion codeql-go-autobuild %} Go,{% endif %} C, C++, and C#, {% data variables.product.prodname_codeql %} analyzes all of the code which was built during the workflow run. To limit the amount of code being analyzed, build ony the code which you wish to analyze by specifying your own build steps in a `run` block. You can combine specifying your own build steps with using the `paths` or `paths-ignore` filters on the `pull_request` and `push` events to ensure that your workflow only runs when specific code is changed. For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestpull_request_targetpathspaths-ignore)."
 
-ソース コードをコンパイルせずに {% data variables.product.prodname_codeql %} で分析される Go、JavaScript、Python、TypeScript などの言語の場合、追加の設定オプションを指定して分析するコードの量を制限できます。 詳細については、「[Specifying directories to scan](/code-security/secure-coding/configuring-code-scanning#specifying-directories-to-scan)」(スキャンするディレクトリの指定) を参照してください。
+For languages like{% ifversion codeql-go-autobuild %}{% else %} Go,{% endif %} JavaScript, Python, and TypeScript, that {% data variables.product.prodname_codeql %} analyzes without compiling the source code, you can specify additional configuration options to limit the amount of code to analyze. For more information, see "[Specifying directories to scan](/code-security/secure-coding/configuring-code-scanning#specifying-directories-to-scan)."
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/code-scanning/analyze-go.md b/translations/ja-JP/data/reusables/code-scanning/analyze-go.md
index 432d0add0d..cd600af953 100644
--- a/translations/ja-JP/data/reusables/code-scanning/analyze-go.md
+++ b/translations/ja-JP/data/reusables/code-scanning/analyze-go.md
@@ -1 +1,9 @@
-For these three languages, {% data variables.product.prodname_codeql %} analyzes the source files in your repository that are built. {% data variables.product.prodname_codeql %} also runs a build for Go projects to set up the project, but then analyzes _all_ Go files in the repository, not just the files that are built. For any of these languages, including Go, you can disable `autobuild` and instead use custom build commands in order to analyze only the files that are built by these custom commands.
\ No newline at end of file
+---
+ms.openlocfilehash: e9f2162fa5c65d4a59b2bd350aea2b131205f9a6
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: ja-JP
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145113374"
+---
+{% data variables.product.prodname_codeql %}は、プロジェクトをセットアップするためにGoのプロジェクトのビルドも実行します。 ただし、他のコンパイル済み言語と対照的に、ビルドされたものだけでなく、リポジトリ内のすべての Go ファイルが抽出されます。 カスタム ビルド コマンドを使用すると、ビルドによって使用されない Go ファイルの抽出をスキップできます。
diff --git a/translations/ja-JP/data/reusables/code-scanning/autobuild-compiled-languages.md b/translations/ja-JP/data/reusables/code-scanning/autobuild-compiled-languages.md
index 60801fcd73..58d3db79d2 100644
--- a/translations/ja-JP/data/reusables/code-scanning/autobuild-compiled-languages.md
+++ b/translations/ja-JP/data/reusables/code-scanning/autobuild-compiled-languages.md
@@ -1,9 +1 @@
----
-ms.openlocfilehash: d772b6eae7cf42f2635bb427605b6d0626bdad05
-ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
-ms.translationtype: HT
-ms.contentlocale: ja-JP
-ms.lasthandoff: 09/11/2022
-ms.locfileid: "145113358"
----
-サポートされているコンパイル言語の場合、{% data variables.product.prodname_codeql_workflow %} の `autobuild` アクションを使用してコードをビルドできます。 これにより、C/C++、C#、Java についての明示的なビルド コマンドを指定する必要がなくなります。
+For the supported compiled languages, you can use the `autobuild` action in the {% data variables.product.prodname_codeql_workflow %} to build your code. This avoids you having to specify explicit build commands for C/C++, C#,{% ifversion codeql-go-autobuild %} Go,{% endif %} and Java.
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/code-scanning/example-configuration-files.md b/translations/ja-JP/data/reusables/code-scanning/example-configuration-files.md
index 51e34a25ac..c5179a14d9 100644
--- a/translations/ja-JP/data/reusables/code-scanning/example-configuration-files.md
+++ b/translations/ja-JP/data/reusables/code-scanning/example-configuration-files.md
@@ -1,10 +1,10 @@
 ---
-ms.openlocfilehash: 94e76ae2e8580c87d4493d454e4921f777da810c
-ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794
+ms.openlocfilehash: 77c9b4b73d2d839bc9c0bdaa73ffc148f0eda6ca
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: ja-JP
-ms.lasthandoff: 09/09/2022
-ms.locfileid: "147717782"
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148109228"
 ---
 この構成ファイルは、コードのスキャン時に {% data variables.product.prodname_codeql %} によって実行されるクエリのリストに `security-and-quality` クエリ スイートを追加します。 使用できるクエリ スイートの詳細については、「[追加のクエリを実行する](#running-additional-queries)」を参照してください。
 
@@ -56,4 +56,4 @@ query-filters:
       - recommendation
 ```
 
-{% endif %}
\ No newline at end of file
+{% endif %}
diff --git a/translations/ja-JP/data/reusables/code-scanning/non-glibc-linux-support.md b/translations/ja-JP/data/reusables/code-scanning/non-glibc-linux-support.md
index 3857ddb2d4..e595949d71 100644
--- a/translations/ja-JP/data/reusables/code-scanning/non-glibc-linux-support.md
+++ b/translations/ja-JP/data/reusables/code-scanning/non-glibc-linux-support.md
@@ -1,9 +1,9 @@
 ---
-ms.openlocfilehash: c33cc3f12d4b55379e23107890edc72673d4552d
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: 2c492c061232518888ac11c439ee5917fe032eeb
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: ja-JP
-ms.lasthandoff: 09/05/2022
-ms.locfileid: "147682688"
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148109227"
 ---
-{% data variables.product.prodname_codeql_cli %} は現在、glibc 以外の Linux ディストリビューション ((musl ベースの) Alpine Linux など) との互換性がありません。
\ No newline at end of file
+{% data variables.product.prodname_codeql_cli %} は現在、glibc 以外の Linux ディストリビューション ((musl ベースの) Alpine Linux など) との互換性がありません。
diff --git a/translations/ja-JP/data/reusables/codespaces/about-changing-default-editor.md b/translations/ja-JP/data/reusables/codespaces/about-changing-default-editor.md
new file mode 100644
index 0000000000..fcf94fe475
--- /dev/null
+++ b/translations/ja-JP/data/reusables/codespaces/about-changing-default-editor.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: ba91a4555a2ae0e8ec359aee8c466e201525647c
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: ja-JP
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148109220"
+---
+個人用設定ページで、{% data variables.product.prodname_codespaces %} の既定のエディターを設定できます。
diff --git a/translations/ja-JP/data/reusables/codespaces/accessing-prebuild-configuration.md b/translations/ja-JP/data/reusables/codespaces/accessing-prebuild-configuration.md
new file mode 100644
index 0000000000..423b9fd764
--- /dev/null
+++ b/translations/ja-JP/data/reusables/codespaces/accessing-prebuild-configuration.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: e18c37f7f93e2125d7280bd5b24a6eebea77d935
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: ja-JP
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148106942"
+---
+{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %}
+1. サイドバーの [コードとオートメーション] セクションで、 **[{% octicon "codespaces" aria-label="The Codespaces icon" %} {% data variables.product.prodname_codespaces %}]** をクリックします。
diff --git a/translations/ja-JP/data/reusables/codespaces/click-remote-explorer-icon-vscode.md b/translations/ja-JP/data/reusables/codespaces/click-remote-explorer-icon-vscode.md
index 9b1dde968f..c64ee3c814 100644
--- a/translations/ja-JP/data/reusables/codespaces/click-remote-explorer-icon-vscode.md
+++ b/translations/ja-JP/data/reusables/codespaces/click-remote-explorer-icon-vscode.md
@@ -1,13 +1,13 @@
 ---
-ms.openlocfilehash: 008615ba94fed6838f09aa137e6da23e89168573
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: a0a609a6e7a1cab14059012a15b6a08be53d8cbd
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: ja-JP
-ms.lasthandoff: 09/05/2022
-ms.locfileid: "147682488"
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148109211"
 ---
 1. {% data variables.product.prodname_vscode_shortname %} の左サイドバーで、[リモート エクスプローラー] のアイコンをクリックします。
 
    ![{% data variables.product.prodname_vscode %} のリモート エクスプローラー アイコン](/assets/images/help/codespaces/click-remote-explorer-icon-vscode.png)
 
-{% indented_data_reference reusables.codespaces.remote-explorer spaces=3 %}
\ No newline at end of file
+{% indented_data_reference reusables.codespaces.remote-explorer spaces=3 %}
diff --git a/translations/ja-JP/data/reusables/codespaces/codespaces-org-policies-note.md b/translations/ja-JP/data/reusables/codespaces/codespaces-org-policies-note.md
index 8ca2465442..4bbbeeb02f 100644
--- a/translations/ja-JP/data/reusables/codespaces/codespaces-org-policies-note.md
+++ b/translations/ja-JP/data/reusables/codespaces/codespaces-org-policies-note.md
@@ -2,4 +2,4 @@
 
 **Note**: Codespace policies only apply to codespaces for which your organization will be billed. If an individual user creates a codespace for a repository in your organization, and the organization is not billed, then the codespace will not be bound by these policies. For information on how to choose who can create codespaces that are billed to your organization, see "[Enabling {% data variables.product.prodname_github_codespaces %} for your organization](/codespaces/managing-codespaces-for-your-organization/enabling-github-codespaces-for-your-organization#choose-who-can-create-codespaces-that-are-billed-to-your-organization)."
 
-{% endnote %}
\ No newline at end of file
+{% endnote %}
diff --git a/translations/ja-JP/data/reusables/codespaces/links-to-get-started.md b/translations/ja-JP/data/reusables/codespaces/links-to-get-started.md
index 37b7fa79a8..b27dca483d 100644
--- a/translations/ja-JP/data/reusables/codespaces/links-to-get-started.md
+++ b/translations/ja-JP/data/reusables/codespaces/links-to-get-started.md
@@ -1 +1 @@
-To get started with {% data variables.product.prodname_github_codespaces %}, see "[Quickstart for {% data variables.product.prodname_github_codespaces %}](/codespaces/getting-started/quickstart)." For more information on creating or reopening a codespace, see "[Creating a codespace](/codespaces/developing-in-codespaces/creating-a-codespace)" and "[Opening an existing codespace](/codespaces/developing-in-codespaces/opening-an-existing-codespace)." To learn more about how {% data variables.product.prodname_github_codespaces %} works, see "[Deep dive into {% data variables.product.prodname_github_codespaces %}](/codespaces/getting-started/deep-dive)."
\ No newline at end of file
+To get started with {% data variables.product.prodname_github_codespaces %}, see "[Quickstart for {% data variables.product.prodname_github_codespaces %}](/codespaces/getting-started/quickstart)." For more information on creating or reopening a codespace, see "[Creating a codespace](/codespaces/developing-in-codespaces/creating-a-codespace)" and "[Opening an existing codespace](/codespaces/developing-in-codespaces/opening-an-existing-codespace)." To learn more about how {% data variables.product.prodname_github_codespaces %} works, see "[Deep dive into {% data variables.product.prodname_github_codespaces %}](/codespaces/getting-started/deep-dive)."
diff --git a/translations/ja-JP/data/reusables/codespaces/max-number-codespaces.md b/translations/ja-JP/data/reusables/codespaces/max-number-codespaces.md
index b84d9dedb5..808e7692ad 100644
--- a/translations/ja-JP/data/reusables/codespaces/max-number-codespaces.md
+++ b/translations/ja-JP/data/reusables/codespaces/max-number-codespaces.md
@@ -1,9 +1,9 @@
 ---
-ms.openlocfilehash: f2d4527cb962dc9dc65d1aa1cc150f048814a917
-ms.sourcegitcommit: 505b84dc7227e8a5d518a71eb5c7eaa65b38ce0e
+ms.openlocfilehash: 5a221eb6ab8719ebea834e50059bbc6aead1fa79
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: ja-JP
-ms.lasthandoff: 09/09/2022
-ms.locfileid: "147878647"
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148109203"
 ---
-作成できる codespace の数と、同時に実行できる codespace の数には制限があります。 これらの制限は、いくつかの要因によって異なります。 codespace の最大数に達してからさらに作成しようとすると、新しい codespace を作成する前に既存のものを削除する必要があることを示すメッセージが表示されます。
\ No newline at end of file
+作成できる codespace の数と、同時に実行できる codespace の数には制限があります。 これらの制限は、いくつかの要因によって異なります。 codespace の最大数に達してからさらに作成しようとすると、新しい codespace を作成する前に既存のものを削除する必要があることを示すメッセージが表示されます。
diff --git a/translations/ja-JP/data/reusables/codespaces/prebuilds-permission-authorization.md b/translations/ja-JP/data/reusables/codespaces/prebuilds-permission-authorization.md
index 4b49500f87..a21b08a741 100644
--- a/translations/ja-JP/data/reusables/codespaces/prebuilds-permission-authorization.md
+++ b/translations/ja-JP/data/reusables/codespaces/prebuilds-permission-authorization.md
@@ -1,10 +1,10 @@
 ---
-ms.openlocfilehash: 21a587f89a71ccd8e9f1a69aa5423a840f26b9a6
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: c32a9f6f6a799c3653cb17fe89721090fc01d155
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: ja-JP
-ms.lasthandoff: 09/05/2022
-ms.locfileid: "147431627"
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148109195"
 ---
    リポジトリの開発コンテナー構成で他のリポジトリにアクセスするためのアクセス許可が指定されている場合は、認可ページが表示されます。 `devcontainer.json` ファイルでこれを指定する方法について詳しくは、「[codespace 内の他のリポジトリへのアクセスを管理する](/codespaces/managing-your-codespaces/managing-repository-access-for-your-codespaces)」を参照してください。   
 
@@ -18,4 +18,4 @@ ms.locfileid: "147431627"
 
    **注**: このプレビルドを使って codespace を作るユーザーも、これらのアクセス許可を付与するように求められます。
 
-   {% endnote %}
\ No newline at end of file
+   {% endnote %}
diff --git a/translations/ja-JP/data/reusables/codespaces/stopping-a-codespace.md b/translations/ja-JP/data/reusables/codespaces/stopping-a-codespace.md
new file mode 100644
index 0000000000..e41bb8fbb8
--- /dev/null
+++ b/translations/ja-JP/data/reusables/codespaces/stopping-a-codespace.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: 5431cd0a877d3a87e4dd22fc3503bb9f67058b76
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: ja-JP
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148109188"
+---
+codespace はいつでも停止できます。 codespace を停止すると、実行中のすべてのプロセスが停止され、ターミナルの履歴が消去されます。 次に codespace を起動するときに、codespace に保存した変更は引き続き使用できます。 codespace を明示的に停止しない場合、非アクティブからタイムアウトするまで実行され続けます。 詳細については、「[Codespace のタイムアウト](/codespaces/developing-in-codespaces/codespaces-lifecycle#codespaces-timeouts)」を参照してください。
+
+実行中の codespace にのみ CPU 料金が発生します。停止した codespace では、ストレージ コストのみが発生します。
+
+codespace を停止し、再起動したときに、変更を適用したいと思うかもしれません。 たとえば、codespace に使用するマシンの種類を変更した場合、変更を有効にするには、その codespace を停止して再起動する必要があります。 また、エラーや予期しない問題が発生した場合に、codespace を停止し、再起動または削除することもできます。
diff --git a/translations/ja-JP/data/reusables/codespaces/using-codespaces-in-vscode.md b/translations/ja-JP/data/reusables/codespaces/using-codespaces-in-vscode.md
new file mode 100644
index 0000000000..df3eb5c14a
--- /dev/null
+++ b/translations/ja-JP/data/reusables/codespaces/using-codespaces-in-vscode.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 93ed5f6170cc81999a5389dbc94453ac93023db1
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: ja-JP
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148109187"
+---
+{% data variables.product.prodname_vscode_shortname %} で {% data variables.product.prodname_github_codespaces %} を使用するには、{% data variables.product.prodname_codespaces %} 拡張機能をインストールする必要があります。
diff --git a/translations/ja-JP/data/reusables/codespaces/your-codespaces-procedure-step.md b/translations/ja-JP/data/reusables/codespaces/your-codespaces-procedure-step.md
index 7ff974f84e..ff9f666cb8 100644
--- a/translations/ja-JP/data/reusables/codespaces/your-codespaces-procedure-step.md
+++ b/translations/ja-JP/data/reusables/codespaces/your-codespaces-procedure-step.md
@@ -1 +1 @@
-1. Navigate to the "Your codespaces" page at [github.com/codespaces](https://github.com/codespaces).
\ No newline at end of file
+1. Navigate to the "Your codespaces" page at [github.com/codespaces](https://github.com/codespaces).
diff --git a/translations/ja-JP/data/reusables/copilot/dotcom-settings.md b/translations/ja-JP/data/reusables/copilot/dotcom-settings.md
index 2207d65d03..8ad69b4238 100644
--- a/translations/ja-JP/data/reusables/copilot/dotcom-settings.md
+++ b/translations/ja-JP/data/reusables/copilot/dotcom-settings.md
@@ -1,10 +1,10 @@
 ---
-ms.openlocfilehash: e1df21c0657c55fb934b9c1d837a0ee19df7e37b
-ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.openlocfilehash: 224ce401421d3af0e9afa5976695c95ed219a7b5
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: ja-JP
-ms.lasthandoff: 09/10/2022
-ms.locfileid: "147419746"
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148109179"
 ---
 ## {% data variables.product.prodname_copilot %} の設定を {% data variables.product.prodname_dotcom_the_website %} で構成する
 
@@ -28,4 +28,4 @@ ms.locfileid: "147419746"
 
 ## 参考資料
 
-- [{% data variables.product.prodname_copilot %} FAQ](https://github.com/features/copilot/#faq)
\ No newline at end of file
+- [{% data variables.product.prodname_copilot %} FAQ](https://github.com/features/copilot/#faq)
diff --git a/translations/ja-JP/data/reusables/dependabot/beta-security-and-version-updates-onboarding.md b/translations/ja-JP/data/reusables/dependabot/beta-security-and-version-updates-onboarding.md
deleted file mode 100644
index 752b254147..0000000000
--- a/translations/ja-JP/data/reusables/dependabot/beta-security-and-version-updates-onboarding.md
+++ /dev/null
@@ -1,17 +0,0 @@
----
-ms.openlocfilehash: 22d4fde4f9dd7adbb4c9620e9d72e6dc52a716d4
-ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
-ms.translationtype: HT
-ms.contentlocale: ja-JP
-ms.lasthandoff: 09/11/2022
-ms.locfileid: "145138876"
----
-{% ifversion ghes > 3.2 %}
-
-{% note %}
-
-**注意:** Dependabot のセキュリティ アップデートとバージョン アップデートは現在、{% data variables.product.prodname_ghe_cloud %}、および {% data variables.product.prodname_ghe_server %} 3.3 のベータ版で利用できます。 Dependabot アップデートを有効にする手順については、[アカウント管理チームにお問い合せください](https://enterprise.github.com/contact)。
-
-{% endnote %}
-
-{% endif %}
diff --git a/translations/ja-JP/data/reusables/dependabot/beta-security-and-version-updates.md b/translations/ja-JP/data/reusables/dependabot/beta-security-and-version-updates.md
index d1a685249b..a6d2d6cd01 100644
--- a/translations/ja-JP/data/reusables/dependabot/beta-security-and-version-updates.md
+++ b/translations/ja-JP/data/reusables/dependabot/beta-security-and-version-updates.md
@@ -1,4 +1,4 @@
-{% ifversion ghes > 3.2 and ghes < 3.5 %}
+{% ifversion ghes < 3.5 %}
 
 {% note %}
 {% ifversion ghes = 3.4 %}
diff --git a/translations/ja-JP/data/reusables/dependabot/enterprise-enable-dependabot.md b/translations/ja-JP/data/reusables/dependabot/enterprise-enable-dependabot.md
index 844b35d9ea..86180c6b2a 100644
--- a/translations/ja-JP/data/reusables/dependabot/enterprise-enable-dependabot.md
+++ b/translations/ja-JP/data/reusables/dependabot/enterprise-enable-dependabot.md
@@ -1,4 +1,4 @@
-{% ifversion ghes > 3.2 %}
+{% ifversion ghes %}
 
 {% note %}
 
diff --git a/translations/ja-JP/data/reusables/dependency-review/action-enterprise.md b/translations/ja-JP/data/reusables/dependency-review/action-enterprise.md
index 9427c650a2..605e2fc50a 100644
--- a/translations/ja-JP/data/reusables/dependency-review/action-enterprise.md
+++ b/translations/ja-JP/data/reusables/dependency-review/action-enterprise.md
@@ -1,10 +1,10 @@
 ---
-ms.openlocfilehash: 5a31b3124d838bfaad532763c644a8b446dcd0aa
-ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.openlocfilehash: ff7a0c836b3df74110b4613fa032541e0f27d347
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: ja-JP
-ms.lasthandoff: 09/12/2022
-ms.locfileid: "147887834"
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148109163"
 ---
 {% ifversion ghes or ghae %} エンタープライズ所有者とリポジトリへの管理アクセス権を持つユーザーは、{% data variables.product.prodname_dependency_review_action %}をそれぞれエンタープライズとリポジトリに追加できます。
-{% endif %}
\ No newline at end of file
+{% endif %}
diff --git a/translations/ja-JP/data/reusables/dependency-review/beta.md b/translations/ja-JP/data/reusables/dependency-review/beta.md
deleted file mode 100644
index c009e2fc88..0000000000
--- a/translations/ja-JP/data/reusables/dependency-review/beta.md
+++ /dev/null
@@ -1,15 +0,0 @@
----
-ms.openlocfilehash: b55c1d61ba8da90884c50184240d2aea8e8b0ee9
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
-ms.translationtype: HT
-ms.contentlocale: ja-JP
-ms.lasthandoff: 09/05/2022
-ms.locfileid: "145138699"
----
-{% ifversion ghes = 3.2 %} {% note %}
-
-**注:** 依存関係のレビューは現在ベータ版であり、変更される可能性があります。
-
-{% endnote %}
-
-{% endif %}
diff --git a/translations/ja-JP/data/reusables/education/about-github-community-exchange-intro.md b/translations/ja-JP/data/reusables/education/about-github-community-exchange-intro.md
index 1612ffd207..88af5246dd 100644
--- a/translations/ja-JP/data/reusables/education/about-github-community-exchange-intro.md
+++ b/translations/ja-JP/data/reusables/education/about-github-community-exchange-intro.md
@@ -1,9 +1,9 @@
 ---
-ms.openlocfilehash: 3419a29bb8fad04801ff8e2846c11da684f61910
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: 82c3a5fa91313a6f2e27e58b62c706ea5b0ef4d9
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: ja-JP
-ms.lasthandoff: 09/05/2022
-ms.locfileid: "147410789"
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148109644"
 ---
-{% data variables.product.prodname_community_exchange %} は、{% data variables.product.prodname_global_campus %} ポータル内の学生コミュニティです。 そこでは、学生は、自分のプロジェクトを公開し、コラボレーターやメンテナンス担当者を必要とする他の学生リポジトリを見つけることができます。
\ No newline at end of file
+{% data variables.product.prodname_community_exchange %} は、{% data variables.product.prodname_global_campus %} ポータル内の学生コミュニティです。 そこでは、学生は、自分のプロジェクトを公開し、コラボレーターやメンテナンス担当者を必要とする他の学生リポジトリを見つけることができます。
diff --git a/translations/ja-JP/data/reusables/education/submit-application.md b/translations/ja-JP/data/reusables/education/submit-application.md
index d881e524c5..5014f7638f 100644
--- a/translations/ja-JP/data/reusables/education/submit-application.md
+++ b/translations/ja-JP/data/reusables/education/submit-application.md
@@ -7,4 +7,4 @@
 
     {% endnote %}
 
- If your application is approved, you'll receive a confirmation email. Applications are usually processed within a few days, but it may take longer during peak times, such as during the start of a new semester.
\ No newline at end of file
+ If your application is approved, you'll receive a confirmation email. Applications are usually processed within a few days, but it may take longer during peak times, such as during the start of a new semester.
diff --git a/translations/ja-JP/data/reusables/enterprise-licensing/about-license-sync.md b/translations/ja-JP/data/reusables/enterprise-licensing/about-license-sync.md
index 82b710c595..5111e2627b 100644
--- a/translations/ja-JP/data/reusables/enterprise-licensing/about-license-sync.md
+++ b/translations/ja-JP/data/reusables/enterprise-licensing/about-license-sync.md
@@ -1,9 +1,9 @@
 ---
-ms.openlocfilehash: 12b28d4c3665573a1cfc0d56e2a61b616ee0a9ec
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: fbb3311774be7ef276adaba8461a100f73c1c6bb
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: ja-JP
-ms.lasthandoff: 09/05/2022
-ms.locfileid: "147572673"
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148109643"
 ---
-複数の {% data variables.product.prodname_enterprise %} 環境を使用しているユーザーが 1 つのライセンスのみを使用するためには、環境間でライセンス利用状況を同期する必要があります。 その後、ユーザー アカウントに関連付けられているメール アドレスに基づいて、{% data variables.product.company_short %} によりユーザーの重複が除去されます。 詳しくは、[{% data variables.product.prodname_enterprise %} のライセンス利用状況のトラブルシューティング](/billing/managing-your-license-for-github-enterprise/troubleshooting-license-usage-for-github-enterprise#about-the-calculation-of-consumed-licenses)に関するページを参照してください。
\ No newline at end of file
+複数の {% data variables.product.prodname_enterprise %} 環境を使用しているユーザーが 1 つのライセンスのみを使用するためには、環境間でライセンス利用状況を同期する必要があります。 その後、ユーザー アカウントに関連付けられているメール アドレスに基づいて、{% data variables.product.company_short %} によりユーザーの重複が除去されます。 詳しくは、[{% data variables.product.prodname_enterprise %} のライセンス利用状況のトラブルシューティング](/billing/managing-your-license-for-github-enterprise/troubleshooting-license-usage-for-github-enterprise#about-the-calculation-of-consumed-licenses)に関するページを参照してください。
diff --git a/translations/ja-JP/data/reusables/enterprise/about-github-for-enterprises.md b/translations/ja-JP/data/reusables/enterprise/about-github-for-enterprises.md
index 37112ad7ad..6bf5f25473 100644
--- a/translations/ja-JP/data/reusables/enterprise/about-github-for-enterprises.md
+++ b/translations/ja-JP/data/reusables/enterprise/about-github-for-enterprises.md
@@ -1,9 +1,9 @@
 ---
-ms.openlocfilehash: de369a16e292dac48d6e6aee2907e28ae1f46af3
-ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.openlocfilehash: a708ef37153f09729c17dd9a06f258cb64579e6b
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: ja-JP
-ms.lasthandoff: 09/11/2022
-ms.locfileid: "147390433"
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148109635"
 ---
-企業が {% data variables.product.company_short %} の製品を使ってソフトウェア開発ライフサイクルをサポートする方法について、詳しくは、「[エンタープライズ向け {% data variables.product.prodname_dotcom %}](/admin/overview/about-github-for-enterprises) について」を参照してください。
\ No newline at end of file
+企業が {% data variables.product.company_short %} の製品を使ってソフトウェア開発ライフサイクルをサポートする方法について、詳しくは、「[エンタープライズ向け {% data variables.product.prodname_dotcom %}](/admin/overview/about-github-for-enterprises) について」を参照してください。
diff --git a/translations/ja-JP/data/reusables/enterprise/repository-caching-release-phase.md b/translations/ja-JP/data/reusables/enterprise/repository-caching-release-phase.md
index 6dd6f32b4f..31a2b15709 100644
--- a/translations/ja-JP/data/reusables/enterprise/repository-caching-release-phase.md
+++ b/translations/ja-JP/data/reusables/enterprise/repository-caching-release-phase.md
@@ -1,13 +1,7 @@
----
-ms.openlocfilehash: 4d2db8622a5ddf12d83595e903e3b2ba1774727b
-ms.sourcegitcommit: 5b1461b419dbef60ae9dbdf8e905a4df30fc91b7
-ms.translationtype: HT
-ms.contentlocale: ja-JP
-ms.lasthandoff: 09/10/2022
-ms.locfileid: "147878943"
----
-{% ifversion ghes < 3.6 %} {% note %}
+{% ifversion ghes < 3.6 %}
+{% note %}
 
-**注:** リポジトリ キャッシュは現在ベータ版であり、変更される可能性があります。
+**Note:** Repository caching is currently in beta and subject to change.
 
-{% endnote %} {% endif %}
\ No newline at end of file
+{% endnote %}
+{% endif %}
diff --git a/translations/ja-JP/data/reusables/enterprise/upgrade-ghes-for-actions.md b/translations/ja-JP/data/reusables/enterprise/upgrade-ghes-for-actions.md
deleted file mode 100644
index 73e58ca754..0000000000
--- a/translations/ja-JP/data/reusables/enterprise/upgrade-ghes-for-actions.md
+++ /dev/null
@@ -1,10 +0,0 @@
----
-ms.openlocfilehash: ce032c1829e6b93f7adcd62e1b731953669ffb91
-ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
-ms.translationtype: HT
-ms.contentlocale: ja-JP
-ms.lasthandoff: 09/10/2022
-ms.locfileid: "145111893"
----
-{% ifversion ghes < 3.3 %} {% data variables.product.prodname_actions %} は、{% data variables.product.prodname_ghe_server %} 3.0 以降で使用できます。 以前のバージョンの {% data variables.product.prodname_ghe_server %} を使用している場合は、{% data variables.product.prodname_actions %} を使用するようにアップグレードする必要があります。 {% data variables.product.prodname_ghe_server %} インスタンスのアップグレードの詳細については、「[新しいリリースへのアップグレードについて](/admin/overview/about-upgrades-to-new-releases)」を参照してください。
-{% endif %}
diff --git a/translations/ja-JP/data/reusables/enterprise_backup_utilities/enterprise-backup-utils-directory.md b/translations/ja-JP/data/reusables/enterprise_backup_utilities/enterprise-backup-utils-directory.md
index 630dfc76aa..afa6a21c84 100644
--- a/translations/ja-JP/data/reusables/enterprise_backup_utilities/enterprise-backup-utils-directory.md
+++ b/translations/ja-JP/data/reusables/enterprise_backup_utilities/enterprise-backup-utils-directory.md
@@ -1,9 +1,9 @@
 ---
-ms.openlocfilehash: 5c1cf00625a805fc4054a78bc4ac675a161a1c1b
-ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794
+ms.openlocfilehash: 5302e6f9d952c4a8881d1f28fe7ea847a70d0efe
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: ja-JP
-ms.lasthandoff: 09/09/2022
-ms.locfileid: "147861699"
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148109628"
 ---
-1. バックアップ ホストで、{% data variables.product.prodname_enterprise_backup_utilities %} ディレクトリ (通常は `backup-utils`) に移動します。
\ No newline at end of file
+1. バックアップ ホストで、{% data variables.product.prodname_enterprise_backup_utilities %} ディレクトリ (通常は `backup-utils`) に移動します。
diff --git a/translations/ja-JP/data/reusables/enterprise_backup_utilities/enterprise-backup-utils-verify-upgrade.md b/translations/ja-JP/data/reusables/enterprise_backup_utilities/enterprise-backup-utils-verify-upgrade.md
index cae65131ea..484c57ea24 100644
--- a/translations/ja-JP/data/reusables/enterprise_backup_utilities/enterprise-backup-utils-verify-upgrade.md
+++ b/translations/ja-JP/data/reusables/enterprise_backup_utilities/enterprise-backup-utils-verify-upgrade.md
@@ -1,10 +1,10 @@
 ---
-ms.openlocfilehash: 8289b9aadf88b85cf8d4dc71d2fc74db42c01289
-ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794
+ms.openlocfilehash: 76be6868da14b227e1b0fbc16b8c9f913b4f04e0
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: ja-JP
-ms.lasthandoff: 09/09/2022
-ms.locfileid: "147861688"
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148109627"
 ---
 1. 正常にアップグレードされたことを確認するには、次のコマンドを実行します。
   ```shell
@@ -15,4 +15,4 @@ ms.locfileid: "147861688"
   ```shell
   ./bin/ghe-host-check
   ```
-  
\ No newline at end of file
+  
diff --git a/translations/ja-JP/data/reusables/enterprise_enterprise_support/installing-releases.md b/translations/ja-JP/data/reusables/enterprise_enterprise_support/installing-releases.md
index 444818f8fe..f9044ae820 100644
--- a/translations/ja-JP/data/reusables/enterprise_enterprise_support/installing-releases.md
+++ b/translations/ja-JP/data/reusables/enterprise_enterprise_support/installing-releases.md
@@ -4,4 +4,4 @@
 
 To ensure that {% data variables.location.product_location %} is stable, you must install and implement {% data variables.product.prodname_ghe_server %} releases. Installing {% data variables.product.prodname_ghe_server %} releases ensures that you have the latest features, modifications, and enhancements as well as any updates to features, code corrections, patches or other general updates and fixes to {% data variables.product.prodname_ghe_server %}.
 
-{% endif %}
\ No newline at end of file
+{% endif %}
diff --git a/translations/ja-JP/data/reusables/enterprise_management_console/unlocking-management-console-with-shell.md b/translations/ja-JP/data/reusables/enterprise_management_console/unlocking-management-console-with-shell.md
new file mode 100644
index 0000000000..95b7ba2b5a
--- /dev/null
+++ b/translations/ja-JP/data/reusables/enterprise_management_console/unlocking-management-console-with-shell.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 88d76852d3e379e556b364b31199800e73ecd0c7
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: ja-JP
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148109363"
+---
+{% data variables.enterprise.management_console %} をただちにロック解除するには、管理シェルから `ghe-reactivate-admin-login` コマンドを使用します。 詳細については、「[コマンド ライン ユーティリティ](/enterprise/admin/guides/installation/command-line-utilities#ghe-reactivate-admin-login)」と「[管理シェルへのアクセス (SSH)](/enterprise/admin/guides/installation/accessing-the-administrative-shell-ssh/)」を参照してください。
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/gated-features/code-scanning.md b/translations/ja-JP/data/reusables/gated-features/code-scanning.md
index 87bb7275dd..3512f732b5 100644
--- a/translations/ja-JP/data/reusables/gated-features/code-scanning.md
+++ b/translations/ja-JP/data/reusables/gated-features/code-scanning.md
@@ -1,13 +1,17 @@
-{%- ifversion fpt %}
-{% data variables.product.prodname_code_scanning_capc %} is available for all public repositories on {% data variables.product.prodname_dotcom_the_website %}. {% data variables.product.prodname_code_scanning_capc %} is also available for private repositories owned by organizations that use {% data variables.product.prodname_ghe_cloud %} and have a license for {% data variables.product.prodname_GH_advanced_security %}.
+---
+ms.openlocfilehash: 0ea67362c541ed183fec256765d5bb9d1fd18e3c
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: ja-JP
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148109355"
+---
+{%- ifversion fpt %} {% data variables.product.prodname_code_scanning_capc %} は、{% data variables.product.prodname_dotcom_the_website %} のすべてのパブリック リポジトリに使用できます。 {% data variables.product.prodname_code_scanning_capc %} は、{% data variables.product.prodname_ghe_cloud %} を使用していて {% data variables.product.prodname_GH_advanced_security %} のライセンスを持つ Organization によって所有されるリポジトリで使用できます。
 
-{%- elsif ghec %}
-{% data variables.product.prodname_code_scanning_capc %} is available for all public repositories on {% data variables.product.prodname_dotcom_the_website %}. To use {% data variables.product.prodname_code_scanning %} in a private repository owned by an organization, you must have a license for {% data variables.product.prodname_GH_advanced_security %}.
+{%- elsif ghec %} {% data variables.product.prodname_code_scanning_capc %} は、{% data variables.product.prodname_dotcom_the_website %} のすべてのパブリック リポジトリに使用できます。 Organization によって所有されるプライベート リポジトリで {% data variables.product.prodname_code_scanning %} を使うには、{% data variables.product.prodname_GH_advanced_security %} のライセンスが必要です。
 
-{%- elsif ghes %}
-{% data variables.product.prodname_code_scanning_capc %} is available for organization-owned repositories in {% data variables.product.product_name %}. This feature requires a license for {% data variables.product.prodname_GH_advanced_security %}.
+{%- elsif ghes %} {% data variables.product.prodname_code_scanning_capc %} は、{% data variables.product.product_name %} の Organization 所有のリポジトリで利用できます。 この機能には、{% data variables.product.prodname_GH_advanced_security %} のライセンスが必要です。
 
-{%- elsif ghae %}
-{% data variables.product.prodname_code_scanning_capc %} is available for organization-owned repositories in {% data variables.product.product_name %}. This is a {% data variables.product.prodname_GH_advanced_security %} feature (free during the beta release).
+{%- elsif ghae %} {% data variables.product.prodname_code_scanning_capc %} は、{% data variables.product.product_name %} の Organization 所有のリポジトリで利用できます。 これは {% data variables.product.prodname_GH_advanced_security %} の機能です (ベータ リリース中は無料)。
 
-{%- endif %} {% data reusables.advanced-security.more-info-ghas %}
\ No newline at end of file
+{%- endif %} {% data reusables.advanced-security.more-info-ghas %}
diff --git a/translations/ja-JP/data/reusables/gated-features/historical-insights-for-projects.md b/translations/ja-JP/data/reusables/gated-features/historical-insights-for-projects.md
index 41cd73318a..73b73c4c8c 100644
--- a/translations/ja-JP/data/reusables/gated-features/historical-insights-for-projects.md
+++ b/translations/ja-JP/data/reusables/gated-features/historical-insights-for-projects.md
@@ -1,9 +1,9 @@
 ---
-ms.openlocfilehash: fd865e1bcf0fb2af69739d4d81fa27796e2e0b33
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: f28c558acbb1dacd503964146c0522145d44948b
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: ja-JP
-ms.lasthandoff: 09/05/2022
-ms.locfileid: "147424210"
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148109347"
 ---
-履歴グラフは、Organization 向けの {% data variables.product.prodname_team %} と {% data variables.product.prodname_ghe_cloud %} で利用できます。 Organization 向けの {% data variables.product.prodname_team %} および {% data variables.product.prodname_ghe_cloud %} と、ユーザー向けの {% data variables.product.prodname_pro %} で、プライベート プロジェクトに無制限のグラフを保存できます。 パブリック プロジェクトを使用しているユーザーと Organization も、無制限のグラフを保存できます。 {% data variables.product.prodname_free_team %} またはレガシ プランを使用しているユーザーと Organization は、プライベート プロジェクトに 2 つのグラフを保存できます。  {% data reusables.gated-features.more-info %}
\ No newline at end of file
+履歴グラフは、Organization 向けの {% data variables.product.prodname_team %} と {% data variables.product.prodname_ghe_cloud %} で利用できます。 Organization 向けの {% data variables.product.prodname_team %} および {% data variables.product.prodname_ghe_cloud %} と、ユーザー向けの {% data variables.product.prodname_pro %} で、プライベート プロジェクトに無制限のグラフを保存できます。 パブリック プロジェクトを使用しているユーザーと Organization も、無制限のグラフを保存できます。 {% data variables.product.prodname_free_team %} またはレガシ プランを使用しているユーザーと Organization は、プライベート プロジェクトに 2 つのグラフを保存できます。  {% data reusables.gated-features.more-info %}
diff --git a/translations/ja-JP/data/reusables/gated-features/hosted-runners.md b/translations/ja-JP/data/reusables/gated-features/hosted-runners.md
index d983a32737..669390e197 100644
--- a/translations/ja-JP/data/reusables/gated-features/hosted-runners.md
+++ b/translations/ja-JP/data/reusables/gated-features/hosted-runners.md
@@ -1,9 +1,9 @@
 ---
-ms.openlocfilehash: 2d2d2bc1f01e722c0f30cf11b642033a762c429c
-ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794
+ms.openlocfilehash: 54a0c4cae87acc79c4d4763521f11da1a37cd2d6
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: ja-JP
-ms.lasthandoff: 09/09/2022
-ms.locfileid: "147853683"
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148109340"
 ---
-{% data variables.actions.hosted_runner %} 機能は、{% data variables.product.prodname_team %} または {% data variables.product.prodname_ghe_cloud %} プランを使用している Organization やエンタープライズでは現在ベータ版で、これは今後変わる可能性があります。 ベータ版の使用を求める場合には、[サインアップ ページ](https://github.com/features/github-hosted-runners/signup)にアクセスします。
\ No newline at end of file
+{% data variables.actions.hosted_runner %} 機能は、{% data variables.product.prodname_team %} または {% data variables.product.prodname_ghe_cloud %} プランを使用している Organization やエンタープライズでは現在ベータ版で、これは今後変わる可能性があります。 ベータ版の使用を求める場合には、[サインアップ ページ](https://github.com/features/github-hosted-runners/signup)にアクセスします。
diff --git a/translations/ja-JP/data/reusables/getting-started/bearer-vs-token.md b/translations/ja-JP/data/reusables/getting-started/bearer-vs-token.md
index 6daf30d07d..741ec870b5 100644
--- a/translations/ja-JP/data/reusables/getting-started/bearer-vs-token.md
+++ b/translations/ja-JP/data/reusables/getting-started/bearer-vs-token.md
@@ -1,9 +1,9 @@
 ---
-ms.openlocfilehash: a6189685e97d4aeabb737421203acb96ccd0f61c
-ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794
+ms.openlocfilehash: 43a23bdc9abc48a087e62f93a6d01a1aaabe0eb0
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: ja-JP
-ms.lasthandoff: 09/09/2022
-ms.locfileid: "147718224"
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148109339"
 ---
-ほとんどの場合は、`Authorization: Bearer` または `Authorization: token` を使用してトークンを渡すことができます。 ただし、JSON Web トークン (JWT) を渡す場合は、`Authorization: Bearer` を使用する必要があります。
\ No newline at end of file
+ほとんどの場合は、`Authorization: Bearer` または `Authorization: token` を使用してトークンを渡すことができます。 ただし、JSON Web トークン (JWT) を渡す場合は、`Authorization: Bearer` を使用する必要があります。
diff --git a/translations/ja-JP/data/reusables/getting-started/math-and-diagrams.md b/translations/ja-JP/data/reusables/getting-started/math-and-diagrams.md
index 8c6f60a5eb..59cadf5151 100644
--- a/translations/ja-JP/data/reusables/getting-started/math-and-diagrams.md
+++ b/translations/ja-JP/data/reusables/getting-started/math-and-diagrams.md
@@ -1,9 +1,9 @@
 ---
-ms.openlocfilehash: d68b3fb76a086f8ba99cd3c968b547f9d94eb8c9
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: ff4fa65700cd685f99a3e94541df48a2f5e77985
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: ja-JP
-ms.lasthandoff: 09/05/2022
-ms.locfileid: "147529763"
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148109332"
 ---
-{% ifversion mermaid %}Markdown を使用して、レンダリングされた数式、ダイアグラム、マップ、3D モデルを Wiki に追加できます。 レンダリングされた数式の作成の詳細については、「[数式の記述](/get-started/writing-on-github/working-with-advanced-formatting/writing-mathematical-expressions)」を参照してください。 ダイアグラム、マップ、3D モデルの作成の詳細については、「[ダイアグラムの作成](/get-started/writing-on-github/working-with-advanced-formatting/creating-diagrams)」を参照してください。{% endif %}
\ No newline at end of file
+{% ifversion mermaid %}Markdown を使用して、レンダリングされた数式、ダイアグラム、マップ、3D モデルを Wiki に追加できます。 レンダリングされた数式の作成の詳細については、「[数式の記述](/get-started/writing-on-github/working-with-advanced-formatting/writing-mathematical-expressions)」を参照してください。 ダイアグラム、マップ、3D モデルの作成の詳細については、「[ダイアグラムの作成](/get-started/writing-on-github/working-with-advanced-formatting/creating-diagrams)」を参照してください。{% endif %}
diff --git a/translations/ja-JP/data/reusables/git/no-credential-manager.md b/translations/ja-JP/data/reusables/git/no-credential-manager.md
index ab4384f3b5..45bee44340 100644
--- a/translations/ja-JP/data/reusables/git/no-credential-manager.md
+++ b/translations/ja-JP/data/reusables/git/no-credential-manager.md
@@ -1,9 +1,9 @@
 ---
-ms.openlocfilehash: c1773da7070760a6a40d198a66f7646536d7a236
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: af8f3c7c0c5378080257097644571e8a0d04a840
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: ja-JP
-ms.lasthandoff: 09/05/2022
-ms.locfileid: "147687147"
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148109331"
 ---
-- 出力に資格情報マネージャーの名前が含まれていない場合は、資格情報マネージャーが構成されていないため、次の手順に進むことができます。
\ No newline at end of file
+- 出力に資格情報マネージャーの名前が含まれていない場合は、資格情報マネージャーが構成されていないため、次の手順に進むことができます。
diff --git a/translations/ja-JP/data/reusables/github-ae/saml-idp-table.md b/translations/ja-JP/data/reusables/github-ae/saml-idp-table.md
index c2ef59482a..dfa948ec5f 100644
--- a/translations/ja-JP/data/reusables/github-ae/saml-idp-table.md
+++ b/translations/ja-JP/data/reusables/github-ae/saml-idp-table.md
@@ -1,8 +1,16 @@
+---
+ms.openlocfilehash: 8afd93954b55495a93b01ca1ed2c0a58946ffbd5
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: ja-JP
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148109324"
+---
 {% ifversion ghae %}
 
-IdP | SAML | User provisioning | Team mapping| 
+IdP | SAML | ユーザー プロビジョニング | Team マッピング| 
 --- | --- | ---------------- | --------- |
 [Azure Active Directory (Azure AD)](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad) | {% octicon "check-circle-fill" aria-label="The check icon" %} | {% octicon "check-circle-fill" aria-label="The check icon" %}| {% octicon "check-circle-fill" aria-label="The check icon" %} |
-[Okta](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/configuring-authentication-and-provisioning-for-your-enterprise-using-okta) | {% octicon "check-circle-fill" aria-label="The check icon" %}[<sup>Beta</sup>](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/configuring-authentication-and-provisioning-for-your-enterprise-using-okta)| {% octicon "check-circle-fill" aria-label="The check icon" %}[<sup>Beta</sup>](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/configuring-authentication-and-provisioning-for-your-enterprise-using-okta)| {% octicon "check-circle-fill" aria-label= "The check icon" %}[<sup>Beta</sup>](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/mapping-okta-groups-to-teams) |
+[Okta](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/configuring-authentication-and-provisioning-for-your-enterprise-using-okta) | {% octicon "check-circle-fill" aria-label="The check icon" %}[<sup>ベータ版</sup>](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/configuring-authentication-and-provisioning-for-your-enterprise-using-okta)| {% octicon "check-circle-fill" aria-label="The check icon" %}[<sup>ベータ版</sup>](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/configuring-authentication-and-provisioning-for-your-enterprise-using-okta)| {% octicon "check-circle-fill" aria-label= "The check icon" %}[<sup>ベータ版</sup>](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/mapping-okta-groups-to-teams) |
 
 {% endif %}
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/gpg/configure-ssh-signing.md b/translations/ja-JP/data/reusables/gpg/configure-ssh-signing.md
index 137509f34f..a16d5d5b94 100644
--- a/translations/ja-JP/data/reusables/gpg/configure-ssh-signing.md
+++ b/translations/ja-JP/data/reusables/gpg/configure-ssh-signing.md
@@ -1,12 +1,12 @@
 ---
-ms.openlocfilehash: fb14a6e9eb1b7ac1846b7b7e39fa1d6b7f000840
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: 0a0e572422bee311ca8adb2b40c81a00907c0dfb
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: ja-JP
-ms.lasthandoff: 09/05/2022
-ms.locfileid: "147653405"
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148109620"
 ---
 1. コミットやタグの署名に SSH を使うよう Git を構成します。
   ```bash
   $ git config --global gpg.format ssh
-  ```
\ No newline at end of file
+  ```
diff --git a/translations/ja-JP/data/reusables/identity-and-permissions/about-adding-ip-allow-list-entries.md b/translations/ja-JP/data/reusables/identity-and-permissions/about-adding-ip-allow-list-entries.md
index e2943e5a06..3c08dedb53 100644
--- a/translations/ja-JP/data/reusables/identity-and-permissions/about-adding-ip-allow-list-entries.md
+++ b/translations/ja-JP/data/reusables/identity-and-permissions/about-adding-ip-allow-list-entries.md
@@ -1,11 +1,11 @@
 ---
-ms.openlocfilehash: 6775f1ca71684e74de0fedce4cb7e6c6b15c2820
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: db4c80c49c4e3effe99073f29010147f3a1efc08
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: ja-JP
-ms.lasthandoff: 09/05/2022
-ms.locfileid: "147682895"
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148108934"
 ---
 それぞれに IP アドレスまたはアドレス範囲を含むエントリを追加することで、IP 許可リストを作成できます。{% ifversion ip-allow-list-address-check %} エントリの追加が完了したら、特定の IP アドレスがリスト内のいずれかの有効なエントリによって許可されるかどうかを確認できます。{% endif %}
 
-Enterprise 内の Organization が所有する {% ifversion ghae %}Enterprise{% else %} プライベート アセット{% endif %}へのアクセスがリストによって制限される前に、許可 IP アドレスも有効にする必要があります。
\ No newline at end of file
+Enterprise 内の Organization が所有する {% ifversion ghae %}Enterprise{% else %} プライベート アセット{% endif %}へのアクセスがリストによって制限される前に、許可 IP アドレスも有効にする必要があります。
diff --git a/translations/ja-JP/data/reusables/identity-and-permissions/about-checking-ip-address.md b/translations/ja-JP/data/reusables/identity-and-permissions/about-checking-ip-address.md
index 7f5fed6b12..4d37fc5e1d 100644
--- a/translations/ja-JP/data/reusables/identity-and-permissions/about-checking-ip-address.md
+++ b/translations/ja-JP/data/reusables/identity-and-permissions/about-checking-ip-address.md
@@ -1,9 +1,9 @@
 ---
-ms.openlocfilehash: ad162035ba2dcbb3c38f368dc7376b8fd5dd0b0c
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: d7e7459f3ed9898a892c8b3504a32c1106e69442
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: ja-JP
-ms.lasthandoff: 09/05/2022
-ms.locfileid: "147682908"
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148108929"
 ---
-許可リストが現時点で有効になっていなくても、特定の IP アドレスがリスト内のいずれかの有効なエントリによって許可されるかどうかを確認できます。
\ No newline at end of file
+許可リストが現時点で有効になっていなくても、特定の IP アドレスがリスト内のいずれかの有効なエントリによって許可されるかどうかを確認できます。
diff --git a/translations/ja-JP/data/reusables/identity-and-permissions/about-editing-ip-allow-list-entries.md b/translations/ja-JP/data/reusables/identity-and-permissions/about-editing-ip-allow-list-entries.md
index d4e1a2e007..f8ace38686 100644
--- a/translations/ja-JP/data/reusables/identity-and-permissions/about-editing-ip-allow-list-entries.md
+++ b/translations/ja-JP/data/reusables/identity-and-permissions/about-editing-ip-allow-list-entries.md
@@ -1,12 +1,12 @@
 ---
-ms.openlocfilehash: 0f621e8e83d20f58e208fd9285082441fe29aa74
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: 8f78a77c83ea498d8d41a0deff20903062542479
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: ja-JP
-ms.lasthandoff: 09/05/2022
-ms.locfileid: "147682894"
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148108928"
 ---
 IP 許可リストのエントリを編集できます。 有効なエントリを編集すると、変更がすぐに適用されます。 
 
 {% ifversion ip-allow-list-address-check %}エントリの編集が完了したら、特定の IP アドレスがリスト内のいずれかの有効なエントリによって許可されるかどうかを確認できます。
-{% endif %}
\ No newline at end of file
+{% endif %}
diff --git a/translations/ja-JP/data/reusables/identity-and-permissions/about-enabling-allowed-ip-addresses.md b/translations/ja-JP/data/reusables/identity-and-permissions/about-enabling-allowed-ip-addresses.md
index d8eb3f5cf3..16814a5064 100644
--- a/translations/ja-JP/data/reusables/identity-and-permissions/about-enabling-allowed-ip-addresses.md
+++ b/translations/ja-JP/data/reusables/identity-and-permissions/about-enabling-allowed-ip-addresses.md
@@ -1,12 +1,12 @@
 ---
-ms.openlocfilehash: 4a8eaf38855e436884a6abdfc8d0b21473e71904
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: 095556009ed66ca0b687734f62f21c70fd87699a
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: ja-JP
-ms.lasthandoff: 09/05/2022
-ms.locfileid: "147682905"
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148108923"
 ---
 IP 許可リストを作成すると、許可 IP アドレスを有効にすることができます。 許可 IP アドレスを有効にすると、IP 許可リスト内のいずれかの有効なエントリが、{% data variables.product.company_short %} によってすぐに適用されます。
 
 {% ifversion ip-allow-list-address-check %} 許可 IP アドレスを有効にする前に、特定の IP アドレスがリスト内のいずれかの有効なエントリによって許可されるかどうかを確認できます。 詳しくは、「[IP アドレスが許可されているかどうかを確認する](#checking-if-an-ip-address-is-permitted)」を参照してください。
-{% endif %}
\ No newline at end of file
+{% endif %}
diff --git a/translations/ja-JP/data/reusables/identity-and-permissions/check-ip-address-step.md b/translations/ja-JP/data/reusables/identity-and-permissions/check-ip-address-step.md
index 1f41542e94..eb6f69a26c 100644
--- a/translations/ja-JP/data/reusables/identity-and-permissions/check-ip-address-step.md
+++ b/translations/ja-JP/data/reusables/identity-and-permissions/check-ip-address-step.md
@@ -1,10 +1,10 @@
 ---
-ms.openlocfilehash: 767afd2426bcfba04a2eb3c845b1041e65d006f9
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: 5eaf0aa831a27f61216ae9574df61fe7445f2f94
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: ja-JP
-ms.lasthandoff: 09/05/2022
-ms.locfileid: "147682888"
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148109619"
 ---
 1. [IP アドレスの確認] で、IP アドレスを入力します。
-   ![[IP アドレスの確認] テキスト フィールドのスクリーンショット](/assets/images/help/security/check-ip-address.png)
\ No newline at end of file
+   ![[IP アドレスの確認] テキスト フィールドのスクリーンショット](/assets/images/help/security/check-ip-address.png)
diff --git a/translations/ja-JP/data/reusables/identity-and-permissions/check-ip-address.md b/translations/ja-JP/data/reusables/identity-and-permissions/check-ip-address.md
index 0dc3ab1849..21bc6ff94a 100644
--- a/translations/ja-JP/data/reusables/identity-and-permissions/check-ip-address.md
+++ b/translations/ja-JP/data/reusables/identity-and-permissions/check-ip-address.md
@@ -1,11 +1,11 @@
 ---
-ms.openlocfilehash: bc619567dc896525b2c11f30ef4b721e17279618
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: 7b848e4c3bb4a9a4578e3f1ff92f6249dd20c699
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: ja-JP
-ms.lasthandoff: 09/05/2022
-ms.locfileid: "147682902"
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148109612"
 ---
 {%- ifversion ip-allow-list-address-check %}
 1. 必要に応じて、特定の IP アドレスがリスト内のいずれかの有効なエントリによって許可されるかどうかを確認できます。 詳しくは、「[IP アドレスが許可されているかどうかを確認する](#checking-if-an-ip-address-is-permitted)」を参照してください。
-{%- endif %}
\ No newline at end of file
+{%- endif %}
diff --git a/translations/ja-JP/data/reusables/identity-and-permissions/ipv6-allow-lists.md b/translations/ja-JP/data/reusables/identity-and-permissions/ipv6-allow-lists.md
index 0746e33cba..c7680a186a 100644
--- a/translations/ja-JP/data/reusables/identity-and-permissions/ipv6-allow-lists.md
+++ b/translations/ja-JP/data/reusables/identity-and-permissions/ipv6-allow-lists.md
@@ -1,13 +1,13 @@
 ---
-ms.openlocfilehash: fdfc231ccda60a08923fd8cd91160fea9389e9b0
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: 1df7a9480c4cfd3a5edfc1ee16cd2a3259921e6b
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: ja-JP
-ms.lasthandoff: 09/05/2022
-ms.locfileid: "147707311"
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148109531"
 ---
 {% ifversion fpt or ghec %} {% note %}
 
 **注:** {% data variables.product.company_short %} では、IPv6 のサポートを段階的にロールアウトしています。 {% data variables.product.prodname_dotcom %} サービスには引き続き IPv6 のサポートが追加されるため、{% data variables.product.prodname_dotcom %} ユーザーの IPv6 アドレスの認識を開始できます。 アクセスの中断の可能性を防ぐには、必要な IPv6 アドレスが自分の IP 許可リストに確実に追加されている状態にしてください。
 
-{% endnote %} {% endif %}
\ No newline at end of file
+{% endnote %} {% endif %}
diff --git a/translations/ja-JP/data/reusables/identity-and-permissions/vigilant-mode-beta-note.md b/translations/ja-JP/data/reusables/identity-and-permissions/vigilant-mode-beta-note.md
index 1913d6e459..8c5bcb44ec 100644
--- a/translations/ja-JP/data/reusables/identity-and-permissions/vigilant-mode-beta-note.md
+++ b/translations/ja-JP/data/reusables/identity-and-permissions/vigilant-mode-beta-note.md
@@ -4,4 +4,4 @@
 **Note:** Vigilant mode is currently in beta and subject to change.
 
 {% endnote %}
-{% endif %}
\ No newline at end of file
+{% endif %}
diff --git a/translations/ja-JP/data/reusables/notifications-v2/custom-notification-types.md b/translations/ja-JP/data/reusables/notifications-v2/custom-notification-types.md
index cd318e85fc..b6445e487a 100644
--- a/translations/ja-JP/data/reusables/notifications-v2/custom-notification-types.md
+++ b/translations/ja-JP/data/reusables/notifications-v2/custom-notification-types.md
@@ -1 +1 @@
-issues, pull requests, releases, security alerts, or discussions
\ No newline at end of file
+issues, pull requests, releases, security alerts, or discussions
diff --git a/translations/ja-JP/data/reusables/organizations/about-following-organizations.md b/translations/ja-JP/data/reusables/organizations/about-following-organizations.md
index 91b83567e4..d42b31bf6a 100644
--- a/translations/ja-JP/data/reusables/organizations/about-following-organizations.md
+++ b/translations/ja-JP/data/reusables/organizations/about-following-organizations.md
@@ -1,9 +1,9 @@
 ---
-ms.openlocfilehash: 9d70c0e47d7aed9253d990146233d8fac92d339c
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: f9490c302fe4534be6937805e0eec85fe9c5db1a
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: ja-JP
-ms.lasthandoff: 09/05/2022
-ms.locfileid: "147692147"
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148109587"
 ---
-{% data variables.product.product_name %} で組織をフォローすると、個人用ダッシュボードに{% ifversion fpt or ghec %}パブリック{% endif %} アクティビティが表示されます。 このアクティビティには、新しいディスカッション、スポンサーシップ、リポジトリが含まれます。
\ No newline at end of file
+{% data variables.product.product_name %} で組織をフォローすると、個人用ダッシュボードに{% ifversion fpt or ghec %}パブリック{% endif %} アクティビティが表示されます。 このアクティビティには、新しいディスカッション、スポンサーシップ、リポジトリが含まれます。
diff --git a/translations/ja-JP/data/reusables/organizations/follow-organizations-beta.md b/translations/ja-JP/data/reusables/organizations/follow-organizations-beta.md
index e358486dbf..09183b3034 100644
--- a/translations/ja-JP/data/reusables/organizations/follow-organizations-beta.md
+++ b/translations/ja-JP/data/reusables/organizations/follow-organizations-beta.md
@@ -1,13 +1,13 @@
 ---
-ms.openlocfilehash: f64274ea187e812242eb07e1dd9a7204b6522e50
-ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794
+ms.openlocfilehash: 4e2e744a966a1e1b8111f6f5194542f7512670fc
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: ja-JP
-ms.lasthandoff: 09/09/2022
-ms.locfileid: "147692140"
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148109611"
 ---
 {% note %}
 
 **注:** 組織をフォローする機能は現在パブリック ベータ段階であり、変更される可能性があります。
 
-{% endnote %}
\ No newline at end of file
+{% endnote %}
diff --git a/translations/ja-JP/data/reusables/organizations/new_team.md b/translations/ja-JP/data/reusables/organizations/new_team.md
index 2e3249f2f5..ad329ffe34 100644
--- a/translations/ja-JP/data/reusables/organizations/new_team.md
+++ b/translations/ja-JP/data/reusables/organizations/new_team.md
@@ -1,12 +1,8 @@
----
-ms.openlocfilehash: 383ba2a3fe279dfa18f20c931a58a5b4785e8727
-ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d
-ms.translationtype: HT
-ms.contentlocale: ja-JP
-ms.lasthandoff: 09/11/2022
-ms.locfileid: "147883757"
----
-1. Organization 名の下で、{% octicon "people" aria-label="The people icon" %} **[Team]** をクリックします。
-  {% ifversion fpt or ghes > 3.2 or ghec %} ![[Team] タブ](/assets/images/help/organizations/organization-teams-tab-with-overview.png) {% else %} ![[Team] タブ](/assets/images/help/organizations/organization-teams-tab.png) {% endif %}
-1. [Team] タブの右側にある **[新しい Team]** をクリックします。
-  ![[新しい Team] ボタン](/assets/images/help/teams/new-team-button.png)
+1. Under your organization name, click {% octicon "people" aria-label="The people icon" %} **Teams**.
+  {% ifversion fpt or ghes or ghec %}
+  ![Teams tab](/assets/images/help/organizations/organization-teams-tab-with-overview.png)
+  {% else %}
+  ![Teams tab](/assets/images/help/organizations/organization-teams-tab.png)
+  {% endif %}
+1. On the right side of the Teams tab, click **New team**.
+  ![New team button](/assets/images/help/teams/new-team-button.png)
diff --git a/translations/ja-JP/data/reusables/organizations/org_settings.md b/translations/ja-JP/data/reusables/organizations/org_settings.md
index b72f78972a..4e84c3e807 100644
--- a/translations/ja-JP/data/reusables/organizations/org_settings.md
+++ b/translations/ja-JP/data/reusables/organizations/org_settings.md
@@ -1,10 +1,6 @@
----
-ms.openlocfilehash: 86e15f92ffd6a5a5b90d7a70a666447a6a51a62a
-ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
-ms.translationtype: HT
-ms.contentlocale: ja-JP
-ms.lasthandoff: 09/10/2022
-ms.locfileid: "145122542"
----
-1. Organization 名の下で、{% octicon "gear" aria-label="The Settings gear" %} **[設定]** をクリックします。
-  {% ifversion fpt or ghes > 3.2 or ghec %} ![Organization の設定ボタン](/assets/images/help/organizations/organization-settings-tab-with-overview-tab.png) {% else %} ![Organization の設定ボタン](/assets/images/help/organizations/organization-settings-tab.png) {% endif %}
+1. Under your organization name, click {% octicon "gear" aria-label="The Settings gear" %} **Settings**.
+  {% ifversion fpt or ghes or ghec %}
+  ![Organization settings button](/assets/images/help/organizations/organization-settings-tab-with-overview-tab.png)
+  {% else %}
+  ![Organization settings button](/assets/images/help/organizations/organization-settings-tab.png)
+  {% endif %}
diff --git a/translations/ja-JP/data/reusables/organizations/organization-wide-project.md b/translations/ja-JP/data/reusables/organizations/organization-wide-project.md
index 5c7821b50e..052670fdf5 100644
--- a/translations/ja-JP/data/reusables/organizations/organization-wide-project.md
+++ b/translations/ja-JP/data/reusables/organizations/organization-wide-project.md
@@ -1,10 +1,6 @@
----
-ms.openlocfilehash: cba236cbf17553914d18f006b2a17a77a4892658
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
-ms.translationtype: HT
-ms.contentlocale: ja-JP
-ms.lasthandoff: 09/05/2022
-ms.locfileid: "145122494"
----
-1. Organization 名の下の {% octicon "project" aria-label="The Projects icon" %} **[プロジェクト]** をクリックします。
-  {% ifversion fpt or ghes > 3.2 or ghec %} ![Organization の [プロジェクト] タブ](/assets/images/help/organizations/organization-projects-tab-with-overview-tab.png) {% else %} ![Organization の [プロジェクト] タブ](/assets/images/help/organizations/organization-projects-tab.png) {% endif %}
+1. Under your organization name, click {% octicon "project" aria-label="The Projects icon" %} **Projects**.
+  {% ifversion fpt or ghes or ghec %}
+  ![Projects tab for your organization](/assets/images/help/organizations/organization-projects-tab-with-overview-tab.png)
+  {% else %}
+  ![Projects tab for your organization](/assets/images/help/organizations/organization-projects-tab.png)
+  {% endif %}
diff --git a/translations/ja-JP/data/reusables/organizations/owners-team.md b/translations/ja-JP/data/reusables/organizations/owners-team.md
index 9b6c7848c6..b66f0838ca 100644
--- a/translations/ja-JP/data/reusables/organizations/owners-team.md
+++ b/translations/ja-JP/data/reusables/organizations/owners-team.md
@@ -1,12 +1,8 @@
----
-ms.openlocfilehash: 953f11ac28cbb526cd4e93bc316cf81b12241f08
-ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
-ms.translationtype: HT
-ms.contentlocale: ja-JP
-ms.lasthandoff: 09/10/2022
-ms.locfileid: "145122469"
----
-1. Organization 名の下で、{% octicon "people" aria-label="The people icon" %} **[Team]** をクリックします。
-  {% ifversion fpt or ghes > 3.2 or ghec %} ![[Team] タブ](/assets/images/help/organizations/organization-teams-tab-with-overview.png) {% else %} ![[Team] タブ](/assets/images/help/organizations/organization-teams-tab.png) {% endif %}
-1. [Team] タブで、 **[オーナー]** をクリックします。
-  ![オーナーの Team が選択されている](/assets/images/help/teams/owners-team.png)
+1. Under your organization name, click {% octicon "people" aria-label="The people icon" %} **Teams**.
+  {% ifversion fpt or ghes or ghec %}
+  ![Teams tab](/assets/images/help/organizations/organization-teams-tab-with-overview.png)
+  {% else %}
+  ![Teams tab](/assets/images/help/organizations/organization-teams-tab.png)
+  {% endif %}
+1. On the Teams tab, click **Owners**.
+  ![Owners team selected](/assets/images/help/teams/owners-team.png)
diff --git a/translations/ja-JP/data/reusables/organizations/people.md b/translations/ja-JP/data/reusables/organizations/people.md
index 451f2a1223..d69d13281b 100644
--- a/translations/ja-JP/data/reusables/organizations/people.md
+++ b/translations/ja-JP/data/reusables/organizations/people.md
@@ -1,10 +1,6 @@
----
-ms.openlocfilehash: 3a40932cc10fd659071bbc951940a79a1c0498bf
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
-ms.translationtype: HT
-ms.contentlocale: ja-JP
-ms.lasthandoff: 09/05/2022
-ms.locfileid: "145122461"
----
-1. Organization 名の下で、{% octicon "person" aria-label="The Person icon" %} **[People]** をクリックします。
-  {% ifversion fpt or ghes > 3.2 or ghec %} ![[People] タブ](/assets/images/help/organizations/organization-people-tab-with-overview-tab.png) {% else %} ![[People] タブ](/assets/images/help/organizations/organization-people-tab.png) {% endif %}
+1. Under your organization name, click {% octicon "person" aria-label="The Person icon" %} **People**.
+  {% ifversion fpt or ghes or ghec %}
+  ![The People tab](/assets/images/help/organizations/organization-people-tab-with-overview-tab.png)
+  {% else %}
+  ![The People tab](/assets/images/help/organizations/organization-people-tab.png)
+  {% endif %}
diff --git a/translations/ja-JP/data/reusables/organizations/specific_team.md b/translations/ja-JP/data/reusables/organizations/specific_team.md
index 96b974a0f4..655628972a 100644
--- a/translations/ja-JP/data/reusables/organizations/specific_team.md
+++ b/translations/ja-JP/data/reusables/organizations/specific_team.md
@@ -1,12 +1,8 @@
----
-ms.openlocfilehash: e073e782e9271d660c789014a93a5b0f7d703de9
-ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
-ms.translationtype: HT
-ms.contentlocale: ja-JP
-ms.lasthandoff: 09/11/2022
-ms.locfileid: "145122286"
----
-1. Organization 名の下で、{% octicon "people" aria-label="The people icon" %} **[Team]** をクリックします。
-  {% ifversion fpt or ghes > 3.2 or ghec %} ![[Team] タブ](/assets/images/help/organizations/organization-teams-tab-with-overview.png) {% else %} ![[Team] タブ](/assets/images/help/organizations/organization-teams-tab.png) {% endif %}
-1. Teamsタブで、Teamの名前をクリックしてください。
-  ![Organization の Team のリスト](/assets/images/help/teams/click-team-name.png)
+1. Under your organization name, click {% octicon "people" aria-label="The people icon" %} **Teams**.
+  {% ifversion fpt or ghes or ghec %}
+  ![Teams tab](/assets/images/help/organizations/organization-teams-tab-with-overview.png)
+  {% else %}
+  ![Teams tab](/assets/images/help/organizations/organization-teams-tab.png)
+  {% endif %}
+1. On the Teams tab, click the name of the team.
+  ![List of the organization's teams](/assets/images/help/teams/click-team-name.png)
diff --git a/translations/ja-JP/data/reusables/organizations/teams.md b/translations/ja-JP/data/reusables/organizations/teams.md
index 533593ff2f..55600311cf 100644
--- a/translations/ja-JP/data/reusables/organizations/teams.md
+++ b/translations/ja-JP/data/reusables/organizations/teams.md
@@ -1,10 +1,6 @@
----
-ms.openlocfilehash: ddf350dbd9a76a2d7168e67fe690662ac2e63c35
-ms.sourcegitcommit: 5b1461b419dbef60ae9dbdf8e905a4df30fc91b7
-ms.translationtype: HT
-ms.contentlocale: ja-JP
-ms.lasthandoff: 09/10/2022
-ms.locfileid: "147878735"
----
-1. 組織名の下で、{% octicon "people" aria-label="The people icon" %} **[Teams]** をクリックします。
-  {% ifversion fpt or ghes > 3.2 or ghec %} ![組織ページの [Teams] タブ](/assets/images/help/organizations/organization-teams-tab-with-overview.png) {% else %} ![組織ページの [Teams] タブ](/assets/images/help/organizations/organization-teams-tab.png) {% endif %}
+1. Under your organization name, click {% octicon "people" aria-label="The people icon" %} **Teams**.
+  {% ifversion fpt or ghes or ghec %}
+  ![Teams tab on the organization page](/assets/images/help/organizations/organization-teams-tab-with-overview.png)
+  {% else %}
+  ![Teams tab on the organization page](/assets/images/help/organizations/organization-teams-tab.png)
+  {% endif %}
diff --git a/translations/ja-JP/data/reusables/package_registry/container-registry-ghes-migration-availability.md b/translations/ja-JP/data/reusables/package_registry/container-registry-ghes-migration-availability.md
index 63d4118408..751ada92e8 100644
--- a/translations/ja-JP/data/reusables/package_registry/container-registry-ghes-migration-availability.md
+++ b/translations/ja-JP/data/reusables/package_registry/container-registry-ghes-migration-availability.md
@@ -1,9 +1,9 @@
 ---
-ms.openlocfilehash: 86b8c01b5dc27c55e316ba0d81176fd693f85e45
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: 4a39732206e0ad91422acfb3977ba7bea7d0b283
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: ja-JP
-ms.lasthandoff: 09/05/2022
-ms.locfileid: "147410747"
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148109516"
 ---
-{% data variables.product.product_name %} 3.6 では、Organization に格納されている Docker イメージの移行がサポートされています。 今後のリリースでは、ユーザー所有のイメージの移行がサポートされます。
\ No newline at end of file
+{% data variables.product.product_name %} 3.6 では、Organization に格納されている Docker イメージの移行がサポートされています。 今後のリリースでは、ユーザー所有のイメージの移行がサポートされます。
diff --git a/translations/ja-JP/data/reusables/package_registry/no-graphql-to-delete-packages.md b/translations/ja-JP/data/reusables/package_registry/no-graphql-to-delete-packages.md
index fde6a42efb..18c9c747d4 100644
--- a/translations/ja-JP/data/reusables/package_registry/no-graphql-to-delete-packages.md
+++ b/translations/ja-JP/data/reusables/package_registry/no-graphql-to-delete-packages.md
@@ -1,9 +1,9 @@
 ---
-ms.openlocfilehash: deca3a28d17f3716b20a84281ad843c47bdbbee2
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: 5f35d3186458109231db91e80343bcb64a2193c1
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: ja-JP
-ms.lasthandoff: 09/05/2022
-ms.locfileid: "147705078"
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148108917"
 ---
-{% ifversion fpt or ghec %} {% data variables.product.prodname_registry %} GraphQL API では、パッケージ名前空間 `https://ghcr.io/OWNER/PACKAGE-NAME` を使用するコンテナーまたは Docker イメージ、またはパッケージ名前空間 `https://npm.pkg.github.com/OWNER/PACKAGE-NAME` を使用する npm イメージはサポートされていません。{% endif %}
\ No newline at end of file
+{% ifversion fpt or ghec %} {% data variables.product.prodname_registry %} GraphQL API では、パッケージ名前空間 `https://ghcr.io/OWNER/PACKAGE-NAME` を使用するコンテナーまたは Docker イメージ、またはパッケージ名前空間 `https://npm.pkg.github.com/OWNER/PACKAGE-NAME` を使用する npm イメージはサポートされていません。{% endif %}
diff --git a/translations/ja-JP/data/reusables/package_registry/package-settings-from-org-level.md b/translations/ja-JP/data/reusables/package_registry/package-settings-from-org-level.md
index 2818915f3a..d46f87514d 100644
--- a/translations/ja-JP/data/reusables/package_registry/package-settings-from-org-level.md
+++ b/translations/ja-JP/data/reusables/package_registry/package-settings-from-org-level.md
@@ -1,11 +1,7 @@
----
-ms.openlocfilehash: f0e8ddbcd9cbfd2166663191a293876d6e2f8a2e
-ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
-ms.translationtype: HT
-ms.contentlocale: ja-JP
-ms.lasthandoff: 09/10/2022
-ms.locfileid: "145121910"
----
-1. {% data variables.product.prodname_dotcom %}で、Organizationのメインページにアクセスしてください。
-2. Organization 名の下で、 **[パッケージ]** をクリックします。
-  {% ifversion fpt or ghes > 3.2 or ghec %} ![Organization ランディングページの [パッケージ] タブ](/assets/images/help/package-registry/org-tab-for-packages-with-overview-tab.png) {% else %} ![Organization ランディングページの [パッケージ] タブ](/assets/images/help/package-registry/org-tab-for-packages.png) {% endif %}
+1. On {% data variables.product.prodname_dotcom %}, navigate to the main page of your organization.
+2. Under your organization name, click **Packages**.
+  {% ifversion fpt or ghes or ghec %}
+  ![Packages tab on org landing page](/assets/images/help/package-registry/org-tab-for-packages-with-overview-tab.png)
+  {% else %}
+  ![Packages tab on org landing page](/assets/images/help/package-registry/org-tab-for-packages.png)
+  {% endif %}
diff --git a/translations/ja-JP/data/reusables/pages/check-workflow-run.md b/translations/ja-JP/data/reusables/pages/check-workflow-run.md
index d6c582a973..c17f524db6 100644
--- a/translations/ja-JP/data/reusables/pages/check-workflow-run.md
+++ b/translations/ja-JP/data/reusables/pages/check-workflow-run.md
@@ -1,10 +1,10 @@
 ---
-ms.openlocfilehash: d2f50ce890ed4d9a90015498ecdf9909348155fb
-ms.sourcegitcommit: 96bbb6b8f3c9172209d80cb1502017ace3019807
+ms.openlocfilehash: 258f73f928cd99de64f45fda0e6cec8e08ff335c
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: ja-JP
-ms.lasthandoff: 09/10/2022
-ms.locfileid: "147879208"
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148108922"
 ---
 {% ifversion build-pages-with-actions %}
 1. {% data variables.product.prodname_pages %} サイトは、{% data variables.product.prodname_actions %} ワークフローでビルドされ、デプロイされます。 詳細については、「[ワークフロー実行の履歴を表示する](/actions/monitoring-and-troubleshooting-workflows/viewing-workflow-run-history)」を参照してください。
@@ -15,4 +15,4 @@ ms.locfileid: "147879208"
 
   {% endnote %}
 
-{% endif %}
\ No newline at end of file
+{% endif %}
diff --git a/translations/ja-JP/data/reusables/pages/pages-custom-workflow-beta.md b/translations/ja-JP/data/reusables/pages/pages-custom-workflow-beta.md
index 3bad436703..75d24f06fa 100644
--- a/translations/ja-JP/data/reusables/pages/pages-custom-workflow-beta.md
+++ b/translations/ja-JP/data/reusables/pages/pages-custom-workflow-beta.md
@@ -1,10 +1,10 @@
 ---
-ms.openlocfilehash: 653ecfef09a75144cb39fc0d3bf47ba7394a1ce8
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: a231b3c0bf02051ba3593f5dd04ac7fdf5506ea7
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: ja-JP
-ms.lasthandoff: 09/05/2022
-ms.locfileid: "147428443"
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148109428"
 ---
 {% ifversion pages-custom-workflow %}
 
@@ -14,4 +14,4 @@ ms.locfileid: "147428443"
 
 {% endnote %}
 
-{% endif %}
\ No newline at end of file
+{% endif %}
diff --git a/translations/ja-JP/data/reusables/profile/navigating-to-profile.md b/translations/ja-JP/data/reusables/profile/navigating-to-profile.md
new file mode 100644
index 0000000000..1fba1ca676
--- /dev/null
+++ b/translations/ja-JP/data/reusables/profile/navigating-to-profile.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 32a0fded4915b0b23b3db1110d556bd14e0830a8
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: ja-JP
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148106646"
+---
+1. 任意の {% data variables.product.product_name %} ページ上の右上隅にある自分のプロフィール写真をクリックしてから、 **[自分のプロフィール]** をクリックします。 
diff --git a/translations/ja-JP/data/reusables/projects/access-workflows.md b/translations/ja-JP/data/reusables/projects/access-workflows.md
new file mode 100644
index 0000000000..f4a8917a8d
--- /dev/null
+++ b/translations/ja-JP/data/reusables/projects/access-workflows.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: 2637ffcb5913f0c84f3ae092653c410ad0a5fdad
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: ja-JP
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148106591"
+---
+1. プロジェクトにアクセスします。
+1. 右上の {% octicon "kebab-horizontal" aria-label="The menu icon" %} をクリックして、メニューを開きます。
+  ![メニュー アイコンを示すスクリーンショット](/assets/images/help/projects-v2/open-menu.png)
+1. メニューで {% octicon "workflow" aria-label="The workflow icon" %} **[ワークフロー]** をクリックします。
+  ![[ワークフロー] メニュー項目を示すスクリーンショット](/assets/images/help/projects-v2/workflows-menu-item.png)
diff --git a/translations/ja-JP/data/reusables/projects/add-draft-issue.md b/translations/ja-JP/data/reusables/projects/add-draft-issue.md
index 4ba1f0bf1b..6f2d3a516d 100644
--- a/translations/ja-JP/data/reusables/projects/add-draft-issue.md
+++ b/translations/ja-JP/data/reusables/projects/add-draft-issue.md
@@ -1,12 +1,12 @@
 ---
-ms.openlocfilehash: 8dd7d544c14de78ff9150bebb1192bbd4a6007f0
-ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.openlocfilehash: 303fc7fa60ba2ccc37689055f6056a59655a6eae
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: ja-JP
-ms.lasthandoff: 09/10/2022
-ms.locfileid: "147880205"
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148109144"
 ---
 {% data reusables.projects.add-item-bottom-row %}
 1. アイデアを入力し、**Enter** キーを押します。
   ![issue URL を貼り付けてプロジェクトに追加することを示すスクリーンショット](/assets/images/help/projects-v2/add-draft-issue.png)
-1. 本文のテキストを追加するには、ドラフトIssueのタイトルをクリックしてください。 表示されるマークダウンの入力ボックスに、ドラフト Issue の本文のテキストを入力し、 **[保存]** をクリックします。
\ No newline at end of file
+1. 本文のテキストを追加するには、ドラフトIssueのタイトルをクリックしてください。 表示されるマークダウンの入力ボックスに、ドラフト Issue の本文のテキストを入力し、 **[保存]** をクリックします。
diff --git a/translations/ja-JP/data/reusables/projects/add-item-bottom-row.md b/translations/ja-JP/data/reusables/projects/add-item-bottom-row.md
index 089f82501c..bd5387bb90 100644
--- a/translations/ja-JP/data/reusables/projects/add-item-bottom-row.md
+++ b/translations/ja-JP/data/reusables/projects/add-item-bottom-row.md
@@ -1,10 +1,10 @@
 ---
-ms.openlocfilehash: 62086a2f270c2d05a7e3774431e23e6ed089e1cb
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: 8af3f341f8b2a91038d1e489a1d2ed59d8743234
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: ja-JP
-ms.lasthandoff: 09/05/2022
-ms.locfileid: "147424231"
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148109126"
 ---
 1. カーソルをプロジェクトの最下行、{% octicon "plus" aria-label="plus icon" %}の隣に持ってきてください。
-  ![項目を追加する一番下の行を示すスクリーンショット](/assets/images/help/projects-v2/add-item.png)
\ No newline at end of file
+  ![項目を追加する一番下の行を示すスクリーンショット](/assets/images/help/projects-v2/add-item.png)
diff --git a/translations/ja-JP/data/reusables/projects/add-item-via-paste.md b/translations/ja-JP/data/reusables/projects/add-item-via-paste.md
index cf56424bcb..8381e50ea8 100644
--- a/translations/ja-JP/data/reusables/projects/add-item-via-paste.md
+++ b/translations/ja-JP/data/reusables/projects/add-item-via-paste.md
@@ -1,12 +1,12 @@
 ---
-ms.openlocfilehash: 0191556eb977c4b657f1fd78330f6f691f34f039
-ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.openlocfilehash: 477122edeb960deca31d1ad0b97b7ad30681f23b
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: ja-JP
-ms.lasthandoff: 09/10/2022
-ms.locfileid: "147424059"
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148109427"
 ---
 {% data reusables.projects.add-item-bottom-row %}
 1. IssueあるいはPull RequestのURLを貼り付けてください。
   ![issue URL を貼り付けてプロジェクトに追加することを示すスクリーンショット](/assets/images/help/projects-v2/paste-url-to-add.png)
-3. issue または pull request を追加するには、<kbd>Return</kbd> キーを押します。
\ No newline at end of file
+3. issue または pull request を追加するには、<kbd>Return</kbd> キーを押します。
diff --git a/translations/ja-JP/data/reusables/projects/bulk-add.md b/translations/ja-JP/data/reusables/projects/bulk-add.md
index d57acfc471..ee959241a6 100644
--- a/translations/ja-JP/data/reusables/projects/bulk-add.md
+++ b/translations/ja-JP/data/reusables/projects/bulk-add.md
@@ -1,14 +1,14 @@
 ---
-ms.openlocfilehash: b8288219bd82b857d0bbeeefef3b27a3c8f0d3de
-ms.sourcegitcommit: 80842b4e4c500daa051eff0ccd7cde91c2d4bb36
+ms.openlocfilehash: d0d7eb973a255091345f61ff69f8f20f6361d0d9
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: ja-JP
-ms.lasthandoff: 09/11/2022
-ms.locfileid: "147884713"
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148109156"
 ---
 1. 必要に応じて、リポジトリを変更するには、ドロップダウンをクリックしてリポジトリを選びます。 特定の issue や pull request を検索することもできます。
   ![[リポジトリ] ドロップダウン示すスクリーンショット](/assets/images/help/projects-v2/add-bulk-select-repo.png)
 1. 追加する issue と pull request を選びます。
   ![追加する issue と pull request が選ばれているところを示すスクリーンショット](/assets/images/help/projects-v2/add-bulk-select-issues.png)
 1. **[選択した項目の追加]** をクリックします。
-  ![[選択した項目の追加] ボタンを示すスクリーンショット](/assets/images/help/projects-v2/add-bulk-save.png)
\ No newline at end of file
+  ![[選択した項目の追加] ボタンを示すスクリーンショット](/assets/images/help/projects-v2/add-bulk-save.png)
diff --git a/translations/ja-JP/data/reusables/projects/classic-project-creation.md b/translations/ja-JP/data/reusables/projects/classic-project-creation.md
index b555c661b1..3ae073c69c 100644
--- a/translations/ja-JP/data/reusables/projects/classic-project-creation.md
+++ b/translations/ja-JP/data/reusables/projects/classic-project-creation.md
@@ -1,10 +1,10 @@
 ---
-ms.openlocfilehash: cd5e613522bc536aa433d900e193ef2276df6410
-ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d
+ms.openlocfilehash: 682ba253ea2660d8608033598343393372ae3cbf
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: ja-JP
-ms.lasthandoff: 09/11/2022
-ms.locfileid: "147375724"
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148109419"
 ---
 {% ifversion fpt or ghec %}
 
@@ -14,4 +14,4 @@ ms.locfileid: "147375724"
 
 {% endnote %}
 
-{% endif %}
\ No newline at end of file
+{% endif %}
diff --git a/translations/ja-JP/data/reusables/projects/new-field.md b/translations/ja-JP/data/reusables/projects/new-field.md
index 29c4e66c17..58541ba367 100644
--- a/translations/ja-JP/data/reusables/projects/new-field.md
+++ b/translations/ja-JP/data/reusables/projects/new-field.md
@@ -1,14 +1,14 @@
 ---
-ms.openlocfilehash: daf5b47c71e8cbde44c6dab38eabf7c6d922be9a
-ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.openlocfilehash: 3acee6d785e2b633f979e7edb8f80544dfa09ced
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: ja-JP
-ms.lasthandoff: 09/11/2022
-ms.locfileid: "147882876"
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148109412"
 ---
 1. テーブル ビューで、右端のフィールド ヘッダーの [{% octicon "plus" aria-label="the plus icon" %}] をクリックします。
    ![新しいフィールドのボタンを示すスクリーンショット](/assets/images/help/projects-v2/new-field-button.png)
 1. **[新しいフィールド]** をクリックします。
    ![新しいフィールドのメニュー項目を示すスクリーンショット](/assets/images/help/projects-v2/new-field-menu-item.png)
 1. 新しいフィールドの名前を入力します。
-   ![フィールド名を示すスクリーンショット](/assets/images/help/projects-v2/new-field-name.png)
\ No newline at end of file
+   ![フィールド名を示すスクリーンショット](/assets/images/help/projects-v2/new-field-name.png)
diff --git a/translations/ja-JP/data/reusables/projects/new-view.md b/translations/ja-JP/data/reusables/projects/new-view.md
index b515b2e349..6e4c439e9f 100644
--- a/translations/ja-JP/data/reusables/projects/new-view.md
+++ b/translations/ja-JP/data/reusables/projects/new-view.md
@@ -1,10 +1,10 @@
 ---
-ms.openlocfilehash: 831716db8a52f44aee809924a38f8288952d23df
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: 9bac51e4098b1da121c0763f8581716a547353af
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: ja-JP
-ms.lasthandoff: 09/05/2022
-ms.locfileid: "147424136"
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148108869"
 ---
 1. 既存のビューの右側にある **[新しいビュー]** をクリックします
-   ![列フィールド メニューを示すスクリーンショット](/assets/images/help/projects-v2/new-view.png)
\ No newline at end of file
+   ![列フィールド メニューを示すスクリーンショット](/assets/images/help/projects-v2/new-view.png)
diff --git a/translations/ja-JP/data/reusables/projects/open-item-menu.md b/translations/ja-JP/data/reusables/projects/open-item-menu.md
index 66f48a0dca..5e48e08c83 100644
--- a/translations/ja-JP/data/reusables/projects/open-item-menu.md
+++ b/translations/ja-JP/data/reusables/projects/open-item-menu.md
@@ -1,9 +1,9 @@
 ---
-ms.openlocfilehash: 15b1ba8ed434c9c9c6bb81c0ca0376c2e42fca48
-ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794
+ms.openlocfilehash: 10c8c2b298fd4eaec742bf9efbc686d6f2bb3c0b
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: ja-JP
-ms.lasthandoff: 09/09/2022
-ms.locfileid: "147878632"
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148109411"
 ---
-1.  {% octicon "triangle-down" aria-label="the item menu" %} (テーブル レイアウトの場合) または {% octicon "kebab-horizontal" aria-label="the item menu" %} (ボード レイアウトの場合) を選びます。
\ No newline at end of file
+1.  {% octicon "triangle-down" aria-label="the item menu" %} (テーブル レイアウトの場合) または {% octicon "kebab-horizontal" aria-label="the item menu" %} (ボード レイアウトの場合) を選びます。
diff --git a/translations/ja-JP/data/reusables/projects/open-view-menu.md b/translations/ja-JP/data/reusables/projects/open-view-menu.md
index cb88dd3387..31956ba97f 100644
--- a/translations/ja-JP/data/reusables/projects/open-view-menu.md
+++ b/translations/ja-JP/data/reusables/projects/open-view-menu.md
@@ -1,10 +1,10 @@
 ---
-ms.openlocfilehash: 0873b7b527997d2472413b016a12f2f413f06e86
-ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.openlocfilehash: 167d4ab0b57e2af8ee07f720db569725829adf69
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: ja-JP
-ms.lasthandoff: 09/10/2022
-ms.locfileid: "147880141"
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148109403"
 ---
 1. 現在開いているビューの名前の横にある {% octicon "triangle-down" aria-label="the drop-down icon" %} をクリックします。
-  ![ビュー メニュー アイコン示すスクリーンショット](/assets/images/help/projects-v2/view-menu-icon.png)
\ No newline at end of file
+  ![ビュー メニュー アイコン示すスクリーンショット](/assets/images/help/projects-v2/view-menu-icon.png)
diff --git a/translations/ja-JP/data/reusables/projects/owners-can-limit-visibility-permissions.md b/translations/ja-JP/data/reusables/projects/owners-can-limit-visibility-permissions.md
index 66cb527f58..c13be1a16f 100644
--- a/translations/ja-JP/data/reusables/projects/owners-can-limit-visibility-permissions.md
+++ b/translations/ja-JP/data/reusables/projects/owners-can-limit-visibility-permissions.md
@@ -1,9 +1,9 @@
 ---
-ms.openlocfilehash: e9790db64c727836fb25001ef5160b0030a12da4
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: a811a75bedf573e347f2346a8872dd533b3a4466
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: ja-JP
-ms.lasthandoff: 09/05/2022
-ms.locfileid: "147614562"
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148108916"
 ---
-Organization の所有者は、パブリック {% data variables.projects.projects_v2_and_v1 %} を作成したり、既存の {% data variables.projects.projects_v2_and_v1 %} の可視性をパブリックに変更したりする Organization のメンバーの機能を制御できます。 詳しくは、「[Organization のプロジェクトの可視性の変更を許可する](/organizations/managing-organization-settings/allowing-project-visibility-changes-in-your-organization)」をご覧ください。
\ No newline at end of file
+Organization の所有者は、パブリック {% data variables.projects.projects_v2_and_v1 %} を作成したり、既存の {% data variables.projects.projects_v2_and_v1 %} の可視性をパブリックに変更したりする Organization のメンバーの機能を制御できます。 詳しくは、「[Organization のプロジェクトの可視性の変更を許可する](/organizations/managing-organization-settings/allowing-project-visibility-changes-in-your-organization)」をご覧ください。
diff --git a/translations/ja-JP/data/reusables/projects/save-view.md b/translations/ja-JP/data/reusables/projects/save-view.md
index 3cf08b91e2..c6ba1ada3f 100644
--- a/translations/ja-JP/data/reusables/projects/save-view.md
+++ b/translations/ja-JP/data/reusables/projects/save-view.md
@@ -1,11 +1,11 @@
 ---
-ms.openlocfilehash: 9103637cf5f41c5c40b4328f050edf1c5ca8eabc
-ms.sourcegitcommit: 76b840f45ba85fb79a7f0c1eb43bc663b3eadf2b
+ms.openlocfilehash: 2a7a472bbfeed56c58e483b61c2a140aa52e63e8
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: ja-JP
-ms.lasthandoff: 09/12/2022
-ms.locfileid: "147424222"
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148108875"
 ---
 {% data reusables.projects.open-view-menu %}
 1. **[変更を保存]** をクリックします。
-   ![保存メニュー項目が表示されたスクリーンショット](/assets/images/help/projects-v2/save-view.png)
\ No newline at end of file
+   ![保存メニュー項目が表示されたスクリーンショット](/assets/images/help/projects-v2/save-view.png)
diff --git a/translations/ja-JP/data/reusables/projects/select-an-item.md b/translations/ja-JP/data/reusables/projects/select-an-item.md
index 363d00954b..57cdff7de9 100644
--- a/translations/ja-JP/data/reusables/projects/select-an-item.md
+++ b/translations/ja-JP/data/reusables/projects/select-an-item.md
@@ -1,13 +1,13 @@
 ---
-ms.openlocfilehash: a78a08bd4cdf72ca732b4c2a664164d0f69f1815
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: 8fef95ca781a57606206a89a8408bcd4774402e2
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: ja-JP
-ms.lasthandoff: 09/05/2022
-ms.locfileid: "147424219"
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148109508"
 ---
 1. 項目を選びます。 複数のアイテムを選択するには、以下のいずれかのようにしてください。
      - <kbd>command</kbd> (Mac) または <kbd>Ctrl</kbd> (Windows または Linux) キーを押しながら各項目をクリックします。
      - 1 つの項目を選んでから <kbd>Shift</kbd>+<kbd>↑</kbd> または <kbd>Shift</kbd>+<kbd>↓</kbd> キーを押して、選んだ項目の上または下にある追加項目を選びます。
      - 1 つの項目を選んでから <kbd>Shift</kbd> キーを押し、もう 1 つの項目をクリックして、2 つの項目の間にあるすべての項目を選びます。
-     - 1 つの行または項目を既に選んだ状態で、<kbd>command</kbd>+<kbd>A</kbd> (Mac) または <kbd>Ctrl</kbd>+<kbd>A</kbd> (Windows または Linux) を押して、列またはボード レイアウトのすべての項目、あるいはテーブル レイアウトのすべての項目を選びます。
\ No newline at end of file
+     - 1 つの行または項目を既に選んだ状態で、<kbd>command</kbd>+<kbd>A</kbd> (Mac) または <kbd>Ctrl</kbd>+<kbd>A</kbd> (Windows または Linux) を押して、列またはボード レイアウトのすべての項目、あるいはテーブル レイアウトのすべての項目を選びます。
diff --git a/translations/ja-JP/data/reusables/pull_requests/merge-queue-beta.md b/translations/ja-JP/data/reusables/pull_requests/merge-queue-beta.md
index fe55c68405..c0b4d6f240 100644
--- a/translations/ja-JP/data/reusables/pull_requests/merge-queue-beta.md
+++ b/translations/ja-JP/data/reusables/pull_requests/merge-queue-beta.md
@@ -1,7 +1,14 @@
-{% ifversion fpt or ghec %}
-{% note %}
+---
+ms.openlocfilehash: 85db1024fd3a47bebaf0a6fef56843c8be2509a9
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: ja-JP
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148008724"
+---
+{% ifversion fpt or ghec %} {% note %}
 
-**Note:** The pull request merge queue feature is currently in limited public beta and subject to change.
+**注:** pull request のマージ キュー機能は現在、限定的なパブリック ベータ版であり、変更される可能性があります。
 
 {% endnote %}
 
diff --git a/translations/ja-JP/data/reusables/repositories/commit-signoffs.md b/translations/ja-JP/data/reusables/repositories/commit-signoffs.md
index 488608a956..37aeb9275e 100644
--- a/translations/ja-JP/data/reusables/repositories/commit-signoffs.md
+++ b/translations/ja-JP/data/reusables/repositories/commit-signoffs.md
@@ -1,10 +1,10 @@
 ---
-ms.openlocfilehash: 50db50aff42d977575a89a2e22287b1672081ee4
-ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.openlocfilehash: 1b3e7f64c7507fde4a126cddaca3c4a97247d967
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: ja-JP
-ms.lasthandoff: 09/11/2022
-ms.locfileid: "147881390"
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148109483"
 ---
 強制コミットのサインオフは、Web インターフェイスを介して行われたコミットにのみ適用されます。 Git コマンド ライン インターフェイスを使用して行われたコミットは、コミット作成者が `--signoff` オプションを使用してコミットにサインオフする必要があります。 詳しくは、[Git ドキュメント](https://git-scm.com/docs/git-commit)を参照してください。
 
@@ -15,4 +15,4 @@ ms.locfileid: "147881390"
 
 コミットでサインオフする前に、コミット先のリポジトリを管理する規則とライセンスに準拠していることを確認する必要があります。 リポジトリでは、Linux Foundation の Developer Certificate of Origin などのサインオフ契約を使用できます。 詳しくは「[Developer Certificate of Origin](https://developercertificate.org/)」をご覧ください。
 
-コミットへの署名は、コミットのサインオフとは異なります。 詳しくは、「[コミットの署名の検証について](/authentication/managing-commit-signature-verification/about-commit-signature-verification)」をご覧ください。
\ No newline at end of file
+コミットへの署名は、コミットのサインオフとは異なります。 詳しくは、「[コミットの署名の検証について](/authentication/managing-commit-signature-verification/about-commit-signature-verification)」をご覧ください。
diff --git a/translations/ja-JP/data/reusables/repositories/security-advisories-republishing.md b/translations/ja-JP/data/reusables/repositories/security-advisories-republishing.md
index 105a68b9f5..c2f7cd1471 100644
--- a/translations/ja-JP/data/reusables/repositories/security-advisories-republishing.md
+++ b/translations/ja-JP/data/reusables/repositories/security-advisories-republishing.md
@@ -1,9 +1 @@
----
-ms.openlocfilehash: 0ac903914a15eacb9f6db488c4c1cac01a6411e6
-ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
-ms.translationtype: HT
-ms.contentlocale: ja-JP
-ms.lasthandoff: 09/11/2022
-ms.locfileid: "145090538"
----
-{% data variables.product.prodname_security_advisories %}を使い、すでに別の場所で公開したセキュリティ脆弱性の詳細をコピーして新しいセキュリティアドバイザリに貼り付けることにより、その詳細を再度公開できます。
+You can also use repository security advisories to republish the details of a security vulnerability that you have already disclosed elsewhere by copying and pasting the details of the vulnerability into a new security advisory.
diff --git a/translations/ja-JP/data/reusables/saml/ae-uses-saml-sso.md b/translations/ja-JP/data/reusables/saml/ae-uses-saml-sso.md
index d515bef08a..24ad8ee1f2 100644
--- a/translations/ja-JP/data/reusables/saml/ae-uses-saml-sso.md
+++ b/translations/ja-JP/data/reusables/saml/ae-uses-saml-sso.md
@@ -1,9 +1,9 @@
 ---
-ms.openlocfilehash: 3657d22416c277ff6af595279480f31134d7b6d8
-ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.openlocfilehash: 8396c212c048ddf20c4b00d4891a21052555325e
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: ja-JP
-ms.lasthandoff: 09/11/2022
-ms.locfileid: "145117750"
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148109127"
 ---
-{% data variables.product.product_name %}は、ユーザ認証にSAML SSOを使用します。 {% data variables.product.prodname_ghe_managed %}へのアクセスは、SAML 2.0標準をサポートするIdPから集中管理できます。
+{% data variables.product.product_name %}は、ユーザ認証にSAML SSOを使用します。 {% data variables.product.prodname_ghe_managed %}へのアクセスは、SAML 2.0標準をサポートするIdPから集中管理できます。
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/saml/authentication-loop.md b/translations/ja-JP/data/reusables/saml/authentication-loop.md
index af2e5e526e..982fde3f9c 100644
--- a/translations/ja-JP/data/reusables/saml/authentication-loop.md
+++ b/translations/ja-JP/data/reusables/saml/authentication-loop.md
@@ -1,10 +1,10 @@
 ---
-ms.openlocfilehash: e7dd0182fdc70186e5b3d137ac99cebd2ff562ea
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: 7e0f711826a1f1ea1bee8cec18bf5b4614815174
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: ja-JP
-ms.lasthandoff: 09/05/2022
-ms.locfileid: "147093192"
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148109132"
 ---
 ## ユーザーが繰り返し認証するようにリダイレクトされる
 
@@ -12,4 +12,4 @@ ms.locfileid: "147093192"
 
 SAML 応答で送信される `SessionNotOnOrAfter` 値によって、ユーザーが認証のために IdP にリダイレクトされるタイミングが決まります。 SAML セッション期間を 2 時間以下に構成した場合、期限切れの 5 分前に SAML セッションは {% data variables.product.prodname_dotcom_the_website %} によって更新されます。 セッション期間を 5 分以下に構成した場合、ユーザーは SAML 認証ループから抜け出せなくなる可能性があります。 
 
-この問題を解決するには、最短 SAML セッション期間を 4 時間に構成することをお勧めします。 詳細については、「[SAML 構成リファレンス](/admin/identity-and-access-management/using-saml-for-enterprise-iam/saml-configuration-reference#session-duration-and-timeout)」をご覧ください。
\ No newline at end of file
+この問題を解決するには、最短 SAML セッション期間を 4 時間に構成することをお勧めします。 詳細については、「[SAML 構成リファレンス](/admin/identity-and-access-management/using-saml-for-enterprise-iam/saml-configuration-reference#session-duration-and-timeout)」をご覧ください。
diff --git a/translations/ja-JP/data/reusables/saml/current-time-earlier-than-notbefore-condition.md b/translations/ja-JP/data/reusables/saml/current-time-earlier-than-notbefore-condition.md
index 8208b7fd3f..f4a0bd2bb1 100644
--- a/translations/ja-JP/data/reusables/saml/current-time-earlier-than-notbefore-condition.md
+++ b/translations/ja-JP/data/reusables/saml/current-time-earlier-than-notbefore-condition.md
@@ -1,10 +1,10 @@
 ---
-ms.openlocfilehash: b0db396765557122de192fe6dde98aeeb0057ec2
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: a9ba68f182b48a4186a4ae63909ef4e146d7c392
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: ja-JP
-ms.lasthandoff: 09/05/2022
-ms.locfileid: "147093208"
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148109133"
 ---
 ## エラー: "Current time is earlier than NotBefore condition" (現在の時刻は NotBefore 条件より前です)
 
@@ -12,4 +12,4 @@ ms.locfileid: "147093208"
 
 {% ifversion ghes %}この問題を防ぐには、可能であれば、IdP と同じネットワーク タイム プロトコル (NTP) ソースを指すようにアプライアンスを設定することをお勧めします。 {% endif %}このエラーが発生した場合は、{% ifversion ghes %}アプライアンス{% else %}IdP {% endif %}の時刻が NTP サーバーと適切に同期していることを確認します。
 
-IdP の立場で ADFS を使っている場合は、{% data variables.product.prodname_dotcom %} のために ADFS の `NotBeforeSkew` も 1 分に設定します。 `NotBeforeSkew` を 0 に設定すると、ミリ秒などの非常に短い時間差でも認証の問題が発生する可能性があります。
\ No newline at end of file
+IdP の立場で ADFS を使っている場合は、{% data variables.product.prodname_dotcom %} のために ADFS の `NotBeforeSkew` も 1 分に設定します。 `NotBeforeSkew` を 0 に設定すると、ミリ秒などの非常に短い時間差でも認証の問題が発生する可能性があります。
diff --git a/translations/ja-JP/data/reusables/saml/okta-ae-sso-beta.md b/translations/ja-JP/data/reusables/saml/okta-ae-sso-beta.md
index 1fc5466e5c..e9b9febc25 100644
--- a/translations/ja-JP/data/reusables/saml/okta-ae-sso-beta.md
+++ b/translations/ja-JP/data/reusables/saml/okta-ae-sso-beta.md
@@ -1,8 +1,16 @@
+---
+ms.openlocfilehash: eef3fbd7285fbea49bf20ed9359b2a7c6c49fff1
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: ja-JP
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148109067"
+---
 {% ifversion ghae %}
 
 {% note %}
 
-**Note:** {% data variables.product.prodname_ghe_managed %} single sign-on (SSO) support for Okta is currently in beta.
+**注:** Okta に対する {% data variables.product.prodname_ghe_managed %} シングル サインオン (SSO) のサポートは、現在ベータ版です。
 
 {% endnote %}
 
diff --git a/translations/ja-JP/data/reusables/saml/okta-sign-on-tab.md b/translations/ja-JP/data/reusables/saml/okta-sign-on-tab.md
index 02c945e55a..bd640b9263 100644
--- a/translations/ja-JP/data/reusables/saml/okta-sign-on-tab.md
+++ b/translations/ja-JP/data/reusables/saml/okta-sign-on-tab.md
@@ -1,10 +1,11 @@
 ---
-ms.openlocfilehash: 0626c11052a92500820ca0a3ac24f0cad784ebd6
-ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.openlocfilehash: c1c07418ac678e38f387f9be4ebc00153558ae22
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: ja-JP
-ms.lasthandoff: 09/10/2022
-ms.locfileid: "145130456"
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148109308"
 ---
 1. アプリケーションの名前の下にある **[サインオン]** をクリックします。
-  ![Okta アプリケーションの [サインオン] タブのスクリーンショット](/assets/images/help/saml/okta-sign-on-tab.png)
+
+   ![[サインオン] タブ](/assets/images/help/saml/okta-ae-sign-on-tab.png)
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/saml/okta-view-setup-instructions.md b/translations/ja-JP/data/reusables/saml/okta-view-setup-instructions.md
index febffcf723..7e7d37cb1a 100644
--- a/translations/ja-JP/data/reusables/saml/okta-view-setup-instructions.md
+++ b/translations/ja-JP/data/reusables/saml/okta-view-setup-instructions.md
@@ -1,9 +1,11 @@
 ---
-ms.openlocfilehash: 0c41ccbde38c607916822e265d7fb749318db717
-ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.openlocfilehash: fef8d78e7518ea1b11d657f0ed82929847cd5575
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: ja-JP
-ms.lasthandoff: 09/10/2022
-ms.locfileid: "145130452"
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148108796"
 ---
 1. [サインオン方法] で **[セットアップ手順の表示]** をクリックします。
+
+   ![[サインオン] タブ](/assets/images/help/saml/okta-ae-view-setup-instructions.png)
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/saml/saml-accounts.md b/translations/ja-JP/data/reusables/saml/saml-accounts.md
index a7b72ffe55..366783c3a0 100644
--- a/translations/ja-JP/data/reusables/saml/saml-accounts.md
+++ b/translations/ja-JP/data/reusables/saml/saml-accounts.md
@@ -1,10 +1,10 @@
 ---
-ms.openlocfilehash: 41c1afacc9dbebc6722e5b60cbd5a52b5786df5d
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: b5ea320db35c6a770853644bcdb50117d3da578d
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: ja-JP
-ms.lasthandoff: 09/05/2022
-ms.locfileid: "147526821"
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148108790"
 ---
 SAML SSO を構成する場合、組織のメンバーは引き続き {% data variables.product.prodname_dotcom_the_website %} で個人アカウントにサインインします。 組織内の非パブリックのリソースにメンバーがアクセスすると、{% data variables.product.prodname_dotcom %} により、認証のためにメンバーが IdP にリダイレクトされます。 認証に成功すると、IdP はメンバーを {% data variables.product.prodname_dotcom %} にリダイレクトして戻します。 詳細については、「[SAML のシングル サインオンでの認証について](/enterprise-cloud@latest/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on)」を参照してください。
 
@@ -12,4 +12,4 @@ SAML SSO を構成する場合、組織のメンバーは引き続き {% data va
 
 **注:** SAML SSO は、{% data variables.product.prodname_dotcom %} の通常のサインイン プロセスに代わるものではありません。 {% data variables.product.prodname_emus %} を使用する場合を除き、メンバーは {% data variables.product.prodname_dotcom_the_website %} で引き続き個人アカウントにサインインし、各個人アカウントは IdP で外部 ID にリンクされます。
 
-{% endnote %}
\ No newline at end of file
+{% endnote %}
diff --git a/translations/ja-JP/data/reusables/secret-scanning/partner-secret-list-private-repo.md b/translations/ja-JP/data/reusables/secret-scanning/partner-secret-list-private-repo.md
index af2f8af01c..3d68fc424b 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
@@ -9,8 +9,7 @@ Alibaba Cloud | Alibaba Cloud Access Key ID with Alibaba Cloud Access Key Secret
 {%- ifversion fpt or ghec or ghes > 3.3 or ghae > 3.3 %}
 Amazon | Amazon OAuth Client ID with Amazon OAuth Client Secret | amazon_oauth_client_id </br>amazon_oauth_client_secret{% endif %}
 Amazon Web Services (AWS) | Amazon AWS Access Key ID with Amazon AWS Secret Access Key | aws_access_key_id </br>aws_secret_access_key
-{%- ifversion fpt or ghec or ghes > 3.2 or ghae %}
-Amazon Web Services (AWS) | Amazon AWS Session Token with Amazon AWS Temporary Access Key ID and Amazon AWS Secret Access Key | aws_session_token </br>aws_temporary_access_key_id </br>aws_secret_access_key{% endif %}
+Amazon Web Services (AWS) | Amazon AWS Session Token with Amazon AWS Temporary Access Key ID and Amazon AWS Secret Access Key | aws_session_token </br>aws_temporary_access_key_id </br>aws_secret_access_key
 Asana | Asana {% data variables.product.pat_generic %} | asana_personal_access_token
 Atlassian | Atlassian API Token | atlassian_api_token
 Atlassian | Atlassian JSON Web Token | atlassian_jwt
@@ -31,14 +30,12 @@ Azure | Azure Service Management Certificate | azure_management_certificate
 {%- ifversion ghes < 3.4 or ghae < 3.4 %}
 Azure | Azure SQL Connection String | azure_sql_connection_string{% endif %}
 Azure | Azure Storage Account Key | azure_storage_account_key
-{%- ifversion fpt or ghec or ghes > 3.2 or ghae %}
-Beamer | Beamer API Key | beamer_api_key{% endif %}
+Beamer | Beamer API Key | beamer_api_key
 Checkout.com | Checkout.com Production Secret Key | checkout_production_secret_key
 Checkout.com | Checkout.com Test Secret Key | checkout_test_secret_key
 Clojars | Clojars Deploy Token | clojars_deploy_token
 CloudBees CodeShip | CloudBees CodeShip Credential | codeship_credential
-{%- ifversion fpt or ghec or ghes > 3.2 or ghae %}
-Contentful | Contentful {% data variables.product.pat_generic %} | contentful_personal_access_token{% endif %}
+Contentful | Contentful {% data variables.product.pat_generic %} | contentful_personal_access_token
 Databricks | Databricks Access Token | databricks_access_token
 {%- ifversion fpt or ghec or ghes > 3.8 or ghae > 3.8 %}
 DevCycle | DevCycle Client API Key | devcycle_client_api_key
@@ -69,8 +66,7 @@ Flutterwave | Flutterwave Live API Secret Key | flutterwave_live_api_secret_key
 Flutterwave | Flutterwave Test API Secret Key | flutterwave_test_api_secret_key
 Frame.io | Frame.io JSON Web Token | frameio_jwt
 Frame.io| Frame.io Developer Token | frameio_developer_token
-{%- ifversion fpt or ghec or ghes > 3.2 or ghae %}
-FullStory | FullStory API Key | fullstory_api_key{% endif %}
+FullStory | FullStory API Key | fullstory_api_key
 GitHub | GitHub {% data variables.product.pat_generic %} | github_personal_access_token
 GitHub | GitHub OAuth Access Token | github_oauth_access_token
 GitHub | GitHub Refresh Token | github_refresh_token
@@ -80,14 +76,11 @@ GitHub | GitHub SSH Private Key | github_ssh_private_key
 GitLab | GitLab Access Token | gitlab_access_token{% endif %}
 GoCardless | GoCardless Live Access Token | gocardless_live_access_token
 GoCardless | GoCardless Sandbox Access Token | gocardless_sandbox_access_token
-{%- ifversion fpt or ghec or ghes > 3.2 or ghae %}
-Google | Firebase Cloud Messaging Server Key | firebase_cloud_messaging_server_key{% endif %}
+Google | Firebase Cloud Messaging Server Key | firebase_cloud_messaging_server_key
 Google | Google API Key | google_api_key
 Google | Google Cloud Private Key ID | 
-{%- ifversion fpt or ghec or ghes > 3.2 or ghae %}
-Google | Google Cloud Storage Service Account Access Key ID with Google Cloud Storage Access Key Secret | google_cloud_storage_service_account_access_key_id </br>google_cloud_storage_access_key_secret{% endif %}
-{%- ifversion fpt or ghec or ghes > 3.2 or ghae %}
-Google | Google Cloud Storage User Access Key ID with Google Cloud Storage Access Key Secret | google_cloud_storage_user_access_key_id </br>google_cloud_storage_access_key_secret{% endif %}
+Google | Google Cloud Storage Service Account Access Key ID with Google Cloud Storage Access Key Secret | google_cloud_storage_service_account_access_key_id </br>google_cloud_storage_access_key_secret
+Google | Google Cloud Storage User Access Key ID with Google Cloud Storage Access Key Secret | google_cloud_storage_user_access_key_id </br>google_cloud_storage_access_key_secret
 {%- ifversion fpt or ghec or ghes > 3.3 or ghae > 3.3 %}
 Google | Google OAuth Access Token | google_oauth_access_token{% endif %}
 {%- ifversion fpt or ghec or ghes > 3.3 or ghae > 3.3 %}
@@ -97,6 +90,8 @@ Google | Google OAuth Refresh Token | google_oauth_refresh_token{% endif %}
 Grafana | Grafana API Key | grafana_api_key
 HashiCorp | Terraform Cloud / Enterprise API Token | terraform_api_token
 HashiCorp | HashiCorp Vault Batch Token | hashicorp_vault_batch_token
+{%- ifversion fpt or ghec or ghes > 3.8 or ghae > 3.8 %}
+HashiCorp | HashiCorp Vault Root Service Token | hashicorp_vault_root_service_token{% endif %}
 HashiCorp | HashiCorp Vault Service Token | hashicorp_vault_service_token
 Hubspot | Hubspot API Key | hubspot_api_key
 Intercom | Intercom Access Token | intercom_access_token
@@ -104,10 +99,8 @@ Ionic | Ionic {% data variables.product.pat_generic %} | ionic_personal_access_t
 Ionic | Ionic Refresh Token | ionic_refresh_token
 {%- ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4 %}
 JD Cloud | JD Cloud Access Key | jd_cloud_access_key{% endif %}
-{%- ifversion fpt or ghec or ghes > 3.2 or ghae %}
-JFrog | JFrog Platform Access Token | jfrog_platform_access_token{% endif %}
-{%- ifversion fpt or ghec or ghes > 3.2 or ghae %}
-JFrog | JFrog Platform API Key | jfrog_platform_api_key{% endif %}
+JFrog | JFrog Platform Access Token | jfrog_platform_access_token
+JFrog | JFrog Platform API Key | jfrog_platform_api_key
 Linear | Linear API Key | linear_api_key
 Linear | Linear OAuth Access Token | linear_oauth_access_token
 Lob | Lob Live API Key | lob_live_api_key
@@ -125,14 +118,10 @@ Meta | Facebook Access Token | facebook_access_token
 Midtrans | Midtrans Production Server Key | midtrans_production_server_key{% endif %}
 {%- ifversion fpt or ghec or ghes > 3.3 or ghae > 3.3 %}
 Midtrans | Midtrans Sandbox Server Key | midtrans_sandbox_server_key{% endif %}
-{%- ifversion fpt or ghec or ghes > 3.2 or ghae %}
-New Relic | New Relic Personal API Key | new_relic_personal_api_key{% endif %}
-{%- ifversion fpt or ghec or ghes > 3.2 or ghae %}
-New Relic | New Relic REST API Key | new_relic_rest_api_key{% endif %}
-{%- ifversion fpt or ghec or ghes > 3.2 or ghae %}
-New Relic | New Relic Insights Query Key | new_relic_insights_query_key{% endif %}
-{%- ifversion fpt or ghec or ghes > 3.2 or ghae %}
-New Relic | New Relic License Key | new_relic_license_key{% endif %}
+New Relic | New Relic Personal API Key | new_relic_personal_api_key
+New Relic | New Relic REST API Key | new_relic_rest_api_key
+New Relic | New Relic Insights Query Key | new_relic_insights_query_key
+New Relic | New Relic License Key | new_relic_license_key
 {%- ifversion fpt or ghec or ghes > 3.3 or ghae > 3.3 %}
 Notion | Notion Integration Token | notion_integration_token{% endif %}
 {%- ifversion fpt or ghec or ghes > 3.3 or ghae > 3.3 %}
@@ -145,14 +134,10 @@ Onfido | Onfido Live API Token | onfido_live_api_token
 Onfido | Onfido Sandbox API Token | onfido_sandbox_api_token
 OpenAI | OpenAI API Key | openai_api_key
 Palantir | Palantir JSON Web Token | palantir_jwt
-{%- ifversion fpt or ghec or ghes > 3.2 or ghae %}
-PlanetScale | PlanetScale Database Password | planetscale_database_password{% endif %}
-{%- ifversion fpt or ghec or ghes > 3.2 or ghae %}
-PlanetScale | PlanetScale OAuth Token | planetscale_oauth_token{% endif %}
-{%- ifversion fpt or ghec or ghes > 3.2 or ghae %}
-PlanetScale | PlanetScale Service Token | planetscale_service_token{% endif %}
-{%- ifversion fpt or ghec or ghes > 3.2 or ghae %}
-Plivo | Plivo Auth ID with Plivo Auth Token | plivo_auth_id </br>plivo_auth_token{% endif %}
+PlanetScale | PlanetScale Database Password | planetscale_database_password
+PlanetScale | PlanetScale OAuth Token | planetscale_oauth_token
+PlanetScale | PlanetScale Service Token | planetscale_service_token
+Plivo | Plivo Auth ID with Plivo Auth Token | plivo_auth_id </br>plivo_auth_token
 Postman | Postman API Key | postman_api_key
 {%- ifversion fpt or ghec or ghes > 3.6 or ghae > 3.6 %}
 Prefect | Prefect Server API Key | prefect_server_api_key
@@ -173,10 +158,8 @@ Samsara | Samsara OAuth Access Token | samsara_oauth_access_token
 {%- ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4 %}
 Segment | Segment Public API Token | segment_public_api_token{% endif %}
 SendGrid | SendGrid API Key | sendgrid_api_key
-{%- ifversion fpt or ghec or ghes > 3.2 or ghae %}
-Sendinblue | Sendinblue API Key | sendinblue_api_key{% endif %}
-{%- ifversion fpt or ghec or ghes > 3.2 or ghae %}
-Sendinblue | Sendinblue SMTP Key | sendinblue_smtp_key{% endif %}
+Sendinblue | Sendinblue API Key | sendinblue_api_key
+Sendinblue | Sendinblue SMTP Key | sendinblue_smtp_key
 Shippo | Shippo Live API Token | shippo_live_api_token
 Shippo | Shippo Test API Token | shippo_test_api_token
 {%- ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4 %}
diff --git a/translations/ja-JP/data/reusables/secret-scanning/push-protection-allow-email.md b/translations/ja-JP/data/reusables/secret-scanning/push-protection-allow-email.md
index bf25ea801c..879300206c 100644
--- a/translations/ja-JP/data/reusables/secret-scanning/push-protection-allow-email.md
+++ b/translations/ja-JP/data/reusables/secret-scanning/push-protection-allow-email.md
@@ -1,10 +1,10 @@
 ---
-ms.openlocfilehash: ba22b3461f3e8bf93257698d2c6f4eb4bc863949
-ms.sourcegitcommit: 80842b4e4c500daa051eff0ccd7cde91c2d4bb36
+ms.openlocfilehash: 46850cadc908d94d514fde76ee0fecbddce0affe
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: ja-JP
-ms.lasthandoff: 09/12/2022
-ms.locfileid: "147409831"
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148109061"
 ---
 {% ifversion secret-scanning-push-protection-email %}共同作成者がシークレットのプッシュ保護ブロックをバイパスすると、{% data variables.product.prodname_dotcom %} により、電子メール通知をオプトインした Organization の所有者、セキュリティ マネージャー、リポジトリ管理者にも電子メール アラートが送信されます。
-{% endif %}
\ No newline at end of file
+{% endif %}
diff --git a/translations/ja-JP/data/reusables/secret-scanning/push-protection-remove-secret.md b/translations/ja-JP/data/reusables/secret-scanning/push-protection-remove-secret.md
index df11ed08b7..58efbca68b 100644
--- a/translations/ja-JP/data/reusables/secret-scanning/push-protection-remove-secret.md
+++ b/translations/ja-JP/data/reusables/secret-scanning/push-protection-remove-secret.md
@@ -1,9 +1,9 @@
 ---
-ms.openlocfilehash: d22214ea8eb5bc89912bed3c43a678fba80f014b
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: 3d0f861b8ee9ff6b4e948dee7dfb67a648021404
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: ja-JP
-ms.lasthandoff: 09/05/2022
-ms.locfileid: "147578734"
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148109388"
 ---
-シークレットが本物であることを確認したら、再度プッシュする前に、ブランチから ("それが表示されるすべてのコミットから") シークレットを削除する必要があります。
\ No newline at end of file
+シークレットが本物であることを確認したら、再度プッシュする前に、ブランチから ("それが表示されるすべてのコミットから") シークレットを削除する必要があります。
diff --git a/translations/ja-JP/data/reusables/secret-scanning/push-protection-web-ui-choice.md b/translations/ja-JP/data/reusables/secret-scanning/push-protection-web-ui-choice.md
index 32360458e8..eacc4cb86f 100644
--- a/translations/ja-JP/data/reusables/secret-scanning/push-protection-web-ui-choice.md
+++ b/translations/ja-JP/data/reusables/secret-scanning/push-protection-web-ui-choice.md
@@ -1,10 +1,10 @@
 ---
-ms.openlocfilehash: 7ebce174e896689b1976b9d43f1f0884ce065229
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: 7bb1603715c255f08ac0bfbe7ff2cdbfe99a3134
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: ja-JP
-ms.lasthandoff: 09/05/2022
-ms.locfileid: "147683800"
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148109121"
 ---
 Web UI を使用して、プッシュ保護が有効になっているシークレット スキャンを使用して、サポートされているシークレットをリポジトリまたは organization にコミットすると、{% data variables.product.prodname_dotcom %} によってプッシュがブロックされます。 
 
@@ -18,4 +18,4 @@ Web UI を使用して、プッシュ保護が有効になっているシーク
 
   ![シークレット スキャンのプッシュ保護のためにブロックされた Web UI でのコミットを示すスクリーンショット](/assets/images/help/repository/secret-scanning-push-protection-web-ui-commit-blocked-banner.png)
   
-{% endif %}
\ No newline at end of file
+{% endif %}
diff --git a/translations/ja-JP/data/reusables/security-advisory/security-advisory-overview.md b/translations/ja-JP/data/reusables/security-advisory/security-advisory-overview.md
index bc7964470e..3c4c6a964f 100644
--- a/translations/ja-JP/data/reusables/security-advisory/security-advisory-overview.md
+++ b/translations/ja-JP/data/reusables/security-advisory/security-advisory-overview.md
@@ -1,9 +1 @@
----
-ms.openlocfilehash: aa9f7cd0b911ddfc6e144c7c91cecd0374286b13
-ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
-ms.translationtype: HT
-ms.contentlocale: ja-JP
-ms.lasthandoff: 09/10/2022
-ms.locfileid: "145137531"
----
-{% data variables.product.prodname_security_advisories %} を使用すると、リポジトリメンテナがプロジェクトのセキュリティの脆弱性について非公開で議論し、修正できます。 共同で修正を行った後、リポジトリ保守担当者はセキュリティ アドバイザリを公開して、セキュリティの脆弱性をプロジェクトのコミュニティに開示することができます。 セキュリティ アドバイザリを公開することにより、リポジトリ保守担当者は、コミュニティがいっそう簡単にパッケージの依存関係を更新したり、セキュリティの脆弱性の影響を調べたりできるようにします。
+Repository security advisories allow repository maintainers to privately discuss and fix a security vulnerability in a project. After collaborating on a fix, repository maintainers can publish the security advisory to publicly disclose the security vulnerability to the project's community. By publishing security advisories, repository maintainers make it easier for their community to update package dependencies and research the impact of the security vulnerabilities.
diff --git a/translations/ja-JP/data/reusables/security-overview/information-varies-GHAS.md b/translations/ja-JP/data/reusables/security-overview/information-varies-GHAS.md
index 807851a0fe..99c5c8d771 100644
--- a/translations/ja-JP/data/reusables/security-overview/information-varies-GHAS.md
+++ b/translations/ja-JP/data/reusables/security-overview/information-varies-GHAS.md
@@ -1,10 +1,10 @@
 ---
-ms.openlocfilehash: f6fdffa80f99a405c65fc6f536b8a821cc1c334d
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: 55863906d744c997149aa2fffd6541f32e42c0d1
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: ja-JP
-ms.lasthandoff: 09/05/2022
-ms.locfileid: "147525741"
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148108905"
 ---
 {% ifversion security-overview-displayed-alerts %} セキュリティの概要に示される情報は、リポジトリへのアクセス権や、{% data variables.product.prodname_GH_advanced_security %} がこれらのリポジトリによって使用されているかどうかに応じて異なります。
-{% endif %}
\ No newline at end of file
+{% endif %}
diff --git a/translations/ja-JP/data/reusables/security-overview/permissions.md b/translations/ja-JP/data/reusables/security-overview/permissions.md
index 2cf85d19c5..43dd55172d 100644
--- a/translations/ja-JP/data/reusables/security-overview/permissions.md
+++ b/translations/ja-JP/data/reusables/security-overview/permissions.md
@@ -1 +1 @@
-Organization owners and security managers can access the security overview for organizations{% ifversion ghec or ghes > 3.4 or ghae > 3.4 %} and view their organization's repositories via the enterprise-level security overview. Enterprise owners can use the enterprise-level security overview to view all repositories in their enterprise's organizations{% endif %}. Members of a team can see the security overview for repositories that the team has admin privileges for.
+{% ifversion not fpt %}Organization owners and security managers can access the organization-level security overview{% ifversion ghec or ghes > 3.4 or ghae > 3.4 %} and view alerts across multiple organizations via the enterprise-level security overview. Enterprise owners can only view repositories and alerts for organizations where they are added as an organization owner or security manager{% endif %}. {% ifversion ghec or ghes > 3.6 or ghae > 3.6 %}Organization members can access the organization-level security overview to view results for repositories where they have admin privileges or have been granted access to security alerts.{% else %}Members of a team can see the security overview for repositories that the team has admin privileges for.{% endif %}{% endif %}
diff --git a/translations/ja-JP/data/reusables/security/displayed-information.md b/translations/ja-JP/data/reusables/security/displayed-information.md
index 91f9a8a279..fa5451eb0e 100644
--- a/translations/ja-JP/data/reusables/security/displayed-information.md
+++ b/translations/ja-JP/data/reusables/security/displayed-information.md
@@ -1,16 +1,8 @@
----
-ms.openlocfilehash: c9e2c1bf2b01805ed973effedd219c3552ac2bf4
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
-ms.translationtype: HT
-ms.contentlocale: ja-JP
-ms.lasthandoff: 09/05/2022
-ms.locfileid: "146455670"
----
-既存のリポジトリで1つ以上のセキュリティ及び分析機能を有効化すると、数分のうちに{% data variables.product.prodname_dotcom %}上に結果が表示されます。
+When you enable one or more security and analysis features for existing repositories, you will see any results displayed on {% data variables.product.prodname_dotcom %} within minutes:
 
-- 既存のすべてのリポジトリは、選択された設定を持ちます。
-- 新しいリポジトリに対するチェックボックスを有効化していれば、新しいリポジトリは選択された設定に従います。{% ifversion fpt or ghec %}
-- 関連するサービスに適用するマニフェストファイルをスキャンするために権限を使用します。
-- 有効化すると、依存関係グラフに依存関係情報が表示されます。
-- 有効化すると、{% data variables.product.prodname_dotcom %} により、脆弱な依存関係またはマルウェアに対して {% data variables.product.prodname_dependabot_alerts %}が生成されます。{% endif %}{% ifversion fpt or ghec or ghes > 3.2 %}
-- 有効化すると、{% data variables.product.prodname_dependabot %} セキュリティ更新プログラムは、{% data variables.product.prodname_dependabot_alerts %} がトリガーされたときに、脆弱な依存関係をアップグレードするための pull request を作成します。{% endif %}
+- All the existing repositories will have the selected configuration.
+- New repositories will follow the selected configuration if you've enabled the checkbox for new repositories.{% ifversion fpt or ghec %}
+- We use the permissions to scan for manifest files to apply the relevant services.
+- If enabled, you'll see dependency information in the dependency graph.
+- If enabled, {% data variables.product.prodname_dotcom %} will generate {% data variables.product.prodname_dependabot_alerts %} for vulnerable dependencies or malware.{% endif %}{% ifversion fpt or ghec or ghes %}
+- If enabled, {% data variables.product.prodname_dependabot %} security updates will create pull requests to upgrade vulnerable dependencies when {% data variables.product.prodname_dependabot_alerts %} are triggered.{% endif %}
diff --git a/translations/ja-JP/data/reusables/ssh/key-type-support.md b/translations/ja-JP/data/reusables/ssh/key-type-support.md
index 324873282a..2c2295e0ba 100644
--- a/translations/ja-JP/data/reusables/ssh/key-type-support.md
+++ b/translations/ja-JP/data/reusables/ssh/key-type-support.md
@@ -25,4 +25,4 @@ Your site administrator can adjust the cutoff date for connections using RSA-SHA
 
 {% endnote %}
 
-{% endif %}
\ No newline at end of file
+{% endif %}
diff --git a/translations/ja-JP/data/reusables/support/entitlements-note.md b/translations/ja-JP/data/reusables/support/entitlements-note.md
index 426b28570e..79040074fe 100644
--- a/translations/ja-JP/data/reusables/support/entitlements-note.md
+++ b/translations/ja-JP/data/reusables/support/entitlements-note.md
@@ -1,13 +1,13 @@
 ---
-ms.openlocfilehash: 52b42a427d098d34e26dc12b20fce44ef15e7458
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: 35ed9fffb50a66b6867f71bf0e7e579284b9ee5d
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: ja-JP
-ms.lasthandoff: 09/05/2022
-ms.locfileid: "147080101"
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148109387"
 ---
 {% note %}
 
 **注:** Organization または Enterprise アカウントに関連付けられたチケットを表示するには、Enterprise サポート エンタイトルメントが必要です。 詳細については、「[Managing support entitlements for your enterprise (エンタープライズのサポート エンタイトルメントの管理)](/enterprise-cloud@latest/admin/user-management/managing-users-in-your-enterprise/managing-support-entitlements-for-your-enterprise)」を参照してください。
 
-{% endnote %}  
\ No newline at end of file
+{% endnote %}  
diff --git a/translations/ja-JP/data/reusables/support/navigate-to-my-tickets.md b/translations/ja-JP/data/reusables/support/navigate-to-my-tickets.md
index 4a4f38ec09..8a7b4dccd2 100644
--- a/translations/ja-JP/data/reusables/support/navigate-to-my-tickets.md
+++ b/translations/ja-JP/data/reusables/support/navigate-to-my-tickets.md
@@ -1,12 +1,12 @@
 ---
-ms.openlocfilehash: 88b8399eab75b7ac5a3c2f0e12eec2fc0000df2d
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: fb2826ec7adf7edcff710866d08654c7f94ab484
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: ja-JP
-ms.lasthandoff: 09/05/2022
-ms.locfileid: "147080095"
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148108868"
 ---
 1. [GitHub サポート ポータル](https://support.github.com/)に移動します。
 1. ヘッダーで **[マイ チケット]** をクリックします。
 
-   ![GitHub サポート ポータルのヘッダーに [マイ チケット] リンクが示されたスクリーンショット。](/assets/images/help/support/my-tickets-header.png)
\ No newline at end of file
+   ![GitHub サポート ポータルのヘッダーに [マイ チケット] リンクが示されたスクリーンショット。](/assets/images/help/support/my-tickets-header.png)
diff --git a/translations/ja-JP/data/reusables/supported-languages/C.md b/translations/ja-JP/data/reusables/supported-languages/C.md
index 0c5b57472a..77a301dce0 100644
--- a/translations/ja-JP/data/reusables/supported-languages/C.md
+++ b/translations/ja-JP/data/reusables/supported-languages/C.md
@@ -1,9 +1 @@
----
-ms.openlocfilehash: 586b13b105c32f8b67218cc277af8916dc2c8783
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
-ms.translationtype: HT
-ms.contentlocale: ja-JP
-ms.lasthandoff: 09/05/2022
-ms.locfileid: "147052201"
----
-| C {% ifversion fpt or ghec %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} | {% octicon "x" aria-label="The X icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif ghes %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} {% ifversion ghes > 3.2 %}| {% octicon "x" aria-label="The X icon" %}{% endif %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif ghae %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% endif %}
+| C {% ifversion fpt or ghec %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} | {% octicon "x" aria-label="The X icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif ghes %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} | {% octicon "x" aria-label="The X icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif ghae %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% endif %}
diff --git a/translations/ja-JP/data/reusables/supported-languages/Cpp.md b/translations/ja-JP/data/reusables/supported-languages/Cpp.md
index dae804a16a..5a255a3ae3 100644
--- a/translations/ja-JP/data/reusables/supported-languages/Cpp.md
+++ b/translations/ja-JP/data/reusables/supported-languages/Cpp.md
@@ -1,9 +1 @@
----
-ms.openlocfilehash: 801a3486a32e80dbb0a85cef76c2c6887babd258
-ms.sourcegitcommit: 80842b4e4c500daa051eff0ccd7cde91c2d4bb36
-ms.translationtype: HT
-ms.contentlocale: ja-JP
-ms.lasthandoff: 09/12/2022
-ms.locfileid: "147052033"
----
-| C++ {% ifversion fpt or ghec %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} | {% octicon "x" aria-label="The X icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif ghes %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} {% ifversion ghes > 3.2 %}| {% octicon "x" aria-label="The X icon" %}{% endif %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif ghae %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% endif %}
+| C++ {% ifversion fpt or ghec %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} | {% octicon "x" aria-label="The X icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif ghes %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} | {% octicon "x" aria-label="The X icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif ghae %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% endif %}
diff --git a/translations/ja-JP/data/reusables/supported-languages/Cs.md b/translations/ja-JP/data/reusables/supported-languages/Cs.md
index f0d4efd984..dc5fa3e1e8 100644
--- a/translations/ja-JP/data/reusables/supported-languages/Cs.md
+++ b/translations/ja-JP/data/reusables/supported-languages/Cs.md
@@ -1,9 +1 @@
----
-ms.openlocfilehash: 5e148185ae940f67f4137f209ce451f74faa1a7e
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
-ms.translationtype: HT
-ms.contentlocale: ja-JP
-ms.lasthandoff: 09/05/2022
-ms.locfileid: "147052361"
----
-| C# {% ifversion fpt or ghec %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>`dotnet` CLI | {% octicon "check" aria-label="The check icon" %}<br>`dotnet` CLI | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>`dotnet` CLI |{% elsif ghes %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>`dotnet` CLI  {% ifversion ghes > 3.2 %}| {% octicon "check" aria-label="The check icon" %}<br>`dotnet` CLI{% endif %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>`dotnet` CLI |{% elsif ghae %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>`dotnet` CLI |{% endif %}
+| C# {% ifversion fpt or ghec %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>`dotnet` CLI | {% octicon "check" aria-label="The check icon" %}<br>`dotnet` CLI | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>`dotnet` CLI |{% elsif ghes %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>`dotnet` CLI  | {% octicon "check" aria-label="The check icon" %}<br>`dotnet` CLI | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>`dotnet` CLI |{% elsif ghae %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>`dotnet` CLI |{% endif %}
diff --git a/translations/ja-JP/data/reusables/supported-languages/go.md b/translations/ja-JP/data/reusables/supported-languages/go.md
index fa73b331e6..2670d677ba 100644
--- a/translations/ja-JP/data/reusables/supported-languages/go.md
+++ b/translations/ja-JP/data/reusables/supported-languages/go.md
@@ -1,9 +1 @@
----
-ms.openlocfilehash: d811deaf63f404f0ded3952a4411fc519d29547a
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
-ms.translationtype: HT
-ms.contentlocale: ja-JP
-ms.lasthandoff: 09/05/2022
-ms.locfileid: "147066979"
----
-| Go {% ifversion fpt or ghec %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>Go モジュール | {% octicon "check" aria-label="The check icon" %}<br> Go モジュール | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif ghes %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>Go モジュール {% ifversion ghes > 3.2 %}| {% octicon "check" aria-label="The check icon" %}<br>Go モジュール {% endif %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif ghes %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif ghae %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% endif %}
+| Go {% ifversion fpt or ghec %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>Go modules | {% octicon "check" aria-label="The check icon" %}<br> Go modules | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif ghes %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>Go modules | {% octicon "check" aria-label="The check icon" %}<br>Go modules | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif ghes %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif ghae %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% endif %}
diff --git a/translations/ja-JP/data/reusables/supported-languages/java.md b/translations/ja-JP/data/reusables/supported-languages/java.md
index 0e516886f1..9572164283 100644
--- a/translations/ja-JP/data/reusables/supported-languages/java.md
+++ b/translations/ja-JP/data/reusables/supported-languages/java.md
@@ -1,9 +1,9 @@
 ---
-ms.openlocfilehash: 7429b486c393de2a4c5184914b3528d1f189c2a5
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: 2e8ea634a95d2bca03b70aef430be7e638272605
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: ja-JP
-ms.lasthandoff: 09/05/2022
-ms.locfileid: "147052025"
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148109452"
 ---
-| Java {% ifversion fpt or ghec %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>Maven | {% octicon "check" aria-label="The check icon" %}<br>Maven、Gradle | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>Maven、Gradle |{% elsif ghes %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>Maven {% ifversion ghes > 3.2 %} | {% octicon "check" aria-label="The check icon" %}<br>Maven、Gradle{% endif %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>Maven、Gradle |{% elsif ghae %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>Maven、Gradle |{% endif %}
+| Java {% ifversion fpt or ghec %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>Maven | {% octicon "check" aria-label="The check icon" %}<br>Maven、Gradle | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>Maven、Gradle |{% elsif ghes %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>Maven | {% octicon "check" aria-label="The check icon" %}<br>Maven、Gradle | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>Maven、Gradle |{% elsif ghae %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>Maven、Gradle |{% endif %}
diff --git a/translations/ja-JP/data/reusables/supported-languages/javascript.md b/translations/ja-JP/data/reusables/supported-languages/javascript.md
index 3e347bf24f..d11df349ce 100644
--- a/translations/ja-JP/data/reusables/supported-languages/javascript.md
+++ b/translations/ja-JP/data/reusables/supported-languages/javascript.md
@@ -1,9 +1,9 @@
 ---
-ms.openlocfilehash: dbf7349c32cb38d666f89d149831f5254e2afee2
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: 9d072e402eca457ea6ebc803c1c56461d909e11a
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: ja-JP
-ms.lasthandoff: 09/05/2022
-ms.locfileid: "147052161"
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148108874"
 ---
-| JavaScript {% ifversion fpt or ghec %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>npm、Yarn | {% octicon "check" aria-label="The check icon" %}<br>npm | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>npm |{% elsif ghes %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>npm、Yarn {% ifversion ghes > 3.2 %}| {% octicon "check" aria-label="The check icon" %}<br>npm{% endif %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>npm |{% elsif ghae %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>npm |{% endif %}
+| JavaScript {% ifversion fpt or ghec %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>npm、Yarn | {% octicon "check" aria-label="The check icon" %}<br>npm | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>npm |{% elsif ghes %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>npm、Yarn | {% octicon "check" aria-label="The check icon" %}<br>npm | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>npm |{% elsif ghae %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>npm |{% endif %}
diff --git a/translations/ja-JP/data/reusables/supported-languages/php.md b/translations/ja-JP/data/reusables/supported-languages/php.md
index 47f8aeca50..a6cde8219a 100644
--- a/translations/ja-JP/data/reusables/supported-languages/php.md
+++ b/translations/ja-JP/data/reusables/supported-languages/php.md
@@ -1,9 +1 @@
----
-ms.openlocfilehash: eb8ee6547c65b4cea6e6528d2f96132f1936e0d6
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
-ms.translationtype: HT
-ms.contentlocale: ja-JP
-ms.lasthandoff: 09/05/2022
-ms.locfileid: "147052242"
----
-| PHP {% ifversion fpt or ghec %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<sup>1</sup> | {% octicon "check" aria-label="The check icon" %}<br>Composer | {% octicon "check" aria-label="The check icon" %}<br>Composer | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif ghes %}| {% octicon "check" aria-label="The check icon" %}<sup>1</sup> | {% octicon "check" aria-label="The check icon" %}<br>Composer {% ifversion ghes > 3.2 %}| {% octicon "check" aria-label="The check icon" %}<br>Composer{% endif %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif ghae %}| {% octicon "check" aria-label="The check icon" %}<sup>1</sup> | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% endif %}
+| PHP {% ifversion fpt or ghec %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<sup>1</sup> | {% octicon "check" aria-label="The check icon" %}<br>Composer | {% octicon "check" aria-label="The check icon" %}<br>Composer | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif ghes %}| {% octicon "check" aria-label="The check icon" %}<sup>1</sup> | {% octicon "check" aria-label="The check icon" %}<br>Composer | {% octicon "check" aria-label="The check icon" %}<br>Composer | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif ghae %}| {% octicon "check" aria-label="The check icon" %}<sup>1</sup> | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% endif %}
diff --git a/translations/ja-JP/data/reusables/supported-languages/products-table-header.md b/translations/ja-JP/data/reusables/supported-languages/products-table-header.md
index 23d8e71ca4..6147ff8b8b 100644
--- a/translations/ja-JP/data/reusables/supported-languages/products-table-header.md
+++ b/translations/ja-JP/data/reusables/supported-languages/products-table-header.md
@@ -1,9 +1,4 @@
----
-ms.openlocfilehash: 2bbdb89e1c3f02014566e38f43cd482cc54af641
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
-ms.translationtype: HT
-ms.contentlocale: ja-JP
-ms.lasthandoff: 09/05/2022
-ms.locfileid: "147052234"
----
-{% ifversion fpt or ghec %}| [GitHub Copilot](/copilot/overview-of-github-copilot/about-github-copilot#about-github-copilot) | [コード ナビゲーション](/github/managing-files-in-a-repository/navigating-code-on-github) | [{% data variables.product.prodname_code_scanning_capc %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning) | [依存関係グラフ、{% data variables.product.prodname_dependabot_alerts %}、{% data variables.product.prodname_dependabot_security_updates %}](/code-security/supply-chain-security/about-the-dependency-graph#supported-package-ecosystems) | [{% data variables.product.prodname_dependabot_version_updates %}](/code-security/supply-chain-security/about-dependabot-version-updates#supported-repositories-and-ecosystems) | [{% data variables.product.prodname_actions %}](/actions/guides/about-continuous-integration#supported-languages) | [{% data variables.product.prodname_registry %}](/packages/learn-github-packages/introduction-to-github-packages#supported-clients-and-formats) | | :-- | :-: | :-: | :-: | :-: | :-: | :-: | :-: |{% elsif ghes %}| [{% data variables.product.prodname_code_scanning_capc %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning) | [依存関係グラフ、{% data variables.product.prodname_dependabot_alerts %}{% ifversion ghes > 3.2 %}、{% data variables.product.prodname_dependabot_security_updates %}{% endif %}](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph#supported-package-ecosystems) {% ifversion ghes > 3.2 %}| [{% data variables.product.prodname_dependabot_version_updates %}](/code-security/supply-chain-security/about-dependabot-version-updates#supported-repositories-and-ecosystems){% endif %} | [{% data variables.product.prodname_actions %}](/actions/guides/about-continuous-integration#supported-languages) | [{% data variables.product.prodname_registry %}](/packages/learn-github-packages/introduction-to-github-packages#supported-clients-and-formats) | | :-- | :-: | :-: {% ifversion ghes > 3.2 %}| :-: {% endif %}| :-: | :-: |{% elsif ghae %}| [{% data variables.product.prodname_code_scanning_capc %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning) | [{% data variables.product.prodname_actions %}](/actions/guides/about-continuous-integration#supported-languages) | [{% data variables.product.prodname_registry %}](/packages/learn-github-packages/introduction-to-github-packages#supported-clients-and-formats) | | :-- | :-: | :-: | :-: |{% endif %}
+{% ifversion fpt or ghec %}| [GitHub Copilot](/copilot/overview-of-github-copilot/about-github-copilot#about-github-copilot) | [Code navigation](/github/managing-files-in-a-repository/navigating-code-on-github) | [{% data variables.product.prodname_code_scanning_capc %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning) | [Dependency graph, {% data variables.product.prodname_dependabot_alerts %}, {% data variables.product.prodname_dependabot_security_updates %}](/code-security/supply-chain-security/about-the-dependency-graph#supported-package-ecosystems) | [{% data variables.product.prodname_dependabot_version_updates %}](/code-security/supply-chain-security/about-dependabot-version-updates#supported-repositories-and-ecosystems) | [{% data variables.product.prodname_actions %}](/actions/guides/about-continuous-integration#supported-languages) | [{% data variables.product.prodname_registry %}](/packages/learn-github-packages/introduction-to-github-packages#supported-clients-and-formats) |
+| :-- | :-: | :-: | :-: | :-: | :-: | :-: | :-: |{% elsif ghes %}| [{% data variables.product.prodname_code_scanning_capc %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning) | [Dependency graph, {% data variables.product.prodname_dependabot_alerts %}, {% data variables.product.prodname_dependabot_security_updates %}](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph#supported-package-ecosystems) {% ifversion ghes %}| [{% data variables.product.prodname_dependabot_version_updates %}](/code-security/supply-chain-security/about-dependabot-version-updates#supported-repositories-and-ecosystems){% endif %} | [{% data variables.product.prodname_actions %}](/actions/guides/about-continuous-integration#supported-languages) | [{% data variables.product.prodname_registry %}](/packages/learn-github-packages/introduction-to-github-packages#supported-clients-and-formats) |
+| :-- | :-: | :-: {% ifversion ghes %}| :-: {% endif %}| :-: | :-: |{% elsif ghae %}| [{% data variables.product.prodname_code_scanning_capc %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning) | [{% data variables.product.prodname_actions %}](/actions/guides/about-continuous-integration#supported-languages) | [{% data variables.product.prodname_registry %}](/packages/learn-github-packages/introduction-to-github-packages#supported-clients-and-formats) |
+| :-- | :-: | :-: | :-: |{% endif %}
diff --git a/translations/ja-JP/data/reusables/supported-languages/python.md b/translations/ja-JP/data/reusables/supported-languages/python.md
index b5d9773952..d8df9a72ba 100644
--- a/translations/ja-JP/data/reusables/supported-languages/python.md
+++ b/translations/ja-JP/data/reusables/supported-languages/python.md
@@ -1,9 +1 @@
----
-ms.openlocfilehash: 0e9bc62ae013232cf0a15ebb3dfd1948b672480e
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
-ms.translationtype: HT
-ms.contentlocale: ja-JP
-ms.lasthandoff: 09/05/2022
-ms.locfileid: "147052337"
----
-| Python {% ifversion fpt or ghec %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} <br>precise | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>pip | {% octicon "check" aria-label="The check icon" %}<br>pip | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif ghes %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>pip {% ifversion ghes > 3.2 %}| {% octicon "check" aria-label="The check icon" %}<br>pip{% endif %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif ghae %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% endif %}
+| Python {% ifversion fpt or ghec %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} <br>precise| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>pip | {% octicon "check" aria-label="The check icon" %}<br>pip | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif ghes %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>pip | {% octicon "check" aria-label="The check icon" %}<br>pip | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif ghae %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% endif %}
diff --git a/translations/ja-JP/data/reusables/supported-languages/ruby.md b/translations/ja-JP/data/reusables/supported-languages/ruby.md
index a0be42ff11..69eaaa15cd 100644
--- a/translations/ja-JP/data/reusables/supported-languages/ruby.md
+++ b/translations/ja-JP/data/reusables/supported-languages/ruby.md
@@ -1,9 +1,9 @@
 ---
-ms.openlocfilehash: a740daee0bb180392f099956cf9dc26b6b8c83ed
-ms.sourcegitcommit: 80842b4e4c500daa051eff0ccd7cde91c2d4bb36
+ms.openlocfilehash: 7609bd15d8e77a5da778cfb3a4acd21ea7884e46
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: ja-JP
-ms.lasthandoff: 09/11/2022
-ms.locfileid: "147885045"
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148109372"
 ---
-| Ruby {% ifversion fpt or ghec %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>RubyGems | {% octicon "check" aria-label="The check icon" %}<br>RubyGems | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>RubyGems |{% elsif ghes %}| {% octicon "check" aria-label="The check icon" %}<sup>1</sup> | {% octicon "check" aria-label="The check icon" %}<br>RubyGems {% ifversion ghes > 3.2 %}| {% octicon "check" aria-label="The check icon" %}<br>RubyGems{% endif %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>RubyGems |{% elsif ghae %}| {% octicon "check" aria-label="The check icon" %}<sup>1</sup> | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>RubyGems |{% endif %}
+| Ruby {% ifversion fpt or ghec %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>RubyGems | {% octicon "check" aria-label="The check icon" %}<br>RubyGems | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>RubyGems |{% elsif ghes %}| {% octicon "check" aria-label="The check icon" %}<sup>1</sup> | {% octicon "check" aria-label="The check icon" %}<br>RubyGems | {% octicon "check" aria-label="The check icon" %}<br>RubyGems | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>RubyGems |{% elsif ghae %}| {% octicon "check" aria-label="The check icon" %}<sup>1</sup> | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>RubyGems |{% endif %}
diff --git a/translations/ja-JP/data/reusables/supported-languages/scala.md b/translations/ja-JP/data/reusables/supported-languages/scala.md
index 01b9533ffc..4da351ea79 100644
--- a/translations/ja-JP/data/reusables/supported-languages/scala.md
+++ b/translations/ja-JP/data/reusables/supported-languages/scala.md
@@ -1,9 +1 @@
----
-ms.openlocfilehash: 3e5390b74f8d438fc7f83cd2f9e1e6917d4282f3
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
-ms.translationtype: HT
-ms.contentlocale: ja-JP
-ms.lasthandoff: 09/05/2022
-ms.locfileid: "147052329"
----
-| Scala {% ifversion fpt or ghec %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} | {% octicon "check" aria-label="The check icon" %}<sup>1</sup> | {% octicon "check" aria-label="The check icon" %}<br>Maven | {% octicon "check" aria-label="The check icon" %}<br>Maven、Gradle | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif ghes %}| {% octicon "check" aria-label="The check icon" %}<sup>1</sup> | {% octicon "check" aria-label="The check icon" %}<br>Maven、Gradle {% ifversion ghes > 3.2 %}| {% octicon "check" aria-label="The check icon" %}<br>Maven、Gradle{% endif %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif ghae %}| {% octicon "check" aria-label="The check icon" %}<sup>1</sup> | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% endif %}
+| Scala {% ifversion fpt or ghec %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} | {% octicon "check" aria-label="The check icon" %}<sup>1</sup> | {% octicon "check" aria-label="The check icon" %}<br>Maven | {% octicon "check" aria-label="The check icon" %}<br>Maven, Gradle | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif ghes %}| {% octicon "check" aria-label="The check icon" %}<sup>1</sup> | {% octicon "check" aria-label="The check icon" %}<br>Maven, Gradle | {% octicon "check" aria-label="The check icon" %}<br>Maven, Gradle | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif ghae %}| {% octicon "check" aria-label="The check icon" %}<sup>1</sup> | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% endif %}
diff --git a/translations/ja-JP/data/reusables/supported-languages/typescript.md b/translations/ja-JP/data/reusables/supported-languages/typescript.md
index 8500ddfb00..168d8b203e 100644
--- a/translations/ja-JP/data/reusables/supported-languages/typescript.md
+++ b/translations/ja-JP/data/reusables/supported-languages/typescript.md
@@ -1,9 +1,9 @@
 ---
-ms.openlocfilehash: 728285dc8fbdfcfa3e6a2f047383bcdc7875b8ff
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: 6128eeee4e46b139b78ce717ed3723ba0dbba3ba
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: ja-JP
-ms.lasthandoff: 09/05/2022
-ms.locfileid: "147052097"
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148109251"
 ---
-| TypeScript {% ifversion fpt or ghec %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>npm、Yarn | {% octicon "check" aria-label="The check icon" %}<br>npm | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>npm |{% elsif ghes %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>npm、Yarn {% ifversion ghes > 3.2 %}| {% octicon "check" aria-label="The check icon" %}<br>npm{% endif %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>npm |{% elsif ghae %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>npm |{% endif %}
+| TypeScript {% ifversion fpt or ghec %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>npm、Yarn | {% octicon "check" aria-label="The check icon" %}<br>npm | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>npm |{% elsif ghes %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>npm、Yarn | {% octicon "check" aria-label="The check icon" %}<br>npm | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>npm |{% elsif ghae %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>npm |{% endif %}
diff --git a/translations/ja-JP/data/reusables/webhooks/webhooks-rest-api-links.md b/translations/ja-JP/data/reusables/webhooks/webhooks-rest-api-links.md
index a6d3d93624..51191b7a9e 100644
--- a/translations/ja-JP/data/reusables/webhooks/webhooks-rest-api-links.md
+++ b/translations/ja-JP/data/reusables/webhooks/webhooks-rest-api-links.md
@@ -1,13 +1,5 @@
----
-ms.openlocfilehash: 3e175aefd9a243a098b5c35ca6d4068a651d2f61
-ms.sourcegitcommit: 9a7b3a9ccb983af5df2cd94da7fecf7a8237529b
-ms.translationtype: HT
-ms.contentlocale: ja-JP
-ms.lasthandoff: 09/09/2022
-ms.locfileid: "147878487"
----
-Webhook REST API を使用すれば、リポジトリ、組織、アプリ Webhook の管理ができます。{% ifversion fpt or ghes > 3.2 or ghae or ghec %}この API を使って Webhook の配信を一覧表示したり、Webhook の個々の配信を取得して再配信したりできます。これは、外部のアプリまたはサービスに統合できます。{% endif %}REST API を使用して、Webhook の構成を変更することもできます。 たとえば、ペイロードURL、コンテントタイプ、SSLの検証、シークレットを変更できます。 詳細については、次を参照してください。
+The webhook REST APIs enable you to manage repository, organization, and app webhooks. You can use this API to list webhook deliveries for a webhook, or get and redeliver an individual delivery for a webhook, which can be integrated into an external app or service. You can also use the REST API to change the configuration of the webhook. For example, you can modify the payload URL, content type, SSL verification, and secret. For more information, see:
 
-- [リポジトリ Webhook REST API](/rest/reference/webhooks#repository-webhooks)
-- [組織の Webhook REST API](/rest/reference/orgs#webhooks)
-- [{% data variables.product.prodname_github_app %} Webhook REST API](/rest/reference/apps#webhooks)
+- [Repository Webhooks REST API](/rest/reference/webhooks#repository-webhooks)
+- [Organization Webhooks REST API](/rest/reference/orgs#webhooks)
+- [{% data variables.product.prodname_github_app %} Webhooks REST API](/rest/reference/apps#webhooks)
diff --git a/translations/ja-JP/data/variables/product.yml b/translations/ja-JP/data/variables/product.yml
index 16646ba56b..09ba187929 100644
--- a/translations/ja-JP/data/variables/product.yml
+++ b/translations/ja-JP/data/variables/product.yml
@@ -72,7 +72,7 @@ prodname_codeql_cli: 'CodeQL CLI'
 # CodeQL usually bumps its minor version for each minor version of GHES.
 # Update this whenever a new enterprise version of CodeQL is being prepared.
 codeql_cli_ghes_recommended_version: >-
-  {% ifversion ghes < 3.3 %}2.6.3{% elsif ghes < 3.5 or ghae < 3.5 %}2.7.6{% elsif ghes = 3.5 or ghae = 3.5 %}2.8.5{% elsif ghes = 3.6 or ghae = 3.6 %}2.9.4{% elsif ghes = 3.7 or ghae = 3.7 %}2.10.5{% endif %}
+  {% ifversion ghes < 3.5 or ghae < 3.5 %}2.7.6{% elsif ghes = 3.5 or ghae = 3.5 %}2.8.5{% elsif ghes = 3.6 or ghae = 3.6 %}2.9.4{% elsif ghes = 3.7 or ghae = 3.7 %}2.10.5{% endif %}
 
 # Projects v2
 prodname_projects_v2: 'Projects'
diff --git a/translations/log/msft-cn-resets.csv b/translations/log/msft-cn-resets.csv
index 25ceaf3944..6b679303f8 100644
--- a/translations/log/msft-cn-resets.csv
+++ b/translations/log/msft-cn-resets.csv
@@ -64,6 +64,7 @@ translations/zh-CN/content/admin/identity-and-access-management/using-enterprise
 translations/zh-CN/content/admin/identity-and-access-management/using-enterprise-managed-users-and-saml-for-iam/index.md,file deleted because it no longer exists in main
 translations/zh-CN/content/admin/identity-and-access-management/using-enterprise-managed-users-and-saml-for-iam/managing-team-memberships-with-identity-provider-groups.md,file deleted because it no longer exists in main
 translations/zh-CN/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/configuring-user-provisioning-for-your-enterprise.md,file deleted because it no longer exists in main
+translations/zh-CN/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-xenserver.md,file deleted because it no longer exists in main
 translations/zh-CN/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-advanced-security-in-your-enterprise.md,file deleted because it no longer exists in main
 translations/zh-CN/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-project-board-policies-in-your-enterprise.md,file deleted because it no longer exists in main
 translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise/managing-unowned-organizations-in-your-enterprise.md,file deleted because it no longer exists in main
@@ -72,7 +73,20 @@ translations/zh-CN/content/authentication/troubleshooting-commit-signature-verif
 translations/zh-CN/content/billing/managing-billing-for-github-codespaces/about-billing-for-codespaces.md,file deleted because it no longer exists in main
 translations/zh-CN/content/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-codespaces.md,file deleted because it no longer exists in main
 translations/zh-CN/content/billing/managing-billing-for-github-codespaces/viewing-your-codespaces-usage.md,file deleted because it no longer exists in main
+translations/zh-CN/content/code-security/dependabot/dependabot-alerts/browsing-security-advisories-in-the-github-advisory-database.md,file deleted because it no longer exists in main
 translations/zh-CN/content/code-security/dependabot/dependabot-alerts/browsing-security-vulnerabilities-in-the-github-advisory-database.md,file deleted because it no longer exists in main
+translations/zh-CN/content/code-security/dependabot/dependabot-alerts/editing-security-advisories-in-the-github-advisory-database.md,file deleted because it no longer exists in main
+translations/zh-CN/content/code-security/repository-security-advisories/about-coordinated-disclosure-of-security-vulnerabilities.md,file deleted because it no longer exists in main
+translations/zh-CN/content/code-security/repository-security-advisories/about-github-security-advisories-for-repositories.md,file deleted because it no longer exists in main
+translations/zh-CN/content/code-security/repository-security-advisories/adding-a-collaborator-to-a-repository-security-advisory.md,file deleted because it no longer exists in main
+translations/zh-CN/content/code-security/repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability.md,file deleted because it no longer exists in main
+translations/zh-CN/content/code-security/repository-security-advisories/creating-a-repository-security-advisory.md,file deleted because it no longer exists in main
+translations/zh-CN/content/code-security/repository-security-advisories/editing-a-repository-security-advisory.md,file deleted because it no longer exists in main
+translations/zh-CN/content/code-security/repository-security-advisories/index.md,file deleted because it no longer exists in main
+translations/zh-CN/content/code-security/repository-security-advisories/permission-levels-for-repository-security-advisories.md,file deleted because it no longer exists in main
+translations/zh-CN/content/code-security/repository-security-advisories/publishing-a-repository-security-advisory.md,file deleted because it no longer exists in main
+translations/zh-CN/content/code-security/repository-security-advisories/removing-a-collaborator-from-a-repository-security-advisory.md,file deleted because it no longer exists in main
+translations/zh-CN/content/code-security/repository-security-advisories/withdrawing-a-repository-security-advisory.md,file deleted because it no longer exists in main
 translations/zh-CN/content/codespaces/codespaces-reference/disaster-recovery-for-codespaces.md,file deleted because it no longer exists in main
 translations/zh-CN/content/codespaces/codespaces-reference/security-in-codespaces.md,file deleted because it no longer exists in main
 translations/zh-CN/content/codespaces/codespaces-reference/understanding-billing-for-codespaces.md,file deleted because it no longer exists in main
@@ -202,6 +216,7 @@ translations/zh-CN/content/site-policy/privacy-policies/github-data-protection-a
 translations/zh-CN/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account.md,file deleted because it no longer exists in main
 translations/zh-CN/data/glossaries/internal.yml,file deleted because it no longer exists in main
 translations/zh-CN/data/graphql/ghes-3.1/graphql_previews.enterprise.yml,file deleted because it no longer exists in main
+translations/zh-CN/data/graphql/ghes-3.2/graphql_previews.enterprise.yml,file deleted because it no longer exists in main
 translations/zh-CN/data/reusables/actions/link-to-example-library.md,file deleted because it no longer exists in main
 translations/zh-CN/data/reusables/actions/perform-blob-storage-precheck.md,file deleted because it no longer exists in main
 translations/zh-CN/data/reusables/actions/self-hosted-runner-configure-runner-group.md,file deleted because it no longer exists in main
@@ -218,7 +233,9 @@ translations/zh-CN/data/reusables/codespaces/concurrent-codespace-limit.md,file
 translations/zh-CN/data/reusables/codespaces/prebuilds-beta-note.md,file deleted because it no longer exists in main
 translations/zh-CN/data/reusables/codespaces/prebuilds-not-available.md,file deleted because it no longer exists in main
 translations/zh-CN/data/reusables/codespaces/unsupported-repos.md,file deleted because it no longer exists in main
+translations/zh-CN/data/reusables/dependabot/beta-security-and-version-updates-onboarding.md,file deleted because it no longer exists in main
 translations/zh-CN/data/reusables/dependabot/create-dependabot-yml.md,file deleted because it no longer exists in main
+translations/zh-CN/data/reusables/dependency-review/beta.md,file deleted because it no longer exists in main
 translations/zh-CN/data/reusables/desktop/paste-email-git-config.md,file deleted because it no longer exists in main
 translations/zh-CN/data/reusables/dotcom_billing/codespaces-minutes.md,file deleted because it no longer exists in main
 translations/zh-CN/data/reusables/dotcom_billing/pricing_calculator/pricing_cal_codespaces.md,file deleted because it no longer exists in main
@@ -226,6 +243,7 @@ translations/zh-CN/data/reusables/education/upgrade-organization.md,file deleted
 translations/zh-CN/data/reusables/education/upgrade-page.md,file deleted because it no longer exists in main
 translations/zh-CN/data/reusables/enterprise-accounts/repository-visibility-policy.md,file deleted because it no longer exists in main
 translations/zh-CN/data/reusables/enterprise-licensing/you-can-sync-for-a-combined-view.md,file deleted because it no longer exists in main
+translations/zh-CN/data/reusables/enterprise/upgrade-ghes-for-actions.md,file deleted because it no longer exists in main
 translations/zh-CN/data/reusables/enterprise_management_console/username_normalization_sample.md,file deleted because it no longer exists in main
 translations/zh-CN/data/reusables/gated-features/advanced-security.md,file deleted because it no longer exists in main
 translations/zh-CN/data/reusables/gated-features/discussions.md,file deleted because it no longer exists in main
@@ -270,7 +288,6 @@ translations/zh-CN/content/account-and-profile/managing-subscriptions-and-notifi
 translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/about-your-organizations-profile.md,rendering error
 translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/managing-your-profile-readme.md,broken liquid tags
 translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/personalizing-your-profile.md,rendering error
-translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/setting-your-profile-to-private.md,broken liquid tags
 translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-settings-on-your-profile/showing-your-private-contributions-and-achievements-on-your-profile.md,rendering error
 translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-settings-on-your-profile/viewing-contributions-on-your-profile.md,broken liquid tags
 translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-settings-on-your-profile/why-are-my-contributions-not-showing-up-on-my-profile.md,broken liquid tags
@@ -284,7 +301,10 @@ translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-pers
 translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/setting-your-commit-email-address.md,rendering error
 translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/changing-your-github-username.md,rendering error
 translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-accessibility-settings.md,broken liquid tags
+translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-security-and-analysis-settings-for-your-personal-account.md,rendering error
 translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-the-default-branch-name-for-your-repositories.md,rendering error
+translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-your-theme-settings.md,broken liquid tags
+translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/permission-levels-for-a-personal-account-repository.md,broken liquid tags
 translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/requesting-organization-approval-for-oauth-apps.md,rendering error
 translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-personal-account/best-practices-for-leaving-your-company.md,broken liquid tags
 translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-personal-account/converting-a-user-into-an-organization.md,broken liquid tags
@@ -307,9 +327,7 @@ translations/zh-CN/content/actions/deployment/deploying-to-your-cloud-provider/d
 translations/zh-CN/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-google-kubernetes-engine.md,rendering error
 translations/zh-CN/content/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect.md,broken liquid tags
 translations/zh-CN/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-cloud-providers.md,broken liquid tags
-translations/zh-CN/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-hashicorp-vault.md,broken liquid tags
 translations/zh-CN/content/actions/examples/using-concurrency-expressions-and-a-test-matrix.md,broken liquid tags
-translations/zh-CN/content/actions/examples/using-the-github-cli-on-a-runner.md,broken liquid tags
 translations/zh-CN/content/actions/hosting-your-own-runners/about-self-hosted-runners.md,rendering error
 translations/zh-CN/content/actions/hosting-your-own-runners/adding-self-hosted-runners.md,rendering error
 translations/zh-CN/content/actions/hosting-your-own-runners/autoscaling-with-self-hosted-runners.md,rendering error
@@ -336,6 +354,7 @@ translations/zh-CN/content/actions/security-guides/automatic-token-authenticatio
 translations/zh-CN/content/actions/security-guides/encrypted-secrets.md,rendering error
 translations/zh-CN/content/actions/security-guides/security-hardening-for-github-actions.md,rendering error
 translations/zh-CN/content/actions/using-github-hosted-runners/about-github-hosted-runners.md,rendering error
+translations/zh-CN/content/actions/using-github-hosted-runners/controlling-access-to-larger-runners.md,rendering error
 translations/zh-CN/content/actions/using-github-hosted-runners/using-larger-runners.md,rendering error
 translations/zh-CN/content/actions/using-workflows/about-workflows.md,rendering error
 translations/zh-CN/content/actions/using-workflows/caching-dependencies-to-speed-up-workflows.md,broken liquid tags
@@ -389,8 +408,12 @@ translations/zh-CN/content/admin/configuration/configuring-your-enterprise/manag
 translations/zh-CN/content/admin/configuration/configuring-your-enterprise/restricting-network-traffic-to-your-enterprise.md,broken liquid tags
 translations/zh-CN/content/admin/configuration/configuring-your-enterprise/site-admin-dashboard.md,broken liquid tags
 translations/zh-CN/content/admin/configuration/configuring-your-enterprise/troubleshooting-tls-errors.md,broken liquid tags
+translations/zh-CN/content/admin/enterprise-management/caching-repositories/about-repository-caching.md,rendering error
+translations/zh-CN/content/admin/enterprise-management/caching-repositories/configuring-a-repository-cache.md,rendering error
+translations/zh-CN/content/admin/enterprise-management/caching-repositories/index.md,rendering error
 translations/zh-CN/content/admin/enterprise-management/configuring-clustering/cluster-network-configuration.md,broken liquid tags
 translations/zh-CN/content/admin/enterprise-management/configuring-clustering/configuring-high-availability-replication-for-a-cluster.md,broken liquid tags
+translations/zh-CN/content/admin/enterprise-management/configuring-high-availability/about-geo-replication.md,broken liquid tags
 translations/zh-CN/content/admin/enterprise-management/configuring-high-availability/creating-a-high-availability-replica.md,broken liquid tags
 translations/zh-CN/content/admin/enterprise-management/monitoring-your-appliance/accessing-the-monitor-dashboard.md,broken liquid tags
 translations/zh-CN/content/admin/enterprise-management/monitoring-your-appliance/configuring-collectd.md,broken liquid tags
@@ -523,8 +546,6 @@ translations/zh-CN/content/authentication/managing-commit-signature-verification
 translations/zh-CN/content/authentication/managing-commit-signature-verification/associating-an-email-with-your-gpg-key.md,broken liquid tags
 translations/zh-CN/content/authentication/managing-commit-signature-verification/displaying-verification-statuses-for-all-of-your-commits.md,rendering error
 translations/zh-CN/content/authentication/managing-commit-signature-verification/index.md,broken liquid tags
-translations/zh-CN/content/authentication/managing-commit-signature-verification/signing-commits.md,broken liquid tags
-translations/zh-CN/content/authentication/managing-commit-signature-verification/signing-tags.md,broken liquid tags
 translations/zh-CN/content/authentication/managing-commit-signature-verification/telling-git-about-your-signing-key.md,broken liquid tags
 translations/zh-CN/content/authentication/securing-your-account-with-two-factor-authentication-2fa/about-two-factor-authentication.md,broken liquid tags
 translations/zh-CN/content/authentication/securing-your-account-with-two-factor-authentication-2fa/accessing-github-using-two-factor-authentication.md,broken liquid tags
@@ -558,6 +579,7 @@ translations/zh-CN/content/billing/managing-your-license-for-github-enterprise/a
 translations/zh-CN/content/billing/managing-your-license-for-github-enterprise/downloading-your-license-for-github-enterprise.md,broken liquid tags
 translations/zh-CN/content/billing/managing-your-license-for-github-enterprise/uploading-a-new-license-to-github-enterprise-server.md,broken liquid tags
 translations/zh-CN/content/billing/managing-your-license-for-github-enterprise/viewing-license-usage-for-github-enterprise.md,broken liquid tags
+translations/zh-CN/content/code-security/adopting-github-advanced-security-at-scale/phase-6-rollout-and-scale-secret-scanning.md,rendering error
 translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts.md,rendering error
 translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-with-codeql.md,rendering error
 translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning.md,rendering error
@@ -577,21 +599,26 @@ translations/zh-CN/content/code-security/code-scanning/using-codeql-code-scannin
 translations/zh-CN/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/installing-codeql-cli-in-your-ci-system.md,broken liquid tags
 translations/zh-CN/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/running-codeql-runner-in-your-ci-system.md,broken liquid tags
 translations/zh-CN/content/code-security/dependabot/dependabot-alerts/about-dependabot-alerts.md,rendering error
-translations/zh-CN/content/code-security/dependabot/dependabot-alerts/browsing-security-advisories-in-the-github-advisory-database.md,rendering error
 translations/zh-CN/content/code-security/dependabot/dependabot-alerts/configuring-notifications-for-dependabot-alerts.md,rendering error
-translations/zh-CN/content/code-security/dependabot/dependabot-alerts/editing-security-advisories-in-the-github-advisory-database.md,broken liquid tags
 translations/zh-CN/content/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts.md,rendering error
 translations/zh-CN/content/code-security/dependabot/dependabot-security-updates/about-dependabot-security-updates.md,rendering error
 translations/zh-CN/content/code-security/dependabot/dependabot-security-updates/configuring-dependabot-security-updates.md,rendering error
 translations/zh-CN/content/code-security/dependabot/dependabot-version-updates/about-dependabot-version-updates.md,rendering error
 translations/zh-CN/content/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file.md,rendering error
 translations/zh-CN/content/code-security/dependabot/dependabot-version-updates/configuring-dependabot-version-updates.md,rendering error
+translations/zh-CN/content/code-security/dependabot/dependabot-version-updates/customizing-dependency-updates.md,rendering error
+translations/zh-CN/content/code-security/dependabot/dependabot-version-updates/listing-dependencies-configured-for-version-updates.md,rendering error
+translations/zh-CN/content/code-security/dependabot/index.md,broken liquid tags
 translations/zh-CN/content/code-security/dependabot/working-with-dependabot/automating-dependabot-with-github-actions.md,rendering error
+translations/zh-CN/content/code-security/dependabot/working-with-dependabot/keeping-your-actions-up-to-date-with-dependabot.md,rendering error
 translations/zh-CN/content/code-security/dependabot/working-with-dependabot/managing-encrypted-secrets-for-dependabot.md,rendering error
+translations/zh-CN/content/code-security/dependabot/working-with-dependabot/troubleshooting-dependabot-errors.md,rendering error
 translations/zh-CN/content/code-security/dependabot/working-with-dependabot/troubleshooting-the-detection-of-vulnerable-dependencies.md,rendering error
+translations/zh-CN/content/code-security/getting-started/adding-a-security-policy-to-your-repository.md,broken liquid tags
 translations/zh-CN/content/code-security/getting-started/github-security-features.md,rendering error
 translations/zh-CN/content/code-security/getting-started/securing-your-organization.md,rendering error
 translations/zh-CN/content/code-security/getting-started/securing-your-repository.md,rendering error
+translations/zh-CN/content/code-security/index.md,rendering error
 translations/zh-CN/content/code-security/secret-scanning/about-secret-scanning.md,rendering error
 translations/zh-CN/content/code-security/secret-scanning/configuring-secret-scanning-for-your-repositories.md,rendering error
 translations/zh-CN/content/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning.md,rendering error
@@ -608,6 +635,7 @@ translations/zh-CN/content/code-security/supply-chain-security/understanding-you
 translations/zh-CN/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph.md,rendering error
 translations/zh-CN/content/code-security/supply-chain-security/understanding-your-software-supply-chain/configuring-dependency-review.md,rendering error
 translations/zh-CN/content/code-security/supply-chain-security/understanding-your-software-supply-chain/configuring-the-dependency-graph.md,broken liquid tags
+translations/zh-CN/content/code-security/supply-chain-security/understanding-your-software-supply-chain/troubleshooting-the-dependency-graph.md,broken liquid tags
 translations/zh-CN/content/codespaces/codespaces-reference/allowing-your-codespace-to-access-a-private-image-registry.md,broken liquid tags
 translations/zh-CN/content/codespaces/codespaces-reference/disaster-recovery-for-github-codespaces.md,broken liquid tags
 translations/zh-CN/content/codespaces/codespaces-reference/security-in-github-codespaces.md,broken liquid tags
@@ -647,6 +675,7 @@ translations/zh-CN/content/codespaces/prebuilding-your-codespaces/allowing-a-pre
 translations/zh-CN/content/codespaces/prebuilding-your-codespaces/configuring-prebuilds.md,broken liquid tags
 translations/zh-CN/content/codespaces/prebuilding-your-codespaces/managing-prebuilds.md,broken liquid tags
 translations/zh-CN/content/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers.md,broken liquid tags
+translations/zh-CN/content/codespaces/setting-up-your-project-for-codespaces/setting-a-minimum-specification-for-codespace-machines.md,broken liquid tags
 translations/zh-CN/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-dotnet-project-for-codespaces.md,broken liquid tags
 translations/zh-CN/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-java-project-for-codespaces.md,broken liquid tags
 translations/zh-CN/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-nodejs-project-for-codespaces.md,broken liquid tags
@@ -757,14 +786,17 @@ translations/zh-CN/content/graphql/reference/mutations.md,broken liquid tags
 translations/zh-CN/content/graphql/reference/objects.md,broken liquid tags
 translations/zh-CN/content/graphql/reference/unions.md,broken liquid tags
 translations/zh-CN/content/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards.md,broken liquid tags
+translations/zh-CN/content/issues/organizing-your-work-with-project-boards/managing-project-boards/changing-project-board-visibility.md,rendering error
+translations/zh-CN/content/issues/organizing-your-work-with-project-boards/managing-project-boards/copying-a-project-board.md,rendering error
+translations/zh-CN/content/issues/organizing-your-work-with-project-boards/managing-project-boards/creating-a-project-board.md,rendering error
 translations/zh-CN/content/issues/planning-and-tracking-with-projects/automating-your-project/automating-projects-using-actions.md,broken liquid tags
 translations/zh-CN/content/issues/planning-and-tracking-with-projects/automating-your-project/using-the-api-to-manage-projects.md,broken liquid tags
+translations/zh-CN/content/issues/planning-and-tracking-with-projects/creating-projects/migrating-from-projects-classic.md,rendering error
 translations/zh-CN/content/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/customizing-a-view.md,broken liquid tags
 translations/zh-CN/content/issues/planning-and-tracking-with-projects/learning-about-projects/best-practices-for-projects.md,broken liquid tags
 translations/zh-CN/content/issues/planning-and-tracking-with-projects/managing-items-in-your-project/adding-items-to-your-project.md,broken liquid tags
 translations/zh-CN/content/issues/planning-and-tracking-with-projects/managing-items-in-your-project/archiving-items-from-your-project.md,broken liquid tags
 translations/zh-CN/content/issues/planning-and-tracking-with-projects/managing-your-project/managing-access-to-your-projects.md,broken liquid tags
-translations/zh-CN/content/issues/planning-and-tracking-with-projects/managing-your-project/managing-visibility-of-your-projects.md,broken liquid tags
 translations/zh-CN/content/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests.md,rendering error
 translations/zh-CN/content/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue.md,rendering error
 translations/zh-CN/content/organizations/collaborating-with-groups-in-organizations/about-your-organizations-news-feed.md,broken liquid tags
@@ -772,16 +804,21 @@ translations/zh-CN/content/organizations/granting-access-to-your-organization-wi
 translations/zh-CN/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization.md,rendering error
 translations/zh-CN/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-security-and-analysis-settings-for-your-organization.md,rendering error
 translations/zh-CN/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization.md,rendering error
+translations/zh-CN/content/organizations/managing-access-to-your-organizations-project-boards/adding-an-outside-collaborator-to-a-project-board-in-your-organization.md,rendering error
+translations/zh-CN/content/organizations/managing-access-to-your-organizations-project-boards/managing-access-to-a-project-board-for-organization-members.md,rendering error
+translations/zh-CN/content/organizations/managing-access-to-your-organizations-project-boards/managing-an-individuals-access-to-an-organization-project-board.md,rendering error
 translations/zh-CN/content/organizations/managing-access-to-your-organizations-project-boards/managing-team-access-to-an-organization-project-board.md,rendering error
+translations/zh-CN/content/organizations/managing-access-to-your-organizations-project-boards/removing-an-outside-collaborator-from-an-organization-project-board.md,rendering error
 translations/zh-CN/content/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities.md,broken liquid tags
 translations/zh-CN/content/organizations/managing-membership-in-your-organization/inviting-users-to-join-your-organization.md,rendering error
-translations/zh-CN/content/organizations/managing-organization-settings/allowing-project-visibility-changes-in-your-organization.md,broken liquid tags
 translations/zh-CN/content/organizations/managing-organization-settings/deleting-an-organization-account.md,rendering error
 translations/zh-CN/content/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization.md,rendering error
 translations/zh-CN/content/organizations/managing-organization-settings/disabling-project-boards-in-your-organization.md,rendering error
 translations/zh-CN/content/organizations/managing-organization-settings/integrating-jira-with-your-organization-project-board.md,rendering error
+translations/zh-CN/content/organizations/managing-organization-settings/managing-the-commit-signoff-policy-for-your-organization.md,rendering error
 translations/zh-CN/content/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization.md,rendering error
 translations/zh-CN/content/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization.md,broken liquid tags
+translations/zh-CN/content/organizations/managing-organization-settings/setting-permissions-for-adding-outside-collaborators.md,broken liquid tags
 translations/zh-CN/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-security-managers-in-your-organization.md,rendering error
 translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on.md,broken liquid tags
 translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/configuring-saml-single-sign-on-and-scim-using-okta.md,broken liquid tags
@@ -809,6 +846,7 @@ translations/zh-CN/content/pages/configuring-a-custom-domain-for-your-github-pag
 translations/zh-CN/content/pages/configuring-a-custom-domain-for-your-github-pages-site/managing-a-custom-domain-for-your-github-pages-site.md,rendering error
 translations/zh-CN/content/pages/getting-started-with-github-pages/about-github-pages.md,broken liquid tags
 translations/zh-CN/content/pages/getting-started-with-github-pages/creating-a-github-pages-site.md,rendering error
+translations/zh-CN/content/pages/getting-started-with-github-pages/unpublishing-a-github-pages-site.md,rendering error
 translations/zh-CN/content/pages/index.md,broken liquid tags
 translations/zh-CN/content/pages/setting-up-a-github-pages-site-with-jekyll/creating-a-github-pages-site-with-jekyll.md,rendering error
 translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-using-the-command-line.md,broken liquid tags
@@ -849,6 +887,7 @@ translations/zh-CN/content/repositories/creating-and-managing-repositories/trans
 translations/zh-CN/content/repositories/creating-and-managing-repositories/troubleshooting-cloning-errors.md,broken liquid tags
 translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners.md,rendering error
 translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-readmes.md,rendering error
+translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/classifying-your-repository-with-topics.md,broken liquid tags
 translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/licensing-a-repository.md,broken liquid tags
 translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository.md,rendering error
 translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-security-and-analysis-settings-for-your-repository.md,rendering error
@@ -890,6 +929,7 @@ translations/zh-CN/content/rest/guides/getting-started-with-the-rest-api.md,rend
 translations/zh-CN/content/rest/guides/traversing-with-pagination.md,rendering error
 translations/zh-CN/content/rest/guides/working-with-comments.md,broken liquid tags
 translations/zh-CN/content/rest/migrations/source-imports.md,broken liquid tags
+translations/zh-CN/content/rest/overview/api-previews.md,rendering error
 translations/zh-CN/content/rest/overview/other-authentication-methods.md,broken liquid tags
 translations/zh-CN/content/rest/overview/permissions-required-for-github-apps.md,rendering error
 translations/zh-CN/content/rest/overview/resources-in-the-rest-api.md,broken liquid tags
@@ -909,8 +949,10 @@ translations/zh-CN/content/sponsors/receiving-sponsorships-through-github-sponso
 translations/zh-CN/content/support/contacting-github-support/providing-data-to-github-support.md,broken liquid tags
 translations/zh-CN/content/support/learning-about-github-support/about-github-premium-support.md,rendering error
 translations/zh-CN/content/support/learning-about-github-support/about-github-support.md,rendering error
+translations/zh-CN/data/glossaries/external.yml,broken liquid tags
 translations/zh-CN/data/learning-tracks/actions.yml,broken liquid tags
 translations/zh-CN/data/learning-tracks/admin.yml,broken liquid tags
+translations/zh-CN/data/learning-tracks/code-security.yml,broken liquid tags
 translations/zh-CN/data/release-notes/enterprise-server/2-20/15.yml,rendering error
 translations/zh-CN/data/release-notes/enterprise-server/2-21/17.yml,rendering error
 translations/zh-CN/data/release-notes/enterprise-server/2-21/6.yml,rendering error
@@ -951,8 +993,8 @@ translations/zh-CN/data/release-notes/enterprise-server/3-5/0-rc1.yml,rendering
 translations/zh-CN/data/release-notes/enterprise-server/3-5/4.yml,rendering error
 translations/zh-CN/data/release-notes/enterprise-server/3-6/0-rc1.yml,rendering error
 translations/zh-CN/data/reusables/actions/about-actions-for-enterprises.md,rendering error
-translations/zh-CN/data/reusables/actions/actions-audit-events-workflow.md,rendering error
 translations/zh-CN/data/reusables/actions/actions-billing.md,broken liquid tags
+translations/zh-CN/data/reusables/actions/add-hosted-runner.md,broken liquid tags
 translations/zh-CN/data/reusables/actions/cache-default-size.md,broken liquid tags
 translations/zh-CN/data/reusables/actions/create-runner-group.md,rendering error
 translations/zh-CN/data/reusables/actions/disabling-github-actions.md,broken liquid tags
@@ -965,12 +1007,15 @@ translations/zh-CN/data/reusables/actions/github-connect-resolution.md,broken li
 translations/zh-CN/data/reusables/actions/ip-allow-list-self-hosted-runners.md,broken liquid tags
 translations/zh-CN/data/reusables/actions/jobs/section-defining-outputs-for-jobs.md,broken liquid tags
 translations/zh-CN/data/reusables/actions/jobs/section-running-jobs-in-a-container.md,broken liquid tags
+translations/zh-CN/data/reusables/actions/message-parameters.md,broken liquid tags
+translations/zh-CN/data/reusables/actions/more-resources-for-ghes.md,rendering error
 translations/zh-CN/data/reusables/actions/ref_name-description.md,broken liquid tags
 translations/zh-CN/data/reusables/actions/reusable-workflow-artifacts.md,rendering error
 translations/zh-CN/data/reusables/actions/reusable-workflow-calling-syntax.md,rendering error
 translations/zh-CN/data/reusables/actions/reusable-workflows.md,rendering error
 translations/zh-CN/data/reusables/actions/runner-groups-add-to-enterprise-first-steps.md,rendering error
 translations/zh-CN/data/reusables/actions/self-hosted-runner-add-to-enterprise.md,rendering error
+translations/zh-CN/data/reusables/actions/self-hosted-runner-auto-removal.md,rendering error
 translations/zh-CN/data/reusables/actions/self-hosted-runner-management-permissions-required.md,broken liquid tags
 translations/zh-CN/data/reusables/actions/self-hosted-runner-networking-to-dotcom.md,broken liquid tags
 translations/zh-CN/data/reusables/actions/self-hosted-runner-ports-protocols.md,broken liquid tags
@@ -987,6 +1032,7 @@ translations/zh-CN/data/reusables/advanced-security/about-committer-numbers-ghec
 translations/zh-CN/data/reusables/advanced-security/about-ghas-organization-policy.md,broken liquid tags
 translations/zh-CN/data/reusables/advanced-security/secret-scanning-add-custom-pattern-details.md,rendering error
 translations/zh-CN/data/reusables/advanced-security/secret-scanning-create-custom-pattern.md,rendering error
+translations/zh-CN/data/reusables/advanced-security/secret-scanning-new-custom-pattern.md,broken liquid tags
 translations/zh-CN/data/reusables/advanced-security/secret-scanning-push-protection-org.md,broken liquid tags
 translations/zh-CN/data/reusables/apps/user-to-server-rate-limits.md,broken liquid tags
 translations/zh-CN/data/reusables/audit_log/audit-log-action-categories.md,rendering error
@@ -995,14 +1041,14 @@ translations/zh-CN/data/reusables/audit_log/audit_log_sidebar_for_org_admins.md,
 translations/zh-CN/data/reusables/audit_log/audit_log_sidebar_for_site_admins.md,rendering error
 translations/zh-CN/data/reusables/branches/new-repo-default-branch.md,broken liquid tags
 translations/zh-CN/data/reusables/classroom/about-autograding.md,broken liquid tags
-translations/zh-CN/data/reusables/code-scanning/analyze-go.md,broken liquid tags
+translations/zh-CN/data/reusables/code-scanning/alerts-found-in-generated-code.md,broken liquid tags
 translations/zh-CN/data/reusables/code-scanning/autobuild-add-build-steps.md,broken liquid tags
+translations/zh-CN/data/reusables/code-scanning/autobuild-compiled-languages.md,broken liquid tags
 translations/zh-CN/data/reusables/code-scanning/codeql-context-for-actions-and-third-party-tools.md,broken liquid tags
 translations/zh-CN/data/reusables/code-scanning/codeql-languages-bullets.md,rendering error
 translations/zh-CN/data/reusables/code-scanning/codeql-languages-keywords.md,rendering error
 translations/zh-CN/data/reusables/code-scanning/enterprise-enable-code-scanning-actions.md,broken liquid tags
 translations/zh-CN/data/reusables/code-scanning/enterprise-enable-code-scanning.md,broken liquid tags
-translations/zh-CN/data/reusables/code-scanning/example-configuration-files.md,broken liquid tags
 translations/zh-CN/data/reusables/code-scanning/licensing-note.md,broken liquid tags
 translations/zh-CN/data/reusables/code-scanning/run-additional-queries.md,broken liquid tags
 translations/zh-CN/data/reusables/code-scanning/what-is-codeql-cli.md,broken liquid tags
@@ -1049,6 +1095,7 @@ translations/zh-CN/data/reusables/enterprise-accounts/repo-creation-policy.md,br
 translations/zh-CN/data/reusables/enterprise-accounts/security-tab.md,broken liquid tags
 translations/zh-CN/data/reusables/enterprise/apply-configuration.md,broken liquid tags
 translations/zh-CN/data/reusables/enterprise/rate_limit.md,broken liquid tags
+translations/zh-CN/data/reusables/enterprise/repository-caching-release-phase.md,rendering error
 translations/zh-CN/data/reusables/enterprise/test-in-staging.md,broken liquid tags
 translations/zh-CN/data/reusables/enterprise_enterprise_support/installing-releases.md,broken liquid tags
 translations/zh-CN/data/reusables/enterprise_installation/download-package.md,broken liquid tags
@@ -1065,7 +1112,6 @@ translations/zh-CN/data/reusables/enterprise_user_management/built-in-authentica
 translations/zh-CN/data/reusables/enterprise_user_management/consider-usernames-for-external-authentication.md,broken liquid tags
 translations/zh-CN/data/reusables/enterprise_user_management/disclaimer-for-git-read-access.md,broken liquid tags
 translations/zh-CN/data/reusables/files/choose-commit-email.md,broken liquid tags
-translations/zh-CN/data/reusables/gated-features/code-scanning.md,broken liquid tags
 translations/zh-CN/data/reusables/gated-features/codespaces-classroom-articles.md,broken liquid tags
 translations/zh-CN/data/reusables/gated-features/dependency-vulnerable-calls.md,rendering error
 translations/zh-CN/data/reusables/gated-features/secret-scanning-partner.md,rendering error
@@ -1078,7 +1124,6 @@ translations/zh-CN/data/reusables/getting-started/enforcing-repo-management-poli
 translations/zh-CN/data/reusables/getting-started/enterprise-advanced-security.md,broken liquid tags
 translations/zh-CN/data/reusables/getting-started/managing-enterprise-members.md,broken liquid tags
 translations/zh-CN/data/reusables/git/git-push.md,broken liquid tags
-translations/zh-CN/data/reusables/github-ae/saml-idp-table.md,broken liquid tags
 translations/zh-CN/data/reusables/identity-and-permissions/ip-allow-lists-enable.md,broken liquid tags
 translations/zh-CN/data/reusables/identity-and-permissions/vigilant-mode-beta-note.md,broken liquid tags
 translations/zh-CN/data/reusables/large_files/storage_assets_location.md,broken liquid tags
@@ -1091,15 +1136,23 @@ translations/zh-CN/data/reusables/organizations/billing_plans.md,rendering error
 translations/zh-CN/data/reusables/organizations/github-apps-settings-sidebar.md,rendering error
 translations/zh-CN/data/reusables/organizations/member-privileges.md,rendering error
 translations/zh-CN/data/reusables/organizations/navigate-to-org.md,broken liquid tags
+translations/zh-CN/data/reusables/organizations/new_team.md,broken liquid tags
+translations/zh-CN/data/reusables/organizations/org_settings.md,broken liquid tags
+translations/zh-CN/data/reusables/organizations/organization-wide-project.md,broken liquid tags
+translations/zh-CN/data/reusables/organizations/owners-team.md,broken liquid tags
+translations/zh-CN/data/reusables/organizations/people.md,broken liquid tags
 translations/zh-CN/data/reusables/organizations/repository-defaults.md,rendering error
 translations/zh-CN/data/reusables/organizations/security-and-analysis.md,rendering error
 translations/zh-CN/data/reusables/organizations/security.md,rendering error
+translations/zh-CN/data/reusables/organizations/specific_team.md,broken liquid tags
+translations/zh-CN/data/reusables/organizations/teams.md,broken liquid tags
 translations/zh-CN/data/reusables/organizations/teams_sidebar.md,rendering error
 translations/zh-CN/data/reusables/organizations/verified-domains.md,rendering error
 translations/zh-CN/data/reusables/package_registry/authenticate-packages.md,broken liquid tags
 translations/zh-CN/data/reusables/package_registry/authenticate-to-container-registry-steps.md,rendering error
 translations/zh-CN/data/reusables/package_registry/next-steps-for-packages-enterprise-setup.md,broken liquid tags
 translations/zh-CN/data/reusables/package_registry/package-registry-with-github-tokens.md,broken liquid tags
+translations/zh-CN/data/reusables/package_registry/package-settings-from-org-level.md,broken liquid tags
 translations/zh-CN/data/reusables/package_registry/packages-billing.md,broken liquid tags
 translations/zh-CN/data/reusables/package_registry/required-scopes.md,broken liquid tags
 translations/zh-CN/data/reusables/pages/build-failure-email-server.md,broken liquid tags
@@ -1110,7 +1163,6 @@ translations/zh-CN/data/reusables/pages/sidebar-pages.md,rendering error
 translations/zh-CN/data/reusables/projects/enable-basic-workflow.md,broken liquid tags
 translations/zh-CN/data/reusables/pull_requests/configure_pull_request_merges_intro.md,broken liquid tags
 translations/zh-CN/data/reusables/pull_requests/default_merge_option.md,broken liquid tags
-translations/zh-CN/data/reusables/pull_requests/merge-queue-beta.md,broken liquid tags
 translations/zh-CN/data/reusables/pull_requests/pull_request_merges_and_contributions.md,broken liquid tags
 translations/zh-CN/data/reusables/pull_requests/rebase_and_merge_summary.md,broken liquid tags
 translations/zh-CN/data/reusables/pull_requests/resolving-conversations.md,broken liquid tags
@@ -1123,6 +1175,7 @@ translations/zh-CN/data/reusables/repositories/navigate-to-code-security-and-ana
 translations/zh-CN/data/reusables/repositories/navigate-to-commit-page.md,broken liquid tags
 translations/zh-CN/data/reusables/repositories/navigate-to-repo.md,broken liquid tags
 translations/zh-CN/data/reusables/repositories/repository-branches.md,rendering error
+translations/zh-CN/data/reusables/repositories/security-advisories-republishing.md,broken liquid tags
 translations/zh-CN/data/reusables/repositories/sidebar-notifications.md,rendering error
 translations/zh-CN/data/reusables/repositories/suggest-changes.md,broken liquid tags
 translations/zh-CN/data/reusables/repositories/you-can-fork.md,broken liquid tags
@@ -1133,7 +1186,6 @@ translations/zh-CN/data/reusables/saml/about-saml-access-enterprise-account.md,b
 translations/zh-CN/data/reusables/saml/authorized-creds-info.md,broken liquid tags
 translations/zh-CN/data/reusables/saml/create-a-machine-user.md,broken liquid tags
 translations/zh-CN/data/reusables/saml/must-authorize-linked-identity.md,broken liquid tags
-translations/zh-CN/data/reusables/saml/okta-ae-sso-beta.md,broken liquid tags
 translations/zh-CN/data/reusables/saml/you-must-periodically-authenticate.md,rendering error
 translations/zh-CN/data/reusables/scim/enterprise-account-scim.md,broken liquid tags
 translations/zh-CN/data/reusables/scim/supported-idps.md,broken liquid tags
@@ -1141,9 +1193,10 @@ translations/zh-CN/data/reusables/search/syntax_tips.md,broken liquid tags
 translations/zh-CN/data/reusables/secret-scanning/enterprise-enable-secret-scanning.md,broken liquid tags
 translations/zh-CN/data/reusables/secret-scanning/partner-secret-list-private-repo.md,rendering error
 translations/zh-CN/data/reusables/secret-scanning/partner-secret-list-public-repo.md,broken liquid tags
-translations/zh-CN/data/reusables/secret-scanning/push-protection-web-ui-choice.md,broken liquid tags
 translations/zh-CN/data/reusables/secret-scanning/secret-list-private-push-protection.md,rendering error
+translations/zh-CN/data/reusables/security-advisory/security-advisory-overview.md,broken liquid tags
 translations/zh-CN/data/reusables/security-overview/permissions.md,rendering error
+translations/zh-CN/data/reusables/security/displayed-information.md,broken liquid tags
 translations/zh-CN/data/reusables/shortdesc/rate_limits_github_apps.md,broken liquid tags
 translations/zh-CN/data/reusables/sponsors/select-sponsorship-billing.md,broken liquid tags
 translations/zh-CN/data/reusables/ssh/about-ssh.md,broken liquid tags
@@ -1151,6 +1204,14 @@ translations/zh-CN/data/reusables/ssh/key-type-support.md,rendering error
 translations/zh-CN/data/reusables/ssh/rsa-sha-1-connection-failure-criteria.md,broken liquid tags
 translations/zh-CN/data/reusables/support/help_resources.md,rendering error
 translations/zh-CN/data/reusables/support/submit-a-ticket.md,broken liquid tags
+translations/zh-CN/data/reusables/supported-languages/C.md,broken liquid tags
+translations/zh-CN/data/reusables/supported-languages/Cpp.md,broken liquid tags
+translations/zh-CN/data/reusables/supported-languages/Cs.md,broken liquid tags
+translations/zh-CN/data/reusables/supported-languages/go.md,broken liquid tags
+translations/zh-CN/data/reusables/supported-languages/php.md,broken liquid tags
+translations/zh-CN/data/reusables/supported-languages/products-table-header.md,broken liquid tags
+translations/zh-CN/data/reusables/supported-languages/python.md,broken liquid tags
+translations/zh-CN/data/reusables/supported-languages/scala.md,broken liquid tags
 translations/zh-CN/data/reusables/user-settings/access_applications.md,rendering error
 translations/zh-CN/data/reusables/user-settings/account_settings.md,rendering error
 translations/zh-CN/data/reusables/user-settings/appearance-settings.md,rendering error
@@ -1168,6 +1229,7 @@ translations/zh-CN/data/reusables/user-settings/ssh.md,rendering error
 translations/zh-CN/data/reusables/webhooks/pull_request_properties.md,broken liquid tags
 translations/zh-CN/data/reusables/webhooks/pull_request_webhook_properties.md,broken liquid tags
 translations/zh-CN/data/reusables/webhooks/repository_vulnerability_alert_short_desc.md,broken liquid tags
+translations/zh-CN/data/reusables/webhooks/webhooks-rest-api-links.md,broken liquid tags
 translations/zh-CN/data/reusables/webhooks/workflow_run_properties.md,broken liquid tags
 translations/zh-CN/data/variables/product.yml,broken liquid tags
 translations/zh-CN/data/variables/projects.yml,broken liquid tags
diff --git a/translations/log/msft-es-resets.csv b/translations/log/msft-es-resets.csv
index 05162ef5ad..f4ba8c7bc1 100644
--- a/translations/log/msft-es-resets.csv
+++ b/translations/log/msft-es-resets.csv
@@ -76,7 +76,20 @@ translations/es-ES/content/authentication/troubleshooting-commit-signature-verif
 translations/es-ES/content/billing/managing-billing-for-github-codespaces/about-billing-for-codespaces.md,file deleted because it no longer exists in main
 translations/es-ES/content/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-codespaces.md,file deleted because it no longer exists in main
 translations/es-ES/content/billing/managing-billing-for-github-codespaces/viewing-your-codespaces-usage.md,file deleted because it no longer exists in main
+translations/es-ES/content/code-security/dependabot/dependabot-alerts/browsing-security-advisories-in-the-github-advisory-database.md,file deleted because it no longer exists in main
 translations/es-ES/content/code-security/dependabot/dependabot-alerts/browsing-security-vulnerabilities-in-the-github-advisory-database.md,file deleted because it no longer exists in main
+translations/es-ES/content/code-security/dependabot/dependabot-alerts/editing-security-advisories-in-the-github-advisory-database.md,file deleted because it no longer exists in main
+translations/es-ES/content/code-security/repository-security-advisories/about-coordinated-disclosure-of-security-vulnerabilities.md,file deleted because it no longer exists in main
+translations/es-ES/content/code-security/repository-security-advisories/about-github-security-advisories-for-repositories.md,file deleted because it no longer exists in main
+translations/es-ES/content/code-security/repository-security-advisories/adding-a-collaborator-to-a-repository-security-advisory.md,file deleted because it no longer exists in main
+translations/es-ES/content/code-security/repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability.md,file deleted because it no longer exists in main
+translations/es-ES/content/code-security/repository-security-advisories/creating-a-repository-security-advisory.md,file deleted because it no longer exists in main
+translations/es-ES/content/code-security/repository-security-advisories/editing-a-repository-security-advisory.md,file deleted because it no longer exists in main
+translations/es-ES/content/code-security/repository-security-advisories/index.md,file deleted because it no longer exists in main
+translations/es-ES/content/code-security/repository-security-advisories/permission-levels-for-repository-security-advisories.md,file deleted because it no longer exists in main
+translations/es-ES/content/code-security/repository-security-advisories/publishing-a-repository-security-advisory.md,file deleted because it no longer exists in main
+translations/es-ES/content/code-security/repository-security-advisories/removing-a-collaborator-from-a-repository-security-advisory.md,file deleted because it no longer exists in main
+translations/es-ES/content/code-security/repository-security-advisories/withdrawing-a-repository-security-advisory.md,file deleted because it no longer exists in main
 translations/es-ES/content/codespaces/codespaces-reference/disaster-recovery-for-codespaces.md,file deleted because it no longer exists in main
 translations/es-ES/content/codespaces/codespaces-reference/security-in-codespaces.md,file deleted because it no longer exists in main
 translations/es-ES/content/codespaces/codespaces-reference/understanding-billing-for-codespaces.md,file deleted because it no longer exists in main
@@ -225,9 +238,7 @@ translations/es-ES/data/reusables/codespaces/concurrent-codespace-limit.md,file
 translations/es-ES/data/reusables/codespaces/prebuilds-beta-note.md,file deleted because it no longer exists in main
 translations/es-ES/data/reusables/codespaces/prebuilds-not-available.md,file deleted because it no longer exists in main
 translations/es-ES/data/reusables/codespaces/unsupported-repos.md,file deleted because it no longer exists in main
-translations/es-ES/data/reusables/dependabot/beta-security-and-version-updates-onboarding.md,file deleted because it no longer exists in main
 translations/es-ES/data/reusables/dependabot/create-dependabot-yml.md,file deleted because it no longer exists in main
-translations/es-ES/data/reusables/dependency-review/beta.md,file deleted because it no longer exists in main
 translations/es-ES/data/reusables/desktop/paste-email-git-config.md,file deleted because it no longer exists in main
 translations/es-ES/data/reusables/dotcom_billing/codespaces-minutes.md,file deleted because it no longer exists in main
 translations/es-ES/data/reusables/dotcom_billing/pricing_calculator/pricing_cal_codespaces.md,file deleted because it no longer exists in main
@@ -235,7 +246,6 @@ translations/es-ES/data/reusables/education/upgrade-organization.md,file deleted
 translations/es-ES/data/reusables/education/upgrade-page.md,file deleted because it no longer exists in main
 translations/es-ES/data/reusables/enterprise-accounts/repository-visibility-policy.md,file deleted because it no longer exists in main
 translations/es-ES/data/reusables/enterprise-licensing/you-can-sync-for-a-combined-view.md,file deleted because it no longer exists in main
-translations/es-ES/data/reusables/enterprise/upgrade-ghes-for-actions.md,file deleted because it no longer exists in main
 translations/es-ES/data/reusables/enterprise_management_console/username_normalization.md,file deleted because it no longer exists in main
 translations/es-ES/data/reusables/enterprise_management_console/username_normalization_sample.md,file deleted because it no longer exists in main
 translations/es-ES/data/reusables/gated-features/advanced-security.md,file deleted because it no longer exists in main
@@ -247,6 +257,47 @@ translations/es-ES/data/reusables/getting-started/learning-lab.md,file deleted b
 translations/es-ES/data/reusables/open-source/open-source-learning-lab.md,file deleted because it no longer exists in main
 translations/es-ES/data/reusables/pages/pages-builds-with-github-actions-public-beta.md,file deleted because it no longer exists in main
 translations/es-ES/data/reusables/repositories/squash-and-rebase-linear-commit-hisitory.md,file deleted because it no longer exists in main
+translations/es-ES/data/reusables/rest-reference/apps/oauth-applications.md,file deleted because it no longer exists in main
+translations/es-ES/data/reusables/rest-reference/billing/billing.md,file deleted because it no longer exists in main
+translations/es-ES/data/reusables/rest-reference/branches/branch-protection.md,file deleted because it no longer exists in main
+translations/es-ES/data/reusables/rest-reference/checks/runs.md,file deleted because it no longer exists in main
+translations/es-ES/data/reusables/rest-reference/deployments/statuses.md,file deleted because it no longer exists in main
+translations/es-ES/data/reusables/rest-reference/enterprise-admin/admin-stats.md,file deleted because it no longer exists in main
+translations/es-ES/data/reusables/rest-reference/enterprise-admin/announcements.md,file deleted because it no longer exists in main
+translations/es-ES/data/reusables/rest-reference/enterprise-admin/audit-log.md,file deleted because it no longer exists in main
+translations/es-ES/data/reusables/rest-reference/enterprise-admin/billing.md,file deleted because it no longer exists in main
+translations/es-ES/data/reusables/rest-reference/enterprise-admin/management-console.md,file deleted because it no longer exists in main
+translations/es-ES/data/reusables/rest-reference/gists/comments.md,file deleted because it no longer exists in main
+translations/es-ES/data/reusables/rest-reference/git/refs.md,file deleted because it no longer exists in main
+translations/es-ES/data/reusables/rest-reference/gitignore/gitignore.md,file deleted because it no longer exists in main
+translations/es-ES/data/reusables/rest-reference/interactions/interactions.md,file deleted because it no longer exists in main
+translations/es-ES/data/reusables/rest-reference/issues/assignees.md,file deleted because it no longer exists in main
+translations/es-ES/data/reusables/rest-reference/issues/issues.md,file deleted because it no longer exists in main
+translations/es-ES/data/reusables/rest-reference/issues/labels.md,file deleted because it no longer exists in main
+translations/es-ES/data/reusables/rest-reference/issues/milestones.md,file deleted because it no longer exists in main
+translations/es-ES/data/reusables/rest-reference/metrics/community.md,file deleted because it no longer exists in main
+translations/es-ES/data/reusables/rest-reference/orgs/custom_roles.md,file deleted because it no longer exists in main
+translations/es-ES/data/reusables/rest-reference/orgs/members.md,file deleted because it no longer exists in main
+translations/es-ES/data/reusables/rest-reference/orgs/outside-collaborators.md,file deleted because it no longer exists in main
+translations/es-ES/data/reusables/rest-reference/projects/cards.md,file deleted because it no longer exists in main
+translations/es-ES/data/reusables/rest-reference/projects/collaborators.md,file deleted because it no longer exists in main
+translations/es-ES/data/reusables/rest-reference/projects/columns.md,file deleted because it no longer exists in main
+translations/es-ES/data/reusables/rest-reference/pulls/review-requests.md,file deleted because it no longer exists in main
+translations/es-ES/data/reusables/rest-reference/rate-limit/rate-limit.md,file deleted because it no longer exists in main
+translations/es-ES/data/reusables/rest-reference/reations/reactions.md,file deleted because it no longer exists in main
+translations/es-ES/data/reusables/rest-reference/releases/assets.md,file deleted because it no longer exists in main
+translations/es-ES/data/reusables/rest-reference/repos/contents.md,file deleted because it no longer exists in main
+translations/es-ES/data/reusables/rest-reference/repos/forks.md,file deleted because it no longer exists in main
+translations/es-ES/data/reusables/rest-reference/repos/lfs.md,file deleted because it no longer exists in main
+translations/es-ES/data/reusables/rest-reference/teams/team-sync.md,file deleted because it no longer exists in main
+translations/es-ES/data/reusables/rest-reference/teams/teams.md,file deleted because it no longer exists in main
+translations/es-ES/data/reusables/rest-reference/users/blocking.md,file deleted because it no longer exists in main
+translations/es-ES/data/reusables/rest-reference/users/emails.md,file deleted because it no longer exists in main
+translations/es-ES/data/reusables/rest-reference/users/followers.md,file deleted because it no longer exists in main
+translations/es-ES/data/reusables/rest-reference/users/keys.md,file deleted because it no longer exists in main
+translations/es-ES/data/reusables/rest-reference/webhooks/repo-config.md,file deleted because it no longer exists in main
+translations/es-ES/data/reusables/rest-reference/webhooks/repos.md,file deleted because it no longer exists in main
+translations/es-ES/data/reusables/security-center/beta.md,file deleted because it no longer exists in main
 translations/es-ES/data/reusables/server-statistics/release-phase.md,file deleted because it no longer exists in main
 translations/es-ES/content/account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/managing-your-subscriptions.md,rendering error
 translations/es-ES/content/account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/viewing-your-subscriptions.md,broken liquid tags
@@ -271,7 +322,8 @@ translations/es-ES/content/account-and-profile/setting-up-and-managing-your-pers
 translations/es-ES/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-accessibility-settings.md,broken liquid tags
 translations/es-ES/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-security-and-analysis-settings-for-your-personal-account.md,rendering error
 translations/es-ES/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-the-default-branch-name-for-your-repositories.md,rendering error
-translations/es-ES/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-your-theme-settings.md,broken liquid tags
+translations/es-ES/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-your-theme-settings.md,rendering error
+translations/es-ES/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/permission-levels-for-a-personal-account-repository.md,broken liquid tags
 translations/es-ES/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/requesting-organization-approval-for-oauth-apps.md,rendering error
 translations/es-ES/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-personal-account/best-practices-for-leaving-your-company.md,rendering error
 translations/es-ES/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-personal-account/converting-a-user-into-an-organization.md,rendering error
@@ -297,7 +349,6 @@ translations/es-ES/content/actions/deployment/deploying-to-your-cloud-provider/d
 translations/es-ES/content/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect.md,broken liquid tags
 translations/es-ES/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-cloud-providers.md,broken liquid tags
 translations/es-ES/content/actions/examples/using-concurrency-expressions-and-a-test-matrix.md,broken liquid tags
-translations/es-ES/content/actions/examples/using-the-github-cli-on-a-runner.md,broken liquid tags
 translations/es-ES/content/actions/hosting-your-own-runners/about-self-hosted-runners.md,rendering error
 translations/es-ES/content/actions/hosting-your-own-runners/adding-self-hosted-runners.md,rendering error
 translations/es-ES/content/actions/hosting-your-own-runners/autoscaling-with-self-hosted-runners.md,rendering error
@@ -380,7 +431,7 @@ translations/es-ES/content/admin/enterprise-management/caching-repositories/conf
 translations/es-ES/content/admin/enterprise-management/caching-repositories/index.md,rendering error
 translations/es-ES/content/admin/enterprise-management/configuring-clustering/cluster-network-configuration.md,broken liquid tags
 translations/es-ES/content/admin/enterprise-management/configuring-clustering/configuring-high-availability-replication-for-a-cluster.md,broken liquid tags
-translations/es-ES/content/admin/enterprise-management/configuring-high-availability/about-geo-replication.md,broken liquid tags
+translations/es-ES/content/admin/enterprise-management/configuring-high-availability/about-geo-replication.md,rendering error
 translations/es-ES/content/admin/enterprise-management/configuring-high-availability/creating-a-high-availability-replica.md,broken liquid tags
 translations/es-ES/content/admin/enterprise-management/monitoring-your-appliance/accessing-the-monitor-dashboard.md,broken liquid tags
 translations/es-ES/content/admin/enterprise-management/monitoring-your-appliance/configuring-collectd.md,broken liquid tags
@@ -564,9 +615,7 @@ translations/es-ES/content/code-security/code-scanning/using-codeql-code-scannin
 translations/es-ES/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/installing-codeql-cli-in-your-ci-system.md,broken liquid tags
 translations/es-ES/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/running-codeql-runner-in-your-ci-system.md,broken liquid tags
 translations/es-ES/content/code-security/dependabot/dependabot-alerts/about-dependabot-alerts.md,rendering error
-translations/es-ES/content/code-security/dependabot/dependabot-alerts/browsing-security-advisories-in-the-github-advisory-database.md,rendering error
 translations/es-ES/content/code-security/dependabot/dependabot-alerts/configuring-notifications-for-dependabot-alerts.md,rendering error
-translations/es-ES/content/code-security/dependabot/dependabot-alerts/editing-security-advisories-in-the-github-advisory-database.md,broken liquid tags
 translations/es-ES/content/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts.md,rendering error
 translations/es-ES/content/code-security/dependabot/dependabot-security-updates/about-dependabot-security-updates.md,rendering error
 translations/es-ES/content/code-security/dependabot/dependabot-security-updates/configuring-dependabot-security-updates.md,rendering error
@@ -575,16 +624,17 @@ translations/es-ES/content/code-security/dependabot/dependabot-version-updates/c
 translations/es-ES/content/code-security/dependabot/dependabot-version-updates/configuring-dependabot-version-updates.md,rendering error
 translations/es-ES/content/code-security/dependabot/dependabot-version-updates/customizing-dependency-updates.md,rendering error
 translations/es-ES/content/code-security/dependabot/dependabot-version-updates/listing-dependencies-configured-for-version-updates.md,rendering error
-translations/es-ES/content/code-security/dependabot/index.md,broken liquid tags
+translations/es-ES/content/code-security/dependabot/index.md,rendering error
 translations/es-ES/content/code-security/dependabot/working-with-dependabot/automating-dependabot-with-github-actions.md,rendering error
 translations/es-ES/content/code-security/dependabot/working-with-dependabot/keeping-your-actions-up-to-date-with-dependabot.md,rendering error
 translations/es-ES/content/code-security/dependabot/working-with-dependabot/managing-encrypted-secrets-for-dependabot.md,rendering error
 translations/es-ES/content/code-security/dependabot/working-with-dependabot/troubleshooting-dependabot-errors.md,rendering error
 translations/es-ES/content/code-security/dependabot/working-with-dependabot/troubleshooting-the-detection-of-vulnerable-dependencies.md,rendering error
+translations/es-ES/content/code-security/getting-started/adding-a-security-policy-to-your-repository.md,broken liquid tags
 translations/es-ES/content/code-security/getting-started/github-security-features.md,rendering error
 translations/es-ES/content/code-security/getting-started/securing-your-organization.md,rendering error
 translations/es-ES/content/code-security/getting-started/securing-your-repository.md,rendering error
-translations/es-ES/content/code-security/repository-security-advisories/about-coordinated-disclosure-of-security-vulnerabilities.md,rendering error
+translations/es-ES/content/code-security/index.md,rendering error
 translations/es-ES/content/code-security/secret-scanning/about-secret-scanning.md,rendering error
 translations/es-ES/content/code-security/secret-scanning/configuring-secret-scanning-for-your-repositories.md,rendering error
 translations/es-ES/content/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning.md,rendering error
@@ -601,7 +651,7 @@ translations/es-ES/content/code-security/supply-chain-security/understanding-you
 translations/es-ES/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph.md,rendering error
 translations/es-ES/content/code-security/supply-chain-security/understanding-your-software-supply-chain/configuring-dependency-review.md,rendering error
 translations/es-ES/content/code-security/supply-chain-security/understanding-your-software-supply-chain/configuring-the-dependency-graph.md,broken liquid tags
-translations/es-ES/content/code-security/supply-chain-security/understanding-your-software-supply-chain/troubleshooting-the-dependency-graph.md,broken liquid tags
+translations/es-ES/content/code-security/supply-chain-security/understanding-your-software-supply-chain/troubleshooting-the-dependency-graph.md,rendering error
 translations/es-ES/content/codespaces/codespaces-reference/allowing-your-codespace-to-access-a-private-image-registry.md,broken liquid tags
 translations/es-ES/content/codespaces/codespaces-reference/disaster-recovery-for-github-codespaces.md,broken liquid tags
 translations/es-ES/content/codespaces/codespaces-reference/security-in-github-codespaces.md,broken liquid tags
@@ -640,6 +690,7 @@ translations/es-ES/content/codespaces/prebuilding-your-codespaces/allowing-a-pre
 translations/es-ES/content/codespaces/prebuilding-your-codespaces/configuring-prebuilds.md,broken liquid tags
 translations/es-ES/content/codespaces/prebuilding-your-codespaces/managing-prebuilds.md,broken liquid tags
 translations/es-ES/content/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers.md,broken liquid tags
+translations/es-ES/content/codespaces/setting-up-your-project-for-codespaces/setting-a-minimum-specification-for-codespace-machines.md,broken liquid tags
 translations/es-ES/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-dotnet-project-for-codespaces.md,broken liquid tags
 translations/es-ES/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-java-project-for-codespaces.md,broken liquid tags
 translations/es-ES/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-nodejs-project-for-codespaces.md,broken liquid tags
@@ -780,7 +831,7 @@ translations/es-ES/content/organizations/managing-organization-settings/integrat
 translations/es-ES/content/organizations/managing-organization-settings/managing-the-commit-signoff-policy-for-your-organization.md,rendering error
 translations/es-ES/content/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization.md,rendering error
 translations/es-ES/content/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization.md,broken liquid tags
-translations/es-ES/content/organizations/managing-organization-settings/setting-permissions-for-adding-outside-collaborators.md,broken liquid tags
+translations/es-ES/content/organizations/managing-organization-settings/setting-permissions-for-adding-outside-collaborators.md,rendering error
 translations/es-ES/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-security-managers-in-your-organization.md,rendering error
 translations/es-ES/content/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on.md,broken liquid tags
 translations/es-ES/content/organizations/managing-saml-single-sign-on-for-your-organization/configuring-saml-single-sign-on-and-scim-using-okta.md,broken liquid tags
@@ -978,7 +1029,7 @@ translations/es-ES/data/reusables/actions/github-connect-resolution.md,broken li
 translations/es-ES/data/reusables/actions/hosted-runner-security.md,broken liquid tags
 translations/es-ES/data/reusables/actions/ip-allow-list-self-hosted-runners.md,broken liquid tags
 translations/es-ES/data/reusables/actions/jobs/section-defining-outputs-for-jobs.md,broken liquid tags
-translations/es-ES/data/reusables/actions/message-parameters.md,broken liquid tags
+translations/es-ES/data/reusables/actions/message-parameters.md,rendering error
 translations/es-ES/data/reusables/actions/more-resources-for-ghes.md,rendering error
 translations/es-ES/data/reusables/actions/moving-a-runner-to-a-group.md,rendering error
 translations/es-ES/data/reusables/actions/ref_name-description.md,broken liquid tags
@@ -1004,7 +1055,7 @@ translations/es-ES/data/reusables/advanced-security/about-committer-numbers-ghec
 translations/es-ES/data/reusables/advanced-security/about-ghas-organization-policy.md,broken liquid tags
 translations/es-ES/data/reusables/advanced-security/secret-scanning-add-custom-pattern-details.md,rendering error
 translations/es-ES/data/reusables/advanced-security/secret-scanning-create-custom-pattern.md,rendering error
-translations/es-ES/data/reusables/advanced-security/secret-scanning-new-custom-pattern.md,broken liquid tags
+translations/es-ES/data/reusables/advanced-security/secret-scanning-new-custom-pattern.md,rendering error
 translations/es-ES/data/reusables/advanced-security/secret-scanning-push-protection-org.md,broken liquid tags
 translations/es-ES/data/reusables/apps/user-to-server-rate-limits.md,broken liquid tags
 translations/es-ES/data/reusables/audit_log/audit-log-action-categories.md,rendering error
@@ -1105,16 +1156,16 @@ translations/es-ES/data/reusables/organizations/billing_plans.md,rendering error
 translations/es-ES/data/reusables/organizations/github-apps-settings-sidebar.md,rendering error
 translations/es-ES/data/reusables/organizations/member-privileges.md,rendering error
 translations/es-ES/data/reusables/organizations/navigate-to-org.md,broken liquid tags
-translations/es-ES/data/reusables/organizations/new_team.md,broken liquid tags
-translations/es-ES/data/reusables/organizations/org_settings.md,broken liquid tags
-translations/es-ES/data/reusables/organizations/organization-wide-project.md,broken liquid tags
-translations/es-ES/data/reusables/organizations/owners-team.md,broken liquid tags
-translations/es-ES/data/reusables/organizations/people.md,broken liquid tags
+translations/es-ES/data/reusables/organizations/new_team.md,rendering error
+translations/es-ES/data/reusables/organizations/org_settings.md,rendering error
+translations/es-ES/data/reusables/organizations/organization-wide-project.md,rendering error
+translations/es-ES/data/reusables/organizations/owners-team.md,rendering error
+translations/es-ES/data/reusables/organizations/people.md,rendering error
 translations/es-ES/data/reusables/organizations/repository-defaults.md,rendering error
 translations/es-ES/data/reusables/organizations/security-and-analysis.md,rendering error
 translations/es-ES/data/reusables/organizations/security.md,rendering error
-translations/es-ES/data/reusables/organizations/specific_team.md,broken liquid tags
-translations/es-ES/data/reusables/organizations/teams.md,broken liquid tags
+translations/es-ES/data/reusables/organizations/specific_team.md,rendering error
+translations/es-ES/data/reusables/organizations/teams.md,rendering error
 translations/es-ES/data/reusables/organizations/teams_sidebar.md,rendering error
 translations/es-ES/data/reusables/organizations/verified-domains.md,rendering error
 translations/es-ES/data/reusables/package_registry/authenticate-packages.md,broken liquid tags
@@ -1122,7 +1173,7 @@ translations/es-ES/data/reusables/package_registry/authenticate-to-container-reg
 translations/es-ES/data/reusables/package_registry/authenticate_with_pat_for_v2_registry.md,broken liquid tags
 translations/es-ES/data/reusables/package_registry/next-steps-for-packages-enterprise-setup.md,broken liquid tags
 translations/es-ES/data/reusables/package_registry/package-registry-with-github-tokens.md,broken liquid tags
-translations/es-ES/data/reusables/package_registry/package-settings-from-org-level.md,broken liquid tags
+translations/es-ES/data/reusables/package_registry/package-settings-from-org-level.md,rendering error
 translations/es-ES/data/reusables/package_registry/packages-billing.md,broken liquid tags
 translations/es-ES/data/reusables/package_registry/required-scopes.md,broken liquid tags
 translations/es-ES/data/reusables/pages/build-failure-email-server.md,broken liquid tags
@@ -1145,6 +1196,7 @@ translations/es-ES/data/reusables/repositories/navigate-to-code-security-and-ana
 translations/es-ES/data/reusables/repositories/navigate-to-commit-page.md,broken liquid tags
 translations/es-ES/data/reusables/repositories/navigate-to-repo.md,broken liquid tags
 translations/es-ES/data/reusables/repositories/repository-branches.md,rendering error
+translations/es-ES/data/reusables/repositories/security-advisories-republishing.md,broken liquid tags
 translations/es-ES/data/reusables/repositories/sidebar-notifications.md,rendering error
 translations/es-ES/data/reusables/repositories/suggest-changes.md,broken liquid tags
 translations/es-ES/data/reusables/repositories/you-can-fork.md,broken liquid tags
@@ -1163,8 +1215,9 @@ translations/es-ES/data/reusables/secret-scanning/enterprise-enable-secret-scann
 translations/es-ES/data/reusables/secret-scanning/partner-secret-list-private-repo.md,rendering error
 translations/es-ES/data/reusables/secret-scanning/partner-secret-list-public-repo.md,broken liquid tags
 translations/es-ES/data/reusables/secret-scanning/secret-list-private-push-protection.md,rendering error
+translations/es-ES/data/reusables/security-advisory/security-advisory-overview.md,broken liquid tags
 translations/es-ES/data/reusables/security-overview/permissions.md,rendering error
-translations/es-ES/data/reusables/security/displayed-information.md,broken liquid tags
+translations/es-ES/data/reusables/security/displayed-information.md,rendering error
 translations/es-ES/data/reusables/shortdesc/rate_limits_github_apps.md,broken liquid tags
 translations/es-ES/data/reusables/sponsors/feedback.md,broken liquid tags
 translations/es-ES/data/reusables/sponsors/select-sponsorship-billing.md,broken liquid tags
@@ -1198,7 +1251,7 @@ translations/es-ES/data/reusables/user-settings/ssh.md,rendering error
 translations/es-ES/data/reusables/webhooks/pull_request_properties.md,broken liquid tags
 translations/es-ES/data/reusables/webhooks/pull_request_webhook_properties.md,broken liquid tags
 translations/es-ES/data/reusables/webhooks/repository_vulnerability_alert_short_desc.md,broken liquid tags
-translations/es-ES/data/reusables/webhooks/webhooks-rest-api-links.md,broken liquid tags
+translations/es-ES/data/reusables/webhooks/webhooks-rest-api-links.md,rendering error
 translations/es-ES/data/reusables/webhooks/workflow_run_properties.md,broken liquid tags
 translations/es-ES/data/variables/product.yml,broken liquid tags
 translations/es-ES/data/variables/projects.yml,broken liquid tags
diff --git a/translations/log/msft-ja-resets.csv b/translations/log/msft-ja-resets.csv
index 352c55ef51..0c39b2403a 100644
--- a/translations/log/msft-ja-resets.csv
+++ b/translations/log/msft-ja-resets.csv
@@ -72,6 +72,7 @@ translations/ja-JP/content/admin/identity-and-access-management/using-enterprise
 translations/ja-JP/content/admin/identity-and-access-management/using-enterprise-managed-users-and-saml-for-iam/index.md,file deleted because it no longer exists in main
 translations/ja-JP/content/admin/identity-and-access-management/using-enterprise-managed-users-and-saml-for-iam/managing-team-memberships-with-identity-provider-groups.md,file deleted because it no longer exists in main
 translations/ja-JP/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/configuring-user-provisioning-for-your-enterprise.md,file deleted because it no longer exists in main
+translations/ja-JP/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-xenserver.md,file deleted because it no longer exists in main
 translations/ja-JP/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-advanced-security-in-your-enterprise.md,file deleted because it no longer exists in main
 translations/ja-JP/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-project-board-policies-in-your-enterprise.md,file deleted because it no longer exists in main
 translations/ja-JP/content/admin/user-management/managing-organizations-in-your-enterprise/managing-unowned-organizations-in-your-enterprise.md,file deleted because it no longer exists in main
@@ -80,7 +81,20 @@ translations/ja-JP/content/authentication/troubleshooting-commit-signature-verif
 translations/ja-JP/content/billing/managing-billing-for-github-codespaces/about-billing-for-codespaces.md,file deleted because it no longer exists in main
 translations/ja-JP/content/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-codespaces.md,file deleted because it no longer exists in main
 translations/ja-JP/content/billing/managing-billing-for-github-codespaces/viewing-your-codespaces-usage.md,file deleted because it no longer exists in main
+translations/ja-JP/content/code-security/dependabot/dependabot-alerts/browsing-security-advisories-in-the-github-advisory-database.md,file deleted because it no longer exists in main
 translations/ja-JP/content/code-security/dependabot/dependabot-alerts/browsing-security-vulnerabilities-in-the-github-advisory-database.md,file deleted because it no longer exists in main
+translations/ja-JP/content/code-security/dependabot/dependabot-alerts/editing-security-advisories-in-the-github-advisory-database.md,file deleted because it no longer exists in main
+translations/ja-JP/content/code-security/repository-security-advisories/about-coordinated-disclosure-of-security-vulnerabilities.md,file deleted because it no longer exists in main
+translations/ja-JP/content/code-security/repository-security-advisories/about-github-security-advisories-for-repositories.md,file deleted because it no longer exists in main
+translations/ja-JP/content/code-security/repository-security-advisories/adding-a-collaborator-to-a-repository-security-advisory.md,file deleted because it no longer exists in main
+translations/ja-JP/content/code-security/repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability.md,file deleted because it no longer exists in main
+translations/ja-JP/content/code-security/repository-security-advisories/creating-a-repository-security-advisory.md,file deleted because it no longer exists in main
+translations/ja-JP/content/code-security/repository-security-advisories/editing-a-repository-security-advisory.md,file deleted because it no longer exists in main
+translations/ja-JP/content/code-security/repository-security-advisories/index.md,file deleted because it no longer exists in main
+translations/ja-JP/content/code-security/repository-security-advisories/permission-levels-for-repository-security-advisories.md,file deleted because it no longer exists in main
+translations/ja-JP/content/code-security/repository-security-advisories/publishing-a-repository-security-advisory.md,file deleted because it no longer exists in main
+translations/ja-JP/content/code-security/repository-security-advisories/removing-a-collaborator-from-a-repository-security-advisory.md,file deleted because it no longer exists in main
+translations/ja-JP/content/code-security/repository-security-advisories/withdrawing-a-repository-security-advisory.md,file deleted because it no longer exists in main
 translations/ja-JP/content/codespaces/codespaces-reference/disaster-recovery-for-codespaces.md,file deleted because it no longer exists in main
 translations/ja-JP/content/codespaces/codespaces-reference/security-in-codespaces.md,file deleted because it no longer exists in main
 translations/ja-JP/content/codespaces/codespaces-reference/understanding-billing-for-codespaces.md,file deleted because it no longer exists in main
@@ -212,6 +226,7 @@ translations/ja-JP/content/site-policy/privacy-policies/github-data-protection-a
 translations/ja-JP/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account.md,file deleted because it no longer exists in main
 translations/ja-JP/data/glossaries/internal.yml,file deleted because it no longer exists in main
 translations/ja-JP/data/graphql/ghes-3.1/graphql_previews.enterprise.yml,file deleted because it no longer exists in main
+translations/ja-JP/data/graphql/ghes-3.2/graphql_previews.enterprise.yml,file deleted because it no longer exists in main
 translations/ja-JP/data/reusables/actions/link-to-example-library.md,file deleted because it no longer exists in main
 translations/ja-JP/data/reusables/actions/perform-blob-storage-precheck.md,file deleted because it no longer exists in main
 translations/ja-JP/data/reusables/actions/self-hosted-runner-configure-runner-group.md,file deleted because it no longer exists in main
@@ -229,7 +244,9 @@ translations/ja-JP/data/reusables/codespaces/concurrent-codespace-limit.md,file
 translations/ja-JP/data/reusables/codespaces/prebuilds-beta-note.md,file deleted because it no longer exists in main
 translations/ja-JP/data/reusables/codespaces/prebuilds-not-available.md,file deleted because it no longer exists in main
 translations/ja-JP/data/reusables/codespaces/unsupported-repos.md,file deleted because it no longer exists in main
+translations/ja-JP/data/reusables/dependabot/beta-security-and-version-updates-onboarding.md,file deleted because it no longer exists in main
 translations/ja-JP/data/reusables/dependabot/create-dependabot-yml.md,file deleted because it no longer exists in main
+translations/ja-JP/data/reusables/dependency-review/beta.md,file deleted because it no longer exists in main
 translations/ja-JP/data/reusables/desktop/paste-email-git-config.md,file deleted because it no longer exists in main
 translations/ja-JP/data/reusables/dotcom_billing/codespaces-minutes.md,file deleted because it no longer exists in main
 translations/ja-JP/data/reusables/dotcom_billing/pricing_calculator/pricing_cal_codespaces.md,file deleted because it no longer exists in main
@@ -237,6 +254,7 @@ translations/ja-JP/data/reusables/education/upgrade-organization.md,file deleted
 translations/ja-JP/data/reusables/education/upgrade-page.md,file deleted because it no longer exists in main
 translations/ja-JP/data/reusables/enterprise-accounts/repository-visibility-policy.md,file deleted because it no longer exists in main
 translations/ja-JP/data/reusables/enterprise-licensing/you-can-sync-for-a-combined-view.md,file deleted because it no longer exists in main
+translations/ja-JP/data/reusables/enterprise/upgrade-ghes-for-actions.md,file deleted because it no longer exists in main
 translations/ja-JP/data/reusables/enterprise_management_console/username_normalization.md,file deleted because it no longer exists in main
 translations/ja-JP/data/reusables/enterprise_management_console/username_normalization_sample.md,file deleted because it no longer exists in main
 translations/ja-JP/data/reusables/gated-features/advanced-security.md,file deleted because it no longer exists in main
@@ -288,7 +306,6 @@ translations/ja-JP/content/account-and-profile/managing-subscriptions-and-notifi
 translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/about-your-organizations-profile.md,rendering error
 translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/managing-your-profile-readme.md,broken liquid tags
 translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/personalizing-your-profile.md,rendering error
-translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/setting-your-profile-to-private.md,broken liquid tags
 translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-settings-on-your-profile/showing-your-private-contributions-and-achievements-on-your-profile.md,broken liquid tags
 translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-settings-on-your-profile/viewing-contributions-on-your-profile.md,broken liquid tags
 translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-settings-on-your-profile/why-are-my-contributions-not-showing-up-on-my-profile.md,broken liquid tags
@@ -302,7 +319,10 @@ translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-pers
 translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/setting-your-commit-email-address.md,rendering error
 translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/changing-your-github-username.md,rendering error
 translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-accessibility-settings.md,broken liquid tags
+translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-security-and-analysis-settings-for-your-personal-account.md,rendering error
 translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-the-default-branch-name-for-your-repositories.md,rendering error
+translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-your-theme-settings.md,broken liquid tags
+translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/permission-levels-for-a-personal-account-repository.md,broken liquid tags
 translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/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-personal-account-on-github/managing-your-personal-account/best-practices-for-leaving-your-company.md,rendering error
 translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-personal-account/converting-a-user-into-an-organization.md,rendering error
@@ -328,9 +348,7 @@ translations/ja-JP/content/actions/deployment/deploying-to-your-cloud-provider/d
 translations/ja-JP/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-to-azure-static-web-app.md,rendering error
 translations/ja-JP/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-google-kubernetes-engine.md,rendering error
 translations/ja-JP/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-cloud-providers.md,broken liquid tags
-translations/ja-JP/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-hashicorp-vault.md,broken liquid tags
 translations/ja-JP/content/actions/examples/using-concurrency-expressions-and-a-test-matrix.md,broken liquid tags
-translations/ja-JP/content/actions/examples/using-the-github-cli-on-a-runner.md,broken liquid tags
 translations/ja-JP/content/actions/hosting-your-own-runners/about-self-hosted-runners.md,rendering error
 translations/ja-JP/content/actions/hosting-your-own-runners/adding-self-hosted-runners.md,rendering error
 translations/ja-JP/content/actions/hosting-your-own-runners/autoscaling-with-self-hosted-runners.md,rendering error
@@ -354,6 +372,7 @@ translations/ja-JP/content/actions/quickstart.md,broken liquid tags
 translations/ja-JP/content/actions/security-guides/automatic-token-authentication.md,rendering error
 translations/ja-JP/content/actions/security-guides/encrypted-secrets.md,rendering error
 translations/ja-JP/content/actions/security-guides/security-hardening-for-github-actions.md,rendering error
+translations/ja-JP/content/actions/using-github-hosted-runners/controlling-access-to-larger-runners.md,rendering error
 translations/ja-JP/content/actions/using-github-hosted-runners/using-larger-runners.md,rendering error
 translations/ja-JP/content/actions/using-workflows/about-workflows.md,rendering error
 translations/ja-JP/content/actions/using-workflows/caching-dependencies-to-speed-up-workflows.md,broken liquid tags
@@ -407,8 +426,12 @@ translations/ja-JP/content/admin/configuration/configuring-your-enterprise/initi
 translations/ja-JP/content/admin/configuration/configuring-your-enterprise/managing-github-mobile-for-your-enterprise.md,rendering error
 translations/ja-JP/content/admin/configuration/configuring-your-enterprise/site-admin-dashboard.md,broken liquid tags
 translations/ja-JP/content/admin/configuration/configuring-your-enterprise/troubleshooting-tls-errors.md,broken liquid tags
+translations/ja-JP/content/admin/enterprise-management/caching-repositories/about-repository-caching.md,rendering error
+translations/ja-JP/content/admin/enterprise-management/caching-repositories/configuring-a-repository-cache.md,rendering error
+translations/ja-JP/content/admin/enterprise-management/caching-repositories/index.md,rendering error
 translations/ja-JP/content/admin/enterprise-management/configuring-clustering/cluster-network-configuration.md,broken liquid tags
 translations/ja-JP/content/admin/enterprise-management/configuring-clustering/configuring-high-availability-replication-for-a-cluster.md,broken liquid tags
+translations/ja-JP/content/admin/enterprise-management/configuring-high-availability/about-geo-replication.md,broken liquid tags
 translations/ja-JP/content/admin/enterprise-management/configuring-high-availability/creating-a-high-availability-replica.md,broken liquid tags
 translations/ja-JP/content/admin/enterprise-management/monitoring-your-appliance/accessing-the-monitor-dashboard.md,broken liquid tags
 translations/ja-JP/content/admin/enterprise-management/monitoring-your-appliance/configuring-collectd.md,broken liquid tags
@@ -571,6 +594,7 @@ translations/ja-JP/content/billing/managing-your-license-for-github-enterprise/a
 translations/ja-JP/content/billing/managing-your-license-for-github-enterprise/downloading-your-license-for-github-enterprise.md,broken liquid tags
 translations/ja-JP/content/billing/managing-your-license-for-github-enterprise/uploading-a-new-license-to-github-enterprise-server.md,broken liquid tags
 translations/ja-JP/content/billing/managing-your-license-for-github-enterprise/viewing-license-usage-for-github-enterprise.md,broken liquid tags
+translations/ja-JP/content/code-security/adopting-github-advanced-security-at-scale/phase-6-rollout-and-scale-secret-scanning.md,rendering error
 translations/ja-JP/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts.md,rendering error
 translations/ja-JP/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-with-codeql.md,rendering error
 translations/ja-JP/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning.md,rendering error
@@ -589,22 +613,26 @@ translations/ja-JP/content/code-security/code-scanning/using-codeql-code-scannin
 translations/ja-JP/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/installing-codeql-cli-in-your-ci-system.md,broken liquid tags
 translations/ja-JP/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/running-codeql-runner-in-your-ci-system.md,broken liquid tags
 translations/ja-JP/content/code-security/dependabot/dependabot-alerts/about-dependabot-alerts.md,rendering error
-translations/ja-JP/content/code-security/dependabot/dependabot-alerts/browsing-security-advisories-in-the-github-advisory-database.md,rendering error
 translations/ja-JP/content/code-security/dependabot/dependabot-alerts/configuring-notifications-for-dependabot-alerts.md,rendering error
-translations/ja-JP/content/code-security/dependabot/dependabot-alerts/editing-security-advisories-in-the-github-advisory-database.md,broken liquid tags
 translations/ja-JP/content/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts.md,rendering error
 translations/ja-JP/content/code-security/dependabot/dependabot-security-updates/about-dependabot-security-updates.md,rendering error
 translations/ja-JP/content/code-security/dependabot/dependabot-security-updates/configuring-dependabot-security-updates.md,rendering error
 translations/ja-JP/content/code-security/dependabot/dependabot-version-updates/about-dependabot-version-updates.md,rendering error
 translations/ja-JP/content/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file.md,rendering error
 translations/ja-JP/content/code-security/dependabot/dependabot-version-updates/configuring-dependabot-version-updates.md,rendering error
+translations/ja-JP/content/code-security/dependabot/dependabot-version-updates/customizing-dependency-updates.md,rendering error
+translations/ja-JP/content/code-security/dependabot/dependabot-version-updates/listing-dependencies-configured-for-version-updates.md,rendering error
+translations/ja-JP/content/code-security/dependabot/index.md,broken liquid tags
 translations/ja-JP/content/code-security/dependabot/working-with-dependabot/automating-dependabot-with-github-actions.md,rendering error
+translations/ja-JP/content/code-security/dependabot/working-with-dependabot/keeping-your-actions-up-to-date-with-dependabot.md,rendering error
 translations/ja-JP/content/code-security/dependabot/working-with-dependabot/managing-encrypted-secrets-for-dependabot.md,rendering error
 translations/ja-JP/content/code-security/dependabot/working-with-dependabot/troubleshooting-dependabot-errors.md,rendering error
 translations/ja-JP/content/code-security/dependabot/working-with-dependabot/troubleshooting-the-detection-of-vulnerable-dependencies.md,rendering error
+translations/ja-JP/content/code-security/getting-started/adding-a-security-policy-to-your-repository.md,broken liquid tags
 translations/ja-JP/content/code-security/getting-started/github-security-features.md,rendering error
 translations/ja-JP/content/code-security/getting-started/securing-your-organization.md,rendering error
 translations/ja-JP/content/code-security/getting-started/securing-your-repository.md,rendering error
+translations/ja-JP/content/code-security/index.md,rendering error
 translations/ja-JP/content/code-security/secret-scanning/about-secret-scanning.md,rendering error
 translations/ja-JP/content/code-security/secret-scanning/configuring-secret-scanning-for-your-repositories.md,rendering error
 translations/ja-JP/content/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning.md,rendering error
@@ -621,6 +649,7 @@ translations/ja-JP/content/code-security/supply-chain-security/understanding-you
 translations/ja-JP/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph.md,rendering error
 translations/ja-JP/content/code-security/supply-chain-security/understanding-your-software-supply-chain/configuring-dependency-review.md,rendering error
 translations/ja-JP/content/code-security/supply-chain-security/understanding-your-software-supply-chain/configuring-the-dependency-graph.md,broken liquid tags
+translations/ja-JP/content/code-security/supply-chain-security/understanding-your-software-supply-chain/troubleshooting-the-dependency-graph.md,broken liquid tags
 translations/ja-JP/content/codespaces/codespaces-reference/allowing-your-codespace-to-access-a-private-image-registry.md,rendering error
 translations/ja-JP/content/codespaces/codespaces-reference/disaster-recovery-for-github-codespaces.md,broken liquid tags
 translations/ja-JP/content/codespaces/codespaces-reference/security-in-github-codespaces.md,broken liquid tags
@@ -659,6 +688,7 @@ translations/ja-JP/content/codespaces/prebuilding-your-codespaces/allowing-a-pre
 translations/ja-JP/content/codespaces/prebuilding-your-codespaces/configuring-prebuilds.md,broken liquid tags
 translations/ja-JP/content/codespaces/prebuilding-your-codespaces/managing-prebuilds.md,broken liquid tags
 translations/ja-JP/content/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers.md,broken liquid tags
+translations/ja-JP/content/codespaces/setting-up-your-project-for-codespaces/setting-a-minimum-specification-for-codespace-machines.md,broken liquid tags
 translations/ja-JP/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-dotnet-project-for-codespaces.md,broken liquid tags
 translations/ja-JP/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-java-project-for-codespaces.md,broken liquid tags
 translations/ja-JP/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-nodejs-project-for-codespaces.md,broken liquid tags
@@ -766,8 +796,12 @@ translations/ja-JP/content/graphql/reference/mutations.md,broken liquid tags
 translations/ja-JP/content/graphql/reference/objects.md,broken liquid tags
 translations/ja-JP/content/graphql/reference/unions.md,broken liquid tags
 translations/ja-JP/content/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards.md,broken liquid tags
+translations/ja-JP/content/issues/organizing-your-work-with-project-boards/managing-project-boards/changing-project-board-visibility.md,rendering error
+translations/ja-JP/content/issues/organizing-your-work-with-project-boards/managing-project-boards/copying-a-project-board.md,rendering error
+translations/ja-JP/content/issues/organizing-your-work-with-project-boards/managing-project-boards/creating-a-project-board.md,rendering error
 translations/ja-JP/content/issues/planning-and-tracking-with-projects/automating-your-project/automating-projects-using-actions.md,broken liquid tags
 translations/ja-JP/content/issues/planning-and-tracking-with-projects/automating-your-project/using-the-api-to-manage-projects.md,broken liquid tags
+translations/ja-JP/content/issues/planning-and-tracking-with-projects/creating-projects/migrating-from-projects-classic.md,rendering error
 translations/ja-JP/content/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/customizing-a-view.md,broken liquid tags
 translations/ja-JP/content/issues/planning-and-tracking-with-projects/learning-about-projects/best-practices-for-projects.md,broken liquid tags
 translations/ja-JP/content/issues/planning-and-tracking-with-projects/managing-items-in-your-project/adding-items-to-your-project.md,broken liquid tags
@@ -780,15 +814,21 @@ translations/ja-JP/content/organizations/granting-access-to-your-organization-wi
 translations/ja-JP/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization.md,rendering error
 translations/ja-JP/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-security-and-analysis-settings-for-your-organization.md,rendering error
 translations/ja-JP/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization.md,rendering error
+translations/ja-JP/content/organizations/managing-access-to-your-organizations-project-boards/adding-an-outside-collaborator-to-a-project-board-in-your-organization.md,rendering error
+translations/ja-JP/content/organizations/managing-access-to-your-organizations-project-boards/managing-access-to-a-project-board-for-organization-members.md,rendering error
+translations/ja-JP/content/organizations/managing-access-to-your-organizations-project-boards/managing-an-individuals-access-to-an-organization-project-board.md,rendering error
 translations/ja-JP/content/organizations/managing-access-to-your-organizations-project-boards/managing-team-access-to-an-organization-project-board.md,rendering error
+translations/ja-JP/content/organizations/managing-access-to-your-organizations-project-boards/removing-an-outside-collaborator-from-an-organization-project-board.md,rendering error
 translations/ja-JP/content/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities.md,broken liquid tags
 translations/ja-JP/content/organizations/managing-membership-in-your-organization/inviting-users-to-join-your-organization.md,rendering error
 translations/ja-JP/content/organizations/managing-organization-settings/deleting-an-organization-account.md,rendering error
 translations/ja-JP/content/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization.md,rendering error
 translations/ja-JP/content/organizations/managing-organization-settings/disabling-project-boards-in-your-organization.md,rendering error
 translations/ja-JP/content/organizations/managing-organization-settings/integrating-jira-with-your-organization-project-board.md,rendering error
+translations/ja-JP/content/organizations/managing-organization-settings/managing-the-commit-signoff-policy-for-your-organization.md,rendering error
 translations/ja-JP/content/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization.md,rendering error
 translations/ja-JP/content/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization.md,broken liquid tags
+translations/ja-JP/content/organizations/managing-organization-settings/setting-permissions-for-adding-outside-collaborators.md,broken liquid tags
 translations/ja-JP/content/organizations/managing-peoples-access-to-your-organization-with-roles/adding-a-billing-manager-to-your-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-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on.md,broken liquid tags
@@ -816,6 +856,7 @@ translations/ja-JP/content/packages/working-with-a-github-packages-registry/work
 translations/ja-JP/content/pages/configuring-a-custom-domain-for-your-github-pages-site/about-custom-domains-and-github-pages.md,broken liquid tags
 translations/ja-JP/content/pages/configuring-a-custom-domain-for-your-github-pages-site/managing-a-custom-domain-for-your-github-pages-site.md,rendering error
 translations/ja-JP/content/pages/getting-started-with-github-pages/about-github-pages.md,broken liquid tags
+translations/ja-JP/content/pages/getting-started-with-github-pages/unpublishing-a-github-pages-site.md,rendering error
 translations/ja-JP/content/pages/index.md,broken liquid tags
 translations/ja-JP/content/pages/setting-up-a-github-pages-site-with-jekyll/creating-a-github-pages-site-with-jekyll.md,rendering error
 translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-using-the-command-line.md,broken liquid tags
@@ -859,6 +900,7 @@ translations/ja-JP/content/repositories/creating-and-managing-repositories/trans
 translations/ja-JP/content/repositories/creating-and-managing-repositories/troubleshooting-cloning-errors.md,broken liquid tags
 translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners.md,rendering error
 translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-readmes.md,rendering error
+translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/classifying-your-repository-with-topics.md,broken liquid tags
 translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/licensing-a-repository.md,broken liquid tags
 translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository.md,rendering error
 translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-security-and-analysis-settings-for-your-repository.md,rendering error
@@ -900,6 +942,7 @@ translations/ja-JP/content/rest/guides/getting-started-with-the-rest-api.md,brok
 translations/ja-JP/content/rest/guides/traversing-with-pagination.md,rendering error
 translations/ja-JP/content/rest/guides/working-with-comments.md,broken liquid tags
 translations/ja-JP/content/rest/migrations/source-imports.md,broken liquid tags
+translations/ja-JP/content/rest/overview/api-previews.md,rendering error
 translations/ja-JP/content/rest/overview/other-authentication-methods.md,broken liquid tags
 translations/ja-JP/content/rest/overview/permissions-required-for-github-apps.md,rendering error
 translations/ja-JP/content/rest/overview/resources-in-the-rest-api.md,broken liquid tags
@@ -920,8 +963,10 @@ translations/ja-JP/content/sponsors/receiving-sponsorships-through-github-sponso
 translations/ja-JP/content/support/contacting-github-support/providing-data-to-github-support.md,broken liquid tags
 translations/ja-JP/content/support/learning-about-github-support/about-github-premium-support.md,rendering error
 translations/ja-JP/content/support/learning-about-github-support/about-github-support.md,rendering error
+translations/ja-JP/data/glossaries/external.yml,broken liquid tags
 translations/ja-JP/data/learning-tracks/actions.yml,broken liquid tags
 translations/ja-JP/data/learning-tracks/admin.yml,broken liquid tags
+translations/ja-JP/data/learning-tracks/code-security.yml,broken liquid tags
 translations/ja-JP/data/release-notes/enterprise-server/2-20/15.yml,rendering error
 translations/ja-JP/data/release-notes/enterprise-server/2-21/17.yml,rendering error
 translations/ja-JP/data/release-notes/enterprise-server/2-21/6.yml,rendering error
@@ -962,7 +1007,7 @@ translations/ja-JP/data/release-notes/enterprise-server/3-5/4.yml,rendering erro
 translations/ja-JP/data/release-notes/enterprise-server/3-6/0-rc1.yml,rendering error
 translations/ja-JP/data/reusables/accounts/create-personal-access-tokens.md,broken liquid tags
 translations/ja-JP/data/reusables/actions/about-actions-for-enterprises.md,broken liquid tags
-translations/ja-JP/data/reusables/actions/actions-audit-events-workflow.md,rendering error
+translations/ja-JP/data/reusables/actions/add-hosted-runner.md,broken liquid tags
 translations/ja-JP/data/reusables/actions/artifact-log-retention-statement.md,broken liquid tags
 translations/ja-JP/data/reusables/actions/cache-default-size.md,broken liquid tags
 translations/ja-JP/data/reusables/actions/changing-the-access-policy-of-a-runner-group.md,rendering error
@@ -979,6 +1024,8 @@ translations/ja-JP/data/reusables/actions/github-connect-resolution.md,broken li
 translations/ja-JP/data/reusables/actions/hosted-runner-security.md,broken liquid tags
 translations/ja-JP/data/reusables/actions/ip-allow-list-self-hosted-runners.md,broken liquid tags
 translations/ja-JP/data/reusables/actions/jobs/section-defining-outputs-for-jobs.md,broken liquid tags
+translations/ja-JP/data/reusables/actions/message-parameters.md,broken liquid tags
+translations/ja-JP/data/reusables/actions/more-resources-for-ghes.md,rendering error
 translations/ja-JP/data/reusables/actions/moving-a-runner-to-a-group.md,rendering error
 translations/ja-JP/data/reusables/actions/ref_name-description.md,broken liquid tags
 translations/ja-JP/data/reusables/actions/reusable-workflow-artifacts.md,rendering error
@@ -986,6 +1033,7 @@ translations/ja-JP/data/reusables/actions/reusable-workflow-calling-syntax.md,re
 translations/ja-JP/data/reusables/actions/reusable-workflows.md,rendering error
 translations/ja-JP/data/reusables/actions/runner-groups-add-to-enterprise-first-steps.md,rendering error
 translations/ja-JP/data/reusables/actions/self-hosted-runner-add-to-enterprise.md,rendering error
+translations/ja-JP/data/reusables/actions/self-hosted-runner-auto-removal.md,rendering error
 translations/ja-JP/data/reusables/actions/self-hosted-runner-check-installation-success.md,broken liquid tags
 translations/ja-JP/data/reusables/actions/self-hosted-runner-management-permissions-required.md,rendering error
 translations/ja-JP/data/reusables/actions/self-hosted-runner-networking-to-dotcom.md,broken liquid tags
@@ -1003,6 +1051,7 @@ translations/ja-JP/data/reusables/advanced-security/about-committer-numbers-ghec
 translations/ja-JP/data/reusables/advanced-security/about-ghas-organization-policy.md,broken liquid tags
 translations/ja-JP/data/reusables/advanced-security/secret-scanning-add-custom-pattern-details.md,rendering error
 translations/ja-JP/data/reusables/advanced-security/secret-scanning-create-custom-pattern.md,rendering error
+translations/ja-JP/data/reusables/advanced-security/secret-scanning-new-custom-pattern.md,broken liquid tags
 translations/ja-JP/data/reusables/advanced-security/secret-scanning-push-protection-org.md,broken liquid tags
 translations/ja-JP/data/reusables/apps/user-to-server-rate-limits.md,broken liquid tags
 translations/ja-JP/data/reusables/audit_log/audit-log-action-categories.md,rendering error
@@ -1011,8 +1060,9 @@ translations/ja-JP/data/reusables/audit_log/audit_log_sidebar_for_org_admins.md,
 translations/ja-JP/data/reusables/audit_log/audit_log_sidebar_for_site_admins.md,rendering error
 translations/ja-JP/data/reusables/branches/new-repo-default-branch.md,broken liquid tags
 translations/ja-JP/data/reusables/classroom/about-autograding.md,broken liquid tags
-translations/ja-JP/data/reusables/code-scanning/analyze-go.md,broken liquid tags
+translations/ja-JP/data/reusables/code-scanning/alerts-found-in-generated-code.md,broken liquid tags
 translations/ja-JP/data/reusables/code-scanning/autobuild-add-build-steps.md,broken liquid tags
+translations/ja-JP/data/reusables/code-scanning/autobuild-compiled-languages.md,broken liquid tags
 translations/ja-JP/data/reusables/code-scanning/codeql-context-for-actions-and-third-party-tools.md,broken liquid tags
 translations/ja-JP/data/reusables/code-scanning/codeql-languages-bullets.md,rendering error
 translations/ja-JP/data/reusables/code-scanning/codeql-languages-keywords.md,rendering error
@@ -1063,6 +1113,7 @@ translations/ja-JP/data/reusables/enterprise-accounts/oidc-gei-warning.md,broken
 translations/ja-JP/data/reusables/enterprise-accounts/security-tab.md,rendering error
 translations/ja-JP/data/reusables/enterprise/apply-configuration.md,broken liquid tags
 translations/ja-JP/data/reusables/enterprise/rate_limit.md,broken liquid tags
+translations/ja-JP/data/reusables/enterprise/repository-caching-release-phase.md,rendering error
 translations/ja-JP/data/reusables/enterprise/test-in-staging.md,broken liquid tags
 translations/ja-JP/data/reusables/enterprise_enterprise_support/installing-releases.md,broken liquid tags
 translations/ja-JP/data/reusables/enterprise_installation/download-package.md,broken liquid tags
@@ -1079,7 +1130,6 @@ translations/ja-JP/data/reusables/enterprise_user_management/built-in-authentica
 translations/ja-JP/data/reusables/enterprise_user_management/consider-usernames-for-external-authentication.md,broken liquid tags
 translations/ja-JP/data/reusables/enterprise_user_management/disclaimer-for-git-read-access.md,broken liquid tags
 translations/ja-JP/data/reusables/files/choose-commit-email.md,broken liquid tags
-translations/ja-JP/data/reusables/gated-features/code-scanning.md,broken liquid tags
 translations/ja-JP/data/reusables/gated-features/codespaces-classroom-articles.md,broken liquid tags
 translations/ja-JP/data/reusables/gated-features/dependency-vulnerable-calls.md,rendering error
 translations/ja-JP/data/reusables/gated-features/secret-scanning-partner.md,rendering error
@@ -1093,7 +1143,6 @@ translations/ja-JP/data/reusables/getting-started/enterprise-advanced-security.m
 translations/ja-JP/data/reusables/getting-started/managing-enterprise-members.md,broken liquid tags
 translations/ja-JP/data/reusables/git/git-push.md,broken liquid tags
 translations/ja-JP/data/reusables/git/provide-credentials.md,broken liquid tags
-translations/ja-JP/data/reusables/github-ae/saml-idp-table.md,broken liquid tags
 translations/ja-JP/data/reusables/identity-and-permissions/vigilant-mode-beta-note.md,broken liquid tags
 translations/ja-JP/data/reusables/large_files/storage_assets_location.md,broken liquid tags
 translations/ja-JP/data/reusables/large_files/use_lfs_tip.md,broken liquid tags
@@ -1105,9 +1154,16 @@ translations/ja-JP/data/reusables/organizations/billing_plans.md,rendering error
 translations/ja-JP/data/reusables/organizations/github-apps-settings-sidebar.md,rendering error
 translations/ja-JP/data/reusables/organizations/member-privileges.md,rendering error
 translations/ja-JP/data/reusables/organizations/navigate-to-org.md,broken liquid tags
+translations/ja-JP/data/reusables/organizations/new_team.md,broken liquid tags
+translations/ja-JP/data/reusables/organizations/org_settings.md,broken liquid tags
+translations/ja-JP/data/reusables/organizations/organization-wide-project.md,broken liquid tags
+translations/ja-JP/data/reusables/organizations/owners-team.md,broken liquid tags
+translations/ja-JP/data/reusables/organizations/people.md,broken liquid tags
 translations/ja-JP/data/reusables/organizations/repository-defaults.md,rendering error
 translations/ja-JP/data/reusables/organizations/security-and-analysis.md,rendering error
 translations/ja-JP/data/reusables/organizations/security.md,rendering error
+translations/ja-JP/data/reusables/organizations/specific_team.md,broken liquid tags
+translations/ja-JP/data/reusables/organizations/teams.md,broken liquid tags
 translations/ja-JP/data/reusables/organizations/teams_sidebar.md,rendering error
 translations/ja-JP/data/reusables/organizations/verified-domains.md,rendering error
 translations/ja-JP/data/reusables/package_registry/authenticate-packages.md,broken liquid tags
@@ -1115,6 +1171,7 @@ translations/ja-JP/data/reusables/package_registry/authenticate-to-container-reg
 translations/ja-JP/data/reusables/package_registry/authenticate_with_pat_for_v2_registry.md,broken liquid tags
 translations/ja-JP/data/reusables/package_registry/next-steps-for-packages-enterprise-setup.md,broken liquid tags
 translations/ja-JP/data/reusables/package_registry/package-registry-with-github-tokens.md,broken liquid tags
+translations/ja-JP/data/reusables/package_registry/package-settings-from-org-level.md,broken liquid tags
 translations/ja-JP/data/reusables/package_registry/packages-billing.md,broken liquid tags
 translations/ja-JP/data/reusables/package_registry/required-scopes.md,broken liquid tags
 translations/ja-JP/data/reusables/pages/build-failure-email-server.md,broken liquid tags
@@ -1125,7 +1182,6 @@ translations/ja-JP/data/reusables/pages/sidebar-pages.md,rendering error
 translations/ja-JP/data/reusables/projects/enable-basic-workflow.md,broken liquid tags
 translations/ja-JP/data/reusables/pull_requests/configure_pull_request_merges_intro.md,broken liquid tags
 translations/ja-JP/data/reusables/pull_requests/default_merge_option.md,broken liquid tags
-translations/ja-JP/data/reusables/pull_requests/merge-queue-beta.md,broken liquid tags
 translations/ja-JP/data/reusables/pull_requests/pull_request_merges_and_contributions.md,broken liquid tags
 translations/ja-JP/data/reusables/pull_requests/rebase_and_merge_summary.md,broken liquid tags
 translations/ja-JP/data/reusables/pull_requests/resolving-conversations.md,broken liquid tags
@@ -1139,6 +1195,7 @@ translations/ja-JP/data/reusables/repositories/navigate-to-code-security-and-ana
 translations/ja-JP/data/reusables/repositories/navigate-to-commit-page.md,broken liquid tags
 translations/ja-JP/data/reusables/repositories/navigate-to-repo.md,broken liquid tags
 translations/ja-JP/data/reusables/repositories/repository-branches.md,rendering error
+translations/ja-JP/data/reusables/repositories/security-advisories-republishing.md,broken liquid tags
 translations/ja-JP/data/reusables/repositories/sidebar-notifications.md,rendering error
 translations/ja-JP/data/reusables/repositories/suggest-changes.md,broken liquid tags
 translations/ja-JP/data/reusables/repositories/you-can-fork.md,broken liquid tags
@@ -1150,7 +1207,6 @@ translations/ja-JP/data/reusables/saml/authorized-creds-info.md,broken liquid ta
 translations/ja-JP/data/reusables/saml/contact-support-if-your-idp-is-unavailable.md,broken liquid tags
 translations/ja-JP/data/reusables/saml/create-a-machine-user.md,broken liquid tags
 translations/ja-JP/data/reusables/saml/must-authorize-linked-identity.md,broken liquid tags
-translations/ja-JP/data/reusables/saml/okta-ae-sso-beta.md,broken liquid tags
 translations/ja-JP/data/reusables/saml/you-must-periodically-authenticate.md,broken liquid tags
 translations/ja-JP/data/reusables/scim/after-you-configure-saml.md,rendering error
 translations/ja-JP/data/reusables/scim/enterprise-account-scim.md,broken liquid tags
@@ -1160,7 +1216,9 @@ translations/ja-JP/data/reusables/secret-scanning/enterprise-enable-secret-scann
 translations/ja-JP/data/reusables/secret-scanning/partner-secret-list-private-repo.md,rendering error
 translations/ja-JP/data/reusables/secret-scanning/partner-secret-list-public-repo.md,broken liquid tags
 translations/ja-JP/data/reusables/secret-scanning/secret-list-private-push-protection.md,rendering error
+translations/ja-JP/data/reusables/security-advisory/security-advisory-overview.md,broken liquid tags
 translations/ja-JP/data/reusables/security-overview/permissions.md,rendering error
+translations/ja-JP/data/reusables/security/displayed-information.md,broken liquid tags
 translations/ja-JP/data/reusables/shortdesc/rate_limits_github_apps.md,broken liquid tags
 translations/ja-JP/data/reusables/sponsors/select-sponsorship-billing.md,broken liquid tags
 translations/ja-JP/data/reusables/ssh/about-ssh.md,broken liquid tags
@@ -1168,6 +1226,14 @@ translations/ja-JP/data/reusables/ssh/key-type-support.md,rendering error
 translations/ja-JP/data/reusables/ssh/rsa-sha-1-connection-failure-criteria.md,broken liquid tags
 translations/ja-JP/data/reusables/support/help_resources.md,rendering error
 translations/ja-JP/data/reusables/support/submit-a-ticket.md,broken liquid tags
+translations/ja-JP/data/reusables/supported-languages/C.md,broken liquid tags
+translations/ja-JP/data/reusables/supported-languages/Cpp.md,broken liquid tags
+translations/ja-JP/data/reusables/supported-languages/Cs.md,broken liquid tags
+translations/ja-JP/data/reusables/supported-languages/go.md,broken liquid tags
+translations/ja-JP/data/reusables/supported-languages/php.md,broken liquid tags
+translations/ja-JP/data/reusables/supported-languages/products-table-header.md,broken liquid tags
+translations/ja-JP/data/reusables/supported-languages/python.md,broken liquid tags
+translations/ja-JP/data/reusables/supported-languages/scala.md,broken liquid tags
 translations/ja-JP/data/reusables/user-settings/access_applications.md,rendering error
 translations/ja-JP/data/reusables/user-settings/account_settings.md,rendering error
 translations/ja-JP/data/reusables/user-settings/appearance-settings.md,rendering error
@@ -1185,6 +1251,7 @@ translations/ja-JP/data/reusables/user-settings/ssh.md,rendering error
 translations/ja-JP/data/reusables/webhooks/pull_request_properties.md,broken liquid tags
 translations/ja-JP/data/reusables/webhooks/pull_request_webhook_properties.md,broken liquid tags
 translations/ja-JP/data/reusables/webhooks/repository_vulnerability_alert_short_desc.md,broken liquid tags
+translations/ja-JP/data/reusables/webhooks/webhooks-rest-api-links.md,broken liquid tags
 translations/ja-JP/data/reusables/webhooks/workflow_run_properties.md,broken liquid tags
 translations/ja-JP/data/variables/product.yml,broken liquid tags
 translations/ja-JP/data/variables/projects.yml,broken liquid tags
diff --git a/translations/log/msft-pt-resets.csv b/translations/log/msft-pt-resets.csv
index c27422a21b..b548c40b6e 100644
--- a/translations/log/msft-pt-resets.csv
+++ b/translations/log/msft-pt-resets.csv
@@ -74,7 +74,20 @@ translations/pt-BR/content/authentication/troubleshooting-commit-signature-verif
 translations/pt-BR/content/billing/managing-billing-for-github-codespaces/about-billing-for-codespaces.md,file deleted because it no longer exists in main
 translations/pt-BR/content/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-codespaces.md,file deleted because it no longer exists in main
 translations/pt-BR/content/billing/managing-billing-for-github-codespaces/viewing-your-codespaces-usage.md,file deleted because it no longer exists in main
+translations/pt-BR/content/code-security/dependabot/dependabot-alerts/browsing-security-advisories-in-the-github-advisory-database.md,file deleted because it no longer exists in main
 translations/pt-BR/content/code-security/dependabot/dependabot-alerts/browsing-security-vulnerabilities-in-the-github-advisory-database.md,file deleted because it no longer exists in main
+translations/pt-BR/content/code-security/dependabot/dependabot-alerts/editing-security-advisories-in-the-github-advisory-database.md,file deleted because it no longer exists in main
+translations/pt-BR/content/code-security/repository-security-advisories/about-coordinated-disclosure-of-security-vulnerabilities.md,file deleted because it no longer exists in main
+translations/pt-BR/content/code-security/repository-security-advisories/about-github-security-advisories-for-repositories.md,file deleted because it no longer exists in main
+translations/pt-BR/content/code-security/repository-security-advisories/adding-a-collaborator-to-a-repository-security-advisory.md,file deleted because it no longer exists in main
+translations/pt-BR/content/code-security/repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability.md,file deleted because it no longer exists in main
+translations/pt-BR/content/code-security/repository-security-advisories/creating-a-repository-security-advisory.md,file deleted because it no longer exists in main
+translations/pt-BR/content/code-security/repository-security-advisories/editing-a-repository-security-advisory.md,file deleted because it no longer exists in main
+translations/pt-BR/content/code-security/repository-security-advisories/index.md,file deleted because it no longer exists in main
+translations/pt-BR/content/code-security/repository-security-advisories/permission-levels-for-repository-security-advisories.md,file deleted because it no longer exists in main
+translations/pt-BR/content/code-security/repository-security-advisories/publishing-a-repository-security-advisory.md,file deleted because it no longer exists in main
+translations/pt-BR/content/code-security/repository-security-advisories/removing-a-collaborator-from-a-repository-security-advisory.md,file deleted because it no longer exists in main
+translations/pt-BR/content/code-security/repository-security-advisories/withdrawing-a-repository-security-advisory.md,file deleted because it no longer exists in main
 translations/pt-BR/content/codespaces/codespaces-reference/disaster-recovery-for-codespaces.md,file deleted because it no longer exists in main
 translations/pt-BR/content/codespaces/codespaces-reference/security-in-codespaces.md,file deleted because it no longer exists in main
 translations/pt-BR/content/codespaces/codespaces-reference/understanding-billing-for-codespaces.md,file deleted because it no longer exists in main
@@ -223,9 +236,7 @@ translations/pt-BR/data/reusables/codespaces/concurrent-codespace-limit.md,file
 translations/pt-BR/data/reusables/codespaces/prebuilds-beta-note.md,file deleted because it no longer exists in main
 translations/pt-BR/data/reusables/codespaces/prebuilds-not-available.md,file deleted because it no longer exists in main
 translations/pt-BR/data/reusables/codespaces/unsupported-repos.md,file deleted because it no longer exists in main
-translations/pt-BR/data/reusables/dependabot/beta-security-and-version-updates-onboarding.md,file deleted because it no longer exists in main
 translations/pt-BR/data/reusables/dependabot/create-dependabot-yml.md,file deleted because it no longer exists in main
-translations/pt-BR/data/reusables/dependency-review/beta.md,file deleted because it no longer exists in main
 translations/pt-BR/data/reusables/desktop/paste-email-git-config.md,file deleted because it no longer exists in main
 translations/pt-BR/data/reusables/dotcom_billing/codespaces-minutes.md,file deleted because it no longer exists in main
 translations/pt-BR/data/reusables/dotcom_billing/pricing_calculator/pricing_cal_codespaces.md,file deleted because it no longer exists in main
@@ -233,7 +244,6 @@ translations/pt-BR/data/reusables/education/upgrade-organization.md,file deleted
 translations/pt-BR/data/reusables/education/upgrade-page.md,file deleted because it no longer exists in main
 translations/pt-BR/data/reusables/enterprise-accounts/repository-visibility-policy.md,file deleted because it no longer exists in main
 translations/pt-BR/data/reusables/enterprise-licensing/you-can-sync-for-a-combined-view.md,file deleted because it no longer exists in main
-translations/pt-BR/data/reusables/enterprise/upgrade-ghes-for-actions.md,file deleted because it no longer exists in main
 translations/pt-BR/data/reusables/enterprise_management_console/username_normalization_sample.md,file deleted because it no longer exists in main
 translations/pt-BR/data/reusables/gated-features/advanced-security.md,file deleted because it no longer exists in main
 translations/pt-BR/data/reusables/gated-features/discussions.md,file deleted because it no longer exists in main
@@ -243,6 +253,35 @@ translations/pt-BR/data/reusables/getting-started/learning-lab.md,file deleted b
 translations/pt-BR/data/reusables/open-source/open-source-learning-lab.md,file deleted because it no longer exists in main
 translations/pt-BR/data/reusables/pages/pages-builds-with-github-actions-public-beta.md,file deleted because it no longer exists in main
 translations/pt-BR/data/reusables/repositories/squash-and-rebase-linear-commit-hisitory.md,file deleted because it no longer exists in main
+translations/pt-BR/data/reusables/rest-reference/apps/oauth-applications.md,file deleted because it no longer exists in main
+translations/pt-BR/data/reusables/rest-reference/branches/branch-protection.md,file deleted because it no longer exists in main
+translations/pt-BR/data/reusables/rest-reference/checks/runs.md,file deleted because it no longer exists in main
+translations/pt-BR/data/reusables/rest-reference/deployments/statuses.md,file deleted because it no longer exists in main
+translations/pt-BR/data/reusables/rest-reference/enterprise-admin/audit-log.md,file deleted because it no longer exists in main
+translations/pt-BR/data/reusables/rest-reference/enterprise-admin/billing.md,file deleted because it no longer exists in main
+translations/pt-BR/data/reusables/rest-reference/interactions/interactions.md,file deleted because it no longer exists in main
+translations/pt-BR/data/reusables/rest-reference/issues/assignees.md,file deleted because it no longer exists in main
+translations/pt-BR/data/reusables/rest-reference/issues/labels.md,file deleted because it no longer exists in main
+translations/pt-BR/data/reusables/rest-reference/issues/milestones.md,file deleted because it no longer exists in main
+translations/pt-BR/data/reusables/rest-reference/metrics/community.md,file deleted because it no longer exists in main
+translations/pt-BR/data/reusables/rest-reference/orgs/custom_roles.md,file deleted because it no longer exists in main
+translations/pt-BR/data/reusables/rest-reference/orgs/members.md,file deleted because it no longer exists in main
+translations/pt-BR/data/reusables/rest-reference/orgs/outside-collaborators.md,file deleted because it no longer exists in main
+translations/pt-BR/data/reusables/rest-reference/projects/cards.md,file deleted because it no longer exists in main
+translations/pt-BR/data/reusables/rest-reference/projects/collaborators.md,file deleted because it no longer exists in main
+translations/pt-BR/data/reusables/rest-reference/projects/columns.md,file deleted because it no longer exists in main
+translations/pt-BR/data/reusables/rest-reference/pulls/review-requests.md,file deleted because it no longer exists in main
+translations/pt-BR/data/reusables/rest-reference/releases/assets.md,file deleted because it no longer exists in main
+translations/pt-BR/data/reusables/rest-reference/repos/forks.md,file deleted because it no longer exists in main
+translations/pt-BR/data/reusables/rest-reference/repos/lfs.md,file deleted because it no longer exists in main
+translations/pt-BR/data/reusables/rest-reference/users/blocking.md,file deleted because it no longer exists in main
+translations/pt-BR/data/reusables/rest-reference/users/emails.md,file deleted because it no longer exists in main
+translations/pt-BR/data/reusables/rest-reference/users/followers.md,file deleted because it no longer exists in main
+translations/pt-BR/data/reusables/rest-reference/users/keys.md,file deleted because it no longer exists in main
+translations/pt-BR/data/reusables/rest-reference/webhooks/repo-config.md,file deleted because it no longer exists in main
+translations/pt-BR/data/reusables/rest-reference/webhooks/repo-deliveries.md,file deleted because it no longer exists in main
+translations/pt-BR/data/reusables/rest-reference/webhooks/repos.md,file deleted because it no longer exists in main
+translations/pt-BR/data/reusables/security-center/beta.md,file deleted because it no longer exists in main
 translations/pt-BR/data/reusables/server-statistics/release-phase.md,file deleted because it no longer exists in main
 translations/pt-BR/content/account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/managing-your-subscriptions.md,rendering error
 translations/pt-BR/content/account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/viewing-your-subscriptions.md,broken liquid tags
@@ -267,7 +306,8 @@ translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-pers
 translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-accessibility-settings.md,broken liquid tags
 translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-security-and-analysis-settings-for-your-personal-account.md,rendering error
 translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-the-default-branch-name-for-your-repositories.md,rendering error
-translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-your-theme-settings.md,broken liquid tags
+translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-your-theme-settings.md,rendering error
+translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/permission-levels-for-a-personal-account-repository.md,broken liquid tags
 translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/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-personal-account-on-github/managing-your-personal-account/best-practices-for-leaving-your-company.md,broken liquid tags
 translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-personal-account/converting-a-user-into-an-organization.md,broken liquid tags
@@ -290,7 +330,6 @@ translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/d
 translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-google-kubernetes-engine.md,rendering error
 translations/pt-BR/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-cloud-providers.md,broken liquid tags
 translations/pt-BR/content/actions/examples/using-concurrency-expressions-and-a-test-matrix.md,broken liquid tags
-translations/pt-BR/content/actions/examples/using-the-github-cli-on-a-runner.md,broken liquid tags
 translations/pt-BR/content/actions/hosting-your-own-runners/about-self-hosted-runners.md,rendering error
 translations/pt-BR/content/actions/hosting-your-own-runners/adding-self-hosted-runners.md,rendering error
 translations/pt-BR/content/actions/hosting-your-own-runners/autoscaling-with-self-hosted-runners.md,rendering error
@@ -376,7 +415,7 @@ translations/pt-BR/content/admin/enterprise-management/caching-repositories/conf
 translations/pt-BR/content/admin/enterprise-management/caching-repositories/index.md,rendering error
 translations/pt-BR/content/admin/enterprise-management/configuring-clustering/cluster-network-configuration.md,broken liquid tags
 translations/pt-BR/content/admin/enterprise-management/configuring-clustering/configuring-high-availability-replication-for-a-cluster.md,broken liquid tags
-translations/pt-BR/content/admin/enterprise-management/configuring-high-availability/about-geo-replication.md,broken liquid tags
+translations/pt-BR/content/admin/enterprise-management/configuring-high-availability/about-geo-replication.md,rendering error
 translations/pt-BR/content/admin/enterprise-management/configuring-high-availability/creating-a-high-availability-replica.md,broken liquid tags
 translations/pt-BR/content/admin/enterprise-management/monitoring-your-appliance/accessing-the-monitor-dashboard.md,broken liquid tags
 translations/pt-BR/content/admin/enterprise-management/monitoring-your-appliance/configuring-collectd.md,broken liquid tags
@@ -561,9 +600,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/installing-codeql-cli-in-your-ci-system.md,broken liquid tags
 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,broken liquid tags
 translations/pt-BR/content/code-security/dependabot/dependabot-alerts/about-dependabot-alerts.md,rendering error
-translations/pt-BR/content/code-security/dependabot/dependabot-alerts/browsing-security-advisories-in-the-github-advisory-database.md,rendering error
 translations/pt-BR/content/code-security/dependabot/dependabot-alerts/configuring-notifications-for-dependabot-alerts.md,rendering error
-translations/pt-BR/content/code-security/dependabot/dependabot-alerts/editing-security-advisories-in-the-github-advisory-database.md,broken liquid tags
 translations/pt-BR/content/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts.md,rendering error
 translations/pt-BR/content/code-security/dependabot/dependabot-security-updates/about-dependabot-security-updates.md,rendering error
 translations/pt-BR/content/code-security/dependabot/dependabot-security-updates/configuring-dependabot-security-updates.md,rendering error
@@ -572,15 +609,17 @@ translations/pt-BR/content/code-security/dependabot/dependabot-version-updates/c
 translations/pt-BR/content/code-security/dependabot/dependabot-version-updates/configuring-dependabot-version-updates.md,rendering error
 translations/pt-BR/content/code-security/dependabot/dependabot-version-updates/customizing-dependency-updates.md,rendering error
 translations/pt-BR/content/code-security/dependabot/dependabot-version-updates/listing-dependencies-configured-for-version-updates.md,rendering error
-translations/pt-BR/content/code-security/dependabot/index.md,broken liquid tags
+translations/pt-BR/content/code-security/dependabot/index.md,rendering error
 translations/pt-BR/content/code-security/dependabot/working-with-dependabot/automating-dependabot-with-github-actions.md,rendering error
 translations/pt-BR/content/code-security/dependabot/working-with-dependabot/keeping-your-actions-up-to-date-with-dependabot.md,rendering error
 translations/pt-BR/content/code-security/dependabot/working-with-dependabot/managing-encrypted-secrets-for-dependabot.md,rendering error
 translations/pt-BR/content/code-security/dependabot/working-with-dependabot/troubleshooting-dependabot-errors.md,rendering error
 translations/pt-BR/content/code-security/dependabot/working-with-dependabot/troubleshooting-the-detection-of-vulnerable-dependencies.md,rendering error
+translations/pt-BR/content/code-security/getting-started/adding-a-security-policy-to-your-repository.md,broken liquid tags
 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/index.md,rendering error
 translations/pt-BR/content/code-security/secret-scanning/about-secret-scanning.md,rendering error
 translations/pt-BR/content/code-security/secret-scanning/configuring-secret-scanning-for-your-repositories.md,rendering error
 translations/pt-BR/content/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning.md,rendering error
@@ -597,7 +636,7 @@ translations/pt-BR/content/code-security/supply-chain-security/understanding-you
 translations/pt-BR/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph.md,rendering error
 translations/pt-BR/content/code-security/supply-chain-security/understanding-your-software-supply-chain/configuring-dependency-review.md,rendering error
 translations/pt-BR/content/code-security/supply-chain-security/understanding-your-software-supply-chain/configuring-the-dependency-graph.md,broken liquid tags
-translations/pt-BR/content/code-security/supply-chain-security/understanding-your-software-supply-chain/troubleshooting-the-dependency-graph.md,broken liquid tags
+translations/pt-BR/content/code-security/supply-chain-security/understanding-your-software-supply-chain/troubleshooting-the-dependency-graph.md,rendering error
 translations/pt-BR/content/codespaces/codespaces-reference/allowing-your-codespace-to-access-a-private-image-registry.md,broken liquid tags
 translations/pt-BR/content/codespaces/codespaces-reference/disaster-recovery-for-github-codespaces.md,broken liquid tags
 translations/pt-BR/content/codespaces/codespaces-reference/security-in-github-codespaces.md,broken liquid tags
@@ -636,6 +675,7 @@ translations/pt-BR/content/codespaces/prebuilding-your-codespaces/allowing-a-pre
 translations/pt-BR/content/codespaces/prebuilding-your-codespaces/configuring-prebuilds.md,broken liquid tags
 translations/pt-BR/content/codespaces/prebuilding-your-codespaces/managing-prebuilds.md,broken liquid tags
 translations/pt-BR/content/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers.md,broken liquid tags
+translations/pt-BR/content/codespaces/setting-up-your-project-for-codespaces/setting-a-minimum-specification-for-codespace-machines.md,broken liquid tags
 translations/pt-BR/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-dotnet-project-for-codespaces.md,broken liquid tags
 translations/pt-BR/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-java-project-for-codespaces.md,broken liquid tags
 translations/pt-BR/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-nodejs-project-for-codespaces.md,broken liquid tags
@@ -778,7 +818,7 @@ translations/pt-BR/content/organizations/managing-organization-settings/integrat
 translations/pt-BR/content/organizations/managing-organization-settings/managing-the-commit-signoff-policy-for-your-organization.md,rendering error
 translations/pt-BR/content/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization.md,rendering error
 translations/pt-BR/content/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization.md,broken liquid tags
-translations/pt-BR/content/organizations/managing-organization-settings/setting-permissions-for-adding-outside-collaborators.md,broken liquid tags
+translations/pt-BR/content/organizations/managing-organization-settings/setting-permissions-for-adding-outside-collaborators.md,rendering error
 translations/pt-BR/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-security-managers-in-your-organization.md,rendering error
 translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on.md,broken liquid tags
 translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/configuring-saml-single-sign-on-and-scim-using-okta.md,broken liquid tags
@@ -981,7 +1021,7 @@ translations/pt-BR/data/reusables/actions/github-connect-resolution.md,broken li
 translations/pt-BR/data/reusables/actions/ip-allow-list-self-hosted-runners.md,broken liquid tags
 translations/pt-BR/data/reusables/actions/jobs/section-defining-outputs-for-jobs.md,broken liquid tags
 translations/pt-BR/data/reusables/actions/jobs/section-running-jobs-in-a-container.md,broken liquid tags
-translations/pt-BR/data/reusables/actions/message-parameters.md,broken liquid tags
+translations/pt-BR/data/reusables/actions/message-parameters.md,rendering error
 translations/pt-BR/data/reusables/actions/more-resources-for-ghes.md,rendering error
 translations/pt-BR/data/reusables/actions/ref_name-description.md,broken liquid tags
 translations/pt-BR/data/reusables/actions/reusable-workflow-artifacts.md,rendering error
@@ -1006,7 +1046,7 @@ translations/pt-BR/data/reusables/advanced-security/about-committer-numbers-ghec
 translations/pt-BR/data/reusables/advanced-security/about-ghas-organization-policy.md,broken liquid tags
 translations/pt-BR/data/reusables/advanced-security/secret-scanning-add-custom-pattern-details.md,rendering error
 translations/pt-BR/data/reusables/advanced-security/secret-scanning-create-custom-pattern.md,rendering error
-translations/pt-BR/data/reusables/advanced-security/secret-scanning-new-custom-pattern.md,broken liquid tags
+translations/pt-BR/data/reusables/advanced-security/secret-scanning-new-custom-pattern.md,rendering error
 translations/pt-BR/data/reusables/advanced-security/secret-scanning-push-protection-org.md,broken liquid tags
 translations/pt-BR/data/reusables/apps/user-to-server-rate-limits.md,broken liquid tags
 translations/pt-BR/data/reusables/audit_log/audit-log-action-categories.md,rendering error
@@ -1109,16 +1149,16 @@ translations/pt-BR/data/reusables/organizations/billing_plans.md,rendering error
 translations/pt-BR/data/reusables/organizations/github-apps-settings-sidebar.md,rendering error
 translations/pt-BR/data/reusables/organizations/member-privileges.md,rendering error
 translations/pt-BR/data/reusables/organizations/navigate-to-org.md,broken liquid tags
-translations/pt-BR/data/reusables/organizations/new_team.md,broken liquid tags
-translations/pt-BR/data/reusables/organizations/org_settings.md,broken liquid tags
-translations/pt-BR/data/reusables/organizations/organization-wide-project.md,broken liquid tags
-translations/pt-BR/data/reusables/organizations/owners-team.md,broken liquid tags
-translations/pt-BR/data/reusables/organizations/people.md,broken liquid tags
+translations/pt-BR/data/reusables/organizations/new_team.md,rendering error
+translations/pt-BR/data/reusables/organizations/org_settings.md,rendering error
+translations/pt-BR/data/reusables/organizations/organization-wide-project.md,rendering error
+translations/pt-BR/data/reusables/organizations/owners-team.md,rendering error
+translations/pt-BR/data/reusables/organizations/people.md,rendering error
 translations/pt-BR/data/reusables/organizations/repository-defaults.md,rendering error
 translations/pt-BR/data/reusables/organizations/security-and-analysis.md,rendering error
 translations/pt-BR/data/reusables/organizations/security.md,rendering error
-translations/pt-BR/data/reusables/organizations/specific_team.md,broken liquid tags
-translations/pt-BR/data/reusables/organizations/teams.md,broken liquid tags
+translations/pt-BR/data/reusables/organizations/specific_team.md,rendering error
+translations/pt-BR/data/reusables/organizations/teams.md,rendering error
 translations/pt-BR/data/reusables/organizations/teams_sidebar.md,rendering error
 translations/pt-BR/data/reusables/organizations/verified-domains.md,rendering error
 translations/pt-BR/data/reusables/package_registry/authenticate-packages.md,broken liquid tags
@@ -1126,7 +1166,7 @@ translations/pt-BR/data/reusables/package_registry/authenticate-to-container-reg
 translations/pt-BR/data/reusables/package_registry/authenticate_with_pat_for_v2_registry.md,broken liquid tags
 translations/pt-BR/data/reusables/package_registry/next-steps-for-packages-enterprise-setup.md,broken liquid tags
 translations/pt-BR/data/reusables/package_registry/package-registry-with-github-tokens.md,broken liquid tags
-translations/pt-BR/data/reusables/package_registry/package-settings-from-org-level.md,broken liquid tags
+translations/pt-BR/data/reusables/package_registry/package-settings-from-org-level.md,rendering error
 translations/pt-BR/data/reusables/package_registry/packages-billing.md,broken liquid tags
 translations/pt-BR/data/reusables/package_registry/required-scopes.md,broken liquid tags
 translations/pt-BR/data/reusables/pages/build-failure-email-server.md,broken liquid tags
@@ -1149,6 +1189,7 @@ translations/pt-BR/data/reusables/repositories/navigate-to-code-security-and-ana
 translations/pt-BR/data/reusables/repositories/navigate-to-commit-page.md,broken liquid tags
 translations/pt-BR/data/reusables/repositories/navigate-to-repo.md,broken liquid tags
 translations/pt-BR/data/reusables/repositories/repository-branches.md,rendering error
+translations/pt-BR/data/reusables/repositories/security-advisories-republishing.md,broken liquid tags
 translations/pt-BR/data/reusables/repositories/sidebar-notifications.md,rendering error
 translations/pt-BR/data/reusables/repositories/suggest-changes.md,broken liquid tags
 translations/pt-BR/data/reusables/repositories/you-can-fork.md,broken liquid tags
@@ -1167,8 +1208,9 @@ translations/pt-BR/data/reusables/secret-scanning/enterprise-enable-secret-scann
 translations/pt-BR/data/reusables/secret-scanning/partner-secret-list-private-repo.md,rendering error
 translations/pt-BR/data/reusables/secret-scanning/partner-secret-list-public-repo.md,broken liquid tags
 translations/pt-BR/data/reusables/secret-scanning/secret-list-private-push-protection.md,rendering error
+translations/pt-BR/data/reusables/security-advisory/security-advisory-overview.md,broken liquid tags
 translations/pt-BR/data/reusables/security-overview/permissions.md,rendering error
-translations/pt-BR/data/reusables/security/displayed-information.md,broken liquid tags
+translations/pt-BR/data/reusables/security/displayed-information.md,rendering error
 translations/pt-BR/data/reusables/shortdesc/rate_limits_github_apps.md,broken liquid tags
 translations/pt-BR/data/reusables/sponsors/select-sponsorship-billing.md,broken liquid tags
 translations/pt-BR/data/reusables/ssh/about-ssh.md,broken liquid tags
@@ -1201,7 +1243,7 @@ translations/pt-BR/data/reusables/user-settings/ssh.md,rendering error
 translations/pt-BR/data/reusables/webhooks/pull_request_properties.md,broken liquid tags
 translations/pt-BR/data/reusables/webhooks/pull_request_webhook_properties.md,broken liquid tags
 translations/pt-BR/data/reusables/webhooks/repository_vulnerability_alert_short_desc.md,broken liquid tags
-translations/pt-BR/data/reusables/webhooks/webhooks-rest-api-links.md,broken liquid tags
+translations/pt-BR/data/reusables/webhooks/webhooks-rest-api-links.md,rendering error
 translations/pt-BR/data/reusables/webhooks/workflow_run_properties.md,broken liquid tags
 translations/pt-BR/data/variables/migrations.yml,broken liquid tags
 translations/pt-BR/data/variables/notifications.yml,broken liquid tags
diff --git a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/permission-levels-for-a-personal-account-repository.md b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/permission-levels-for-a-personal-account-repository.md
index e31b878645..e113259b91 100644
--- a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/permission-levels-for-a-personal-account-repository.md
+++ b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/permission-levels-for-a-personal-account-repository.md
@@ -1,6 +1,6 @@
 ---
-title: Níveis de permissão para um repositório da conta pessoal
-intro: 'Um repositório pertencente a uma conta pessoal tem dois níveis de permissão: proprietário do repositório e colaboradores.'
+title: Permission levels for a personal account repository
+intro: 'A repository owned by a personal account has two permission levels: the repository owner and collaborators.'
 redirect_from:
   - /articles/permission-levels-for-a-user-account-repository
   - /github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository
@@ -14,84 +14,79 @@ versions:
 topics:
   - Accounts
 shortTitle: Repository permissions
-ms.openlocfilehash: e7c7a542204c7b1ce69bc19ac326fb248bbbff12
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
-ms.translationtype: HT
-ms.contentlocale: pt-BR
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147066303'
 ---
-## Sobre os níveis de permissões para um repositório de conta pessoal
+## About permissions levels for a personal account repository
 
-Repositórios pertencentes a contas pessoais têm um proprietário. As permissões de propriedade não podem ser compartilhadas com outra conta pessoal.
+Repositories owned by personal accounts have one owner. Ownership permissions can't be shared with another personal account.
 
-Você também pode {% ifversion fpt or ghec %}convidar{% else %}add{% endif %} usuários no {% data variables.product.product_name %} para seu repositório como colaboradores. Para obter mais informações, confira "[Como convidar colaboradores para um repositório pessoal](/github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository)".
+You can also {% ifversion fpt or ghec %}invite{% else %}add{% endif %} users on {% data variables.product.product_name %} to your repository as collaborators. For more information, see "[Inviting collaborators to a personal repository](/github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository)."
 
 {% tip %}
 
-**Dica:** caso você precise ter um acesso mais granular a um repositório pertencente a sua conta pessoal, considere a possibilidade de transferir o repositório para uma organização. Para obter mais informações, confira "[Como transferir um repositório](/github/administering-a-repository/transferring-a-repository#transferring-a-repository-owned-by-your-personal-account)".
+**Tip:** If you require more granular access to a repository owned by your personal account, consider transferring the repository to an organization. For more information, see "[Transferring a repository](/github/administering-a-repository/transferring-a-repository#transferring-a-repository-owned-by-your-personal-account)."
 
 {% endtip %}
 
-## Acesso de proprietário para um repositório de propriedade de uma conta pessoal
+## Owner access for a repository owned by a personal account
 
-O proprietário do repositório tem controle total do repositório. Além das ações que qualquer colaborador pode executar, o proprietário do repositório pode executar as ações a seguir.
+The repository owner has full control of the repository. In addition to the actions that any collaborator can perform, the repository owner can perform the following actions.
 
-| Ação | Mais informações |
+| Action | More information |
 | :- | :- |
-| {% ifversion fpt or ghec %}Convidar colaboradores{% else %}Adicionar colaboradores{% endif %} | "[Como convidar colaboradores para um repositório pessoal](/github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository)" |
-| Alterar a visibilidade do repositório | "[Como definir a visibilidade do repositório](/github/administering-a-repository/setting-repository-visibility)" |{% ifversion fpt or ghec %}
-| Limitar interações com o repositório | "[Como limitar as interações no seu repositório](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository)" |{% endif %}
-| Renomear um branch, incluindo o branch padrão | "[Como renomear um branch](/github/administering-a-repository/renaming-a-branch)" |
-| Fazer merge de uma pull request em um branch protegido, mesmo sem revisões de aprovação | "[Sobre os branches protegidos](/github/administering-a-repository/about-protected-branches)" |
-| Excluir o repositório | "[Como excluir um repositório](/repositories/creating-and-managing-repositories/deleting-a-repository)" |
-| Gerenciar tópicos do repositório | "[Como classificar seu repositório com tópicos](/github/administering-a-repository/classifying-your-repository-with-topics)" |{% ifversion fpt or ghec %}
-| Gerenciar configurações de segurança e análise para o repositório | "[Como gerenciar as configurações de segurança e de análise do seu repositório](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)" |{% endif %}{% ifversion fpt or ghec %}
-| Habilitar o gráfico de dependências para um repositório privado | "[Como explorar as dependências de um repositório](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository#enabling-and-disabling-the-dependency-graph-for-a-private-repository)" |{% endif %}
-| Excluir e restaurar pacotes | "[Como excluir e restaurar um pacote](/packages/learn-github-packages/deleting-and-restoring-a-package)" |
-| Personalizar a visualização das mídias sociais do repositório | "[Como personalizar a visualização de mídia social do seu repositório](/github/administering-a-repository/customizing-your-repositorys-social-media-preview)" |
-| Criar um modelo a partir do repositório | "[Como criar um repositório de modelo](/github/creating-cloning-and-archiving-repositories/creating-a-template-repository)" |
-| Controlar o acesso a {% data variables.product.prodname_dependabot_alerts %}| "[Como gerenciar as configurações de segurança e de análise do seu repositório](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts)" |{% ifversion fpt or ghec %}
-| Ignorar {% data variables.product.prodname_dependabot_alerts %} no repositório | "[Como ver e atualizar {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts)" |
-| Gerenciar o uso de dados para um repositório privado | "[Como gerenciar configurações de uso de dados para seu repositório privado](/get-started/privacy-on-github/managing-data-use-settings-for-your-private-repository)"|{% endif %}
-| Definir os proprietários do código do repositório | "[Sobre os proprietários de código](/github/creating-cloning-and-archiving-repositories/about-code-owners)" |
-| Arquivar o repositório | "[Como arquivar repositórios](/repositories/archiving-a-github-repository/archiving-repositories)" |{% ifversion fpt or ghec %}
-| Criar avisos de segurança | "[Sobre os {% data variables.product.prodname_security_advisories %}](/github/managing-security-vulnerabilities/about-github-security-advisories)" |
-| Exibir um botão de patrocinador | "[Como exibir um botão de patrocinador no seu repositório](/github/administering-a-repository/displaying-a-sponsor-button-in-your-repository)" |{% endif %}
-| Permitir ou negar merge automático para pull requests | "[Como gerenciar a mesclagem automática para solicitações de pull no seu repositório](/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository)" | 
+| {% ifversion fpt or ghec %}Invite collaborators{% else %}Add collaborators{% endif %} | "[Inviting collaborators to a personal repository](/github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository)" |
+| Change the visibility of the repository | "[Setting repository visibility](/github/administering-a-repository/setting-repository-visibility)" |{% ifversion fpt or ghec %}
+| Limit interactions with the repository | "[Limiting interactions in your repository](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository)" |{% endif %}
+| Rename a branch, including the default branch | "[Renaming a branch](/github/administering-a-repository/renaming-a-branch)" |
+| Merge a pull request on a protected branch, even if there are no approving reviews | "[About protected branches](/github/administering-a-repository/about-protected-branches)" |
+| Delete the repository | "[Deleting a repository](/repositories/creating-and-managing-repositories/deleting-a-repository)" |
+| Manage the repository's topics | "[Classifying your repository with topics](/github/administering-a-repository/classifying-your-repository-with-topics)" |{% ifversion fpt or ghec %}
+| Manage security and analysis settings for the repository | "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)" |{% endif %}{% ifversion fpt or ghec %}
+| Enable the dependency graph for a private repository | "[Exploring the dependencies of a repository](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository#enabling-and-disabling-the-dependency-graph-for-a-private-repository)" |{% endif %}
+| Delete and restore packages | "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)" |
+| 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)" |
+| Control access to {% data variables.product.prodname_dependabot_alerts %}| "[Managing security and analysis settings for your repository](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts)" |{% ifversion fpt or ghec %}
+| Dismiss {% data variables.product.prodname_dependabot_alerts %} in the repository | "[Viewing and updating {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts)" |
+| Manage data use for a private repository | "[Managing data use settings for your private repository](/get-started/privacy-on-github/managing-data-use-settings-for-your-private-repository)"|{% endif %}
+| Define code owners for the repository | "[About code owners](/github/creating-cloning-and-archiving-repositories/about-code-owners)" |
+| Archive the repository | "[Archiving repositories](/repositories/archiving-a-github-repository/archiving-repositories)" |{% ifversion fpt or ghec %}
+| Create security advisories | "[About repository security advisories](/github/managing-security-vulnerabilities/about-github-security-advisories)" |
+| Display a sponsor button | "[Displaying a sponsor button in your repository](/github/administering-a-repository/displaying-a-sponsor-button-in-your-repository)" |{% endif %}
+| Allow or disallow auto-merge for pull requests | "[Managing auto-merge for pull requests in your repository](/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository)" | 
+| Manage webhooks and deploy keys	| "[Managing deploy keys](/developers/overview/managing-deploy-keys#deploy-keys)" |
 
-## Acesso colaborador para um repositório de propriedade de uma conta pessoal
+## Collaborator access for a repository owned by a personal account
 
-Os colaboradores em um repositório pessoal podem extrair (ler) os conteúdos do repositório e fazer push (gravação) das alterações no repositório.
+Collaborators on a personal repository can pull (read) the contents of the repository and push (write) changes to the repository.
 
 {% note %}
 
-**Observação:** em um repositório privado, os proprietários do repositório só podem permitir acesso de gravação aos colaboradores. Os colaboradores não podem ter acesso somente leitura a repositórios pertencentes a uma conta pessoal.
+**Note:** In a private repository, repository owners can only grant write access to collaborators. Collaborators can't have read-only access to repositories owned by a personal account.
 
 {% endnote %}
 
-Os colaboradores também podem executar as seguintes ações.
+Collaborators can also perform the following actions.
 
-| Ação | Mais informações |
+| Action | More information |
 | :- | :- |
-| Criar um fork do repositório | "[Sobre os forks](/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks)" |
-| Renomear um branch diferente do branch padrão | "[Como renomear um branch](/github/administering-a-repository/renaming-a-branch)" |
-| Criar, editar e excluir comentários em commits, pull requests e problemas no repositório | <ul><li>"[Sobre os problemas](/github/managing-your-work-on-github/about-issues)"</li><li>"[Como adicionar comentários a uma solicitação de pull](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request)"</li><li>"[Como gerenciar comentários ofensivos](/communities/moderating-comments-and-conversations/managing-disruptive-comments)"</li></ul> |
-| Criar, atribuir, fechar e reabrir problemas no repositório | "[Como gerenciar seu trabalho com problemas](/github/managing-your-work-on-github/managing-your-work-with-issues)" |
-| Gerenciar etiquetas para problemas e pull requests no repositório | "[Como rotular problemas e solicitações de pull](/github/managing-your-work-on-github/labeling-issues-and-pull-requests)" |
-| Gerenciar marcos para problemas e pull requests no repositório | "[Como criar e editar marcos para problemas e solicitações de pull](/github/managing-your-work-on-github/creating-and-editing-milestones-for-issues-and-pull-requests)" |
-| Marcar um problema ou pull request no repositório como duplicado | "[Sobre as solicitações de pull e os problemas duplicados](/github/managing-your-work-on-github/about-duplicate-issues-and-pull-requests)" |
-| Criar, mesclar e fechar pull requests no repositório | "[Como propor alterações no seu trabalho com solicitações de pull](/github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests)" |
-| Habilitar e desabilitar o merge automático para um pull request | "[Como mesclar automaticamente uma solicitação de pull](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request)"
-| Aplicar alterações sugeridas aos pull requests no repositório |"[Como incorporar comentários na sua solicitação de pull](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/incorporating-feedback-in-your-pull-request)" |
-| Criar um pull request a partir de uma bifurcação do repositório | "[Como criar uma solicitação de pull com base em um fork](/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request-from-a-fork)" |
-| Enviar uma revisão em um pull request que afeta a capacidade de merge do pull request | "[Como revisar as alterações propostas em uma solicitação de pull](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request)" |
-| Criar e editar uma wiki para o repositório | "[Sobre os wikis](/communities/documenting-your-project-with-wikis/about-wikis)" |
-| Criar e editar versões para o repositório | "[Como gerenciar versões em um repositório](/github/administering-a-repository/managing-releases-in-a-repository)" |
-| Agir como proprietário do código para o repositório | "[Sobre os proprietários de código](/articles/about-code-owners)" |{% ifversion fpt or ghae or ghec %}
-| Publicar, visualizar ou instalar pacotes | "[Como publicar e gerenciar pacotes](/github/managing-packages-with-github-packages/publishing-and-managing-packages)" |{% endif %}
-| Remover a si mesmos como colaboradores do repositório | "[Como remover a si mesmo de um repositório de colaborador](/github/setting-up-and-managing-your-github-user-account/removing-yourself-from-a-collaborators-repository)" |
+| Fork the repository | "[About forks](/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks)" |
+| Rename a branch other than the default branch | "[Renaming a branch](/github/administering-a-repository/renaming-a-branch)" |
+| Create, edit, and delete comments on commits, pull requests, and issues in the repository | <ul><li>"[About issues](/github/managing-your-work-on-github/about-issues)"</li><li>"[Commenting on a pull request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request)"</li><li>"[Managing disruptive comments](/communities/moderating-comments-and-conversations/managing-disruptive-comments)"</li></ul> |
+| Create, assign, close, and re-open issues in the repository | "[Managing your work with issues](/github/managing-your-work-on-github/managing-your-work-with-issues)" |
+| Manage labels for issues and pull requests in the repository | "[Labeling issues and pull requests](/github/managing-your-work-on-github/labeling-issues-and-pull-requests)" |
+| Manage milestones for issues and pull requests in the repository | "[Creating and editing milestones for issues and pull requests](/github/managing-your-work-on-github/creating-and-editing-milestones-for-issues-and-pull-requests)" |
+| Mark an issue or pull request in the repository as a duplicate | "[About duplicate issues and pull requests](/github/managing-your-work-on-github/about-duplicate-issues-and-pull-requests)" |
+| Create, merge, and close pull requests in the repository | "[Proposing changes to your work with pull requests](/github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests)" |
+| Enable and disable auto-merge for a pull request | "[Automatically merging a pull request](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request)"
+| Apply suggested changes to pull requests in the repository |"[Incorporating feedback in your pull request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/incorporating-feedback-in-your-pull-request)" |
+| Create a pull request from a fork of the repository | "[Creating a pull request from a fork](/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request-from-a-fork)" |
+| Submit a review on a pull request that affects the mergeability of the pull request | "[Reviewing proposed changes in a pull request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request)" |
+| Create and edit a wiki for the repository | "[About wikis](/communities/documenting-your-project-with-wikis/about-wikis)" |
+| Create and edit releases for the repository | "[Managing releases in a repository](/github/administering-a-repository/managing-releases-in-a-repository)" |
+| Act as a code owner for the repository | "[About code owners](/articles/about-code-owners)" |{% ifversion fpt or ghae or ghec %}
+| Publish, view, or install packages | "[Publishing and managing packages](/github/managing-packages-with-github-packages/publishing-and-managing-packages)" |{% endif %}
+| Remove themselves as collaborators on the repository | "[Removing yourself from a collaborator's repository](/github/setting-up-and-managing-your-github-user-account/removing-yourself-from-a-collaborators-repository)" |
 
-## Leitura adicional
+## Further reading
 
-- "[Funções de repositório para uma organização](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)"
+- "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)"
diff --git a/translations/pt-BR/content/actions/examples/using-the-github-cli-on-a-runner.md b/translations/pt-BR/content/actions/examples/using-the-github-cli-on-a-runner.md
index 351014a933..e8a533b466 100644
--- a/translations/pt-BR/content/actions/examples/using-the-github-cli-on-a-runner.md
+++ b/translations/pt-BR/content/actions/examples/using-the-github-cli-on-a-runner.md
@@ -1,7 +1,7 @@
 ---
-title: Using the GitHub CLI on a runner
+title: Usando a CLI do GitHub em um executor
 shortTitle: Use the GitHub CLI on a runner
-intro: 'How to use advanced {% data variables.product.prodname_actions %} features for continuous integration (CI).'
+intro: 'Como usar recursos avançados do {% data variables.product.prodname_actions %} para CI (integração contínua).'
 versions:
   fpt: '*'
   ghes: '> 3.1'
@@ -10,40 +10,34 @@ versions:
 type: how_to
 topics:
   - Workflows
+ms.openlocfilehash: e0787d09cd194de0038d259c1aff777cc91a4a6a
+ms.sourcegitcommit: bf11c3e08cbb5eab6320e0de35b32ade6d863c03
+ms.translationtype: HT
+ms.contentlocale: pt-BR
+ms.lasthandoff: 10/27/2022
+ms.locfileid: '148111582'
 ---
-
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Example overview
+## Visão geral de exemplo
 
-{% data reusables.actions.example-workflow-intro-ci %} When this workflow is triggered, it automatically runs a script that checks whether the {% data variables.product.prodname_dotcom %} Docs site has any broken links. If any broken links are found, the workflow uses the {% data variables.product.prodname_dotcom %} CLI to create a {% data variables.product.prodname_dotcom %} issue with the details.
+{% data reusables.actions.example-workflow-intro-ci %} Quando esse fluxo de trabalho é disparado, ele executa automaticamente um script que verifica se o site {% data variables.product.prodname_dotcom %} Docs tem links desfeitos. Quando são encontrados links desfeitos, o fluxo de trabalho usa a CLI do {% data variables.product.prodname_dotcom %} para criar um problema do {% data variables.product.prodname_dotcom %} com os detalhes.
 
 {% data reusables.actions.example-diagram-intro %}
 
-![Overview diagram of workflow steps](/assets/images/help/images/overview-actions-using-cli-ci-example.png)
+![Diagrama de visão geral das etapas do fluxo de trabalho](/assets/images/help/images/overview-actions-using-cli-ci-example.png)
 
-## Features used in this example
+## Recursos usados neste exemplo
 
 {% data reusables.actions.example-table-intro %}
 
-| **Feature**  | **Implementation** |
+| **Recurso**  | **Implementação** |
 | --- | --- |
-{% data reusables.actions.cron-table-entry %}
-{% data reusables.actions.permissions-table-entry %}
-{% data reusables.actions.if-conditions-table-entry %}
-{% data reusables.actions.secrets-table-entry %}
-{% data reusables.actions.checkout-action-table-entry %}
-{% data reusables.actions.setup-node-table-entry %}
-| Using a third-party action: | [`peter-evans/create-issue-from-file`](https://github.com/peter-evans/create-issue-from-file)|
-| Running shell commands on the runner: | [`run`](/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idstepsrun) |
-| Running a script on the runner: | Using `script/check-english-links.js` |
-| Generating an output file: | Piping the output using the `>` operator |
-| Checking for existing issues using {% data variables.product.prodname_cli %}: | [`gh issue list`](https://cli.github.com/manual/gh_issue_list) |
-| Commenting on an issue using {% data variables.product.prodname_cli %}: | [`gh issue comment`](https://cli.github.com/manual/gh_issue_comment) |
+{% data reusables.actions.cron-table-entry %} {% data reusables.actions.permissions-table-entry %} {% data reusables.actions.if-conditions-table-entry %} {% data reusables.actions.secrets-table-entry %} {% data reusables.actions.checkout-action-table-entry %} {% data reusables.actions.setup-node-table-entry %} | Como usar uma ação de terceiros: | [`peter-evans/create-issue-from-file`](https://github.com/peter-evans/create-issue-from-file)| | Como executar comandos do shell no executor: | [`run`](/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idstepsrun) | | Como executar um script no executor: | Como usar `script/check-english-links.js` | | Como gerar um arquivo de saída: | Como direcionar a saída usando o operador `>` | | Como verificar se há problemas usando a {% data variables.product.prodname_cli %}: | [`gh issue list`](https://cli.github.com/manual/gh_issue_list) | | Como comentar em um problema usando a {% data variables.product.prodname_cli %}: | [`gh issue comment`](https://cli.github.com/manual/gh_issue_comment) |
 
-## Example workflow
+## Fluxo de trabalho de exemplo
 
-{% data reusables.actions.example-docs-engineering-intro %} [`check-all-english-links.yml`](https://github.com/github/docs/blob/main/.github/workflows/check-all-english-links.yml).
+{% data reusables.actions.example-docs-engineering-intro %} [`check-all-english-links.yml`](https://github.com/github/docs/blob/6e01c0653836c10d7e092a17566a2c88b10504ce/.github/workflows/check-all-english-links.yml).
 
 {% data reusables.actions.note-understanding-example %}
 
@@ -178,15 +172,15 @@ jobs:
 </tbody>
 </table>
 
-## Understanding the example
+## Compreendendo o exemplo
 
 {% data reusables.actions.example-explanation-table-intro %}
 
 <table style="table-layout: fixed;">
 <thead>
   <tr>
-    <th style="width:60%"><b>Code</b></th>
-    <th style="width:40%"><b>Explanation</b></th>
+    <th style="width:60%"><b>Código</b></th>
+    <th style="width:40%"><b>Explicação</b></th>
   </tr>
 </thead>
 <tbody>
@@ -214,10 +208,10 @@ on:
 </td>
 <td>
 
-Defines the `workflow_dispatch` and `scheduled` as triggers for the workflow:
+Define `workflow_dispatch` e `scheduled` como gatilhos para o fluxo de trabalho:
 
-* The `workflow_dispatch` lets you manually run this workflow from the UI. For more information, see [`workflow_dispatch`](/actions/using-workflows/events-that-trigger-workflows#workflow_dispatch).
-* The `schedule` event lets you use `cron` syntax to define a regular interval for automatically triggering the workflow. For more information, see [`schedule`](/actions/reference/events-that-trigger-workflows#schedule).
+* O `workflow_dispatch` permite executar manualmente esse fluxo de trabalho por meio da interface do usuário. Para obter mais informações, confira [`workflow_dispatch`](/actions/using-workflows/events-that-trigger-workflows#workflow_dispatch).
+* O evento `schedule` permite que você use a sintaxe `cron` para definir um intervalo regular para disparar automaticamente o fluxo de trabalho. Para obter mais informações, confira [`schedule`](/actions/reference/events-that-trigger-workflows#schedule).
 </td>
 </tr>
 <tr>
@@ -231,7 +225,7 @@ permissions:
 </td>
 <td>
 
-Modifies the default permissions granted to `GITHUB_TOKEN`. This will vary depending on the needs of your workflow. For more information, see "[Assigning permissions to jobs](/actions/using-jobs/assigning-permissions-to-jobs)."
+Modifica as permissões padrão concedidas a `GITHUB_TOKEN`. Isso variará dependendo das necessidades do fluxo de trabalho. Para obter mais informações, confira "[Como atribuir permissões a trabalhos](/actions/using-jobs/assigning-permissions-to-jobs)".
 </td>
 </tr>
 <tr>
@@ -243,7 +237,7 @@ jobs:
 </td>
 <td>
 
-Groups together all the jobs that run in the workflow file.
+Agrupa todos os trabalhos executados no arquivo de fluxo de trabalho.
 </td>
 </tr>
 <tr>
@@ -256,7 +250,7 @@ Groups together all the jobs that run in the workflow file.
 </td>
 <td>
 
-Defines a job with the ID `check_all_english_links`, and the name `Check all links`, that is stored within the `jobs` key.
+Define um trabalho com a ID `check_all_english_links` e o nome `Check all links`, armazenados dentro da chave `jobs`.
 </td>
 </tr>
 <tr>
@@ -268,7 +262,7 @@ if: github.repository == 'github/docs-internal'
 </td>
 <td>
 
-Only run the `check_all_english_links` job if the repository is named `docs-internal` and is within the `github` organization. Otherwise, the job is marked as _skipped_.
+O trabalho `check_all_english_links` só será executado se o repositório chamar `docs-internal` e estiver dentro da organização `github`. Caso contrário, o trabalho será marcado como _ignorado_.
 </td>
 </tr>
 <tr>
@@ -280,7 +274,7 @@ runs-on: ubuntu-latest
 </td>
 <td>
 
-Configures the job to run on an Ubuntu Linux runner. This means that the job will execute on a fresh virtual machine hosted by {% data variables.product.prodname_dotcom %}. For syntax examples using other runners, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idruns-on)."
+Configura o trabalho a ser executado em um executor do Ubuntu Linux. Isto significa que o trabalho será executado em uma nova máquina virtual hospedada pelo {% data variables.product.prodname_dotcom %}. Para ver exemplos de sintaxe que usam outros executores, confira "[Sintaxe de fluxo de trabalho do {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idruns-on)".
 </td>
 </tr>
 <tr>
@@ -296,7 +290,7 @@ Configures the job to run on an Ubuntu Linux runner. This means that the job wil
 </td>
 <td>
 
-Creates custom environment variables, and redefines the built-in `GITHUB_TOKEN` variable to use a custom [secret](/actions/security-guides/encrypted-secrets). These variables will be referenced later in the workflow.
+Cria variáveis de ambiente personalizadas e redefine a variável interna `GITHUB_TOKEN` para usar um [segredo](/actions/security-guides/encrypted-secrets) personalizado. Essas variáveis serão referenciadas mais tarde no fluxo de trabalho.
 </td>
 </tr>
 <tr>
@@ -308,7 +302,7 @@ Creates custom environment variables, and redefines the built-in `GITHUB_TOKEN`
 </td>
 <td>
 
-Groups together all the steps that will run as part of the `check_all_english_links` job. Each job in the workflow has its own `steps` section.
+Agrupa todas as etapas que serão executadas durante o trabalho `check_all_english_links`. Cada trabalho no fluxo de trabalho tem a própria seção `steps`.
 </td>
 </tr>
 <tr>
@@ -321,7 +315,7 @@ Groups together all the steps that will run as part of the `check_all_english_li
 </td>
 <td>
 
-The `uses` keyword tells the job to retrieve the action named `actions/checkout`. This is an action that checks out your repository and downloads it to the runner, allowing you to run actions against your code (such as testing tools). You must use the checkout action any time your workflow will run against the repository's code or you are using an action defined in the repository.
+A palavra-chave `uses` informa que o trabalho deve recuperar a ação chamada `actions/checkout`. Esta é uma ação que verifica seu repositório e o faz o download do runner, permitindo que você execute ações contra seu código (como, por exemplo, ferramentas de teste). Você deve usar a ação de checkout sempre que o fluxo de trabalho for executado no código do repositório ou você estiver usando uma ação definida no repositório.
 </td>
 </tr>
 <tr>
@@ -337,7 +331,7 @@ The `uses` keyword tells the job to retrieve the action named `actions/checkout`
 </td>
 <td>
 
-This step uses the `actions/setup-node` action to install the specified version of the `node` software package on the runner, which gives you access to the `npm` command.
+Essa etapa usa a ação `actions/setup-node` para instalar a versão especificada do pacote de software `node` no executor, o que permite que você acesse o comando `npm`.
 </td>
 </tr>
 <tr>
@@ -352,7 +346,7 @@ This step uses the `actions/setup-node` action to install the specified version
 </td>
 <td>
 
-The `run` keyword tells the job to execute a command on the runner. In this case, the `npm ci` and `npm run build` commands are run as separate steps to install and build the Node.js application in the repository.
+A palavra-chave `run` instrui o trabalho a executar um comando no executor. Nesse caso, os comandos `npm ci` e `npm run build` são executados como etapas separadas para instalar e compilar o aplicativo Node.js no repositório.
 </td>
 </tr>
 <tr>
@@ -366,7 +360,7 @@ The `run` keyword tells the job to execute a command on the runner. In this case
 </td>
 <td>
 
-This `run` command executes a script that is stored in the repository at `script/check-english-links.js`, and pipes the output to a file called `broken_links.md`.
+Esse comando `run` executa um script que é armazenado no repositório em `script/check-english-links.js` e direciona a saída para um arquivo chamado `broken_links.md`.
 </td>
 </tr>
 <tr>
@@ -385,7 +379,7 @@ This `run` command executes a script that is stored in the repository at `script
 </td>
 <td>
 
-If the `check-english-links.js` script detects broken links and returns a non-zero (failure) exit status, then use a [workflow command](/actions/using-workflows/workflow-commands-for-github-actions#setting-an-output-parameter) to set an output that has the value of the first line of the `broken_links.md` file (this is used the next step).
+Se o script `check-english-links.js` detectar links desfeitos e retornar um status de saída diferente de zero (falha), use um [comando de fluxo de trabalho](/actions/using-workflows/workflow-commands-for-github-actions#setting-an-output-parameter) para definir uma saída que tenha o valor da primeira linha do arquivo `broken_links.md` (usado na próxima etapa).
 </td>
 </tr>
 <tr>
@@ -407,7 +401,7 @@ If the `check-english-links.js` script detects broken links and returns a non-ze
 </td>
 <td>
 
-Uses the `peter-evans/create-issue-from-file` action to create a new {% data variables.product.prodname_dotcom %} issue. This example is pinned to a specific version of the action, using the `b4f9ee0a9d4abbfc6986601d9b1a4f8f8e74c77e` SHA.
+Usa a ação `peter-evans/create-issue-from-file` para criar um problema do {% data variables.product.prodname_dotcom %}. Este exemplo é fixado a uma versão específica da ação, usando o SHA `b4f9ee0a9d4abbfc6986601d9b1a4f8f8e74c77e`.
 </td>
 </tr>
 <tr>
@@ -435,9 +429,9 @@ Uses the `peter-evans/create-issue-from-file` action to create a new {% data var
 </td>
 <td>
 
-Uses [`gh issue list`](https://cli.github.com/manual/gh_issue_list) to locate the previously created issue from earlier runs. This is [aliased](https://cli.github.com/manual/gh_alias_set) to `gh list-reports` for simpler processing in later steps. To get the issue URL, the `jq` expression processes the resulting JSON output.
+Usa [`gh issue list`](https://cli.github.com/manual/gh_issue_list) para localizar o problema que já foi criado de execuções anteriores. O [alias](https://cli.github.com/manual/gh_alias_set) `gh list-reports` é usado para simplificar o processamento nas próximas etapas. Para obter a URL do problema, a expressão `jq` processa a saída JSON resultante.
 
-[`gh issue comment`](https://cli.github.com/manual/gh_issue_comment) is then used to add a comment to the new issue that links to the previous one.
+Depois, [`gh issue comment`](https://cli.github.com/manual/gh_issue_comment) é usado para adicionar um comentário ao novo problema vinculado ao anterior.
 </td>
 </tr>
 <tr>
@@ -455,7 +449,7 @@ Uses [`gh issue list`](https://cli.github.com/manual/gh_issue_list) to locate th
 </td>
 <td>
 
-If an issue from a previous run is open and assigned to someone, then use [`gh issue comment`](https://cli.github.com/manual/gh_issue_comment) to add a comment with a link to the new issue.
+Se um problema de uma execução anterior estiver aberto e atribuído a alguém, use [`gh issue comment`](https://cli.github.com/manual/gh_issue_comment) para adicionar um comentário com um link para o novo problema.
 </td>
 </tr>
 <tr>
@@ -476,16 +470,16 @@ If an issue from a previous run is open and assigned to someone, then use [`gh i
 </td>
 <td>
 
-If an issue from a previous run is open and is not assigned to anyone, then:
+Se um problema de uma execução anterior estiver aberto e não estiver atribuído a ninguém:
 
-* Use [`gh issue comment`](https://cli.github.com/manual/gh_issue_comment) to add a comment with a link to the new issue.
-* Use [`gh issue close`](https://cli.github.com/manual/gh_issue_close) to close the old issue.
-* Use [`gh issue edit`](https://cli.github.com/manual/gh_issue_edit) to edit the old issue to remove it from a specific {% data variables.product.prodname_dotcom %} project board.
+* Use [`gh issue comment`](https://cli.github.com/manual/gh_issue_comment) para adicionar um comentário com um link para o novo problema.
+* Use [`gh issue close`](https://cli.github.com/manual/gh_issue_close) para fechar o problema antigo.
+* Use [`gh issue edit`](https://cli.github.com/manual/gh_issue_edit) para editar o problema antigo a fim de removê-lo de um quadro de projeto do {% data variables.product.prodname_dotcom %}.
 </td>
 </tr>
 </tbody>
 </table>
 
-## Next steps
+## Próximas etapas
 
 {% data reusables.actions.learning-actions %}
diff --git a/translations/pt-BR/content/actions/using-workflows/workflow-commands-for-github-actions.md b/translations/pt-BR/content/actions/using-workflows/workflow-commands-for-github-actions.md
index 61b705ee40..710052edb7 100644
--- a/translations/pt-BR/content/actions/using-workflows/workflow-commands-for-github-actions.md
+++ b/translations/pt-BR/content/actions/using-workflows/workflow-commands-for-github-actions.md
@@ -581,6 +581,8 @@ console.log("The running PID from the main action is: " +  process.env.STATE_pro
 
 During the execution of a workflow, the runner generates temporary files that can be used to perform certain actions. The path to these files are exposed via environment variables. You will need to use UTF-8 encoding when writing to these files to ensure proper processing of the commands. Multiple commands can be written to the same file, separated by newlines.
 
+Most commands in the following examples use double quotes for echoing strings, which will attempt to interpolate characters like `$` for shell variable names. To always use literal values in quoted strings, you can use single quotes instead.
+
 {% powershell %}
 
 {% note %}
diff --git a/translations/pt-BR/content/admin/index.md b/translations/pt-BR/content/admin/index.md
index 8b1ce2e5b0..aefca3a42e 100644
--- a/translations/pt-BR/content/admin/index.md
+++ b/translations/pt-BR/content/admin/index.md
@@ -125,11 +125,11 @@ children:
   - /guides
   - /release-notes
   - /all-releases
-ms.openlocfilehash: ebd1473538d42928ff3d9abb3c0e2bd9f12767f5
-ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.openlocfilehash: 3980ad01e56bf1e38dd6473c5e5246c6d45350eb
+ms.sourcegitcommit: 3268914369fb29540e4d88ee5e56bc7a41f2a60e
 ms.translationtype: HT
 ms.contentlocale: pt-BR
-ms.lasthandoff: 09/11/2022
-ms.locfileid: '147881152'
+ms.lasthandoff: 10/26/2022
+ms.locfileid: '148111302'
 ---
 
diff --git a/translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-the-codeql-workflow-for-compiled-languages.md b/translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-the-codeql-workflow-for-compiled-languages.md
index 242ee8f56a..1220575d5d 100644
--- a/translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-the-codeql-workflow-for-compiled-languages.md
+++ b/translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-the-codeql-workflow-for-compiled-languages.md
@@ -125,8 +125,8 @@ After removing the `autobuild` step, uncomment the `run` step and add build comm
 
 ``` yaml
 - run: |
-  make bootstrap
-  make release
+    make bootstrap
+    make release
 ```
 
 For more information about the `run` keyword, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepsrun)."
diff --git a/translations/pt-BR/content/code-security/dependabot/dependabot-alerts/browsing-security-advisories-in-the-github-advisory-database.md b/translations/pt-BR/content/code-security/dependabot/dependabot-alerts/browsing-security-advisories-in-the-github-advisory-database.md
deleted file mode 100644
index 663dc63e1b..0000000000
--- a/translations/pt-BR/content/code-security/dependabot/dependabot-alerts/browsing-security-advisories-in-the-github-advisory-database.md
+++ /dev/null
@@ -1,188 +0,0 @@
----
-title: Browsing security advisories in the GitHub Advisory Database
-intro: 'You can browse the {% data variables.product.prodname_advisory_database %} to find advisories for security risks in open source projects that are hosted on {% data variables.product.company_short %}.'
-shortTitle: Browse Advisory Database
-miniTocMaxHeadingLevel: 3
-redirect_from:
-  - /github/managing-security-vulnerabilities/browsing-security-vulnerabilities-in-the-github-advisory-database
-  - /code-security/supply-chain-security/browsing-security-vulnerabilities-in-the-github-advisory-database
-  - /code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/browsing-security-vulnerabilities-in-the-github-advisory-database
-  - /code-security/dependabot/dependabot-alerts/browsing-security-vulnerabilities-in-the-github-advisory-database
-versions:
-  fpt: '*'
-  ghec: '*'
-  ghes: '*'
-  ghae: '*'
-type: how_to
-topics:
-  - Security advisories
-  - Alerts
-  - Dependabot
-  - Vulnerabilities
-  - CVEs
----
-<!--Marketing-LINK: From /features/security/software-supply-chain page "Browsing security vulnerabilities in the GitHub Advisory Database".-->
-
-## About the {% data variables.product.prodname_advisory_database %}
-
-The {% data variables.product.prodname_advisory_database %} contains a list of known security vulnerabilities {% ifversion GH-advisory-db-supports-malware %}and malware, {% endif %}grouped in two categories: {% data variables.product.company_short %}-reviewed advisories and unreviewed advisories.
-
-{% data reusables.repositories.tracks-vulnerabilities %}
-
-## About types of security advisories
-
-{% data reusables.advisory-database.beta-malware-advisories %}
-
-Each advisory in the {% data variables.product.prodname_advisory_database %} is for a vulnerability in open source projects{% ifversion GH-advisory-db-supports-malware %} or for malicious open source software{% endif %}. 
-
-{% data reusables.repositories.a-vulnerability-is %} Vulnerabilities in code are usually introduced by accident and fixed soon after they are discovered. You should update your code to use the fixed version of the dependency as soon as it is available.
-
-{% ifversion GH-advisory-db-supports-malware %}
-
-In contrast, malicious software, or malware, is code that is intentionally designed to perform unwanted or harmful functions. The malware may target hardware, software, confidential data, or users of any application that uses the malware. You need to remove the malware from your project and find an alternative, more secure replacement for the dependency.
-
-{% endif %}
-
-### {% data variables.product.company_short %}-reviewed advisories
-
-{% data variables.product.company_short %}-reviewed advisories are security vulnerabilities{% ifversion GH-advisory-db-supports-malware %} or malware{% endif %} that have been mapped to packages in ecosystems we support. We carefully review each advisory for validity and ensure that they have a full description, and contain both ecosystem and package information.
-
-Generally, we name our supported ecosystems after the software programming language's associated package registry. We review advisories if they are for a vulnerability in a package that comes from a supported registry.
-
-- Composer (registry: https://packagist.org/){% ifversion GH-advisory-db-erlang-support %}
-- Erlang (registry: https://hex.pm/){% endif %}
-- Go (registry: https://pkg.go.dev/)
-{%- ifversion fpt or ghec or ghes > 3.6 or ghae > 3.6 %}
-- GitHub Actions (https://github.com/marketplace?type=actions/) {% endif %}
-- Maven (registry: https://repo.maven.apache.org/maven2)
-- npm (registry: https://www.npmjs.com/)
-- NuGet (registry: https://www.nuget.org/)
-- pip (registry: https://pypi.org/){% ifversion dependency-graph-dart-support %}
-- pub (registry: https://pub.dev/packages/registry){% endif %}
-- RubyGems (registry: https://rubygems.org/)
-- Rust (registry: https://crates.io/)
-
-If you have a suggestion for a new ecosystem we should support, please open an [issue](https://github.com/github/advisory-database/issues) for discussion.
-
-If you enable {% data variables.product.prodname_dependabot_alerts %} for your repositories, you are automatically notified when a new {% data variables.product.company_short %}-reviewed advisory reports a vulnerability {% ifversion GH-advisory-db-supports-malware %}or malware{% endif %} for a package you depend on. For more information, see "[About {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)."
-
-### Unreviewed advisories
-
-Unreviewed advisories are security vulnerabilites that we publish automatically into the {% data variables.product.prodname_advisory_database %}, directly from the National Vulnerability Database feed. 
-
-{% data variables.product.prodname_dependabot %} doesn't create {% data variables.product.prodname_dependabot_alerts %} for unreviewed advisories as this type of advisory isn't checked for validity or completion.
-
-## About information in security advisories
-
-Each security advisory contains information about the vulnerability{% ifversion GH-advisory-db-supports-malware %} or malware,{% endif %} which may include the description, severity, affected package, package ecosystem, affected versions and patched versions, impact, and optional information such as references, workarounds, and credits. In addition, advisories from the National Vulnerability Database list contain a link to the CVE record, where you can read more details about the vulnerability, its CVSS scores, and its qualitative severity level. For more information, see the "[National Vulnerability Database](https://nvd.nist.gov/)" from the National Institute of Standards and Technology.
-
-The severity level is one of four possible levels defined in the "[Common Vulnerability Scoring System (CVSS), Section 5](https://www.first.org/cvss/specification-document)."
-- Low
-- Medium/Moderate
-- High
-- Critical
-
-The {% data variables.product.prodname_advisory_database %} uses the CVSS levels described above. If {% data variables.product.company_short %} obtains a CVE, the {% data variables.product.prodname_advisory_database %} uses CVSS version 3.1. If the CVE is imported, the {% data variables.product.prodname_advisory_database %} supports both CVSS versions 3.0 and 3.1.
-
-{% data reusables.repositories.github-security-lab %}
-
-## Accessing an advisory in the {% data variables.product.prodname_advisory_database %}
-
-1. Navigate to https://github.com/advisories.
-2. Optionally, to filter the list, use any of the drop-down menus.
-  ![Dropdown filters](/assets/images/help/security/advisory-database-dropdown-filters.png)
-   {% tip %}
-
-   **Tip:** You can use the sidebar on the left to explore  {% data variables.product.company_short %}-reviewed and unreviewed advisories separately.
-
-   {% endtip %}
-3. Click an advisory to view details. By default, you will see {% data variables.product.company_short %}-reviewed advisories for security vulnerabilities. {% ifversion GH-advisory-db-supports-malware %}To show malware advisories, use `type:malware` in the search bar.{% endif %}
-
-
-{% note %}
-
-The database is also accessible using the GraphQL API. {% ifversion GH-advisory-db-supports-malware %}By default, queries will return {% data variables.product.company_short %}-reviewed advisories for security vulnerabilities unless you specify `type:malware`.{% endif %} For more information, see the "[`security_advisory` webhook event](/webhooks/event-payloads/#security_advisory)."
-
-{% endnote %}
-
-## Editing an advisory in the {% data variables.product.prodname_advisory_database %}
-You can suggest improvements to any advisory in the {% data variables.product.prodname_advisory_database %}. For more information, see "[Editing security advisories in the {% data variables.product.prodname_advisory_database %}](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/editing-security-advisories-in-the-github-advisory-database)."
-
-## Searching the {% data variables.product.prodname_advisory_database %}
-
-You can search the database, and use qualifiers to narrow your search. For example, you can search for advisories created on a certain date, in a specific ecosystem, or in a particular library.
-
-{% data reusables.time_date.date_format %} {% data reusables.time_date.time_format %}
-
-{% data reusables.search.date_gt_lt %}
-
-| Qualifier  | Example |
-| ------------- | ------------- |
-| `type:reviewed`| [**type:reviewed**](https://github.com/advisories?query=type%3Areviewed) will show {% data variables.product.company_short %}-reviewed advisories for security vulnerabilities. |
-{% ifversion GH-advisory-db-supports-malware %}| `type:malware` | [**type:malware**](https://github.com/advisories?query=type%3Amalware) will show {% data variables.product.company_short %}-reviewed advisories for malware. |
-{% endif %}| `type:unreviewed`| [**type:unreviewed**](https://github.com/advisories?query=type%3Aunreviewed) will show unreviewed advisories. |
-| `GHSA-ID`| [**GHSA-49wp-qq6x-g2rf**](https://github.com/advisories?query=GHSA-49wp-qq6x-g2rf) will show the advisory with this {% data variables.product.prodname_advisory_database %} ID. |
-| `CVE-ID`| [**CVE-2020-28482**](https://github.com/advisories?query=CVE-2020-28482) will show the advisory with this CVE ID number. |
-| `ecosystem:ECOSYSTEM`| [**ecosystem:npm**](https://github.com/advisories?utf8=%E2%9C%93&query=ecosystem%3Anpm) will show only advisories affecting NPM packages. |
-| `severity:LEVEL`| [**severity:high**](https://github.com/advisories?utf8=%E2%9C%93&query=severity%3Ahigh) will show only advisories with a high severity level. |
-| `affects:LIBRARY`| [**affects:lodash**](https://github.com/advisories?utf8=%E2%9C%93&query=affects%3Alodash) will show only advisories affecting the lodash library. |
-| `cwe:ID`| [**cwe:352**](https://github.com/advisories?query=cwe%3A352) will show only advisories with this CWE number. |
-| `credit:USERNAME`| [**credit:octocat**](https://github.com/advisories?query=credit%3Aoctocat) will show only advisories credited to the "octocat" user account. |
-| `sort:created-asc`| [**sort:created-asc**](https://github.com/advisories?utf8=%E2%9C%93&query=sort%3Acreated-asc) will sort by the oldest advisories first. |
-| `sort:created-desc`| [**sort:created-desc**](https://github.com/advisories?utf8=%E2%9C%93&query=sort%3Acreated-desc) will sort by the newest advisories first. |
-| `sort:updated-asc`| [**sort:updated-asc**](https://github.com/advisories?utf8=%E2%9C%93&query=sort%3Aupdated-asc) will sort by the least recently updated first. |
-| `sort:updated-desc`| [**sort:updated-desc**](https://github.com/advisories?utf8=%E2%9C%93&query=sort%3Aupdated-desc) will sort by the most recently updated first. |
-| `is:withdrawn`| [**is:withdrawn**](https://github.com/advisories?utf8=%E2%9C%93&query=is%3Awithdrawn) will show only advisories that have been withdrawn. |
-| `created:YYYY-MM-DD`| [**created:2021-01-13**](https://github.com/advisories?utf8=%E2%9C%93&query=created%3A2021-01-13) will show only advisories created on this date. |
-| `updated:YYYY-MM-DD`| [**updated:2021-01-13**](https://github.com/advisories?utf8=%E2%9C%93&query=updated%3A2021-01-13) will show only advisories updated on this date. |
-
-## Viewing your vulnerable repositories
-
-For any {% data variables.product.company_short %}-reviewed advisory in the {% data variables.product.prodname_advisory_database %}, you can see which of your repositories are affected by that security vulnerability{% ifversion GH-advisory-db-supports-malware %} or malware{% endif %}. To see a vulnerable repository, you must have access to {% data variables.product.prodname_dependabot_alerts %} for that repository. For more information, see "[About {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies#access-to-dependabot-alerts)."
-
-1. Navigate to https://github.com/advisories.
-2. Click an advisory.
-3. At the top of the advisory page, click **Dependabot alerts**.
-   ![Dependabot alerts](/assets/images/help/security/advisory-database-dependabot-alerts.png)
-4. Optionally, to filter the list, use the search bar or the drop-down menus. The "Organization" drop-down menu allows you to filter the {% data variables.product.prodname_dependabot_alerts %} per owner (organization or user).
-   ![Search bar and drop-down menus to filter alerts](/assets/images/help/security/advisory-database-dependabot-alerts-filters.png)
-5. For more details about the advisory, and for advice on how to fix the vulnerable repository, click the repository name.
-
-{% ifversion security-advisories-ghes-ghae %}
-## Accessing the local advisory database on {% data variables.location.product_location %}
-
-If your site administrator has enabled {% data variables.product.prodname_github_connect %} for {% data variables.location.product_location %}, you can also browse reviewed advisories locally. For more information, see "[About {% data variables.product.prodname_github_connect %}](/admin/configuration/configuring-github-connect/about-github-connect)".
-
-You can use your local advisory database to check whether a specific security vulnerability is included, and therefore whether you'd get alerts for vulnerable dependencies. You can also view any vulnerable repositories. 
-
-1. Navigate to `https://HOSTNAME/advisories`.
-2. Optionally, to filter the list, use any of the drop-down menus.
-  ![Dropdown filters](/assets/images/help/security/advisory-database-dropdown-filters.png)
-   {% note %}
-
-   **Note:** Only reviewed advisories will be listed. Unreviewed advisories can be viewed in the {% data variables.product.prodname_advisory_database %} on {% data variables.product.prodname_dotcom_the_website %}. For more information, see "[Accessing an advisory in the GitHub Advisory Database](#accessing-an-advisory-in-the-github-advisory-database)". 
-
-   {% endnote %}
-3. Click an advisory to view details.{% ifversion GH-advisory-db-supports-malware %} By default, you will see {% data variables.product.company_short %}-reviewed advisories for security vulnerabilities. To show malware advisories, use `type:malware` in the search bar.{% endif %}
-
-You can also suggest improvements to any advisory directly from your local advisory database. For more information, see "[Editing advisories from {% data variables.location.product_location %}](/code-security/dependabot/dependabot-alerts/editing-security-advisories-in-the-github-advisory-database#editing-advisories-from-your-github-enterprise-server-instance)".
-
-### Viewing vulnerable repositories for {% data variables.location.product_location %}
-
-{% data reusables.repositories.enable-security-alerts %}
-
-In the local advisory database, you can see which repositories are affected by each security vulnerability{% ifversion GH-advisory-db-supports-malware %} or malware{% endif %}. To see a vulnerable repository, you must have access to {% data variables.product.prodname_dependabot_alerts %} for that repository. For more information, see "[About {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies#access-to-dependabot-alerts)."
-
-1. Navigate to `https://HOSTNAME/advisories`.
-2. Click an advisory.
-3. At the top of the advisory page, click **Dependabot alerts**.
-   ![Dependabot alerts](/assets/images/help/security/advisory-database-dependabot-alerts.png)
-4. Optionally, to filter the list, use the search bar or the drop-down menus. The "Organization" drop-down menu allows you to filter the {% data variables.product.prodname_dependabot_alerts %} per owner (organization or user).
-   ![Search bar and drop-down menus to filter alerts](/assets/images/help/security/advisory-database-dependabot-alerts-filters.png)
-5. For more details about the advisory, and for advice on how to fix the vulnerable repository, click the repository name.
-
-{% endif %}
-
-## Further reading
-
-- MITRE's [definition of "vulnerability"](https://www.cve.org/ResourcesSupport/Glossary#vulnerability)
diff --git a/translations/pt-BR/content/code-security/dependabot/dependabot-alerts/index.md b/translations/pt-BR/content/code-security/dependabot/dependabot-alerts/index.md
index 8448bd2665..49ffd87e44 100644
--- a/translations/pt-BR/content/code-security/dependabot/dependabot-alerts/index.md
+++ b/translations/pt-BR/content/code-security/dependabot/dependabot-alerts/index.md
@@ -15,8 +15,6 @@ topics:
   - Repositories
   - Dependencies
 children:
-  - /browsing-security-advisories-in-the-github-advisory-database
-  - /editing-security-advisories-in-the-github-advisory-database
   - /about-dependabot-alerts
   - /configuring-dependabot-alerts
   - /viewing-and-updating-dependabot-alerts
diff --git a/translations/pt-BR/content/code-security/getting-started/adding-a-security-policy-to-your-repository.md b/translations/pt-BR/content/code-security/getting-started/adding-a-security-policy-to-your-repository.md
index dc8156e6bb..9c14fe91d4 100644
--- a/translations/pt-BR/content/code-security/getting-started/adding-a-security-policy-to-your-repository.md
+++ b/translations/pt-BR/content/code-security/getting-started/adding-a-security-policy-to-your-repository.md
@@ -1,6 +1,6 @@
 ---
-title: Adicionar uma política de segurança a um repositório
-intro: 'Você pode dar instruções sobre como relatar uma vulnerabilidade de segurança no seu projeto, adicionando uma política de segurança ao seu repositório.'
+title: Adding a security policy to your repository
+intro: You can give instructions for how to report a security vulnerability in your project by adding a security policy to your repository.
 redirect_from:
   - /articles/adding-a-security-policy-to-your-repository
   - /github/managing-security-vulnerabilities/adding-a-security-policy-to-your-repository
@@ -17,47 +17,49 @@ topics:
   - Repositories
   - Health
 shortTitle: Add a security policy
-ms.openlocfilehash: f081d6e6bd99f604e7e86bc094f76de9041adf4b
-ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
-ms.translationtype: HT
-ms.contentlocale: pt-BR
-ms.lasthandoff: 09/10/2022
-ms.locfileid: '145083360'
 ---
-## Sobre políticas de segurança
 
-Para fornecer instruções às pessoas para relatar vulnerabilidades de segurança no seu projeto,{% ifversion fpt or ghes or ghec %} você pode adicionar um arquivo _SECURITY.md_ à raiz do repositório, a `docs` ou à pasta `.github`.{% else %} você pode adicionar um arquivo _SECURITY.md_ à raiz do repositório ou à pasta `docs`.{% endif %} Quando alguém criar um problema no seu repositório, ele verá um link para a política de segurança do projeto.
+## About security policies
+
+To give people instructions for reporting security vulnerabilities in your project,{% ifversion fpt or ghes or ghec %} you can add a _SECURITY.md_ file to your repository's root, `docs`, or `.github` folder.{% else %} you can add a _SECURITY.md_ file to your repository's root, or `docs` folder.{% endif %} When someone creates an issue in your repository, they will see a link to your project's security policy.
 
 {% ifversion not ghae %}
 <!-- no public repos in GHAE -->
-Você pode criar uma política de segurança padrão para sua organização ou conta pessoal. Para obter mais informações, confira "[Como criar 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 for your organization or personal account. For more information, see "[Creating a default community health file](/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file)."
 {% endif %}
 
 {% tip %}
 
-**Dica:** para ajudar as pessoas a encontrar sua política de segurança, crie um link para o arquivo _SECURITY.md_ de outros locais no repositório, como o arquivo LEIAME. Para obter mais informações, confira "[Sobre os arquivos LEIAME](/articles/about-readmes)".
+**Tip:** To help people find your security policy, you can link to your _SECURITY.md_ file from other places in your repository, such as your README file. For more information, see "[About READMEs](/articles/about-readmes)."
 
 {% endtip %}
 
-{% ifversion fpt or ghec %} Depois que alguém relatar uma vulnerabilidade de segurança no seu projeto, use as {% data variables.product.prodname_security_advisories %} para divulgar, corrigir e publicar informações sobre a vulnerabilidade. Para obter mais informações sobre o processo de relatório e divulgação de vulnerabilidades no {% data variables.product.prodname_dotcom %}, confira "[Sobre a divulgação coordenada de vulnerabilidades de segurança](/code-security/security-advisories/about-coordinated-disclosure-of-security-vulnerabilities#about-reporting-and-disclosing-vulnerabilities-in-projects-on-github)". Para obter mais informações sobre as {% data variables.product.prodname_security_advisories %}, confira "[Sobre as {% data variables.product.prodname_security_advisories %}](/github/managing-security-vulnerabilities/about-github-security-advisories)".
+{% ifversion fpt or ghec %}
+After someone reports a security vulnerability in your project, you can use {% data variables.product.prodname_security_advisories %} to disclose, fix, and publish information about the vulnerability. For more information about the process of reporting and disclosing vulnerabilities in {% data variables.product.prodname_dotcom %}, see "[About coordinated disclosure of security vulnerabilities](/code-security/security-advisories/about-coordinated-disclosure-of-security-vulnerabilities#about-reporting-and-disclosing-vulnerabilities-in-projects-on-github)." For more information about repository security advisories, see "[About repository security advisories](/github/managing-security-vulnerabilities/about-github-security-advisories)."
 
-{% data reusables.repositories.github-security-lab %} {% endif %} {% ifversion ghes or ghae %}
+{% data reusables.repositories.github-security-lab %}
+{% endif %}
+{% ifversion ghes or ghae %}
 <!-- alternative to the content about GitHub Security Advisories in the dotcom article -->
-Ao disponibilizar claramente instruções de relatório de segurança, você torna mais fácil para os usuários relatar quaisquer vulnerabilidades de segurança que encontrem no repositório usando seu canal de comunicação preferido.
+By making security reporting instructions clearly available, you make it easy for your users to report any security vulnerabilities they find in your repository using your preferred communication channel.
 {% endif %}
 
-## Adicionar uma política de segurança a um repositório
+## Adding a security policy to your repository
 
-{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %}
-3. Na barra lateral esquerda, clique em **Política de segurança**.
-  ![Guia Política de segurança](/assets/images/help/security/security-policy-tab.png)
-4. Clique em **Iniciar instalação**.
-  ![Botão Iniciar configuração](/assets/images/help/security/start-setup-security-policy-button.png)
-5. No novo arquivo _SECURITY.md_, adicione informações sobre as versões compatíveis com seu projeto e como relatar uma vulnerabilidade.
-{% data reusables.files.write_commit_message %} {% data reusables.files.choose-commit-email %} {% data reusables.files.choose_commit_branch %} {% data reusables.files.propose_file_change %}
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.sidebar-security %}
+3. In the left sidebar, click **Security policy**.
+  ![Security policy tab](/assets/images/help/security/security-policy-tab.png)
+4. Click **Start setup**.
+  ![Start setup button](/assets/images/help/security/start-setup-security-policy-button.png)
+5. In the new _SECURITY.md_ file, add information about supported versions of your project and how to report a vulnerability.
+{% data reusables.files.write_commit_message %}
+{% data reusables.files.choose-commit-email %}
+{% data reusables.files.choose_commit_branch %}
+{% data reusables.files.propose_file_change %}
 
-## Leitura adicional
+## Further reading
 
-- "[Como proteger seu repositório](/code-security/getting-started/securing-your-repository)"{% ifversion not ghae %}
-- "[Como configurar seu projeto para contribuições úteis](/communities/setting-up-your-project-for-healthy-contributions)"{% endif %}{% ifversion fpt or ghec %}
+- "[Securing your repository](/code-security/getting-started/securing-your-repository)"{% ifversion not ghae %}
+- "[Setting up your project for healthy contributions](/communities/setting-up-your-project-for-healthy-contributions)"{% endif %}{% ifversion fpt or ghec %}
 - [{% data variables.product.prodname_security %}]({% data variables.product.prodname_security_link %}){% endif %}
diff --git a/translations/pt-BR/content/code-security/getting-started/github-security-features.md b/translations/pt-BR/content/code-security/getting-started/github-security-features.md
index fe09160461..081272149c 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
@@ -28,7 +28,7 @@ Make it easy for your users to confidentially report security vulnerabilities th
 {% ifversion fpt or ghec %}
 ### Security advisories
 
-Privately discuss and fix security vulnerabilities in your repository's code. You can then publish a security advisory to alert your community to the vulnerability and encourage community members to upgrade. For more information, see "[About {% data variables.product.prodname_security_advisories %}](/github/managing-security-vulnerabilities/about-github-security-advisories)."
+Privately discuss and fix security vulnerabilities in your repository's code. You can then publish a security advisory to alert your community to the vulnerability and encourage community members to upgrade. For more information, see "[About repository security advisories](/github/managing-security-vulnerabilities/about-github-security-advisories)."
 
 {% endif %}
 {% ifversion fpt or ghec or ghes %}
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 f30c86cc01..63cff8ac9b 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
@@ -125,7 +125,7 @@ For more information, see "[Managing security and analysis settings for your org
 ## 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 {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts),"{% endif %} {% ifversion fpt or ghec or ghes %}"[Managing pull requests for dependency updates](/code-security/supply-chain-security/managing-pull-requests-for-dependency-updates)," {% endif %}"[Managing {% data variables.product.prodname_code_scanning %} for your repository](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository)," and "[Managing alerts from {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/managing-alerts-from-secret-scanning)."
 
-{% ifversion fpt or ghec %}If you have a security vulnerability, you can create a security advisory to privately discuss and fix the vulnerability. For more information, see "[About {% data variables.product.prodname_security_advisories %}](/code-security/security-advisories/about-github-security-advisories)" and "[Creating a security advisory](/code-security/security-advisories/creating-a-security-advisory)."
+{% 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 repository security advisories](/code-security/security-advisories/about-github-security-advisories)" and "[Creating a security advisory](/code-security/security-advisories/creating-a-security-advisory)."
 {% endif %}
 
 {% ifversion ghes or ghec or ghae %}You{% elsif fpt %}Organizations that use {% data variables.product.prodname_ghe_cloud %}{% endif %} can view, filter, and sort security alerts for repositories owned by {% ifversion ghes or ghec or ghae %}your{% elsif fpt %}their{% endif %} organization in the security overview. For more information, see{% ifversion ghes or ghec or ghae %} "[About the security overview](/code-security/security-overview/about-the-security-overview)."{% elsif fpt %} "[About the security overview](/enterprise-cloud@latest/code-security/security-overview/about-the-security-overview)" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% 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 59b241eefe..3e84f7c163 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
@@ -133,5 +133,5 @@ You can set up {% data variables.product.prodname_code_scanning %} to automatica
 ## 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 {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts),"{% endif %} {% ifversion fpt or ghec or ghes %}"[Managing pull requests for dependency updates](/code-security/supply-chain-security/managing-pull-requests-for-dependency-updates)," {% endif %}"[Managing {% data variables.product.prodname_code_scanning %} for your repository](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository)," and "[Managing alerts from {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/managing-alerts-from-secret-scanning)."
 
-{% ifversion fpt or ghec %}If you have a security vulnerability, you can create a security advisory to privately discuss and fix the vulnerability. For more information, see "[About {% data variables.product.prodname_security_advisories %}](/code-security/security-advisories/about-github-security-advisories)" and "[Creating a security advisory](/code-security/security-advisories/creating-a-security-advisory)."
+{% 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 repository 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/index.md b/translations/pt-BR/content/code-security/index.md
index a86c22e406..e9d02c2953 100644
--- a/translations/pt-BR/content/code-security/index.md
+++ b/translations/pt-BR/content/code-security/index.md
@@ -1,7 +1,7 @@
 ---
-title: Segurança do código
+title: Code security
 shortTitle: Code security
-intro: 'Crie segurança no seu fluxo de trabalho de {% data variables.product.prodname_dotcom %} com recursos para manter segredos e vulnerabilidades fora da base de código{% ifversion not ghae %} e para manter a sua cadeia de suprimentos de software{% endif %}.'
+intro: 'Build security into your {% data variables.product.prodname_dotcom %} workflow with features to keep secrets and vulnerabilities out of your codebase{% ifversion not ghae %}, and to maintain your software supply chain{% endif %}.'
 introLinks:
   overview: /code-security/getting-started/github-security-features
 featuredLinks:
@@ -53,16 +53,10 @@ children:
   - /adopting-github-advanced-security-at-scale
   - /secret-scanning
   - /code-scanning
-  - /repository-security-advisories
+  - /security-advisories
   - /supply-chain-security
   - /dependabot
   - /security-overview
   - /guides
-ms.openlocfilehash: 90d3ad046a6531849edd8e783db265866f118d90
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
-ms.translationtype: HT
-ms.contentlocale: pt-BR
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147145236'
 ---
 
diff --git a/translations/pt-BR/content/code-security/repository-security-advisories/about-coordinated-disclosure-of-security-vulnerabilities.md b/translations/pt-BR/content/code-security/repository-security-advisories/about-coordinated-disclosure-of-security-vulnerabilities.md
deleted file mode 100644
index aa94f1b931..0000000000
--- a/translations/pt-BR/content/code-security/repository-security-advisories/about-coordinated-disclosure-of-security-vulnerabilities.md
+++ /dev/null
@@ -1,76 +0,0 @@
----
-title: Sobre a divulgação coordenada de vulnerabilidades de segurança
-intro: A divulgação das vulnerabilidades é um esforço coordenado entre os relatores de segurança e os mantenedores de repositório.
-redirect_from:
-  - /code-security/security-advisories/about-coordinated-disclosure-of-security-vulnerabilities
-miniTocMaxHeadingLevel: 3
-versions:
-  fpt: '*'
-  ghec: '*'
-type: overview
-topics:
-  - Security advisories
-  - Vulnerabilities
-shortTitle: Coordinated disclosure
-ms.openlocfilehash: a5d4445525b46536cbfd3301cccb78140589de22
-ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
-ms.translationtype: HT
-ms.contentlocale: pt-BR
-ms.lasthandoff: 09/11/2022
-ms.locfileid: '145083343'
----
-## Sobre a divulgação de vulnerabilidades no setor
-
-{% data reusables.security-advisory.disclosing-vulnerabilities %}
-
-O relatório inicial de uma vulnerabilidade é tornado privado, e os detalhes completos só são publicados depois de o mantenedor reconhecer o problema e, idealmente, são disponibilizadas soluções ou atualizações, às vezes com um atraso para dar mais tempo para a instalação das atualizações. Para obter mais informações, confira a "[Folha de referências do OWASP sobre a divulgação de vulnerabilidades](https://cheatsheetseries.owasp.org/cheatsheets/Vulnerability_Disclosure_Cheat_Sheet.html#commercial-and-open-source-software)" no site OWASP Cheat Sheet Series.
-
-### Práticas recomendadas para relatores de vulnerabilidade
-
-É uma prática recomendada relatar de forma privada vulnerabilidades para os mantenedores. Quando possível, como um relator de vulnerabilidades, recomendamos que você evite:
-- Divulgar a vulnerabilidade publicamente sem dar aos mantenedores a oportunidade de remediar.
-- Ignorar os mantenedores.
-- Divulgar a vulnerabilidade antes de uma versão fixa do código estar disponível.
-- Esperar ser compensado por relatar um problema, quando não há nenhum programa de recompensa pública.
-
-É aceitável para os relatores de vulnerabilidade revelar uma vulnerabilidade publicamente após um período de tempo, se eles tentaram entrar em contato com os mantenedores e não receberem uma resposta, ou caso tenha entrado em contato com eles e solicitado para esperar muito tempo para divulgá-lo. 
-
-Recomendamos que os relatores de vulnerabilidade indiquem claramente os termos da sua política de divulgação como parte do seu processo de relatório. Mesmo que o relator de vulnerabilidade não adira a uma política rigorosa, é bom estabelecer expectativas claras para os mantenedores em termos de cronogramas sobre divulgações de vulnerabilidades intencionais. Para ver um exemplo de política de divulgação, confira a "[política de divulgação do Security Lab](https://securitylab.github.com/advisories#policy)" no site do GitHub Security Lab.
-
-### Práticas recomendadas para mantenedores
-
-Como mantenedor, considera-se uma prática recomendada indicar claramente como e onde você deseja receber relatórios de vulnerabilidades. Se essas informações não estiverem claramente disponíveis, os relatores de vulnerabilidade não saberão como entrar em contato com você, e poderão recorrer à extração de endereços de e-mail do desenvolvedor a partir do histórico de commit do git para tentar encontrar um contato de segurança apropriado. Isso pode gerar atritos, relatórios perdidos ou publicação de relatórios não resolvidos.
-
-Os mantenedores devem divulgar as vulnerabilidades em tempo oportuno. Se houver uma vulnerabilidade de segurança no seu repositório, recomendamos que você:
-- Trate a vulnerabilidade como um problema de segurança em vez de um erro simples, tanto na sua resposta quanto na sua divulgação. Por exemplo, você deverá mencionar explicitamente que o problema é uma vulnerabilidade de segurança nas observações da versão.
-- Reconhecer o recebimento do relatório de vulnerabilidade o mais rapidamente possível, mesmo que recursos imediatos não estejam disponíveis para investigação. Isso envia a mensagem de que você está rapidamente para responder e agir e define um tom positivo para o resto da interação entre você e o relator da vulnerabilidade.
-- Envolva o relator da vulnerabilidade após verificar o impacto e a veracidade do relatório. É provável que o relator da vulnerabilidade já tenha gasto tempo considerando a vulnerabilidade em uma série de cenários. alguns dos quais você pode não ter se considerado.
-- Remedeie o problema de uma forma que você considere adequada, considerando, de forma ponderada, as preocupações e conselhos fornecidos pelo relator de vulnerabilidade. Muitas vezes, o relator da vulnerabilidade tem conhecimento de certos casos extremos e correções desviadas que são fáceis de perder sem uma pesquisa de segurança em segundo plano.
-- Sempre reconheça o relator da vulnerabilidade quando você der crédito para a descoberta.
-- Busque publicar uma correção assim que puder.
-- Certifique-se de que você conscientize o ecossistema mais amplo sobre o problema e sua correção quando você publicar a vulnerabilidade. Não é incomum ver casos em que um problema de segurança reconhecido é corrigido no branch de desenvolvimento atual de um projeto. mas o commit ou versão posterior não é explicitamente marcado como uma correção ou versão de segurança. Isso pode causar problemas para consumidores em níveis inferiores.
-
-Publicar os detalhes de uma vulnerabilidade de segurança não faz com que os mantenedores pareçam ruins. As vulnerabilidades de segurança estão presentes em todos os lugares no software, e os usuários confiarão nos mantenedores que têm um processo claro e estabelecido para divulgar as vulnerabilidades de segurança no seu código.
-
-## Sobre relatar e publicar vulnerabilidades em projetos em {% data variables.product.prodname_dotcom %}
-
-O processo de relatório e divulgação de vulnerabilidades para projetos em {% data variables.product.prodname_dotcom_the_website %} é o seguinte:
-
- Se você é um relator de vulnerabilidades (por exemplo, um pesquisador de segurança) que gostaria de relatar uma vulnerabilidade, primeiro verifique se existe uma política de segurança para o repositório relacionado. Para obter mais informações, confira "[Sobre as políticas de segurança](/code-security/getting-started/adding-a-security-policy-to-your-repository#about-security-policies)". Se houver uma, siga-a para entender o processo antes de entrar em contato com a equipe de segurança do repositório. 
- 
- Se não houver uma política de segurança, a forma mais eficiente de estabelecer um meio privado de comunicação com os mantenedores é criar uma problema, solicitando um contato de segurança preferido. Vale a pena notar que o problema será imediatamente visível ao público. Portanto, não deve incluir nenhuma informação sobre o erro. Quando a comunicação for estabelecida, você poderá sugerir que os mantenedores definam uma política de segurança para uso futuro.
-
-{% note %}
-
-**Observação**: _somente para o npm_ – Se recebermos uma denúncia de malware em um pacote npm, tentaremos entrar em contato com você em particular. Se você não resolver o problema em tempo, iremos divulgá-lo. Para obter mais informações, confira "[Como denunciar malware em um pacote npm](https://docs.npmjs.com/reporting-malware-in-an-npm-package)" no site do npm Docs.
-
-{% endnote %}
-
- Se você encontrou uma vulnerabilidade de segurança em {% data variables.product.prodname_dotcom_the_website %}, informe a vulnerabilidade por meio de nosso processo de divulgação coordenada. Para obter mais informações, confira o site [{% data variables.product.prodname_dotcom %} Security Bug Bounty](https://bounty.github.com/).
-
- Se for mantenedor, você poderá assumir a propriedade do processo no início do pipeline, configurando uma política de segurança para o seu repositório, ou disponibilizando as instruções de relatórios de segurança de forma clara, por exemplo, no arquivo LEIAME do seu projeto. Para obter informações sobre como adicionar uma política de segurança, confira "[Sobre as políticas de segurança](/code-security/getting-started/adding-a-security-policy-to-your-repository#about-security-policies)". Se não houver política de segurança, é provável que um relator de vulnerabilidade tente enviar um e-mail para você ou entrar em contato com você de forma privada. Como alternativa, alguém pode abrir um problema (público) com detalhes de um problema de segurança.
-
- Como mantenedor, para divulgar uma vulnerabilidade no seu código, você primeiro cria um rascunho de uma consultoria de segurança no repositório do pacote em {% data variables.product.prodname_dotcom %}. {% data reusables.security-advisory.security-advisory-overview %} Para obter mais informações, confira "[Sobre os {% data variables.product.prodname_security_advisories %} para repositórios](/code-security/repository-security-advisories/about-github-security-advisories-for-repositories)".
-
-
- Para começar, confira "[Como criar um aviso de segurança de repositório](/code-security/repository-security-advisories/creating-a-repository-security-advisory)".
diff --git a/translations/pt-BR/content/code-security/repository-security-advisories/about-github-security-advisories-for-repositories.md b/translations/pt-BR/content/code-security/repository-security-advisories/about-github-security-advisories-for-repositories.md
deleted file mode 100644
index 63ac43b57c..0000000000
--- a/translations/pt-BR/content/code-security/repository-security-advisories/about-github-security-advisories-for-repositories.md
+++ /dev/null
@@ -1,66 +0,0 @@
----
-title: Sobre as Consultorias de Segurança do GitHub para repositórios
-intro: 'Você pode usar o {% data variables.product.prodname_security_advisories %} para discutir, corrigir e publicar informações sobre vulnerabilidades de segurança no seu repositório.'
-redirect_from:
-  - /articles/about-maintainer-security-advisories
-  - /github/managing-security-vulnerabilities/about-maintainer-security-advisories
-  - /github/managing-security-vulnerabilities/about-github-security-advisories
-  - /code-security/security-advisories/about-github-security-advisories
-versions:
-  fpt: '*'
-  ghec: '*'
-type: overview
-topics:
-  - Security advisories
-  - Vulnerabilities
-  - CVEs
-shortTitle: Repository security advisories
-ms.openlocfilehash: 5c8ad99a2bee30f52a185fa15421bc6b23429fbf
-ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
-ms.translationtype: HT
-ms.contentlocale: pt-BR
-ms.lasthandoff: 09/10/2022
-ms.locfileid: '145083342'
----
-{% data reusables.repositories.security-advisory-admin-permissions %}
-
-{% data reusables.security-advisory.security-researcher-cannot-create-advisory %}
-
-## Sobre os {% data variables.product.prodname_security_advisories %}
-
-{% data reusables.security-advisory.disclosing-vulnerabilities %} Para obter mais informações, confira "[Sobre a divulgação coordenada de vulnerabilidades de segurança](/code-security/repository-security-advisories/about-coordinated-disclosure-of-security-vulnerabilities)".
-
-{% data reusables.security-advisory.security-advisory-overview %}
-
-Com {% data variables.product.prodname_security_advisories %}, você pode:
-
-1. Criar um aviso de segurança rascunho e usar o rascunho para discutir em particular o impacto da vulnerabilidade no seu projeto. Para obter mais informações, confira "[Como criar um aviso de segurança do repositório](/code-security/repository-security-advisories/creating-a-repository-security-advisory)".
-2. Colaborar de modo particular com a correção da vulnerabilidade em uma bifurcação privada temporária.
-3. Publique a consultoria de segurança para alertar a sua comunidade sobre a vulnerabilidade depois que um patch for lançado. Para obter mais informações, confira "[Como publicar um aviso de segurança do repositório](/code-security/repository-security-advisories/publishing-a-repository-security-advisory)".
-
-{% data reusables.repositories.security-advisories-republishing %}
-
-Você pode dar crédito a indivíduos que contribuíram para um aviso de segurança. Para obter mais informações, confira "[Como editar uma consultoria de segurança do repositório](/code-security/repository-security-advisories/editing-a-repository-security-advisory#about-credits-for-security-advisories)".
-
-{% data reusables.repositories.security-guidelines %}
-
-Se você criou uma consultoria de segurança no seu repositório, o consultório de segurança permanecerá no seu repositório. Publicamos avisos de segurança para qualquer um dos ecossistemas compatíveis com o grafo de dependência no {% data variables.product.prodname_advisory_database %} em [github.com/advisories](https://github.com/advisories). Qualquer um pode enviar uma alteração para um consultor publicado em {% data variables.product.prodname_advisory_database %}. Para obter mais informações, confira "[Como editar avisos de segurança no {% data variables.product.prodname_advisory_database %}](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/editing-security-advisories-in-the-github-advisory-database)".
-
-Se uma consultoria de segurança for especificamente para o npm, nós também publicamos a consultoria nas consultorias de segurança do npm. Para obter mais informações, confira [npmjs.com/advisories](https://www.npmjs.com/advisories).
-
-{% data reusables.repositories.github-security-lab %}
-
-## Números de identificação CVE
-
-{% data variables.product.prodname_security_advisories %} baseia-se na base da lista de Vulnerabilidades e Exposições Comuns (CVE). O formulário de consultoria de segurança em {% data variables.product.prodname_dotcom %} é um formulário padronizado que corresponde ao formato de descrição CVE. 
-
-{% data variables.product.prodname_dotcom %} é uma Autoridade de Numeração CVE (CNA) e está autorizada a atribuir números de identificação CVE. Para obter mais informações, confira "[Sobre o CVE](https://www.cve.org/About/Overview)" e "[Autoridades de Numeração do CVE](https://www.cve.org/ProgramOrganization/CNAs)" no site do CVE.
-
-Ao criar um aviso de segurança para um repositório público no {% data variables.product.prodname_dotcom %}, você tem a opção de fornecer um número de identificação CVE existente para a vulnerabilidade de segurança. {% data reusables.repositories.request-security-advisory-cve-id %}
-
-Uma que você publicou a consultoria de segurança e o {% data variables.product.prodname_dotcom %} atribuiu um número de identificação CVE para a vulnerabilidade, o {% data variables.product.prodname_dotcom %} irá publicar o CVE no banco de dados do MITRE.
-Para obter mais informações, confira "[Como publicar um aviso de segurança do repositório](/code-security/repository-security-advisories/publishing-a-repository-security-advisory)".
-
-## {% data variables.product.prodname_dependabot_alerts %} para consultorias de segurança publicadas
-
-{% data reusables.repositories.github-reviews-security-advisories %}
diff --git a/translations/pt-BR/content/code-security/repository-security-advisories/adding-a-collaborator-to-a-repository-security-advisory.md b/translations/pt-BR/content/code-security/repository-security-advisories/adding-a-collaborator-to-a-repository-security-advisory.md
deleted file mode 100644
index 8a46c03bd8..0000000000
--- a/translations/pt-BR/content/code-security/repository-security-advisories/adding-a-collaborator-to-a-repository-security-advisory.md
+++ /dev/null
@@ -1,50 +0,0 @@
----
-title: Adicionando um colaborador a uma consultoria de segurança de repositório
-intro: É possível adicionar outros usuários ou equipes para colaborar em uma consultoria de segurança com você.
-redirect_from:
-  - /articles/adding-a-collaborator-to-a-maintainer-security-advisory
-  - /github/managing-security-vulnerabilities/adding-a-collaborator-to-a-maintainer-security-advisory
-  - /github/managing-security-vulnerabilities/adding-a-collaborator-to-a-security-advisory
-  - /code-security/security-advisories/adding-a-collaborator-to-a-security-advisory
-versions:
-  fpt: '*'
-  ghec: '*'
-type: how_to
-topics:
-  - Security advisories
-  - Vulnerabilities
-  - Collaboration
-shortTitle: Add collaborators
-ms.openlocfilehash: 6fa4062fab8e4ffc59724ceb0ba3b6b536871df9
-ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
-ms.translationtype: HT
-ms.contentlocale: pt-BR
-ms.lasthandoff: 09/10/2022
-ms.locfileid: '147875690'
----
-Todas as pessoas com permissões de administrador para uma consultora de segurança podem adicionar colaboradores à consultora de segurança.
-
-{% data reusables.security-advisory.repository-level-advisory-note %}
-
-## Adicionar um colaborador a uma consultora de segurança
-
-Os colaboradores têm permissões de gravação para a consultoria de segurança. Para obter mais informações, confira "[Níveis de permissão para consultorias de segurança do repositório](/code-security/repository-security-advisories/permission-levels-for-repository-security-advisories)".
-
-{% note %}
-
-{% data reusables.repositories.security-advisory-collaborators-public-repositories %} Para obter mais informações sobre como remover um colaborador em uma consultoria de segurança, confira "[Como remover um colaborador de uma consultoria de segurança do repositório](/code-security/repository-security-advisories/removing-a-collaborator-from-a-repository-security-advisory)".
-
-{% endnote %}
-
-{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %} {% data reusables.repositories.sidebar-advisories %}
-4. Na lista "consultoria de segurança", clique na consultoria de segurança à qual deseja adicionar um colaborador.
-5. No lado direito da página, em "Colaboradores", digite o nome do usuário ou da equipe que você gostaria de adicionar à consultora de segurança.
-  ![Campo usado para digitar o nome de usuário ou a equipe](/assets/images/help/security/add-collaborator-field.png)
-6. Clique em **Adicionar**.
-  ![Botão Adicionar](/assets/images/help/security/security-advisory-add-collaborator-button.png)
-
-## Leitura adicional
-
-- "[Níveis de permissão para consultorias de segurança do repositório](/code-security/repository-security-advisories/permission-levels-for-repository-security-advisories)"
-- "[Colaboração em um fork privado temporário para resolver uma vulnerabilidade de segurança do repositório](/code-security/repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability)"
-- "[Como remover um colaborador de uma consultoria de segurança do repositório](/code-security/repository-security-advisories/removing-a-collaborator-from-a-repository-security-advisory)"
diff --git a/translations/pt-BR/content/code-security/repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability.md b/translations/pt-BR/content/code-security/repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability.md
deleted file mode 100644
index 08863f6f4c..0000000000
--- a/translations/pt-BR/content/code-security/repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability.md
+++ /dev/null
@@ -1,90 +0,0 @@
----
-title: Colaborando em uma bifurcação privada temporária para resolver uma vulnerabilidade de segurança do repositório
-intro: Você pode criar uma bifurcação privada temporária para colaborar de maneira privada na correção de uma vulnerabilidade de segurança em seu repositório.
-redirect_from:
-  - /articles/collaborating-in-a-temporary-private-fork-to-resolve-a-security-vulnerability
-  - /github/managing-security-vulnerabilities/collaborating-in-a-temporary-private-fork-to-resolve-a-security-vulnerability
-  - /code-security/security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-security-vulnerability
-versions:
-  fpt: '*'
-  ghec: '*'
-type: how_to
-topics:
-  - Security advisories
-  - Vulnerabilities
-  - Collaboration
-  - Forks
-shortTitle: Temporary private forks
-ms.openlocfilehash: c03892c3ad1bd7345a7a066c9a9564858db4b84d
-ms.sourcegitcommit: ac00e2afa6160341c5b258d73539869720b395a4
-ms.translationtype: HT
-ms.contentlocale: pt-BR
-ms.lasthandoff: 09/09/2022
-ms.locfileid: '147875519'
----
-{% data reusables.security-advisory.repository-level-advisory-note %}
-
-## Pré-requisitos
-
-Antes de poder colaborar em uma bifurcação privada temporária, você deverá criar um rascunho da consultoria de segurança. Para obter mais informações, confira "[Como criar um aviso de segurança do repositório](/code-security/repository-security-advisories/creating-a-repository-security-advisory)".
-
-## Criar uma bifurcação privada temporária
-
-Qualquer pessoa com permissões de administrador em uma consultoria de segurança pode criar uma bifurcação privada temporária.
-
-Para manter as informações sobre vulnerabilidades em segurança, as integrações, incluindo CI, não podem acessar bifurcações privadas temporárias.
-
-{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %} {% data reusables.repositories.sidebar-advisories %}
-4. Na lista "consultoria de segurança", clique na consultoria de segurança que você gostaria de criar uma bifurcação privada temporária.
-  ![Aviso de segurança na lista](/assets/images/help/security/security-advisory-in-list.png)
-5. Clique em **Novo fork privado temporário**.
-  ![Botão Novo fork privado temporário](/assets/images/help/security/new-temporary-private-fork-button.png)
-
-## Adicionar colaboradores a uma bifurcação temporária privada
-
-Qualquer pessoa com permissão de administrador para uma consultoria de segurança pode adicionar colaboradores ao consultor de segurança, e os colaboradores na consultoria de segurança podem acessar uma bifurcação privada temporária. Para obter mais informações, confira "[Como adicionar um colaborador a um aviso de segurança do repositório](/code-security/repository-security-advisories/adding-a-collaborator-to-a-repository-security-advisory)".
-
-## Adicionar alterações a uma bifurcação privada temporária
-
-Qualquer pessoa com permissões de gravação em uma consultoria de segurança pode adicionar alterações a uma bifurcação privada temporária.
-
-{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %} {% data reusables.repositories.sidebar-advisories %}
-4. Na lista "consultoria de segurança", clique na consultoria de segurança à qual deseja adicionar alterações.
-  ![Aviso de segurança na lista](/assets/images/help/security/security-advisory-in-list.png)
-5. Adicione as alterações no {% data variables.product.product_name %} ou localmente:
-   - Para adicionar alterações no {% data variables.product.product_name %}, em "Adicionar alterações a este aviso", clique **no fork privado temporário**. Em seguida, crie um branch e edite os arquivos. Para obter mais informações, confira "[Como criar e excluir branches no seu repositório](/articles/creating-and-deleting-branches-within-your-repository)" e "[Como editar arquivos](/repositories/working-with-files/managing-files/editing-files)".
-   - Para adicionar as alterações localmente, siga as instruções em "Clonar e criar um novo branch" e "Faça suas alterações e, em seguida, faça o push."
-   ![Caixa Adicionar alterações a este aviso](/assets/images/help/security/add-changes-to-this-advisory-box.png)
-
-## Criar uma pull request de uma bifurcação privada temporária
-
-Qualquer pessoa com permissões de gravação em uma consultoria de segurança pode criar uma pull request de uma bifurcação privada temporária.
-
-{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %} {% data reusables.repositories.sidebar-advisories %}
-4. Na lista "consultoria de segurança" clique na consultoria de segurança na qual deseja criar um pull request.
-  ![Aviso de segurança na lista](/assets/images/help/security/security-advisory-in-list.png)
-5. À direita do nome do branch, clique em **Comparação e solicitação de pull**.
-  ![Botão Comparação e solicitação de pull](/assets/images/help/security/security-advisory-compare-and-pr.png) {% data reusables.repositories.pr-title-description %} {% data reusables.repositories.create-pull-request %}
-
-{% data reusables.repositories.merge-all-pulls-together %} Para obter mais informações, confira "[Como mesclar alterações em um aviso de segurança](#merging-changes-in-a-security-advisory)".
-
-## Mesclar alterações em uma consultoria de segurança
-
-Qualquer pessoa com permissão de administrador para uma consultoria de segurança pode mesclar alterações em uma consultora de segurança.
-
-{% data reusables.repositories.merge-all-pulls-together %}
-
-Antes de poder mesclar as alterações em uma consultoria de segurança, todo pull request aberto na bifurcação privada temporária deverá ser mesclada. Pode haver conflitos de merge e os requisitos de proteção do branch devem ser atendidos. Para manter as informações sobre vulnerabilidades seguras, as verificações de status não são executadas em pull requests de bifurcações privadas temporárias. Para obter mais informações, confira "[Sobre os branches protegidos](/articles/about-protected-branches)".
-
-{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %} {% data reusables.repositories.sidebar-advisories %}
-4. Na lista "consultoria de segurança", clique na consultoria de segurança com as alterações que gostaria de mesclar.
-  ![Aviso de segurança na lista](/assets/images/help/security/security-advisory-in-list.png)
-5. Para mesclar todas as solicitações de pull em aberto no fork privado temporário, clique em **Mesclar solicitações de pull**.
-  ![Botão Mesclar solicitações de pull](/assets/images/help/security/merge-pull-requests-button.png)
-
-Após mesclar as alterações em uma consultoria de segurança, você poderá publicar a consultoria de segurança para alertar a sua comunidade sobre a vulnerabilidade de segurança em versões anteriores do seu projeto. Para obter mais informações, confira "[Como publicar um aviso de segurança do repositório](/code-security/repository-security-advisories/publishing-a-repository-security-advisory)".
-
-## Leitura adicional
-
-- "[Níveis de permissão para avisos de segurança do repositório](/code-security/repository-security-advisories/permission-levels-for-repository-security-advisories)"
-- "[Como publicar um aviso de segurança do repositório](/code-security/repository-security-advisories/publishing-a-repository-security-advisory)"
diff --git a/translations/pt-BR/content/code-security/repository-security-advisories/creating-a-repository-security-advisory.md b/translations/pt-BR/content/code-security/repository-security-advisories/creating-a-repository-security-advisory.md
deleted file mode 100644
index 3d9d4e59af..0000000000
--- a/translations/pt-BR/content/code-security/repository-security-advisories/creating-a-repository-security-advisory.md
+++ /dev/null
@@ -1,44 +0,0 @@
----
-title: Criando uma consultoria de segurança do repositório
-intro: Você pode criar um projeto de consultoria de segurança para discutir e corrigir de forma privada uma vulnerabilidade de segurança no seu projeto de código aberto.
-redirect_from:
-  - /articles/creating-a-maintainer-security-advisory
-  - /github/managing-security-vulnerabilities/creating-a-maintainer-security-advisory
-  - /github/managing-security-vulnerabilities/creating-a-security-advisory
-  - /code-security/security-advisories/creating-a-security-advisory
-versions:
-  fpt: '*'
-  ghec: '*'
-type: how_to
-topics:
-  - Security advisories
-  - Vulnerabilities
-shortTitle: Create repository advisories
-ms.openlocfilehash: d4b47f84b20873e97b18106448b768288fff3039
-ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
-ms.translationtype: HT
-ms.contentlocale: pt-BR
-ms.lasthandoff: 09/10/2022
-ms.locfileid: '145095647'
----
-Qualquer pessoa com permissões de administrador em um repositório pode criar uma consultoria de segurança.
-
-{% data reusables.security-advisory.security-researcher-cannot-create-advisory %}
-
-## Como criar um aviso de segurança
-
-{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %} {% data reusables.repositories.sidebar-advisories %}
-4. Clique em **Nova consultoria de segurança de rascunho**.
-  ![Botão Abrir consultoria de rascunho](/assets/images/help/security/security-advisory-new-draft-security-advisory-button.png)
-5. Digite um título para sua consultoria de segurança.
-{% data reusables.repositories.security-advisory-edit-details %} {% data reusables.repositories.security-advisory-edit-severity %} {% data reusables.repositories.security-advisory-edit-cwe-cve %} {% data reusables.repositories.security-advisory-edit-description %}
-11. Clique em **Criar consultoria de segurança de rascunho**.
-  ![Botão Criar consultoria de segurança](/assets/images/help/security/security-advisory-create-security-advisory-button.png)
-
-## Próximas etapas
-
-- Faça um comentário sobre o rascunho da consultoria de segurança para discutir a vulnerabilidade com sua equipe.
-- Adicione colaboradores à consultora de segurança. Para obter mais informações, confira "[Como adicionar um colaborador a uma consultoria de segurança do repositório](/code-security/repository-security-advisories/adding-a-collaborator-to-a-repository-security-advisory)".
-- Colaborar de modo particular com a correção da vulnerabilidade em uma bifurcação privada temporária. Para obter mais informações, confira "[Colaboração em um fork privado temporário para resolver uma vulnerabilidade de segurança do repositório](/code-security/repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability)".
-- Adicione indivíduos que deveriam receber crédito por contribuírem para a consultoria de segurança. Para obter mais informações, confira "[Como editar uma consultoria de segurança do repositório](/code-security/repository-security-advisories/editing-a-repository-security-advisory#about-credits-for-security-advisories)".
-- Publicar a consultoria de segurança para notificar a sua comunidade sobre a vulnerabilidade de segurança. Para obter mais informações, confira "[Como publicar uma consultoria de segurança do repositório](/code-security/repository-security-advisories/publishing-a-repository-security-advisory)".
diff --git a/translations/pt-BR/content/code-security/repository-security-advisories/editing-a-repository-security-advisory.md b/translations/pt-BR/content/code-security/repository-security-advisories/editing-a-repository-security-advisory.md
deleted file mode 100644
index a0ff442acd..0000000000
--- a/translations/pt-BR/content/code-security/repository-security-advisories/editing-a-repository-security-advisory.md
+++ /dev/null
@@ -1,48 +0,0 @@
----
-title: Editando uma consultoria de segurança do repositório
-intro: 'Você pode editar os metadados e a descrição de uma consultoria de segurança do repositório, se precisar atualizar detalhes ou corrigir erros.'
-redirect_from:
-  - /github/managing-security-vulnerabilities/editing-a-security-advisory
-  - /code-security/security-advisories/editing-a-security-advisory
-versions:
-  fpt: '*'
-  ghec: '*'
-type: how_to
-topics:
-  - Security advisories
-  - Vulnerabilities
-shortTitle: Edit repository advisories
-ms.openlocfilehash: 2ea2f588374d83be677589b4f3bf4e74a7fc6e91
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
-ms.translationtype: HT
-ms.contentlocale: pt-BR
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '145095645'
----
-As pessoas com permissões de administrador para uma consultoria de segurança de repositório podem editar a consultoria de segurança.
-
-{% data reusables.security-advisory.repository-level-advisory-note %}
-
-## Sobre os créditos para a consultoria de segurança
-
-Você pode creditar pessoas que ajudaram a descobrir, relatar ou corrigir uma vulnerabilidade de segurança. Se você creditar alguém, essa pessoa poderá optar por aceitar ou recusar crédito.
-
-Se alguém aceitar o crédito, o nome de usuário da pessoa aparecerá na seção "Créditos" da consultoria de segurança. Qualquer pessoa com acesso de leitura ao repositório pode ver a consultoria e as pessoas que aceitaram o crédito por ela.
-
-Se você acredita que deveria ser creditado por uma consultoria de segurança, entre em contato com a pessoa que criou a consultoria e peça que edite a consultoria para incluir o seu crédito. Somente o criador da consultoria pode dar-lhe crédito. Portanto, não entre em contato com o suporte do GitHub com relação a créditos para consultorias de segurança.
-
-## Editar uma consultoria de segurança
-
-{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %} {% data reusables.repositories.sidebar-advisories %}
-4. Na lista "consultorias de segurança", clique na consultoria de segurança que deseja editar.
-5. No canto superior direito dos detalhes da consultoria de segurança, clique em {% octicon "pencil" aria-label="The edit icon" %}.
-  ![Botão Editar em uma consultoria de segurança](/assets/images/help/security/security-advisory-edit-button.png) {% data reusables.repositories.security-advisory-edit-details %} {% data reusables.repositories.security-advisory-edit-severity %} {% data reusables.repositories.security-advisory-edit-cwe-cve %} {% data reusables.repositories.security-advisory-edit-description %}
-11. Opcionalmente, edite os "Créditos" para a consultoria de segurança.
-  ![Créditos para uma consultoria de segurança](/assets/images/help/security/security-advisory-credits.png)
-12. Clique em **Atualizar consultoria de segurança**.
-  ![Botão "Atualizar consultoria de segurança"](/assets/images/help/security/update-advisory-button.png)
-13. As pessoas listadas na seção "Créditos" receberão um e-mail ou uma notificação da web convidando-os a aceitar o crédito. Se uma pessoa aceitar, seu nome de usuário ficará visível publicamente assim que a consultoria de segurança for publicada.
-
-## Leitura adicional
-
-- "[Como retirar uma consultoria de segurança do repositório](/code-security/repository-security-advisories/withdrawing-a-repository-security-advisory)"
diff --git a/translations/pt-BR/content/code-security/repository-security-advisories/index.md b/translations/pt-BR/content/code-security/repository-security-advisories/index.md
deleted file mode 100644
index befa2694b4..0000000000
--- a/translations/pt-BR/content/code-security/repository-security-advisories/index.md
+++ /dev/null
@@ -1,36 +0,0 @@
----
-title: Gerenciando consultorias de segurança de repositório para vulnerabilidades no seu projeto
-shortTitle: Repository security advisories
-intro: 'Discuta, corrija e publique vulnerabilidades de segurança nos seus repositórios usando consultorias de segurança de repositório.'
-redirect_from:
-  - /articles/managing-security-vulnerabilities-in-your-project
-  - /github/managing-security-vulnerabilities/managing-security-vulnerabilities-in-your-project
-  - /code-security/security-advisories
-versions:
-  fpt: '*'
-  ghec: '*'
-topics:
-  - Security advisories
-  - Vulnerabilities
-  - Repositories
-  - CVEs
-children:
-  - /about-coordinated-disclosure-of-security-vulnerabilities
-  - /about-github-security-advisories-for-repositories
-  - /permission-levels-for-repository-security-advisories
-  - /creating-a-repository-security-advisory
-  - /adding-a-collaborator-to-a-repository-security-advisory
-  - /removing-a-collaborator-from-a-repository-security-advisory
-  - /collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability
-  - /publishing-a-repository-security-advisory
-  - /editing-a-repository-security-advisory
-  - /withdrawing-a-repository-security-advisory
-  - /best-practices-for-writing-repository-security-advisories
-ms.openlocfilehash: 43efe7ceaf307da4a8a7c02c45f744a4967b05b0
-ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
-ms.translationtype: HT
-ms.contentlocale: pt-BR
-ms.lasthandoff: 09/10/2022
-ms.locfileid: '145095644'
----
-
diff --git a/translations/pt-BR/content/code-security/repository-security-advisories/permission-levels-for-repository-security-advisories.md b/translations/pt-BR/content/code-security/repository-security-advisories/permission-levels-for-repository-security-advisories.md
deleted file mode 100644
index b91aa06ad5..0000000000
--- a/translations/pt-BR/content/code-security/repository-security-advisories/permission-levels-for-repository-security-advisories.md
+++ /dev/null
@@ -1,50 +0,0 @@
----
-title: Níveis de permissão para consultorias de segurança do repositório
-intro: As ações que você pode tomar em uma consultoria de segurança dependem do fato de você ter permissões de administrador ou de gravação na consultoria de segurança.
-redirect_from:
-  - /articles/permission-levels-for-maintainer-security-advisories
-  - /github/managing-security-vulnerabilities/permission-levels-for-maintainer-security-advisories
-  - /github/managing-security-vulnerabilities/permission-levels-for-security-advisories
-  - /code-security/security-advisories/permission-levels-for-security-advisories
-versions:
-  fpt: '*'
-  ghec: '*'
-type: reference
-topics:
-  - Security advisories
-  - Vulnerabilities
-  - Permissions
-shortTitle: Permission levels
-ms.openlocfilehash: 9c2ad0d30b98b79786df09a224766bd826cb84f6
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
-ms.translationtype: HT
-ms.contentlocale: pt-BR
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '145095646'
----
-Este artigo aplica-se apenas às consultorias de segurança a nível de repositório. Qualquer pessoa pode contribuir com avisos de segurança global no {% data variables.product.prodname_advisory_database %} em [github.com/advisories](https://github.com/advisories). As edições nas consultorias globais não mudarão ou afetarão a forma como a consultoria aparece no repositório.  Para obter mais informações, confira "[Como editar avisos de segurança no {% data variables.product.prodname_advisory_database %}](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/editing-security-advisories-in-the-github-advisory-database)".
-
-## Visão geral das permissões
-
-{% data reusables.repositories.security-advisory-admin-permissions %} Para obter mais informações sobre como adicionar um colaborador a um aviso de segurança, confira "[Como adicionar um colaborador a um aviso de segurança do repositório](/code-security/repository-security-advisories/adding-a-collaborator-to-a-repository-security-advisory)".
-
-Ação | Permissões de gravação | Permissões de administrador |
------- | ----------------- | ----------------- |
-Veja um rascunho da consultoria de segurança | X | X |
-Adicionar colaboradores ao aviso de segurança (confira "[Como adicionar um colaborador a um aviso de segurança do repositório](/code-security/repository-security-advisories/adding-a-collaborator-to-a-repository-security-advisory)") | | X |
-Editar e excluir quaisquer comentários na consultoria de segurança | X | X |
-Criar um fork privado temporário no aviso de segurança (confira "[Colaboração em um fork privado temporário para resolver uma vulnerabilidade de segurança do repositório](/code-security/repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability)") | | X |
-Adicionar alterações a um fork privado temporário no aviso de segurança (confira "[Colaboração em um fork privado temporário para resolver uma vulnerabilidade de segurança do repositório](/code-security/repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability)") | X | X |
-Criar solicitações de pull em um fork privado temporário (confira "[Colaboração em um fork privado temporário para resolver uma vulnerabilidade de segurança do repositório](/code-security/repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability)") | X | X |
-Mesclar alterações no aviso de segurança (confira "[Colaboração em um fork privado temporário para resolver uma vulnerabilidade de segurança do repositório](/code-security/repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability)") | | X |
-Adicionar e editar metadados no aviso de segurança (confira "[Como publicar um aviso de segurança do repositório](/code-security/repository-security-advisories/publishing-a-repository-security-advisory)") | X | X |
-Adicionar e remover créditos para um aviso de segurança (confira "[Como editar um aviso de segurança do repositório](/code-security/repository-security-advisories/editing-a-repository-security-advisory)") | X | X |
-Fechar o rascunho da consultoria de segurança | | X |
-Publicar o aviso de segurança (confira "[Como publicar um aviso de segurança do repositório](/code-security/repository-security-advisories/publishing-a-repository-security-advisory)") | | X |
-
-## Leitura adicional
-
-- "[Como adicionar um colaborador a um aviso de segurança do repositório](/code-security/repository-security-advisories/adding-a-collaborator-to-a-repository-security-advisory)"
-- "[Colaboração em um fork privado temporário para resolver uma vulnerabilidade de segurança do repositório](/code-security/repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability)"
-- "[Como remover um colaborador de um aviso de segurança do repositório](/code-security/repository-security-advisories/removing-a-collaborator-from-a-repository-security-advisory)"
-- "[Como retirar um aviso de segurança do repositório](/code-security/repository-security-advisories/withdrawing-a-repository-security-advisory)"
diff --git a/translations/pt-BR/content/code-security/repository-security-advisories/publishing-a-repository-security-advisory.md b/translations/pt-BR/content/code-security/repository-security-advisories/publishing-a-repository-security-advisory.md
deleted file mode 100644
index ec7fe7aca3..0000000000
--- a/translations/pt-BR/content/code-security/repository-security-advisories/publishing-a-repository-security-advisory.md
+++ /dev/null
@@ -1,101 +0,0 @@
----
-title: Publicando uma consultoria de segurança do repositório
-intro: Você pode publicar uma consultoria de segurança para alertar a sua comunidade sobre uma vulnerabilidade de segurança no seu projeto.
-redirect_from:
-  - /articles/publishing-a-maintainer-security-advisory
-  - /github/managing-security-vulnerabilities/publishing-a-maintainer-security-advisory
-  - /github/managing-security-vulnerabilities/publishing-a-security-advisory
-  - /code-security/security-advisories/publishing-a-security-advisory
-versions:
-  fpt: '*'
-  ghec: '*'
-type: how_to
-topics:
-  - Security advisories
-  - Vulnerabilities
-  - CVEs
-  - Repositories
-shortTitle: Publish repository advisories
-ms.openlocfilehash: f3e3bfdb6b44ec1c86bb903c66271b854f4fb041
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
-ms.translationtype: HT
-ms.contentlocale: pt-BR
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '145095643'
----
-<!--Marketing-LINK: From /features/security/software-supply-chain page "Publishing a security advisory".-->
-
-Qualquer pessoa com permissão de administrador para um consultor de segurança pode publicar a consultoria de segurança.
-
-{% data reusables.security-advisory.repository-level-advisory-note %}
-
-## Pré-requisitos
-
-Antes de publicar uma consultoria de segurança ou solicitar um número de identificação CVE, você deve criar um rascunho da consultoria de segurança e fornecer informações sobre as versões do seu projeto afetadas pela vulnerabilidade de segurança. Para obter mais informações, confira "[Como criar um aviso de segurança do repositório](/code-security/repository-security-advisories/creating-a-repository-security-advisory)".
-
-Se você criou uma consultoria de segurança, mas ainda não forneceu as informações sobre as versões do seu projeto que a vulnerabilidade de segurança afeta, você pode editar a consultoria de segurança. Para obter mais informações, confira "[Como editar um aviso de segurança do repositório](/code-security/repository-security-advisories/editing-a-repository-security-advisory)".
-
-## Sobre a publicação de uma consultoria de segurança
-
-Ao publicar uma consultoria de segurança, você notifica a sua comunidade sobre a vulnerabilidade de segurança que a consultoria de segurança aborda. A publicação de uma consultoria de segurança torna mais fácil para a sua comunidade atualizar as dependências do pacote e pesquisar o impacto da vulnerabilidade de segurança.
-
-{% data reusables.repositories.security-advisories-republishing %}
-
-Antes de publicar uma consultoria de segurança, você pode colaborar de forma privada para consertar a vulnerabilidade em uma bifurcação privada temporária. Para obter mais informações, confira "[Colaboração em um fork privado temporário para resolver uma vulnerabilidade de segurança do repositório](/code-security/repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability)".
-
-{% warning %}
-
-**Aviso**: sempre que possível, adicione uma versão de correção a um aviso de segurança antes de publicar o aviso. Se você não fizer isso, a sua consultoria será publicado sem uma versão de correção e {% data variables.product.prodname_dependabot %} alertará os seus usuários sobre o problema, sem oferecer qualquer versão segura para a qual atualizar.
-
-Recomendamos que você tome as seguintes medidas nestas situações diferentes:
-
-- Se uma versão de correção estiver disponível imediatamente, e você puder, espere para divulgar o problema quando a correção estiver pronta.
-- Se uma versão de correção estiver em desenvolvimento mas ainda não disponível, mencione isso no consultor e edite a consultoria mais tarde, após a publicação.
-- Se você não está planejando corrigir o problema, tenha isso claro na consultoria para que os usuários não entrem em contato com você para perguntar quando será feita uma correção. Neste caso, é útil incluir as etapas que os usuários podem seguir para mitigar o problema.
-
-{% endwarning %}
-
-Ao publicar um rascunho de consultoria a partir de um repositório público, todos poderão ver:
-
-- A versão atual dos dados da consultoria.
-- Todos os créditos da consultoria que os usuários creditados aceitaram.
-  
-{% note %}
-
-**Observação**: o público-alvo em geral nunca terá acesso ao histórico de edição do aviso e verá apenas a versão publicada.
-
-{% endnote %}
-
-Depois de publicar uma consultoria de segurança, sua URL permanecerá a mesma de antes da publicação da consultoria de segurança. Qualquer pessoa com acesso de leitura ao repositório pode ver a consultoria de segurança. Os colaboradores na consultoria de segurança podem continuar a visualizar conversas anteriores, incluindo o fluxo de comentários completo na consultoria de segurança, a menos que alguém com permissões de administração remova o colaborador da consultoria de segurança. 
-
-Se você precisar atualizar ou corrigir informações em uma consultoria de segurança que publicou, poderá editar a consultoria de segurança. Para obter mais informações, confira "[Como editar um aviso de segurança do repositório](/code-security/repository-security-advisories/editing-a-repository-security-advisory)".
-
-## Publicar uma consultoria de segurança
-
-A publicação de uma consultor de segurança elimina a bifurcação privada temporária para a consultoria de segurança.
-
-{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %} {% data reusables.repositories.sidebar-advisories %}
-4. Na lista "consultoria de segurança", clique na consultoria de segurança que deseja publicar.
-  ![Aviso de segurança na lista](/assets/images/help/security/security-advisory-in-list.png)
-5. Na parte inferior da página, clique em **Publicar aviso**.
-  ![Botão Publicar aviso](/assets/images/help/security/publish-advisory-button.png)
-  
-## {% data variables.product.prodname_dependabot_alerts %} para consultorias de segurança publicadas
-
-{% data reusables.repositories.github-reviews-security-advisories %}
-
-## Solicitando um número de identificação CVE (Opcional)
-
-{% data reusables.repositories.request-security-advisory-cve-id %} Para obter mais informações, confira "[Sobre os {% data variables.product.prodname_security_advisories %} para repositórios](/code-security/repository-security-advisories/about-github-security-advisories-for-repositories#cve-identification-numbers)".
-
-{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %} {% data reusables.repositories.sidebar-advisories %}
-4. Na lista "consultoria de segurança", clique na consultoria de segurança para o qual deseja solicitar um número de identificação CVE.
-  ![Aviso de segurança na lista](/assets/images/help/security/security-advisory-in-list.png)
-5. Use o menu suspenso **Publicar aviso** e clique em **Solicitar CVE**.
-  ![Solicitar CVE no menu suspenso](/assets/images/help/security/security-advisory-drop-down-request-cve.png)
-6. Clique em **Solicitar CVE**.
-  ![Botão Solicitar CVE](/assets/images/help/security/security-advisory-request-cve-button.png)
-
-## Leitura adicional
-
-- "[Como retirar uma consultoria de segurança do repositório](/code-security/repository-security-advisories/withdrawing-a-repository-security-advisory)"
diff --git a/translations/pt-BR/content/code-security/repository-security-advisories/removing-a-collaborator-from-a-repository-security-advisory.md b/translations/pt-BR/content/code-security/repository-security-advisories/removing-a-collaborator-from-a-repository-security-advisory.md
deleted file mode 100644
index e7207201c4..0000000000
--- a/translations/pt-BR/content/code-security/repository-security-advisories/removing-a-collaborator-from-a-repository-security-advisory.md
+++ /dev/null
@@ -1,42 +0,0 @@
----
-title: Removendo um colaborador de uma consultoria de segurança de repositório
-intro: 'Ao remover um colaborador de uma consultoria de segurança do repositório, ele perderá acesso de leitura e gravação às discussões e metadados da consultoria de segurança.'
-redirect_from:
-  - /github/managing-security-vulnerabilities/removing-a-collaborator-from-a-security-advisory
-  - /code-security/security-advisories/removing-a-collaborator-from-a-security-advisory
-versions:
-  fpt: '*'
-  ghec: '*'
-type: how_to
-topics:
-  - Security advisories
-  - Vulnerabilities
-  - Collaboration
-shortTitle: Remove collaborators
-ms.openlocfilehash: ced0edd0614304c0d33ddd40dce3c6a24a9ffcfd
-ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
-ms.translationtype: HT
-ms.contentlocale: pt-BR
-ms.lasthandoff: 09/10/2022
-ms.locfileid: '145095638'
----
-As pessoas com permissões de administrador para uma consultoria de segurança podem remover colaboradores da consultoria de segurança.
-
-{% data reusables.security-advisory.repository-level-advisory-note %}
-
-## Remover um colaborador de uma consultoria de segurança
-
-{% data reusables.repositories.security-advisory-collaborators-public-repositories %}
-
-{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %} {% data reusables.repositories.sidebar-advisories %}
-4. Na lista "consultoria de segurança" clique na consultoria de segurança da qual deseja remover um colaborador.
-  ![Aviso de segurança na lista](/assets/images/help/security/security-advisory-in-list.png)
-5. No lado direito da página, em "Colaboradores", encontre o nome do usuário ou da equipe que deseja remover da consultoria de segurança.
-  ![Colaborador no aviso de segurança](/assets/images/help/security/security-advisory-collaborator.png)
-6. Ao lado do colaborador que deseja remover, clique no ícone **X**.
-  ![Ícone X para remover o colaborador no aviso de segurança](/assets/images/help/security/security-advisory-remove-collaborator-x.png)
-
-## Leitura adicional
-
-- "[Níveis de permissão para avisos de segurança do repositório](/code-security/repository-security-advisories/permission-levels-for-repository-security-advisories)"
-- "[Como adicionar um colaborador a um aviso de segurança do repositório](/code-security/repository-security-advisories/adding-a-collaborator-to-a-repository-security-advisory)"
diff --git a/translations/pt-BR/content/code-security/repository-security-advisories/withdrawing-a-repository-security-advisory.md b/translations/pt-BR/content/code-security/repository-security-advisories/withdrawing-a-repository-security-advisory.md
deleted file mode 100644
index 39081fc68c..0000000000
--- a/translations/pt-BR/content/code-security/repository-security-advisories/withdrawing-a-repository-security-advisory.md
+++ /dev/null
@@ -1,28 +0,0 @@
----
-title: Retirando uma consultoria de segurança do repositório
-intro: Você pode retirar uma consultoria de segurança do repositório que você publicou.
-redirect_from:
-  - /github/managing-security-vulnerabilities/withdrawing-a-security-advisory
-  - /code-security/security-advisories/withdrawing-a-security-advisory
-versions:
-  fpt: '*'
-  ghec: '*'
-type: how_to
-topics:
-  - Security advisories
-  - Vulnerabilities
-shortTitle: Withdraw repository advisories
-ms.openlocfilehash: 1d85afddaadbd25c5b24ab945dac998b7842ae23
-ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
-ms.translationtype: HT
-ms.contentlocale: pt-BR
-ms.lasthandoff: 09/10/2022
-ms.locfileid: '145095630'
----
-{% data reusables.security-advisory.repository-level-advisory-note %}
-
-Se você publicar uma consultoria de segurança por engano, poderá retirar a consultoria de segurança entrando em contato com {% data variables.contact.contact_support %}.
-
-## Leitura adicional
-
-- "[Editando uma consultoria de segurança do repositório](/code-security/repository-security-advisories/editing-a-repository-security-advisory)"
diff --git a/translations/pt-BR/content/code-security/security-overview/about-the-security-overview.md b/translations/pt-BR/content/code-security/security-overview/about-the-security-overview.md
index 69e55a8adc..c763b80753 100644
--- a/translations/pt-BR/content/code-security/security-overview/about-the-security-overview.md
+++ b/translations/pt-BR/content/code-security/security-overview/about-the-security-overview.md
@@ -67,17 +67,23 @@ The security overview displays active alerts raised by security features. If the
 
 At the organization-level, the security overview displays aggregate and repository-specific security information for repositories owned by your organization. You can filter information by security features at the organization-level.
 
+Organization owners and security managers for organizations have access to the organization-level security overview. {% ifversion ghec or ghes > 3.6 or ghae > 3.6 %}Organization members can access the organization-level security overview to view results for repositories where they have admin privileges or have been granted access to security alerts. For more information on managing security alert access, see "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)".{% endif %}
+
 {% ifversion ghec or ghes > 3.4 or ghae > 3.4 %}
 ### About the enterprise-level security overview
 At the enterprise-level, the security overview displays aggregate and repository-specific security information for your enterprise. You can view repositories owned by your enterprise that have security alerts, view all security alerts, or security feature-specific alerts from across your enterprise.
 
-Organization owners and security managers for organizations in your enterprise also have limited access to the enterprise-level security overview. They can only view repositories and alerts for the organizations that they have full access to.
+Organization owners and security managers for organizations in your enterprise have access to the enterprise-level security overview. They can view repositories and alerts for the organizations that they have full access to.
+
+Enterprise owners can only see alerts for organizations that they are an owner or a security manager of.{% ifversion ghec or ghes > 3.5 or ghae > 3.5 %} Enterprise owners can join an organization as an organization owner to see all of its alerts in the enterprise-level security overview. For more information, see "[Managing your role in an organization owned by your enterprise](/admin/user-management/managing-organizations-in-your-enterprise/managing-your-role-in-an-organization-owned-by-your-enterprise)."{% endif %}
 
 {% elsif fpt %}
 ### About the enterprise-level security overview
 At the enterprise-level, the security overview displays aggregate and repository-specific information for an enterprise. For more information, see "[About the enterprise-level security overview](/enterprise-cloud@latest/code-security/security-overview/about-the-security-overview#about-the-enterprise-level-security-overview)" in the {% data variables.product.prodname_ghe_cloud %} documentation.
 {% endif %}
 
+{% ifversion ghes < 3.7 or ghae < 3.7 %}
 ### About the team-level security overview
 At the team-level, the security overview displays repository-specific security information for repositories that the team has admin privileges for. For more information, see "[Managing team access to an organization repository](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository)."
 {% endif %}
+{% endif %}
diff --git a/translations/pt-BR/content/codespaces/codespaces-reference/allowing-your-codespace-to-access-a-private-image-registry.md b/translations/pt-BR/content/codespaces/codespaces-reference/allowing-your-codespace-to-access-a-private-image-registry.md
index 40094b5db2..fe7c29fd82 100644
--- a/translations/pt-BR/content/codespaces/codespaces-reference/allowing-your-codespace-to-access-a-private-image-registry.md
+++ b/translations/pt-BR/content/codespaces/codespaces-reference/allowing-your-codespace-to-access-a-private-image-registry.md
@@ -30,7 +30,7 @@ If you publish a container image to {% data variables.packages.prodname_ghcr_or_
 
 By default, when you publish a container image to {% data variables.packages.prodname_ghcr_or_npm_registry %}, the image inherits the access setting of the repository from which the image was published. For example, if the repository is public, the image is also public. If the repository is private, the image is also private, but is accessible from the repository.
 
-This behavior is controlled by the **Inherit access from repo** option. **Inherit access from repo** is selected by default when publishing via {% data variables.product.prodname_actions %}, but not when publishing directly to {% data variables.packages.prodname_ghcr_or_npm_registry %} using a % data variables.product.pat_generic %}.
+This behavior is controlled by the **Inherit access from repo** option. **Inherit access from repo** is selected by default when publishing via {% data variables.product.prodname_actions %}, but not when publishing directly to {% data variables.packages.prodname_ghcr_or_npm_registry %} using a {% data variables.product.pat_generic %}.
 
 If the **Inherit access from repo** option was not selected when the image was published, you can manually add the repository to the published container image's access controls. For more information, see "[Configuring a package's access control and visibility](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility#inheriting-access-for-a-container-image-from-a-repository)."
 
diff --git a/translations/pt-BR/content/codespaces/guides.md b/translations/pt-BR/content/codespaces/guides.md
index 71bf48a31e..239552e325 100644
--- a/translations/pt-BR/content/codespaces/guides.md
+++ b/translations/pt-BR/content/codespaces/guides.md
@@ -15,6 +15,8 @@ includeGuides:
   - /codespaces/setting-up-your-project-for-codespaces/setting-up-your-python-project-for-codespaces
   - /codespaces/setting-up-your-project-for-codespaces/setting-up-your-dotnet-project-for-codespaces
   - /codespaces/setting-up-your-project-for-codespaces/setting-up-your-java-project-for-codespaces
+  - /codespaces/setting-up-your-project-for-codespaces/setting-a-minimum-specification-for-codespace-machines
+  - /codespaces/setting-up-your-project-for-codespaces/automatically-opening-files-in-the-codespaces-for-a-repository
   - /codespaces/setting-up-your-project-for-codespaces/adding-a-codespaces-badge
   - /codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project
   - /codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account
diff --git a/translations/pt-BR/content/codespaces/setting-up-your-project-for-codespaces/index.md b/translations/pt-BR/content/codespaces/setting-up-your-project-for-codespaces/index.md
index aa85f70e3f..8bf26a6ec1 100644
--- a/translations/pt-BR/content/codespaces/setting-up-your-project-for-codespaces/index.md
+++ b/translations/pt-BR/content/codespaces/setting-up-your-project-for-codespaces/index.md
@@ -17,6 +17,7 @@ children:
   - /setting-up-your-java-project-for-codespaces
   - /setting-up-your-python-project-for-codespaces
   - /setting-a-minimum-specification-for-codespace-machines
+  - /automatically-opening-files-in-the-codespaces-for-a-repository
   - /adding-a-codespaces-badge
 ms.openlocfilehash: 1e172243dc351f0a173c8624b66914e1c3795495
 ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794
diff --git a/translations/pt-BR/content/codespaces/setting-up-your-project-for-codespaces/setting-a-minimum-specification-for-codespace-machines.md b/translations/pt-BR/content/codespaces/setting-up-your-project-for-codespaces/setting-a-minimum-specification-for-codespace-machines.md
index e6c38add71..9bd36a5a2a 100644
--- a/translations/pt-BR/content/codespaces/setting-up-your-project-for-codespaces/setting-a-minimum-specification-for-codespace-machines.md
+++ b/translations/pt-BR/content/codespaces/setting-up-your-project-for-codespaces/setting-a-minimum-specification-for-codespace-machines.md
@@ -1,7 +1,7 @@
 ---
-title: Definindo uma especificação mínima para máquinas de codespaces
+title: Setting a minimum specification for codespace machines
 shortTitle: Set a minimum machine spec
-intro: 'Você pode evitar que tipos de computador com recursos insuficientes sejam usados nos {% data variables.product.prodname_github_codespaces %} do repositório.'
+intro: 'You can avoid under-resourced machine types being used for {% data variables.product.prodname_github_codespaces %} for your repository.'
 permissions: People with write permissions to a repository can create or edit the codespace configuration.
 versions:
   fpt: '*'
@@ -11,29 +11,24 @@ topics:
   - Codespaces
   - Set up
 product: '{% data reusables.gated-features.codespaces %}'
-ms.openlocfilehash: 368b7c73d13bb0624c9d838ac2d7bb18a2b050e3
-ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
-ms.translationtype: HT
-ms.contentlocale: pt-BR
-ms.lasthandoff: 09/10/2022
-ms.locfileid: '147880803'
 ---
-## Visão geral
 
-Cada codespace criado é hospedado em uma máquina virtual separada e você geralmente pode escolher entre diferentes tipos de máquinas virtuais. Cada tipo de computador tem recursos diferentes (CPUs, memória, armazenamento) e, por padrão, o tipo de computador com menos recursos é usado. Para obter mais informações, confira "[Como alterar o tipo de computador para seu codespace](/codespaces/customizing-your-codespace/changing-the-machine-type-for-your-codespace#about-machine-types)".
+## Overview
 
-Se o seu projeto precisar de um nível de capacidade de computação específico, você poderá configurar {% data variables.product.prodname_github_codespaces %} para que apenas os tipos de computador que atenderem a esses requisitos possam ser usados por padrão ou selecionados pelos usuários. Você configura isso em um arquivo `devcontainer.json`.
+Each codespace that you create is hosted on a separate virtual machine, and you can usually choose from different types of virtual machines. Each machine type has different resources (processor cores, memory, storage) and, by default, the machine type with the least resources is used. For more information, see "[Changing the machine type for your codespace](/codespaces/customizing-your-codespace/changing-the-machine-type-for-your-codespace#about-machine-types)."
+
+If your project needs a certain level of compute power, you can configure {% data variables.product.prodname_github_codespaces %} so that only machine types that meet these requirements can be used by default, or selected by users. You configure this in a `devcontainer.json` file.
 
 {% note %}
 
-**Importante:** o acesso a alguns tipos de computadores pode ser restrito no nível da organização. De modo geral, isso é feito para evitar que as pessoas escolham máquinas de maior recursos que são cobradas a uma taxa mais alta. Se seu repositório for afetado por uma política a nível da organização para tipos de máquinas, você deverá certificar-se de que não definiu uma especificação mínima que não deixaria nenhum tipo de máquina disponível para as pessoas escolherem. Para obter mais informações, confira "[Como restringir o acesso aos tipos de computadores](/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types)".
+**Important:** Access to some machine types may be restricted at the organization level. Typically this is done to prevent people choosing higher resourced machines that are billed at a higher rate. If your repository is affected by an organization-level policy for machine types you should make sure you don't set a minimum specification that would leave no available machine types for people to choose. For more information, see "[Restricting access to machine types](/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types)."
 
 {% endnote %}
 
-## Definindo uma especificação mínima de máquina
+## Setting a minimum machine specification
 
-1. Os {% data variables.product.prodname_github_codespaces %} do repositório são configurados em um arquivo `devcontainer.json`. Se o repositório ainda não contiver um arquivo `devcontainer.json`, adicione-o agora. Confira "[Adicionar uma configuração de contêiner de desenvolvimento ao repositório](/free-pro-team@latest/codespaces/setting-up-your-project-for-codespaces/setting-up-your-project-for-codespaces)".
-1. Edite o arquivo `devcontainer.json`, adicionando uma propriedade `hostRequirements` como esta:
+{% data reusables.codespaces.edit-devcontainer-json %}
+1. Edit the `devcontainer.json` file, adding the `hostRequirements` property at the top level of the file, within the enclosing JSON object. For example:
 
    ```json{:copy}
    "hostRequirements": {
@@ -43,16 +38,16 @@ Se o seu projeto precisar de um nível de capacidade de computação específico
    }
    ```
 
-   Você pode especificar uma ou todas as opções: `cpus`, `memory` e `storage`.
+   You can specify any or all of the options: `cpus`, `memory`, and `storage`.
    
-   Para verificar as especificações dos tipos de computador do {% data variables.product.prodname_github_codespaces %} que estão disponíveis para o repositório no momento, siga o processo de criação de um codespace até que apareçam as opções de tipos de computador. Para obter mais informações, confira "[Como criar um codespace](/codespaces/developing-in-codespaces/creating-a-codespace#creating-a-codespace)".
+   To check the specifications of the {% data variables.product.prodname_github_codespaces %} machine types that are currently available for your repository, step through the process of creating a codespace until you see the choice of machine types. For more information, see "[Creating a codespace](/codespaces/developing-in-codespaces/creating-a-codespace#creating-a-codespace)."
    
-1. Salve o arquivo e faça commit as alterações no branch necessário do repositório.
+1. Save the file and commit your changes to the required branch of the repository.
 
-   Agora, quando você criar um codespace para esse branch do repositório e acessar as opções de configuração de criação, você só poderá selecionar os tipos de máquina que correspondem ou excedem os recursos que você especificou.
+   Now when you create a codespace for that branch of the repository, and you go to the creation configuration options, you will only be able to select machine types that match or exceed the resources you've specified.
 
-   ![Caixa de diálogo que mostra uma escolha limitada de tipos de máquina](/assets/images/help/codespaces/machine-types-limited-choice.png)
+   ![Dialog box showing a limited choice of machine types](/assets/images/help/codespaces/machine-types-limited-choice.png)
 
-## Leitura adicional
+## Further reading
 
-- "[Introdução aos contêineres de desenvolvimento](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers)"
+- "[Introduction to dev containers](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers)"
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 f17d1a1b94..e687fd7b2b 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
@@ -142,14 +142,14 @@ You can use `publishConfig` element in the *package.json* file to specify the re
   {% endif %}
   ```shell
   "publishConfig": {
-    "registry":"https://{% ifversion fpt or ghec %}npm.pkg.github.com{% else %}npm.HOSTNAME/{% endif %}"
+    "registry": "https://{% ifversion fpt or ghec %}npm.pkg.github.com{% else %}npm.HOSTNAME/{% endif %}"
   },
   ```
   {% ifversion ghes %}
   If your instance has subdomain isolation disabled:
    ```shell
    "publishConfig": {
-     "registry":"https://HOSTNAME/_registry/npm/"
+     "registry": "https://HOSTNAME/_registry/npm/"
    },
   ```
   {% endif %}
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 2b581bcc4d..a2808b957d 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
@@ -187,7 +187,7 @@ When you enable branch restrictions, only users, teams, or apps that have been g
 Optionally, you can apply the same restrictions to the creation of branches that match the rule. For example, if you create a rule that only allows a certain team to push to any branches that contain the word `release`, only members of that team would be able to create a new branch that contains the word `release`.
 {% endif %}
 
-You can only give push access to a protected branch, or give permission to create a matching 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 or create a matching branch.
+You can only give push access to a protected branch, or give permission to create a matching 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{% ifversion restrict-pushes-create-branch %} or create a matching branch{% endif %}.
 
 ### Allow force pushes
 
diff --git a/translations/pt-BR/content/repositories/creating-and-managing-repositories/transferring-a-repository.md b/translations/pt-BR/content/repositories/creating-and-managing-repositories/transferring-a-repository.md
index dff4c98d4d..ca7dd28f84 100644
--- a/translations/pt-BR/content/repositories/creating-and-managing-repositories/transferring-a-repository.md
+++ b/translations/pt-BR/content/repositories/creating-and-managing-repositories/transferring-a-repository.md
@@ -51,6 +51,12 @@ When you transfer a repository, its issues, pull requests, wiki, stars, and watc
   $ git remote set-url origin NEW_URL
   ```
 
+  {% warning %}
+
+  **Warning**: If you create a new repository under your account in the future, do not reuse the original name of the transferred repository. If you do, redirects to the transferred repository will no longer work.
+
+  {% endwarning %}
+
 - When you transfer a repository from an organization to a personal account, the repository's read-only collaborators will not be transferred. This is because collaborators can't have read-only access to repositories owned by a personal account. For more information about repository permission levels, see "[Permission levels for a personal account repository](/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository)" and "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)."{% ifversion fpt or ghec %}
 - Sponsors who have access to the repository through a sponsorship tier may be affected. For more information, see "[Adding a repository to a sponsorship tier](/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers#adding-a-repository-to-a-sponsorship-tier)".{% endif %}
 
diff --git a/translations/pt-BR/data/learning-tracks/code-security.yml b/translations/pt-BR/data/learning-tracks/code-security.yml
index a614b6945c..3b35eb0a73 100644
--- a/translations/pt-BR/data/learning-tracks/code-security.yml
+++ b/translations/pt-BR/data/learning-tracks/code-security.yml
@@ -4,15 +4,18 @@ security_advisories:
   description: 'Using repository security advisories to privately fix a reported vulnerability and get a CVE.'
   featured_track: '{% ifversion fpt or ghec %}true{% else %}false{% endif %}'
   guides:
-    - /code-security/repository-security-advisories/about-coordinated-disclosure-of-security-vulnerabilities
-    - /code-security/repository-security-advisories/creating-a-repository-security-advisory
-    - /code-security/repository-security-advisories/adding-a-collaborator-to-a-repository-security-advisory
-    - /code-security/repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability
-    - /code-security/repository-security-advisories/publishing-a-repository-security-advisory
-    - /code-security/repository-security-advisories/editing-a-repository-security-advisory
-    - /code-security/repository-security-advisories/withdrawing-a-repository-security-advisory
-    - /code-security/repository-security-advisories/removing-a-collaborator-from-a-repository-security-advisory
-    - /code-security/repository-security-advisories/best-practices-for-writing-repository-security-advisories
+    - /code-security/security-advisories/repository-security-advisories/about-coordinated-disclosure-of-security-vulnerabilities
+    - /code-security/security-advisories/global-security-advisories/about-the-github-advisory-database
+    - /code-security/security-advisories/global-security-advisories/about-global-security-advisories
+    - /code-security/security-advisories/repository-security-advisories/about-repository-security-advisories
+    - /code-security/security-advisories/repository-security-advisories/creating-a-repository-security-advisory
+    - /code-security/security-advisories/repository-security-advisories/adding-a-collaborator-to-a-repository-security-advisory
+    - /code-security/security-advisories/repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability
+    - /code-security/security-advisories/repository-security-advisories/publishing-a-repository-security-advisory
+    - /code-security/security-advisories/repository-security-advisories/editing-a-repository-security-advisory
+    - /code-security/security-advisories/repository-security-advisories/withdrawing-a-repository-security-advisory
+    - /code-security/security-advisories/repository-security-advisories/removing-a-collaborator-from-a-repository-security-advisory
+    - /code-security/security-advisories/guidance-on-reporting-and-writing/best-practices-for-writing-repository-security-advisories
 
 # Feature available on dotcom and GHES 3.3+, so articles available on GHAE and earlier GHES hidden to hide the learning track
 dependabot_alerts:
diff --git a/translations/pt-BR/data/reusables/repositories/security-advisories-republishing.md b/translations/pt-BR/data/reusables/repositories/security-advisories-republishing.md
index 53ec781b02..c2f7cd1471 100644
--- a/translations/pt-BR/data/reusables/repositories/security-advisories-republishing.md
+++ b/translations/pt-BR/data/reusables/repositories/security-advisories-republishing.md
@@ -1,9 +1 @@
----
-ms.openlocfilehash: 0ac903914a15eacb9f6db488c4c1cac01a6411e6
-ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
-ms.translationtype: HT
-ms.contentlocale: pt-BR
-ms.lasthandoff: 09/11/2022
-ms.locfileid: "145084204"
----
-Você também pode usar {% data variables.product.prodname_security_advisories %} para republicar as informações de uma vulnerabilidade de segurança que você já revelou em outro lugar, copiando e colando as informações de vulnerabilidade em uma nova consultoria de segurança.
+You can also use repository security advisories to republish the details of a security vulnerability that you have already disclosed elsewhere by copying and pasting the details of the vulnerability into a new security advisory.
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 be855d2fd0..3d68fc424b 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
@@ -90,6 +90,8 @@ Google | Google OAuth Refresh Token | google_oauth_refresh_token{% endif %}
 Grafana | Grafana API Key | grafana_api_key
 HashiCorp | Terraform Cloud / Enterprise API Token | terraform_api_token
 HashiCorp | HashiCorp Vault Batch Token | hashicorp_vault_batch_token
+{%- ifversion fpt or ghec or ghes > 3.8 or ghae > 3.8 %}
+HashiCorp | HashiCorp Vault Root Service Token | hashicorp_vault_root_service_token{% endif %}
 HashiCorp | HashiCorp Vault Service Token | hashicorp_vault_service_token
 Hubspot | Hubspot API Key | hubspot_api_key
 Intercom | Intercom Access Token | intercom_access_token
diff --git a/translations/pt-BR/data/reusables/security-advisory/security-advisory-overview.md b/translations/pt-BR/data/reusables/security-advisory/security-advisory-overview.md
index 009c664aed..3c4c6a964f 100644
--- a/translations/pt-BR/data/reusables/security-advisory/security-advisory-overview.md
+++ b/translations/pt-BR/data/reusables/security-advisory/security-advisory-overview.md
@@ -1,9 +1 @@
----
-ms.openlocfilehash: aa9f7cd0b911ddfc6e144c7c91cecd0374286b13
-ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
-ms.translationtype: HT
-ms.contentlocale: pt-BR
-ms.lasthandoff: 09/10/2022
-ms.locfileid: "145127286"
----
-{% data variables.product.prodname_security_advisories %} permite que os mantenedores de repositório discutam e consertem uma vulnerabilidade de segurança em um projeto. Depois de colaborar em uma correção, os responsáveis pelo repositório podem publicar o aviso de segurança para divulgar publicamente a vulnerabilidade de segurança na comunidade do projeto. Ao publicar avisos de segurança, os responsáveis pelo repositório facilitam para a comunidade a atualização das dependências do pacote e a pesquisa sobre o impacto das vulnerabilidades de segurança.
+Repository security advisories allow repository maintainers to privately discuss and fix a security vulnerability in a project. After collaborating on a fix, repository maintainers can publish the security advisory to publicly disclose the security vulnerability to the project's community. By publishing security advisories, repository maintainers make it easier for their community to update package dependencies and research the impact of the security vulnerabilities.
diff --git a/translations/pt-BR/data/reusables/security-overview/permissions.md b/translations/pt-BR/data/reusables/security-overview/permissions.md
index 2cf85d19c5..43dd55172d 100644
--- a/translations/pt-BR/data/reusables/security-overview/permissions.md
+++ b/translations/pt-BR/data/reusables/security-overview/permissions.md
@@ -1 +1 @@
-Organization owners and security managers can access the security overview for organizations{% ifversion ghec or ghes > 3.4 or ghae > 3.4 %} and view their organization's repositories via the enterprise-level security overview. Enterprise owners can use the enterprise-level security overview to view all repositories in their enterprise's organizations{% endif %}. Members of a team can see the security overview for repositories that the team has admin privileges for.
+{% ifversion not fpt %}Organization owners and security managers can access the organization-level security overview{% ifversion ghec or ghes > 3.4 or ghae > 3.4 %} and view alerts across multiple organizations via the enterprise-level security overview. Enterprise owners can only view repositories and alerts for organizations where they are added as an organization owner or security manager{% endif %}. {% ifversion ghec or ghes > 3.6 or ghae > 3.6 %}Organization members can access the organization-level security overview to view results for repositories where they have admin privileges or have been granted access to security alerts.{% else %}Members of a team can see the security overview for repositories that the team has admin privileges for.{% endif %}{% endif %}
diff --git a/translations/zh-CN/content/account-and-profile/managing-subscriptions-and-notifications-on-github/viewing-and-triaging-notifications/managing-notifications-from-your-inbox.md b/translations/zh-CN/content/account-and-profile/managing-subscriptions-and-notifications-on-github/viewing-and-triaging-notifications/managing-notifications-from-your-inbox.md
index ba60987068..a006c11816 100644
--- a/translations/zh-CN/content/account-and-profile/managing-subscriptions-and-notifications-on-github/viewing-and-triaging-notifications/managing-notifications-from-your-inbox.md
+++ b/translations/zh-CN/content/account-and-profile/managing-subscriptions-and-notifications-on-github/viewing-and-triaging-notifications/managing-notifications-from-your-inbox.md
@@ -161,7 +161,7 @@ For example, to see notifications from the octo-org organization, use `org:octo-
 
 ## {% data variables.product.prodname_dependabot %} custom filters
 
-{% ifversion fpt or ghec or ghes > 3.2 %}
+{% ifversion fpt or ghec or ghes %}
 If you use {% data variables.product.prodname_dependabot %} to keep your dependencies up-to-date, you can use and save these custom filters:
 - `is:repository_vulnerability_alert` to show notifications for {% data variables.product.prodname_dependabot_alerts %}.
 - `reason:security_alert` to show notifications for {% data variables.product.prodname_dependabot_alerts %} and security update pull requests.
@@ -170,7 +170,7 @@ If you use {% data variables.product.prodname_dependabot %} to keep your depende
 For more information about {% data variables.product.prodname_dependabot %}, see "[About {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)."
 {% endif %}
 
-{% ifversion ghes < 3.3 or ghae %}
+{% ifversion ghae %}
 
 If you use {% data variables.product.prodname_dependabot %} to tell you about insecure dependencies, you can use and save these custom filters to show notifications for {% data variables.product.prodname_dependabot_alerts %}:
 - `is:repository_vulnerability_alert` 
diff --git a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/about-your-organizations-profile.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/about-your-organizations-profile.md
index a2124b6092..e90733dfb6 100644
--- a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/about-your-organizations-profile.md
+++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/about-your-organizations-profile.md
@@ -24,7 +24,7 @@ Organizations that use {% data variables.product.prodname_ghe_cloud %} can confi
 To confirm your organization's identity and display a "Verified" badge on your organization profile page, you can verify your organization's domains with {% data variables.product.prodname_dotcom %}. For more information, see "[Verifying or approving a domain for your organization](/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization)."
 {% endif %}
 
-{% ifversion fpt or ghes > 3.2 or ghec %}
+{% ifversion fpt or ghes or ghec %}
 ![Sample organization profile page](/assets/images/help/organizations/org_profile_with_overview.png)
 {% else %}
 ![Sample organization profile page](/assets/images/help/profile/org_profile.png)
diff --git a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/setting-your-profile-to-private.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/setting-your-profile-to-private.md
index 9ef85f8450..401f6b29e2 100644
--- a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/setting-your-profile-to-private.md
+++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/setting-your-profile-to-private.md
@@ -1,56 +1,62 @@
 ---
-title: Setting your profile to private
-intro: 'A private profile displays only limited information, and hides some activity.'
+title: 将配置文件设置为私密
+intro: 专用配置文件仅显示有限的信息，并隐藏了一些活动。
 versions:
   fpt: '*'
 topics:
   - Profiles
 shortTitle: Set profile to private
+ms.openlocfilehash: c00718c84d99de95a9ca1352f32954279906451d
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: zh-CN
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148007886'
 ---
-## About private profiles
+## 关于私密配置文件
 
-To hide parts of your profile page, you can make your profile private. This also hides your activity in various social features on {% data variables.product.prodname_dotcom_the_website %}. A private profile hides information from all users, and there is currently no option to allow specified users to see your activity.
+若要隐藏配置文件页的某些部分，可以将配置文件设置为私密。 这还会隐藏你在 {% data variables.product.prodname_dotcom_the_website %} 上的各种社交功能中的活动。 私密配置文件对所有用户隐藏信息，目前没有允许指定用户查看你的活动的选项。
 
-After making your profile private, you can still view all your information when you visit your own profile.
+将配置文件设置为私密后，你仍可在访问自己的配置文件时查看所有信息。
 
-Private profiles cannot receive sponsorships under [{% data variables.product.prodname_sponsors %}](/sponsors/getting-started-with-github-sponsors/about-github-sponsors). To be eligible for {% data variables.product.prodname_sponsors %}, your profile cannot be private.
+私密配置文件收不到 [{% data variables.product.prodname_sponsors %}](/sponsors/getting-started-with-github-sponsors/about-github-sponsors) 的赞助。 要想获得 {% data variables.product.prodname_sponsors %} 赞助资格，配置文件不能设置为私密。
 
-## Differences between private and public profiles
+## 私密配置文件和公共配置文件之间的差异
 
-When your profile is private, the following content is hidden from your profile page:
+当配置文件设置为私密时，配置文件页中会隐藏以下内容：
 
-- Achievements and highlights.
-- Activity overview and activity feed.
-- Contribution graph.
-- Follower and following counts.
-- Follow and Sponsor buttons.
-- Organization memberships.
-- Stars, projects, packages, and sponsoring tabs.
+- 成就和亮点。
+- 活动概述和活动源。
+- 贡献图。
+- 关注者和关注计数。
+- “关注”和“赞助”按钮。
+- 组织成员身份。
+- 星级、项目、包和赞助选项卡。
 
 {% note %}
 
-**Note**: When your profile is private, some optional fields are still publicly visible, such as the README, biography, and profile photo.
+注意：当配置文件设置为私密时，一些可选字段仍然是公开可见的，例如自述文件、传记和个人资料照片。
 
 {% endnote %}
 
-## Changes to reporting on your activities
+## 对活动报告所做的更改
 
-By making your profile private, you will not remove or hide past activity; this setting only applies to your activity while the private setting is enabled.
+通过将配置文件设置为私密，不会删除或隐藏过去的活动；此设置仅适用于启用了私密设置时的活动。
 
-When your profile is private, your {% data variables.product.prodname_dotcom_the_website %} activity will not appear in the following locations:
+配置文件设置为私密后，{% data variables.product.prodname_dotcom_the_website %} 活动不会出现在以下位置：
 
-- Activity feeds for other users.
-- Discussions leaderboards.
-- The [Trending](https://github.com/trending) page.
+- 其他用户的活动源。
+- 讨论排行榜。
+- [趋势](https://github.com/trending)页面。
 
 {% note %}
 
-**Note**: Your activity on public repositories will still be publicly visible to anyone viewing those repositories, and some activity data may still be available through the {% data variables.product.prodname_dotcom %} API.
+注意：你在公共存储库上的活动仍将对查看这些存储库的任何人公开可见，并且某些活动数据可能仍可通过 {% data variables.product.prodname_dotcom %} API 获得。
 
 {% endnote %}
 
-## Changing your profile's privacy settings
+## 更改配置文件的隐私设置
 
 {% data reusables.user-settings.access_settings %}
-1. Under "Contributions & Activity", select the checkbox next to **Make profile private and hide activity**.
+1. 在“贡献和活动”下，选中“将配置文件设置为私密并隐藏活动”旁边的复选框。
 {% data reusables.user-settings.update-preferences %}
diff --git a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-settings-on-your-profile/why-are-my-contributions-not-showing-up-on-my-profile.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-settings-on-your-profile/why-are-my-contributions-not-showing-up-on-my-profile.md
index 3e24053ec8..fa16c3f01b 100644
--- a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-settings-on-your-profile/why-are-my-contributions-not-showing-up-on-my-profile.md
+++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-settings-on-your-profile/why-are-my-contributions-not-showing-up-on-my-profile.md
@@ -69,11 +69,15 @@ The email address in the `From:` field is the address that was set in the [local
 
 If the email address used for the commit is not connected to your account on {% data variables.location.product_location %}, {% ifversion ghae %}change the email address used to author commits in Git. For more information, see "[Setting your commit email address](/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address#setting-your-commit-email-address-in-git)."{% else %}you must [add the email address](/articles/adding-an-email-address-to-your-github-account) to your account on {% data variables.location.product_location %}. Your contributions graph will be rebuilt automatically when you add the new address.{% endif %}
 
-{% warning %}
+{% ifversion fpt or ghec %}
+{% note %}
 
-**Warning**: Generic email addresses, such as `jane@computer.local`, cannot be added to {% data variables.product.prodname_dotcom %} accounts. If you use such an email for your commits, the commits will not be linked to your {% data variables.product.prodname_dotcom %} profile and will not show up in your contribution graph.
+**Note**: If you use a {% data variables.enterprise.prodname_managed_user %}, you cannot add additional email addresses to the account, even if multiple email addresses are registered with your identity provider (IdP). Therefore, only commits that are authored by the primary email address registered with your IdP can be associated with your {% data variables.enterprise.prodname_managed_user %}.
 
-{% endwarning %}
+{% endnote %}
+{% endif %}
+
+Generic email addresses, such as `jane@computer.local`, cannot be added to {% data variables.product.prodname_dotcom %} accounts and linked to commits. If you've authored any commits using a generic email address, the commits will not be linked to your {% data variables.product.prodname_dotcom %} profile and will not show up in your contribution graph.
 
 ### Commit was not made in the default or `gh-pages` branch
 
diff --git a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/index.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/index.md
index 63b2860091..d72f863eba 100644
--- a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/index.md
+++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/index.md
@@ -1,6 +1,6 @@
 ---
 title: Setting up and managing your personal account on GitHub
-intro: You can manage settings for your personal account on {% ifversion fpt or ghec or ghes %}{% data variables.location.product_location %}{% elsif ghae %}{% data variables.product.product_name %}{% endif %}, including email preferences, access to personal repositories, and organization memberships. You can also manage the account itself.
+intro: 'You can manage settings for your personal account on {% ifversion fpt or ghec or ghes %}{% data variables.location.product_location %}{% elsif ghae %}{% data variables.product.product_name %}{% endif %}, including email preferences, access to personal repositories, and organization memberships. You can also manage the account itself.'
 shortTitle: Personal accounts
 redirect_from:
   - /categories/setting-up-and-managing-your-github-user-account
diff --git a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-accessibility-settings.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-accessibility-settings.md
index 20771e8187..68a58042b1 100644
--- a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-accessibility-settings.md
+++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-accessibility-settings.md
@@ -1,7 +1,7 @@
 ---
 title: Managing accessibility settings
 shortTitle: Manage accessibility settings
-intro: "{% data variables.product.product_name %}'s user interface can adapt to your vision, hearing, motor, cognitive, or learning needs."
+intro: '{% data variables.product.product_name %}''s user interface can adapt to your vision, hearing, motor, cognitive, or learning needs.'
 versions:
   feature: keyboard-shortcut-accessibility-setting
 redirect_from:
diff --git a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-security-and-analysis-settings-for-your-personal-account.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-security-and-analysis-settings-for-your-personal-account.md
index 23259e074e..52815b7a7d 100644
--- a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-security-and-analysis-settings-for-your-personal-account.md
+++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-security-and-analysis-settings-for-your-personal-account.md
@@ -1,10 +1,10 @@
 ---
-title: 管理个人帐户的安全和分析设置
-intro: '您可以控制功能以保护 {% data variables.product.prodname_dotcom %} 上项目的安全并分析其中的代码。'
+title: Managing security and analysis settings for your personal account
+intro: 'You can control features that secure and analyze the code in your projects on {% data variables.product.prodname_dotcom %}.'
 versions:
   fpt: '*'
   ghec: '*'
-  ghes: '>3.2'
+  ghes: '*'
 topics:
   - Accounts
 redirect_from:
@@ -12,47 +12,43 @@ redirect_from:
   - /github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-security-and-analysis-settings-for-your-user-account
   - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-security-and-analysis-settings-for-your-user-account
 shortTitle: Manage security & analysis
-ms.openlocfilehash: 61d1944219fd1b75f476c7aef8305018c85735c5
-ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
-ms.translationtype: HT
-ms.contentlocale: zh-CN
-ms.lasthandoff: 09/11/2022
-ms.locfileid: '145164780'
 ---
-## 关于安全性和分析设置的管理
+## About management of security and analysis settings
 
-{% data variables.product.prodname_dotcom %} 可保护您的仓库。 本主题介绍如何管理所有现有或新仓库的安全和分析功能。
+{% data variables.product.prodname_dotcom %} can help secure your repositories. This topic tells you how you can manage the security and analysis features for all your existing or new repositories.
 
-您仍然可以管理单个仓库的安全和分析功能。 有关详细信息，请参阅“[管理存储库的安全和分析设置](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)”。
+You can still manage the security and analysis features for individual repositories. For more information, see "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)."
 
-你还可以查看个人帐户上所有活动的安全日志。 有关详细信息，请参阅“[查看安全日志](/authentication/keeping-your-account-and-data-secure/reviewing-your-security-log)”。
+You can also review the security log for all activity on your personal account. For more information, see "[Reviewing your security log](/authentication/keeping-your-account-and-data-secure/reviewing-your-security-log)."
 
 {% data reusables.security.some-security-and-analysis-features-are-enabled-by-default %}
 
 {% data reusables.security.security-and-analysis-features-enable-read-only %}
 
-有关存储库级安全性的概述，请参阅“[保护存储库](/code-security/getting-started/securing-your-repository)”。
+For an overview of repository-level security, see "[Securing your repository](/code-security/getting-started/securing-your-repository)."
 
-## 启用或禁用现有仓库的功能
+## Enabling or disabling features for existing repositories
 
-{% data reusables.user-settings.access_settings %} {% data reusables.user-settings.security-analysis %}
-3. 在“代码安全和分析”下，单击功能右侧的“全部禁用”或“全部启用” 。
-  {% ifversion ghes > 3.2 %}![用于“配置安全和分析”功能的“全部启用”或“全部禁用”按钮](/assets/images/enterprise/3.3/settings/security-and-analysis-disable-or-enable-all.png){% else %}![用于“配置安全和分析”功能的“全部启用”或“全部禁用”按钮](/assets/images/help/settings/security-and-analysis-disable-or-enable-all.png){% endif %}
-6. （可选）默认情况下为您拥有的新存储库启用该功能。
-  {% ifversion ghes > 3.2 %}![用于新建存储库的“默认启用”选项](/assets/images/enterprise/3.3/settings/security-and-analysis-enable-by-default-in-modal.png){% else %}![用于新建存储库的“默认启用”选项](/assets/images/help/settings/security-and-analysis-enable-by-default-in-modal.png){% endif %}
-7. 单击“禁用功能”或“启用功能”，以为所拥有的所有存储库禁用或启用该功能 。
-  {% ifversion ghes > 3.2 %}![用于禁用或启用功能的按钮](/assets/images/enterprise/3.3/settings/security-and-analysis-enable-dependency-graph.png){% else %}![用于禁用或启用功能的按钮](/assets/images/help/settings/security-and-analysis-enable-dependency-graph.png){% endif %}
+{% data reusables.user-settings.access_settings %}
+{% data reusables.user-settings.security-analysis %}
+3. Under "Code security and analysis", to the right of the feature, click **Disable all** or **Enable all**.
+  {% ifversion ghes %}!["Enable all" or "Disable all" button for "Configure security and analysis" features](/assets/images/enterprise/3.3/settings/security-and-analysis-disable-or-enable-all.png){% else %}!["Enable all" or "Disable all" button for "Configure security and analysis" features](/assets/images/help/settings/security-and-analysis-disable-or-enable-all.png){% endif %}
+6. Optionally, enable the feature by default for new repositories that you own.
+  {% ifversion ghes %}!["Enable by default" option for new repositories](/assets/images/enterprise/3.3/settings/security-and-analysis-enable-by-default-in-modal.png){% else %}!["Enable by default" option for new repositories](/assets/images/help/settings/security-and-analysis-enable-by-default-in-modal.png){% endif %}
+7. Click **Disable FEATURE** or **Enable FEATURE** to disable or enable the feature for all the repositories you own.
+  {% ifversion ghes %}![Button to disable or enable feature](/assets/images/enterprise/3.3/settings/security-and-analysis-enable-dependency-graph.png){% else %}![Button to disable or enable feature](/assets/images/help/settings/security-and-analysis-enable-dependency-graph.png){% endif %}
 
 {% data reusables.security.displayed-information %}
 
-## 对新仓库启用或禁用功能
+## Enabling or disabling features for new repositories
 
-{% data reusables.user-settings.access_settings %} {% data reusables.user-settings.security-analysis %}
-3. 在“Code security and analysis（代码安全和分析）”下，在功能右侧，默认为您拥有的新存储库启用或禁用该功能。
-  {% ifversion ghes > 3.2 %}![用于启用或禁用新建存储库功能的复选框](/assets/images/enterprise/3.3/settings/security-and-analysis-enable-or-disable-feature-checkbox.png){% else %}![用于启用或禁用新建存储库功能的复选框](/assets/images/help/settings/security-and-analysis-enable-or-disable-feature-checkbox.png){% endif %}
+{% data reusables.user-settings.access_settings %}
+{% data reusables.user-settings.security-analysis %}
+3. Under "Code security and analysis", to the right of the feature, enable or disable the feature by default for new repositories that you own.
+  {% ifversion ghes %}![Checkbox for enabling or disabling a feature for new repositories](/assets/images/enterprise/3.3/settings/security-and-analysis-enable-or-disable-feature-checkbox.png){% else %}![Checkbox for enabling or disabling a feature for new repositories](/assets/images/help/settings/security-and-analysis-enable-or-disable-feature-checkbox.png){% endif %}
 
-## 延伸阅读
+## Further reading
 
-- “[关于依赖项图](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)”
-- “[关于 {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)”
-- “[自动更新依赖项](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically)”
+- "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)"
+- "[About {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)"
+- "[Keeping your dependencies updated automatically](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically)"
diff --git a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-your-cookie-preferences-for-githubs-enterprise-marketing-pages.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-your-cookie-preferences-for-githubs-enterprise-marketing-pages.md
index c0e2f95e7a..672c241996 100644
--- a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-your-cookie-preferences-for-githubs-enterprise-marketing-pages.md
+++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-your-cookie-preferences-for-githubs-enterprise-marketing-pages.md
@@ -9,12 +9,12 @@ versions:
 topics:
   - Accounts
 shortTitle: Manage cookie preferences
-ms.openlocfilehash: f2fdbcf8bd552902e7db491aa1b3c6622c5673ab
-ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794
+ms.openlocfilehash: 44f0324a91f8447a10947d5f5c7be111241ad091
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: zh-CN
-ms.lasthandoff: 09/09/2022
-ms.locfileid: '147760918'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148108025'
 ---
 ## 关于企业营销页面的 Cookie 首选项
 
diff --git a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-your-theme-settings.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-your-theme-settings.md
index 9725f22439..584121c0e5 100644
--- a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-your-theme-settings.md
+++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-your-theme-settings.md
@@ -1,6 +1,6 @@
 ---
-title: 管理主题设置
-intro: '通过设置主题首选项以遵循系统设置或始终使用浅色模式或深色模式，您可以管理 {% data variables.product.product_name %} 的外观，'
+title: Managing your theme settings
+intro: 'You can manage how {% data variables.product.product_name %} looks to you by setting a theme preference that either follows your system settings or always uses a light or dark mode.'
 versions:
   fpt: '*'
   ghae: '*'
@@ -13,52 +13,51 @@ redirect_from:
   - /github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings
   - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings
 shortTitle: Manage theme settings
-ms.openlocfilehash: 6251b265d99271f58a4ad02d2f6cb7fdf722cb6b
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
-ms.translationtype: HT
-ms.contentlocale: zh-CN
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147580445'
 ---
-为了选择和灵活地使用 {% data variables.product.product_name %}，您可以配置主题设置来更改 {% data variables.product.product_name %} 的外观。 您可以在浅色和深色两个主题中进行选择，也可以配置 {% data variables.product.product_name %} 遵循系统设置。
 
-您可能需要使用深色主题来减少某些设备的功耗，以在低光条件下减小眼睛的压力，或者因为您更喜欢主题的外观。
+For choice and flexibility in how and when you use {% data variables.product.product_name %}, you can configure theme settings to change how {% data variables.product.product_name %} looks to you. You can choose from themes that are light or dark, or you can configure {% data variables.product.product_name %} to follow your system settings.
 
-{% ifversion fpt or ghes > 3.2 or ghae or ghec %}如果你视力低下，你可能会受益于高对比度主题，其前景和背景元素之间的对比度更高。{% endif %}{% ifversion fpt or ghae or ghec %} 如果你有色盲，你可能会从我们的浅色和深色色盲主题中受益。
+You may want to use a dark theme to reduce power consumption on certain devices, to reduce eye strain in low-light conditions, or because you prefer how the theme looks.
+
+If you have low vision, you may benefit from a high contrast theme, with greater contrast between foreground and background elements.{% ifversion fpt or ghae or ghec %} If you have colorblindness, you may benefit from our light and dark colorblind themes.
 
 {% endif %}
 
-{% data reusables.user-settings.access_settings %} {% data reusables.user-settings.appearance-settings %}
+{% data reusables.user-settings.access_settings %}
+{% data reusables.user-settings.appearance-settings %}
 
-1. 在“Theme mode（主题模式）”下，选择下拉菜单，然后单击主题首选项。
+1. Under "Theme mode", select the drop-down menu, then click a theme preference.
 
-   ![“主题模式”下的下拉菜单，用于选择主题首选项](/assets/images/help/settings/theme-mode-drop-down-menu.png)
-1. 单击想要使用的主题。
-    - 如果您选择单个主题，请单击一个主题。
+   ![Drop-down menu under "Theme mode" for selection of theme preference](/assets/images/help/settings/theme-mode-drop-down-menu.png)
+1. Click the theme you'd like to use.
+    - If you chose a single theme, click a theme.
 
-      {%- ifversion ghes = 3.5 %} {% note %}
+      {%- ifversion ghes = 3.5 %}
+      {% note %}
 
-      **注意**：在 {% data variables.product.product_name %} 3.5.0、3.5.1、3.5.2 和 3.5.3 中，浅色高对比度主题不可用。 此主题在 3.5.4 及更高版本中可用。 有关升级的详细信息，请联系站点管理员。
+      **Note**: The light high contrast theme was unavailable in {% data variables.product.product_name %} 3.5.0, 3.5.1, 3.5.2, and 3.5.3. The theme is available in 3.5.4 and later. For more information about upgrades, contact your site administrator.
 
-      有关确定所使用的 {% data variables.product.product_name %} 版本的详细信息，请参阅“[关于 {% data variables.product.prodname_docs %} 的版本](/get-started/learning-about-github/about-versions-of-github-docs#github-enterprise-server)”。
-      {% endnote %} {%- endif %}
+      For more information about determining the version of {% data variables.product.product_name %} you're using, see "[About versions of  {% data variables.product.prodname_docs %}](/get-started/learning-about-github/about-versions-of-github-docs#github-enterprise-server)."
+      {% endnote %}
+      {%- endif %}
 
-      {% ifversion fpt or ghes > 3.2 or ghae or ghec %}![用于选择单个主题的单选按钮](/assets/images/help/settings/theme-choose-a-single-theme-highcontrast.png){% else %}![用于选择单个主题的单选按钮](/assets/images/help/settings/theme-choose-a-single-theme.png){% endif %}
-    - 如果您选择遵循系统设置，请单击白天主题和夜间主题。
+      ![Radio buttons for the choice of a single theme](/assets/images/help/settings/theme-choose-a-single-theme-highcontrast.png)
+    - If you chose to follow your system settings, click a day theme and a night theme.
 
-      {% ifversion fpt or ghes > 3.2 or ghae or ghec %}![用于选择要与系统设置同步的主题的按钮](/assets/images/help/settings/theme-choose-a-day-and-night-theme-to-sync-highcontrast.png){% else %}![用于选择与系统设置同步的主题的按钮](/assets/images/help/settings/theme-choose-a-day-and-night-theme-to-sync.png){% endif %} {% ifversion fpt or ghec %}
-    - 如果您想选择当前处于公开测试阶段的主题，则首先需要通过功能预览启用它。 有关详细信息，请参阅“[使用功能预览探索抢先体验版](/get-started/using-github/exploring-early-access-releases-with-feature-preview)”。{% endif %}
+      ![Buttons for the choice of a theme to sync with the system setting](/assets/images/help/settings/theme-choose-a-day-and-night-theme-to-sync-highcontrast.png)
+    {% ifversion fpt or ghec %}
+    - If you would like to choose a theme which is currently in public beta, you will first need to enable it with feature preview. For more information, see "[Exploring early access releases with feature preview](/get-started/using-github/exploring-early-access-releases-with-feature-preview)."{% endif %}
 
 {% ifversion command-palette %}
 
 {% note %}
 
-注意：你还可以使用命令面板更改主题设置。 有关详细信息，请参阅“[{% data variables.product.prodname_command_palette %}](/get-started/using-github/github-command-palette)”。
+**Note:** You can also change your theme settings with the command palette. For more information, see "[{% data variables.product.prodname_command_palette %}](/get-started/using-github/github-command-palette)".
 
 {% endnote %}
 
 {% endif %}
 
-## 延伸阅读
+## Further reading
 
-- “[为 {% data variables.product.prodname_desktop %} 设置主题](/desktop/installing-and-configuring-github-desktop/setting-a-theme-for-github-desktop)”
+- "[Setting a theme for {% data variables.product.prodname_desktop %}](/desktop/installing-and-configuring-github-desktop/setting-a-theme-for-github-desktop)"
diff --git a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/permission-levels-for-a-personal-account-repository.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/permission-levels-for-a-personal-account-repository.md
index c45ea9a3ca..e113259b91 100644
--- a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/permission-levels-for-a-personal-account-repository.md
+++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/permission-levels-for-a-personal-account-repository.md
@@ -1,6 +1,6 @@
 ---
-title: 个人帐户存储库的权限级别
-intro: 个人帐户拥有的存储库有两种权限级别：存储库所有者和协作者 。
+title: Permission levels for a personal account repository
+intro: 'A repository owned by a personal account has two permission levels: the repository owner and collaborators.'
 redirect_from:
   - /articles/permission-levels-for-a-user-account-repository
   - /github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository
@@ -14,84 +14,79 @@ versions:
 topics:
   - Accounts
 shortTitle: Repository permissions
-ms.openlocfilehash: e7c7a542204c7b1ce69bc19ac326fb248bbbff12
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
-ms.translationtype: HT
-ms.contentlocale: zh-CN
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147066304'
 ---
-## 关于个人帐户存储库的权限级别
+## About permissions levels for a personal account repository
 
-个人帐户拥有的存储库有一个所有者。 所有权权限无法与其他个人帐户共享。
+Repositories owned by personal accounts have one owner. Ownership permissions can't be shared with another personal account.
 
-还可以{% ifversion fpt or ghec %}邀请{% else %}添加{% endif %} {% data variables.product.product_name %} 上的用户成为存储库的协作者。 有关详细信息，请参阅“[邀请协作者访问个人存储库](/github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository)”。
+You can also {% ifversion fpt or ghec %}invite{% else %}add{% endif %} users on {% data variables.product.product_name %} to your repository as collaborators. For more information, see "[Inviting collaborators to a personal repository](/github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository)."
 
 {% tip %}
 
-提示：如果需要对个人帐户拥有的存储库实施更精细的访问控制，请考虑将存储库转让给组织。 有关详细信息，请参阅“[转让存储库](/github/administering-a-repository/transferring-a-repository#transferring-a-repository-owned-by-your-personal-account)”。
+**Tip:** If you require more granular access to a repository owned by your personal account, consider transferring the repository to an organization. For more information, see "[Transferring a repository](/github/administering-a-repository/transferring-a-repository#transferring-a-repository-owned-by-your-personal-account)."
 
 {% endtip %}
 
-## 所有者对个人帐户拥有的存储库的权限
+## Owner access for a repository owned by a personal account
 
-仓库所有者对仓库具有完全控制权。 除了任何协作者可以执行的操作外，仓库所有者还可以执行以下操作。
+The repository owner has full control of the repository. In addition to the actions that any collaborator can perform, the repository owner can perform the following actions.
 
-| 操作 | 详细信息 |
+| Action | More information |
 | :- | :- |
-| {% ifversion fpt or ghec %}邀请协作者{% else %}添加协作者{% endif %} | [邀请协作者加入个人存储库](/github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository) |
-| 更改仓库的可见性 | [设置存储库可见性](/github/administering-a-repository/setting-repository-visibility) |{% ifversion fpt or ghec %}
-| 限制与仓库的交互 | [限制存储库中的交互](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository) |{% endif %}
-| 重命名分支，包括默认分支 | [重命名分支](/github/administering-a-repository/renaming-a-branch) |
-| 合并受保护分支上的拉取请求（即使没有批准审查） | [关于受保护分支](/github/administering-a-repository/about-protected-branches) |
-| 删除仓库 | [删除存储库](/repositories/creating-and-managing-repositories/deleting-a-repository) |
-| 管理仓库的主题 | [使用主题对存储库分类](/github/administering-a-repository/classifying-your-repository-with-topics) |{% ifversion fpt or ghec %}
-| 管理仓库的安全性和分析设置 | [管理存储库的安全和分析设置](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository) |{% endif %}{% ifversion fpt or ghec %}
-| 为私有仓库启用依赖项图 | [探索存储库的依赖项](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository#enabling-and-disabling-the-dependency-graph-for-a-private-repository) |{% endif %}
-| 删除和恢复包 | [删除和恢复包](/packages/learn-github-packages/deleting-and-restoring-a-package) |
-| 自定义仓库的社交媒体预览 | [自定义存储库的社交媒体预览](/github/administering-a-repository/customizing-your-repositorys-social-media-preview) |
-| 从仓库创建模板 | [创建模板存储库](/github/creating-cloning-and-archiving-repositories/creating-a-template-repository) |
-| {% data variables.product.prodname_dependabot_alerts %} 的控制访问| [管理存储库的安全性和分析设置](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts) |{% ifversion fpt or ghec %}
-| 忽略仓库中的 {% data variables.product.prodname_dependabot_alerts %} | [查看和更新 {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts) |
-| 管理私有仓库的数据使用 | [管理专用存储库的数据使用设置](/get-started/privacy-on-github/managing-data-use-settings-for-your-private-repository)|{% endif %}
-| 定义仓库的代码所有者 | “[关于代码所有者](/github/creating-cloning-and-archiving-repositories/about-code-owners)” |
-| 存档仓库 | [存档存储库](/repositories/archiving-a-github-repository/archiving-repositories) |{% ifversion fpt or ghec %}
-| 创建安全通告 | [关于 {% data variables.product.prodname_security_advisories %}](/github/managing-security-vulnerabilities/about-github-security-advisories) |
-| 显示赞助按钮 | [在存储库中显示赞助者按钮](/github/administering-a-repository/displaying-a-sponsor-button-in-your-repository) |{% endif %}
-| 允许或禁止自动合并拉取请求 | [管理存储库中拉取请求的自动合并](/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository) | 
+| {% ifversion fpt or ghec %}Invite collaborators{% else %}Add collaborators{% endif %} | "[Inviting collaborators to a personal repository](/github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository)" |
+| Change the visibility of the repository | "[Setting repository visibility](/github/administering-a-repository/setting-repository-visibility)" |{% ifversion fpt or ghec %}
+| Limit interactions with the repository | "[Limiting interactions in your repository](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository)" |{% endif %}
+| Rename a branch, including the default branch | "[Renaming a branch](/github/administering-a-repository/renaming-a-branch)" |
+| Merge a pull request on a protected branch, even if there are no approving reviews | "[About protected branches](/github/administering-a-repository/about-protected-branches)" |
+| Delete the repository | "[Deleting a repository](/repositories/creating-and-managing-repositories/deleting-a-repository)" |
+| Manage the repository's topics | "[Classifying your repository with topics](/github/administering-a-repository/classifying-your-repository-with-topics)" |{% ifversion fpt or ghec %}
+| Manage security and analysis settings for the repository | "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)" |{% endif %}{% ifversion fpt or ghec %}
+| Enable the dependency graph for a private repository | "[Exploring the dependencies of a repository](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository#enabling-and-disabling-the-dependency-graph-for-a-private-repository)" |{% endif %}
+| Delete and restore packages | "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)" |
+| 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)" |
+| Control access to {% data variables.product.prodname_dependabot_alerts %}| "[Managing security and analysis settings for your repository](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts)" |{% ifversion fpt or ghec %}
+| Dismiss {% data variables.product.prodname_dependabot_alerts %} in the repository | "[Viewing and updating {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts)" |
+| Manage data use for a private repository | "[Managing data use settings for your private repository](/get-started/privacy-on-github/managing-data-use-settings-for-your-private-repository)"|{% endif %}
+| Define code owners for the repository | "[About code owners](/github/creating-cloning-and-archiving-repositories/about-code-owners)" |
+| Archive the repository | "[Archiving repositories](/repositories/archiving-a-github-repository/archiving-repositories)" |{% ifversion fpt or ghec %}
+| Create security advisories | "[About repository security advisories](/github/managing-security-vulnerabilities/about-github-security-advisories)" |
+| Display a sponsor button | "[Displaying a sponsor button in your repository](/github/administering-a-repository/displaying-a-sponsor-button-in-your-repository)" |{% endif %}
+| Allow or disallow auto-merge for pull requests | "[Managing auto-merge for pull requests in your repository](/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository)" | 
+| Manage webhooks and deploy keys	| "[Managing deploy keys](/developers/overview/managing-deploy-keys#deploy-keys)" |
 
-## 协作者对个人帐户拥有的存储库的权限
+## Collaborator access for a repository owned by a personal account
 
-个人仓库的协作者可以拉取（读取）仓库的内容并向仓库推送（写入）更改。
+Collaborators on a personal repository can pull (read) the contents of the repository and push (write) changes to the repository.
 
 {% note %}
 
-注意：在专用存储库中，存储库所有者只能为协作者授予写入权限。 协作者不能对个人帐户拥有的存储库具有只读权限。
+**Note:** In a private repository, repository owners can only grant write access to collaborators. Collaborators can't have read-only access to repositories owned by a personal account.
 
 {% endnote %}
 
-协作者还可以执行以下操作。
+Collaborators can also perform the following actions.
 
-| 操作 | 详细信息 |
+| Action | More information |
 | :- | :- |
-| 为存储库创建分支 | [关于分支](/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks) |
-| 重命名除默认分支以外的分支 | [重命名分支](/github/administering-a-repository/renaming-a-branch) |
-| 在仓库中创建、编辑和删除关于提交、拉取请求和议题的评论 | <ul><li>[关于问题](/github/managing-your-work-on-github/about-issues)</li><li>[评论拉取请求](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request)</li><li>[管理中断性注释](/communities/moderating-comments-and-conversations/managing-disruptive-comments)</li></ul> |
-| 在仓库中创建、分配、关闭和重新打开议题 | [使用问题管理工作](/github/managing-your-work-on-github/managing-your-work-with-issues) |
-| 在仓库中管理议题和拉取请求的标签 | [标记问题和拉取请求](/github/managing-your-work-on-github/labeling-issues-and-pull-requests) |
-| 在仓库中管理议题和拉取请求的里程碑 | “[创建和编辑议题及拉取请求的里程碑](/github/managing-your-work-on-github/creating-and-editing-milestones-for-issues-and-pull-requests)” |
-| 将仓库中的议题或拉取请求标记为重复项 | [关于重复的问题和拉取请求](/github/managing-your-work-on-github/about-duplicate-issues-and-pull-requests) |
-| 在仓库中创建、合并和关闭拉取请求 | [通过拉取请求提议工作更改](/github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests) |
-| 启用或禁用自动合并拉取请求 | [自动合并拉取请求](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request)
-| 将建议的更改应用于仓库中的拉取请求 |[在拉取请求中加入反馈](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/incorporating-feedback-in-your-pull-request) |
-| 从仓库的复刻创建拉取请求 | “[从复刻创建拉取请求](/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request-from-a-fork)” |
-| 提交影响拉取请求可合并性的拉取请求审查 | [查看拉取请求中的建议更改](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request) |
-| 为仓库创建和编辑 wiki | [关于 Wiki](/communities/documenting-your-project-with-wikis/about-wikis) |
-| 为仓库创建和编辑发行版 | [管理存储库中的发行版](/github/administering-a-repository/managing-releases-in-a-repository) |
-| 作为仓库的代码所有者 | “[关于代码所有者](/articles/about-code-owners)” |{% ifversion fpt or ghae or ghec %}
-| 发布、查看或安装包 | [发布和管理包](/github/managing-packages-with-github-packages/publishing-and-managing-packages) |{% endif %}
-| 作为仓库协作者删除自己 | [从协作者的存储库中删除你自己](/github/setting-up-and-managing-your-github-user-account/removing-yourself-from-a-collaborators-repository) |
+| Fork the repository | "[About forks](/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks)" |
+| Rename a branch other than the default branch | "[Renaming a branch](/github/administering-a-repository/renaming-a-branch)" |
+| Create, edit, and delete comments on commits, pull requests, and issues in the repository | <ul><li>"[About issues](/github/managing-your-work-on-github/about-issues)"</li><li>"[Commenting on a pull request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request)"</li><li>"[Managing disruptive comments](/communities/moderating-comments-and-conversations/managing-disruptive-comments)"</li></ul> |
+| Create, assign, close, and re-open issues in the repository | "[Managing your work with issues](/github/managing-your-work-on-github/managing-your-work-with-issues)" |
+| Manage labels for issues and pull requests in the repository | "[Labeling issues and pull requests](/github/managing-your-work-on-github/labeling-issues-and-pull-requests)" |
+| Manage milestones for issues and pull requests in the repository | "[Creating and editing milestones for issues and pull requests](/github/managing-your-work-on-github/creating-and-editing-milestones-for-issues-and-pull-requests)" |
+| Mark an issue or pull request in the repository as a duplicate | "[About duplicate issues and pull requests](/github/managing-your-work-on-github/about-duplicate-issues-and-pull-requests)" |
+| Create, merge, and close pull requests in the repository | "[Proposing changes to your work with pull requests](/github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests)" |
+| Enable and disable auto-merge for a pull request | "[Automatically merging a pull request](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request)"
+| Apply suggested changes to pull requests in the repository |"[Incorporating feedback in your pull request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/incorporating-feedback-in-your-pull-request)" |
+| Create a pull request from a fork of the repository | "[Creating a pull request from a fork](/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request-from-a-fork)" |
+| Submit a review on a pull request that affects the mergeability of the pull request | "[Reviewing proposed changes in a pull request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request)" |
+| Create and edit a wiki for the repository | "[About wikis](/communities/documenting-your-project-with-wikis/about-wikis)" |
+| Create and edit releases for the repository | "[Managing releases in a repository](/github/administering-a-repository/managing-releases-in-a-repository)" |
+| Act as a code owner for the repository | "[About code owners](/articles/about-code-owners)" |{% ifversion fpt or ghae or ghec %}
+| Publish, view, or install packages | "[Publishing and managing packages](/github/managing-packages-with-github-packages/publishing-and-managing-packages)" |{% endif %}
+| Remove themselves as collaborators on the repository | "[Removing yourself from a collaborator's repository](/github/setting-up-and-managing-your-github-user-account/removing-yourself-from-a-collaborators-repository)" |
 
-## 延伸阅读
+## Further reading
 
-- [组织的存储库角色](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)
+- "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)"
diff --git a/translations/zh-CN/content/actions/creating-actions/metadata-syntax-for-github-actions.md b/translations/zh-CN/content/actions/creating-actions/metadata-syntax-for-github-actions.md
index 5409856a9d..6fd1dab0b3 100644
--- a/translations/zh-CN/content/actions/creating-actions/metadata-syntax-for-github-actions.md
+++ b/translations/zh-CN/content/actions/creating-actions/metadata-syntax-for-github-actions.md
@@ -231,19 +231,11 @@ For example, this `cleanup.js` will only run on Linux-based runners:
 
 ### `runs.steps`
 
-{% ifversion fpt or ghes > 3.2 or ghae or ghec %}
 **Required** The steps that you plan to run in this action. These can be either `run` steps or `uses` steps.
-{% else %}
-**Required** The steps that you plan to run in this action.
-{% endif %}
 
 #### `runs.steps[*].run`
 
-{% ifversion fpt or ghes > 3.2 or ghae or ghec %}
 **Optional** The command you want to run. This can be inline or a script in your action repository:
-{% else %}
-**Required** The command you want to run. This can be inline or a script in your action repository:
-{% endif %}
 
 {% raw %}
 ```yaml
@@ -269,11 +261,7 @@ For more information, see "[`github context`](/actions/reference/context-and-exp
 
 #### `runs.steps[*].shell`
 
-{% ifversion fpt or ghes > 3.2 or ghae or ghec %}
 **Optional** The shell where you want to run the command. You can use any of the shells listed [here](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepsshell). Required if `run` is set.
-{% else %}
-**Required** The shell where you want to run the command. You can use any of the shells listed [here](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepsshell). Required if `run` is set.
-{% endif %}
 
 {% ifversion fpt or ghes > 3.3 or ghae > 3.3 or ghec %}
 #### `runs.steps[*].if`
@@ -322,7 +310,6 @@ steps:
 
 **Optional**  Specifies the working directory where the command is run.
 
-{% ifversion fpt or ghes > 3.2 or ghae or ghec %}
 #### `runs.steps[*].uses`
 
 **Optional**  Selects an action to run as part of a step in your job. An action is a reusable unit of code. You can use an action defined in the same repository as the workflow, a public repository, or in a [published Docker container image](https://hub.docker.com/).
@@ -371,7 +358,6 @@ runs:
         middle_name: The
         last_name: Octocat
 ```
-{% endif %}
 
 {% ifversion ghes > 3.5 or ghae > 3.5 %}
 
diff --git a/translations/zh-CN/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-hashicorp-vault.md b/translations/zh-CN/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-hashicorp-vault.md
index 9d8f3e75a0..c952e2cf5a 100644
--- a/translations/zh-CN/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-hashicorp-vault.md
+++ b/translations/zh-CN/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-hashicorp-vault.md
@@ -1,7 +1,7 @@
 ---
-title: Configuring OpenID Connect in HashiCorp Vault
+title: 在 HashiCorp Vault 中配置 OpenID Connect
 shortTitle: OpenID Connect in HashiCorp Vault
-intro: Use OpenID Connect within your workflows to authenticate with HashiCorp Vault.
+intro: 在工作流程中使用 OpenID Connect 通过 HashiCorp Vault 进行身份验证。
 miniTocMaxHeadingLevel: 3
 versions:
   fpt: '*'
@@ -10,31 +10,35 @@ versions:
 type: tutorial
 topics:
   - Security
+ms.openlocfilehash: 174243818443709ee6ffe3b22aa668cff254266f
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: zh-CN
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148106627'
 ---
+{% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %}
 
-{% data reusables.actions.enterprise-beta %}
-{% data reusables.actions.enterprise-github-hosted-runners %}
+## 概述
 
-## Overview
+OpenID Connect (OIDC) 允许您的 {% data variables.product.prodname_actions %} 工作流程使用 HashiCorp Vault 进行身份验证以检索机密。
 
-OpenID Connect (OIDC) allows your {% data variables.product.prodname_actions %} workflows to authenticate with a HashiCorp Vault to retrieve secrets.
+本指南概述如何将 HashiCorp Vault 配置为信任作为联合标识的 {% data variables.product.prodname_dotcom %} 的 OIDC，并演示如何在 [hashicorp/vault-action](https://github.com/hashicorp/vault-action) 操作中使用此配置从 HashiCorp Vault 检索机密。
 
-This guide gives an overview of how to configure HashiCorp Vault to trust {% data variables.product.prodname_dotcom %}'s OIDC as a federated identity, and demonstrates how to use this configuration in the [hashicorp/vault-action](https://github.com/hashicorp/vault-action) action to retrieve secrets from HashiCorp Vault.
-
-## Prerequisites
+## 先决条件
 
 {% data reusables.actions.oidc-link-to-intro %}
 
 {% data reusables.actions.oidc-security-notice %}
 
-## Adding the identity provider to HashiCorp Vault
+## 将身份提供商添加到 HashiCorp Vault
 
-To use OIDC with HashiCorp Vault, you will need to add a trust configuration for the {% data variables.product.prodname_dotcom %} OIDC provider. For more information, see the HashiCorp Vault [documentation](https://www.vaultproject.io/docs/auth/jwt).
+要将 OIDC 与 HashiCorp Vault 配合使用，您需要为 {% data variables.product.prodname_dotcom %} OIDC 提供商添加信任配置。 有关详细信息，请参阅 HashiCorp Vault [文档](https://www.vaultproject.io/docs/auth/jwt)。
 
-To configure your Vault server to accept JSON Web Tokens (JWT) for authentication:
+将 Vault 服务器配置为接受 JSON Web 令牌 (JWT) 进行身份验证：
 
-1. Enable the JWT `auth` method, and use `write` to apply the configuration to your Vault. 
-  For `oidc_discovery_url` and `bound_issuer` parameters, use {% ifversion ghes %}`https://HOSTNAME/_services/token`{% else %}`https://token.actions.githubusercontent.com`{% endif %}. These parameters allow the Vault server to verify the received JSON Web Tokens (JWT) during the authentication process.
+1. 启用 JWT `auth` 方法，并使用 `write` 将配置应用于 Vault。 
+  对于 `oidc_discovery_url` 和 `bound_issuer` 参数，请使用 {% ifversion ghes %}`https://HOSTNAME/_services/token`{% else %}`https://token.actions.githubusercontent.com`{% endif %}。 这些参数使 Vault 服务器可以在身份验证过程中验证收到的 JSON Web 令牌 (JWT)。
 
     ```sh{:copy}
     vault auth enable jwt
@@ -45,7 +49,7 @@ To configure your Vault server to accept JSON Web Tokens (JWT) for authenticatio
       bound_issuer="{% ifversion ghes %}https://HOSTNAME/_services/token{% else %}https://token.actions.githubusercontent.com{% endif %}" \
       oidc_discovery_url="{% ifversion ghes %}https://HOSTNAME/_services/token{% else %}https://token.actions.githubusercontent.com{% endif %}"
     ```
-2. Configure a policy that only grants access to the specific paths your workflows will use to retrieve secrets. For more advanced policies, see the HashiCorp Vault [Policies documentation](https://www.vaultproject.io/docs/concepts/policies).
+2. 配置策略以便仅授予对工作流将用于检索机密的特定路径的访问权限。 有关更高级的策略，请参阅 HashiCorp Vault [策略文档](https://www.vaultproject.io/docs/concepts/policies)。
 
     ```sh{:copy}
     vault policy write myproject-production - <<EOF
@@ -56,7 +60,7 @@ To configure your Vault server to accept JSON Web Tokens (JWT) for authenticatio
     }
     EOF
     ```
-3. Configure roles to group different policies together. If the authentication is successful, these policies are attached to the resulting Vault access token.
+3. 配置角色以将不同策略分组在一起。 如果身份验证成功，这些策略会附加到生成的 Vault 访问令牌。
 
     ```sh{:copy}
     vault write auth/jwt/role/myproject-production -<<EOF
@@ -72,51 +76,51 @@ To configure your Vault server to accept JSON Web Tokens (JWT) for authenticatio
     EOF
     ```
 
-- `ttl` defines the validity of the resulting access token.
-- Ensure that the `bound_claims` parameter is defined for your security requirements, and has at least one condition. Optionally, you can also set the `bound_subject` as well as the `bound_audiences` parameter.
-- To check arbitrary claims in the received JWT payload, the `bound_claims` parameter contains a set of claims and their required values. In the above example, the role will accept any incoming authentication requests from the `repo-name` repository owned by the `user-or-org-name` account.
-- To see all the available claims supported by {% data variables.product.prodname_dotcom %}'s OIDC provider, see ["Configuring the OIDC trust with the cloud"](/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect#configuring-the-oidc-trust-with-the-cloud).
+- `ttl` 定义所生成的访问令牌的有效性。
+- 确保针对安全要求定义 `bound_claims` 参数，并且该参数至少有一个条件。 （可选）还可以设置 `bound_subject` 和 `bound_audiences` 参数。
+- 为了检查收到的 JWT 有效负载中的任意声明，`bound_claims` 参数包含一组声明及其所需值。 在上面的示例中，角色会接受来自 `user-or-org-name` 帐户拥有的 `repo-name` 存储库的任何传入身份验证请求。
+- 若要查看 {% data variables.product.prodname_dotcom %} 的 OIDC 提供程序支持的所有可用声明，请参阅[“通过云配置 OIDC 信任”](/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect#configuring-the-oidc-trust-with-the-cloud)。
 
-For more information, see the HashiCorp Vault [documentation](https://www.vaultproject.io/docs/auth/jwt).
+有关详细信息，请参阅 HashiCorp Vault [文档](https://www.vaultproject.io/docs/auth/jwt)。
 
-## Updating your {% data variables.product.prodname_actions %} workflow
+## 更新 {% data variables.product.prodname_actions %} 工作流程
 
-To update your workflows for OIDC, you will need to make two changes to your YAML:
-1. Add permissions settings for the token.
-2. Use the [`hashicorp/vault-action`](https://github.com/hashicorp/vault-action) action to exchange the OIDC token (JWT) for a cloud access token.
+要更新 OIDC 的工作流程，您需要对 YAML 进行两项更改：
+1. 为令牌添加权限设置。
+2. 使用操作 [`hashicorp/vault-action`](https://github.com/hashicorp/vault-action) 将 OIDC 令牌 (JWT) 交换为云访问令牌。
 
 
-To add OIDC integration to your workflows that allow them to access secrets in Vault, you will need to add the following code changes:
+要将 OIDC 集成添加到您的工作流程中，以允许他们访问 Vault 中的密钥，您需要添加以下代码更改：
 
-- Grant permission to fetch the token from the {% data variables.product.prodname_dotcom %} OIDC provider:
-  - The workflow needs `permissions:` settings with the `id-token` value set to `write`. This lets you fetch the OIDC token from every job in the workflow.
-- Request the JWT from the {% data variables.product.prodname_dotcom %} OIDC provider, and present it to HashiCorp Vault to receive an access token:
-  - You can use the [`hashicorp/vault-action`](https://github.com/hashicorp/vault-action) action to fetch the JWT and receive the access token from Vault, or you could use the [Actions toolkit](https://github.com/actions/toolkit/) to fetch the tokens for your job.
+- 授予从 {% data variables.product.prodname_dotcom %} OIDC 提供程序提取令牌的权限：
+  - 工作流需要将 `id-token` 值设置为 `write` 的 `permissions:` 设置。 这样，便可以从工作流中的每个作业中提取 OIDC 令牌。
+- 向 {% data variables.product.prodname_dotcom %} OIDC 提供商请求 JWT，并将其提供给 HashiCorp Vault 以接收访问令牌：
+  - 可以使用 [`hashicorp/vault-action`](https://github.com/hashicorp/vault-action) 操作提取 JWT 并从 Vault 接收访问令牌，也可以使用[操作工具包](https://github.com/actions/toolkit/) 提取作业的令牌。
 
-This example demonstrates how to use OIDC with the official action to request a secret from HashiCorp Vault.
+此示例演示如何将 OIDC 与官方操作结合使用，以向 HashiCorp Vault 请求机密。
 
-### Adding permissions settings
+### 添加权限设置
 
  {% data reusables.actions.oidc-permissions-token %}
 
 {% note %}
 
-**Note**:
+**注意**：
 
-When the `permissions` key is used, all unspecified permissions are set to _no access_, with the exception of the metadata scope, which always gets _read_ access. As a result, you may need to add other permissions, such as `contents: read`. See [Automatic token authentication](/actions/security-guides/automatic-token-authentication) for more information.
+使用 `permissions` 密钥时，所有未指定的权限都设置为无访问权限，但元数据范围除外，它始终拥有读取访问权限 。 因此，可能需要添加其他权限，例如 `contents: read`。 有关详细信息，请参阅[自动令牌身份验证](/actions/security-guides/automatic-token-authentication)。
 
 {% endnote %}
 
-### Requesting the access token
+### 请求访问令牌
 
-The `hashicorp/vault-action` action receives a JWT from the {% data variables.product.prodname_dotcom %} OIDC provider, and then requests an access token from your HashiCorp Vault instance to retrieve secrets. For more information, see the HashiCorp Vault GitHub Action [documentation](https://github.com/hashicorp/vault-action).
+`hashicorp/vault-action` 操作从 {% data variables.product.prodname_dotcom %} OIDC 提供程序接收 JWT，然后从 HashiCorp Vault 实例请求访问令牌以检索机密。 有关详细信息，请参阅 HashiCorp Vault GitHub 操作[文档](https://github.com/hashicorp/vault-action)。
 
-This example demonstrates how to create a job that requests a secret from HashiCorp Vault.
+此示例演示如何创建从 HashiCorp Vault请求机密的作业。
 
-- `<Vault URL>`: Replace this with the URL of your HashiCorp Vault.
-- `<Vault Namespace>`: Replace this with the Namespace you've set in HashiCorp Vault. For example: `admin`.
-- `<Role name>`: Replace this with the role you've set in the HashiCorp Vault trust relationship.
-- `<Secret-Path>`: Replace this with the path to the secret you're retrieving from HashiCorp Vault. For example: `secret/data/production/ci npmToken`.
+- `<Vault URL>`：将此替换为 HashiCorp Vault 的 URL。
+- `<Vault Namespace>`：将此值替换为在 HashiCorp Vault 中设置的命名空间。 例如：`admin`。
+- `<Role name>`：将此值替换为在 HashiCorp Vault 信任关系中设置的角色。
+- `<Secret-Path>`：将此值替换为从 HashiCorp Vault 检索的机密的路径。 例如：`secret/data/production/ci npmToken`。
 
 ```yaml{:copy}
 jobs:
@@ -142,19 +146,19 @@ jobs:
 
 {% note %}
 
-**Note**:
+**注意**：
 
-- If your Vault server is not accessible from the public network, consider using a self-hosted runner with other available Vault [auth methods](https://www.vaultproject.io/docs/auth). For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners)."
-- `<Vault Namespace>` must be set for a Vault Enterprise (including HCP Vault) deployment. For more information, see [Vault namespace](https://www.vaultproject.io/docs/enterprise/namespaces).
+- 如果无法从公共网络访问 Vault 服务器，请考虑将自承载运行程序与其他可用 Vault [身份验证方法](https://www.vaultproject.io/docs/auth)配合使用。 有关详细信息，请参阅[关于自承载运行器](/actions/hosting-your-own-runners/about-self-hosted-runners)。
+- 必须针对 Vault Enterprise（包括 HCP Vault）部署设置 `<Vault Namespace>`。 有关详细信息，请参阅 [Vault 命名空间](https://www.vaultproject.io/docs/enterprise/namespaces)。
 
 {% endnote %}
 
-### Revoking the access token
+### 撤销访问令牌
 
-By default, the Vault server will automatically revoke access tokens when their TTL is expired, so you don't have to manually revoke the access tokens. However, if you do want to revoke access tokens immediately after your job has completed or failed, you can manually revoke the issued token using the [Vault API](https://www.vaultproject.io/api/auth/token#revoke-a-token-self).
+默认情况下，Vault 服务器会在 TTL 过期时自动撤销访问令牌，因此无需手动撤销访问令牌。 但是，如果确实要在作业完成或失败后立即撤销访问令牌，则可以使用 [Vault API](https://www.vaultproject.io/api/auth/token#revoke-a-token-self) 手动撤销颁发的令牌。
 
-1. Set the `exportToken` option to `true` (default: `false`). This exports the issued Vault access token as an environment variable: `VAULT_TOKEN`.
-2. Add a step to call the [Revoke a Token (Self)](https://www.vaultproject.io/api/auth/token#revoke-a-token-self) Vault API to revoke the access token.
+1. 将 `exportToken` 选项设置为 `true`（默认值：`false`）。 这会将颁发的 Vault 访问令牌导出为环境变量：`VAULT_TOKEN`。
+2. 添加一个步骤以调用[撤销令牌（自行）](https://www.vaultproject.io/api/auth/token#revoke-a-token-self) Vault API 来撤销访问令牌。
 
 ```yaml{:copy}
 jobs:
@@ -183,4 +187,4 @@ jobs:
         run: |
           curl -X POST -sv -H "X-Vault-Token: {% raw %}${{ env.VAULT_TOKEN }}{% endraw %}" \
             <Vault URL>/v1/auth/token/revoke-self
-```
\ No newline at end of file
+```
diff --git a/translations/zh-CN/content/actions/examples/using-the-github-cli-on-a-runner.md b/translations/zh-CN/content/actions/examples/using-the-github-cli-on-a-runner.md
index 351014a933..3dd3e14c47 100644
--- a/translations/zh-CN/content/actions/examples/using-the-github-cli-on-a-runner.md
+++ b/translations/zh-CN/content/actions/examples/using-the-github-cli-on-a-runner.md
@@ -1,7 +1,7 @@
 ---
-title: Using the GitHub CLI on a runner
+title: 在运行器上使用 GitHub CLI
 shortTitle: Use the GitHub CLI on a runner
-intro: 'How to use advanced {% data variables.product.prodname_actions %} features for continuous integration (CI).'
+intro: '如何使用高级 {% data variables.product.prodname_actions %} 功能进行持续集成 (CI)。'
 versions:
   fpt: '*'
   ghes: '> 3.1'
@@ -10,40 +10,34 @@ versions:
 type: how_to
 topics:
   - Workflows
+ms.openlocfilehash: e0787d09cd194de0038d259c1aff777cc91a4a6a
+ms.sourcegitcommit: bf11c3e08cbb5eab6320e0de35b32ade6d863c03
+ms.translationtype: HT
+ms.contentlocale: zh-CN
+ms.lasthandoff: 10/27/2022
+ms.locfileid: '148111583'
 ---
-
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## Example overview
+## 示例概述
 
-{% data reusables.actions.example-workflow-intro-ci %} When this workflow is triggered, it automatically runs a script that checks whether the {% data variables.product.prodname_dotcom %} Docs site has any broken links. If any broken links are found, the workflow uses the {% data variables.product.prodname_dotcom %} CLI to create a {% data variables.product.prodname_dotcom %} issue with the details.
+{% data reusables.actions.example-workflow-intro-ci %} 此工作流触发后，会自动运行一个脚本，用于检查 {% data variables.product.prodname_dotcom %} Docs 站点是否有任何损坏的链接。 如果找到任何损坏的链接，工作流将使用 {% data variables.product.prodname_dotcom %} CLI 创建包含详细信息的 {% data variables.product.prodname_dotcom %} 问题。
 
 {% data reusables.actions.example-diagram-intro %}
 
-![Overview diagram of workflow steps](/assets/images/help/images/overview-actions-using-cli-ci-example.png)
+![工作流步骤概述图](/assets/images/help/images/overview-actions-using-cli-ci-example.png)
 
-## Features used in this example
+## 此示例中使用的功能
 
 {% data reusables.actions.example-table-intro %}
 
-| **Feature**  | **Implementation** |
+| **功能**  | **实现** |
 | --- | --- |
-{% data reusables.actions.cron-table-entry %}
-{% data reusables.actions.permissions-table-entry %}
-{% data reusables.actions.if-conditions-table-entry %}
-{% data reusables.actions.secrets-table-entry %}
-{% data reusables.actions.checkout-action-table-entry %}
-{% data reusables.actions.setup-node-table-entry %}
-| Using a third-party action: | [`peter-evans/create-issue-from-file`](https://github.com/peter-evans/create-issue-from-file)|
-| Running shell commands on the runner: | [`run`](/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idstepsrun) |
-| Running a script on the runner: | Using `script/check-english-links.js` |
-| Generating an output file: | Piping the output using the `>` operator |
-| Checking for existing issues using {% data variables.product.prodname_cli %}: | [`gh issue list`](https://cli.github.com/manual/gh_issue_list) |
-| Commenting on an issue using {% data variables.product.prodname_cli %}: | [`gh issue comment`](https://cli.github.com/manual/gh_issue_comment) |
+{% data reusables.actions.cron-table-entry %} {% data reusables.actions.permissions-table-entry %} {% data reusables.actions.if-conditions-table-entry %} {% data reusables.actions.secrets-table-entry %} {% data reusables.actions.checkout-action-table-entry %} {% data reusables.actions.setup-node-table-entry %} | 使用第三方操作：| [`peter-evans/create-issue-from-file`](https://github.com/peter-evans/create-issue-from-file)| | 在运行器上运行 shell 命令：| [`run`](/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idstepsrun) | | 在运行器上运行脚本：| 使用 `script/check-english-links.js` | | 生成输出文件：| 使用 `>` 运算符通过管道传输输出 | | 使用 {% data variables.product.prodname_cli %} 检查现有问题：| [`gh issue list`](https://cli.github.com/manual/gh_issue_list) | | 使用 {% data variables.product.prodname_cli %} 对问题进行注释：| [`gh issue comment`](https://cli.github.com/manual/gh_issue_comment) |
 
-## Example workflow
+## 示例工作流
 
-{% data reusables.actions.example-docs-engineering-intro %} [`check-all-english-links.yml`](https://github.com/github/docs/blob/main/.github/workflows/check-all-english-links.yml).
+{% data reusables.actions.example-docs-engineering-intro %} [`check-all-english-links.yml`](https://github.com/github/docs/blob/6e01c0653836c10d7e092a17566a2c88b10504ce/.github/workflows/check-all-english-links.yml)。
 
 {% data reusables.actions.note-understanding-example %}
 
@@ -178,15 +172,15 @@ jobs:
 </tbody>
 </table>
 
-## Understanding the example
+## 了解示例
 
 {% data reusables.actions.example-explanation-table-intro %}
 
 <table style="table-layout: fixed;">
 <thead>
   <tr>
-    <th style="width:60%"><b>Code</b></th>
-    <th style="width:40%"><b>Explanation</b></th>
+    <th style="width:60%"><b>代码</b></th>
+    <th style="width:40%"><b>解释</b></th>
   </tr>
 </thead>
 <tbody>
@@ -214,10 +208,10 @@ on:
 </td>
 <td>
 
-Defines the `workflow_dispatch` and `scheduled` as triggers for the workflow:
+将 `workflow_dispatch` 和 `scheduled` 定义为工作流的触发器：
 
-* The `workflow_dispatch` lets you manually run this workflow from the UI. For more information, see [`workflow_dispatch`](/actions/using-workflows/events-that-trigger-workflows#workflow_dispatch).
-* The `schedule` event lets you use `cron` syntax to define a regular interval for automatically triggering the workflow. For more information, see [`schedule`](/actions/reference/events-that-trigger-workflows#schedule).
+* 通过 `workflow_dispatch`，可从 UI 手动运行此工作流。 有关详细信息，请参阅 [`workflow_dispatch`](/actions/using-workflows/events-that-trigger-workflows#workflow_dispatch)。
+* 通过 `schedule` 事件，可使用 `cron` 语法来定义自动触发工作流的定期间隔。 有关详细信息，请参阅 [`schedule`](/actions/reference/events-that-trigger-workflows#schedule)。
 </td>
 </tr>
 <tr>
@@ -231,7 +225,7 @@ permissions:
 </td>
 <td>
 
-Modifies the default permissions granted to `GITHUB_TOKEN`. This will vary depending on the needs of your workflow. For more information, see "[Assigning permissions to jobs](/actions/using-jobs/assigning-permissions-to-jobs)."
+修改授予 `GITHUB_TOKEN` 的默认权限。 这将因工作流的需求而异。 有关详细信息，请参阅“[为作业分配权限](/actions/using-jobs/assigning-permissions-to-jobs)”。
 </td>
 </tr>
 <tr>
@@ -243,7 +237,7 @@ jobs:
 </td>
 <td>
 
-Groups together all the jobs that run in the workflow file.
+将工作流文件中运行的所有作业组合在一起。
 </td>
 </tr>
 <tr>
@@ -256,7 +250,7 @@ Groups together all the jobs that run in the workflow file.
 </td>
 <td>
 
-Defines a job with the ID `check_all_english_links`, and the name `Check all links`, that is stored within the `jobs` key.
+定义 ID 为 `check_all_english_links`、名称为 `Check all links` 的作业，该作业存储在 `jobs` 密钥中。
 </td>
 </tr>
 <tr>
@@ -268,7 +262,7 @@ if: github.repository == 'github/docs-internal'
 </td>
 <td>
 
-Only run the `check_all_english_links` job if the repository is named `docs-internal` and is within the `github` organization. Otherwise, the job is marked as _skipped_.
+仅当存储库名为 `docs-internal` 且位于 `github` 组织内时，才运行 `check_all_english_links` 作业。 否则，作业会被标记为“跳过”。
 </td>
 </tr>
 <tr>
@@ -280,7 +274,7 @@ runs-on: ubuntu-latest
 </td>
 <td>
 
-Configures the job to run on an Ubuntu Linux runner. This means that the job will execute on a fresh virtual machine hosted by {% data variables.product.prodname_dotcom %}. For syntax examples using other runners, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idruns-on)."
+配置作业在 Ubuntu Linux 运行器上运行。 这意味着作业将在 {% data variables.product.prodname_dotcom %}. 托管的新虚拟机上执行。 有关使用其他运行器的语法示例，请参阅“[{% data variables.product.prodname_actions %} 的工作流语法](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idruns-on)”。
 </td>
 </tr>
 <tr>
@@ -296,7 +290,7 @@ Configures the job to run on an Ubuntu Linux runner. This means that the job wil
 </td>
 <td>
 
-Creates custom environment variables, and redefines the built-in `GITHUB_TOKEN` variable to use a custom [secret](/actions/security-guides/encrypted-secrets). These variables will be referenced later in the workflow.
+创建自定义环境变量，并重新定义内置的 `GITHUB_TOKEN` 变量以使用自定义[机密](/actions/security-guides/encrypted-secrets)。 稍后将在工作流中引用这些变量。
 </td>
 </tr>
 <tr>
@@ -308,7 +302,7 @@ Creates custom environment variables, and redefines the built-in `GITHUB_TOKEN`
 </td>
 <td>
 
-Groups together all the steps that will run as part of the `check_all_english_links` job. Each job in the workflow has its own `steps` section.
+将作为 `check_all_english_links` 作业一部分运行的所有步骤组合在一起。 工作流中的每个作业都有其自己的 `steps` 部分。
 </td>
 </tr>
 <tr>
@@ -321,7 +315,7 @@ Groups together all the steps that will run as part of the `check_all_english_li
 </td>
 <td>
 
-The `uses` keyword tells the job to retrieve the action named `actions/checkout`. This is an action that checks out your repository and downloads it to the runner, allowing you to run actions against your code (such as testing tools). You must use the checkout action any time your workflow will run against the repository's code or you are using an action defined in the repository.
+`uses` 关键字指示作业检索名为 `actions/checkout` 的操作。 这是检出仓库并将其下载到运行器的操作，允许针对您的代码运行操作（例如测试工具）。 只要工作流程针对仓库的代码运行，或者您使用仓库中定义的操作，您都必须使用检出操作。
 </td>
 </tr>
 <tr>
@@ -337,7 +331,7 @@ The `uses` keyword tells the job to retrieve the action named `actions/checkout`
 </td>
 <td>
 
-This step uses the `actions/setup-node` action to install the specified version of the `node` software package on the runner, which gives you access to the `npm` command.
+此步骤使用 `actions/setup-node` 操作在运行器上安装指定版本的 `node` 软件包，以便你可访问 `npm` 命令。
 </td>
 </tr>
 <tr>
@@ -352,7 +346,7 @@ This step uses the `actions/setup-node` action to install the specified version
 </td>
 <td>
 
-The `run` keyword tells the job to execute a command on the runner. In this case, the `npm ci` and `npm run build` commands are run as separate steps to install and build the Node.js application in the repository.
+`run` 关键字指示作业在运行器上执行命令。 在这种情况下，`npm ci` 和 `npm run build` 命令作为单独的步骤运行，用于在存储库中安装和生成 Node.js 应用程序。
 </td>
 </tr>
 <tr>
@@ -366,7 +360,7 @@ The `run` keyword tells the job to execute a command on the runner. In this case
 </td>
 <td>
 
-This `run` command executes a script that is stored in the repository at `script/check-english-links.js`, and pipes the output to a file called `broken_links.md`.
+此 `run` 命令执行存储库 (`script/check-english-links.js`) 中存储的脚本，并通过管道将输出传递给名为 `broken_links.md` 的文件。
 </td>
 </tr>
 <tr>
@@ -385,7 +379,7 @@ This `run` command executes a script that is stored in the repository at `script
 </td>
 <td>
 
-If the `check-english-links.js` script detects broken links and returns a non-zero (failure) exit status, then use a [workflow command](/actions/using-workflows/workflow-commands-for-github-actions#setting-an-output-parameter) to set an output that has the value of the first line of the `broken_links.md` file (this is used the next step).
+如果 `check-english-links.js` 脚本检测到损坏的链接并返回非零（失败）退出状态，则使用[工作流命令](/actions/using-workflows/workflow-commands-for-github-actions#setting-an-output-parameter)设置具有 `broken_links.md` 文件第一行值的输出（下一步中会用到它）。
 </td>
 </tr>
 <tr>
@@ -407,7 +401,7 @@ If the `check-english-links.js` script detects broken links and returns a non-ze
 </td>
 <td>
 
-Uses the `peter-evans/create-issue-from-file` action to create a new {% data variables.product.prodname_dotcom %} issue. This example is pinned to a specific version of the action, using the `b4f9ee0a9d4abbfc6986601d9b1a4f8f8e74c77e` SHA.
+使用 `peter-evans/create-issue-from-file` 操作创建新的 {% data variables.product.prodname_dotcom %} 问题。 此示例使用 `b4f9ee0a9d4abbfc6986601d9b1a4f8f8e74c77e` SHA 固定到操作的特定版本。
 </td>
 </tr>
 <tr>
@@ -435,9 +429,9 @@ Uses the `peter-evans/create-issue-from-file` action to create a new {% data var
 </td>
 <td>
 
-Uses [`gh issue list`](https://cli.github.com/manual/gh_issue_list) to locate the previously created issue from earlier runs. This is [aliased](https://cli.github.com/manual/gh_alias_set) to `gh list-reports` for simpler processing in later steps. To get the issue URL, the `jq` expression processes the resulting JSON output.
+使用 [`gh issue list`](https://cli.github.com/manual/gh_issue_list) 查找之前在早期运行中创建的问题。 在后续步骤中，为了简化处理，这将[别名](https://cli.github.com/manual/gh_alias_set)设置为 `gh list-reports`。 若要获取问题 URL，`jq` 表达式将处理生成的 JSON 输出。
 
-[`gh issue comment`](https://cli.github.com/manual/gh_issue_comment) is then used to add a comment to the new issue that links to the previous one.
+然后，使用 [`gh issue comment`](https://cli.github.com/manual/gh_issue_comment) 向链接到上一个问题的新问题添加注释。
 </td>
 </tr>
 <tr>
@@ -455,7 +449,7 @@ Uses [`gh issue list`](https://cli.github.com/manual/gh_issue_list) to locate th
 </td>
 <td>
 
-If an issue from a previous run is open and assigned to someone, then use [`gh issue comment`](https://cli.github.com/manual/gh_issue_comment) to add a comment with a link to the new issue.
+如果上一次运行中的问题已打开且已分配给某人，则使用 [`gh issue comment`](https://cli.github.com/manual/gh_issue_comment) 添加注释并附上指向新问题的链接。
 </td>
 </tr>
 <tr>
@@ -476,16 +470,16 @@ If an issue from a previous run is open and assigned to someone, then use [`gh i
 </td>
 <td>
 
-If an issue from a previous run is open and is not assigned to anyone, then:
+如果上一次运行中的问题已打开但未分配给任何人，则：
 
-* Use [`gh issue comment`](https://cli.github.com/manual/gh_issue_comment) to add a comment with a link to the new issue.
-* Use [`gh issue close`](https://cli.github.com/manual/gh_issue_close) to close the old issue.
-* Use [`gh issue edit`](https://cli.github.com/manual/gh_issue_edit) to edit the old issue to remove it from a specific {% data variables.product.prodname_dotcom %} project board.
+* 使用 [`gh issue comment`](https://cli.github.com/manual/gh_issue_comment) 添加一个的注释并附上指向新问题的链接。
+* 使用 [`gh issue close`](https://cli.github.com/manual/gh_issue_close) 关闭旧问题。
+* 使用 [`gh issue edit`](https://cli.github.com/manual/gh_issue_edit) 编辑旧问题，将其从特定的 {% data variables.product.prodname_dotcom %} 项目板中删除。
 </td>
 </tr>
 </tbody>
 </table>
 
-## Next steps
+## 后续步骤
 
 {% data reusables.actions.learning-actions %}
diff --git a/translations/zh-CN/content/actions/hosting-your-own-runners/about-self-hosted-runners.md b/translations/zh-CN/content/actions/hosting-your-own-runners/about-self-hosted-runners.md
index f66ea675e4..1f447b00f9 100644
--- a/translations/zh-CN/content/actions/hosting-your-own-runners/about-self-hosted-runners.md
+++ b/translations/zh-CN/content/actions/hosting-your-own-runners/about-self-hosted-runners.md
@@ -69,13 +69,10 @@ You can use any machine as a self-hosted runner as long at it meets these requir
 * The machine has enough hardware resources for the type of workflows you plan to run. The self-hosted runner application itself only requires minimal resources.
 * If you want to run workflows that use Docker container actions or service containers, you must use a Linux machine and Docker must be installed.
 
-{% ifversion fpt or ghes > 3.2 or ghec or ghae %}
 ## Autoscaling your self-hosted runners
 
 You can automatically increase or decrease the number of self-hosted runners in your environment in response to the webhook events you receive. For more information, see "[Autoscaling with self-hosted runners](/actions/hosting-your-own-runners/autoscaling-with-self-hosted-runners)."
 
-{% endif %}
-
 ## Usage limits
 
 There are some limits on {% data variables.product.prodname_actions %} usage when using self-hosted runners. These limits are subject to change.
@@ -249,7 +246,6 @@ codeload.github.com
 
 {% endnote %}
 
-
 {% endif %}
 
 ## Self-hosted runner security
diff --git a/translations/zh-CN/content/actions/hosting-your-own-runners/adding-self-hosted-runners.md b/translations/zh-CN/content/actions/hosting-your-own-runners/adding-self-hosted-runners.md
index 3ccfe230c8..3ea5bd9887 100644
--- a/translations/zh-CN/content/actions/hosting-your-own-runners/adding-self-hosted-runners.md
+++ b/translations/zh-CN/content/actions/hosting-your-own-runners/adding-self-hosted-runners.md
@@ -32,7 +32,7 @@ For more information, see "[About self-hosted runners](/github/automating-your-w
 {% endwarning %}
 {% endif %}
 
-{% ifversion fpt or ghec or ghes > 3.2 %}
+{% ifversion fpt or ghec or ghes %}
 
 You can set up automation to scale the number of self-hosted runners. For more information, see "[Autoscaling with self-hosted runners](/actions/hosting-your-own-runners/autoscaling-with-self-hosted-runners)."
 
diff --git a/translations/zh-CN/content/actions/hosting-your-own-runners/autoscaling-with-self-hosted-runners.md b/translations/zh-CN/content/actions/hosting-your-own-runners/autoscaling-with-self-hosted-runners.md
index 89ba5d874e..01c8c1cb9f 100644
--- a/translations/zh-CN/content/actions/hosting-your-own-runners/autoscaling-with-self-hosted-runners.md
+++ b/translations/zh-CN/content/actions/hosting-your-own-runners/autoscaling-with-self-hosted-runners.md
@@ -5,7 +5,7 @@ intro: You can automatically scale your self-hosted runners in response to webho
 versions:
   fpt: '*'
   ghec: '*'
-  ghes: '>3.2'
+  ghes: '*'
   ghae: '*'
 type: overview
 ---
diff --git a/translations/zh-CN/content/actions/learn-github-actions/contexts.md b/translations/zh-CN/content/actions/learn-github-actions/contexts.md
index 2629ad6dba..bdf5bb0bfb 100644
--- a/translations/zh-CN/content/actions/learn-github-actions/contexts.md
+++ b/translations/zh-CN/content/actions/learn-github-actions/contexts.md
@@ -608,7 +608,7 @@ jobs:
 
 ## `secrets` context
 
-The `secrets` context contains the names and values of secrets that are available to a workflow run. The `secrets` context is not available for composite actions. For more information about secrets, see "[Encrypted secrets](/actions/security-guides/encrypted-secrets)."
+The `secrets` context contains the names and values of secrets that are available to a workflow run. The `secrets` context is not available for composite actions due to security reasons. If you want to pass a secret to a composite action, you need to do it explicitly as an input. For more information about secrets, see "[Encrypted secrets](/actions/security-guides/encrypted-secrets)."
 
 `GITHUB_TOKEN` is a secret that is automatically created for every workflow run, and is always included in the `secrets` context. For more information, see "[Automatic token authentication](/actions/security-guides/automatic-token-authentication)."
 
diff --git a/translations/zh-CN/content/actions/security-guides/automatic-token-authentication.md b/translations/zh-CN/content/actions/security-guides/automatic-token-authentication.md
index a7a52992a7..ba4f2ce5f5 100644
--- a/translations/zh-CN/content/actions/security-guides/automatic-token-authentication.md
+++ b/translations/zh-CN/content/actions/security-guides/automatic-token-authentication.md
@@ -87,9 +87,7 @@ The following table shows the permissions granted to the `GITHUB_TOKEN` by defau
 | issues        | read/write  | none | read |
 | metadata      | read        | read | read |
 | packages      | read/write  | none | read |
-{%- ifversion fpt or ghec or ghes > 3.2 or ghae %}
 | pages         | read/write  | none | read |
-{%- endif %}
 | pull-requests | read/write  | none | read |
 | repository-projects | read/write | none | read |
 | security-events     | read/write | none | read |
diff --git a/translations/zh-CN/content/actions/security-guides/encrypted-secrets.md b/translations/zh-CN/content/actions/security-guides/encrypted-secrets.md
index cd8cf7b99a..693eb7bb34 100644
--- a/translations/zh-CN/content/actions/security-guides/encrypted-secrets.md
+++ b/translations/zh-CN/content/actions/security-guides/encrypted-secrets.md
@@ -7,6 +7,8 @@ redirect_from:
   - /actions/configuring-and-managing-workflows/creating-and-storing-encrypted-secrets
   - /actions/configuring-and-managing-workflows/using-variables-and-secrets-in-a-workflow
   - /actions/reference/encrypted-secrets
+  - /actions/managing-workflows/storing-secrets
+  
 miniTocMaxHeadingLevel: 3
 versions:
   fpt: '*'
diff --git a/translations/zh-CN/content/actions/using-github-hosted-runners/controlling-access-to-larger-runners.md b/translations/zh-CN/content/actions/using-github-hosted-runners/controlling-access-to-larger-runners.md
new file mode 100644
index 0000000000..97c4628d94
--- /dev/null
+++ b/translations/zh-CN/content/actions/using-github-hosted-runners/controlling-access-to-larger-runners.md
@@ -0,0 +1,50 @@
+---
+title: Controlling access to larger runners
+shortTitle: 'Control access to {% data variables.actions.hosted_runner %}s'
+intro: 'You can use policies to limit access to {% data variables.actions.hosted_runner %}s that have been added to an organization or enterprise.'
+product: '{% data reusables.gated-features.hosted-runners %}'
+versions:
+  feature: actions-hosted-runners
+type: tutorial
+---
+
+{% data reusables.actions.enterprise-beta %}
+{% data reusables.actions.enterprise-github-hosted-runners %}
+
+## About runner groups
+
+{% data reusables.actions.about-runner-groups %} {% ifversion fpt %}For more information, see the [{% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest/actions/using-github-hosted-runners/controlling-access-to-larger-runners).{% endif %}
+
+{% ifversion ghec or ghes or ghae %}
+
+## Creating a runner group for an organization
+
+{% data reusables.actions.hosted-runner-security-admonition %}
+{% data reusables.actions.creating-a-runner-group-for-an-organization %}
+
+## Creating a runner group for an enterprise
+
+{% data reusables.actions.hosted-runner-security-admonition %}
+{% data reusables.actions.creating-a-runner-group-for-an-enterprise %}
+
+{% endif %}
+
+## Changing the access policy of a runner group
+
+{% data reusables.actions.hosted-runner-security-admonition %}
+{% data reusables.actions.changing-the-access-policy-of-a-runner-group %}
+
+## Changing the name of a runner group
+
+{% data reusables.actions.changing-the-name-of-a-runner-group %}
+
+{% ifversion ghec or ghes or ghae %}
+## Moving a runner to a group
+
+{% data reusables.actions.moving-a-runner-to-a-group %}
+
+## Removing a runner group
+
+{% data reusables.actions.removing-a-runner-group %}
+
+{% endif %}
diff --git a/translations/zh-CN/content/actions/using-github-hosted-runners/using-larger-runners.md b/translations/zh-CN/content/actions/using-github-hosted-runners/using-larger-runners.md
index ed6b379be2..b0f14df4a0 100644
--- a/translations/zh-CN/content/actions/using-github-hosted-runners/using-larger-runners.md
+++ b/translations/zh-CN/content/actions/using-github-hosted-runners/using-larger-runners.md
@@ -1,11 +1,11 @@
 ---
 title: Using larger runners
-shortTitle: 'Larger runners'
+shortTitle: Larger runners
 intro: '{% data variables.product.prodname_dotcom %} offers larger runners with more RAM and CPU.'
 miniTocMaxHeadingLevel: 3
 product: '{% data reusables.gated-features.hosted-runners %}'
 versions:
-  feature: 'actions-hosted-runners'
+  feature: actions-hosted-runners
 ---
 
 ## Overview of {% data variables.actions.hosted_runner %}s
diff --git a/translations/zh-CN/content/actions/using-workflows/workflow-commands-for-github-actions.md b/translations/zh-CN/content/actions/using-workflows/workflow-commands-for-github-actions.md
index 190fb29822..710052edb7 100644
--- a/translations/zh-CN/content/actions/using-workflows/workflow-commands-for-github-actions.md
+++ b/translations/zh-CN/content/actions/using-workflows/workflow-commands-for-github-actions.md
@@ -139,8 +139,8 @@ The following table shows which toolkit functions are available within a workflo
 | Toolkit function | Equivalent workflow command |
 | ----------------- |  ------------- |
 | `core.addPath`    | Accessible using environment file `GITHUB_PATH` |
-| `core.debug`      | `debug` |{% ifversion fpt or ghes > 3.2 or ghae or ghec %}
-| `core.notice`     | `notice` |{% endif %}
+| `core.debug`      | `debug` |
+| `core.notice`     | `notice` |
 | `core.error`      | `error` |
 | `core.endGroup`   | `endgroup` |
 | `core.exportVariable` | Accessible using environment file `GITHUB_ENV` |
@@ -216,8 +216,6 @@ Write-Output "::debug::Set the Octocat variable"
 
 {% endpowershell %}
 
-{% ifversion fpt or ghes > 3.2 or ghae or ghec %}
-
 ## Setting a notice message
 
 Creates a notice message and prints the message to the log. {% data reusables.actions.message-annotation-explanation %}
@@ -245,7 +243,6 @@ Write-Output "::notice file=app.js,line=1,col=5,endColumn=7::Missing semicolon"
 ```
 
 {% endpowershell %}
-{% endif %}
 
 ## Setting a warning message
 
@@ -584,6 +581,8 @@ console.log("The running PID from the main action is: " +  process.env.STATE_pro
 
 During the execution of a workflow, the runner generates temporary files that can be used to perform certain actions. The path to these files are exposed via environment variables. You will need to use UTF-8 encoding when writing to these files to ensure proper processing of the commands. Multiple commands can be written to the same file, separated by newlines.
 
+Most commands in the following examples use double quotes for echoing strings, which will attempt to interpolate characters like `$` for shell variable names. To always use literal values in quoted strings, you can use single quotes instead.
+
 {% powershell %}
 
 {% note %}
diff --git a/translations/zh-CN/content/actions/using-workflows/workflow-syntax-for-github-actions.md b/translations/zh-CN/content/actions/using-workflows/workflow-syntax-for-github-actions.md
index 5c778a85ca..4969f6b53e 100644
--- a/translations/zh-CN/content/actions/using-workflows/workflow-syntax-for-github-actions.md
+++ b/translations/zh-CN/content/actions/using-workflows/workflow-syntax-for-github-actions.md
@@ -32,7 +32,7 @@ The name of your workflow. {% data variables.product.prodname_dotcom %} displays
 {% ifversion actions-run-name %}
 ## `run-name`
 
-The name for workflow runs generated from the workflow. {% data variables.product.prodname_dotcom %} displays the workflow run name in the list of workflow runs on your repository's "Actions" tab. If you omit `run-name`, the run name is set to event-specific information for the workflow run. For example, for a workflow triggered by a `push` or `pull_request` event, it is set as the commit message.
+The name for workflow runs generated from the workflow. {% data variables.product.prodname_dotcom %} displays the workflow run name in the list of workflow runs on your repository's "Actions" tab. If `run-name` is omitted or is only whitespace, then the run name is set to event-specific information for the workflow run. For example, for a workflow triggered by a `push` or `pull_request` event, it is set as the commit message.
 
 This value can include expressions and can reference the [`github`](/actions/learn-github-actions/contexts#github-context) and [`inputs`](/actions/learn-github-actions/contexts#inputs-context) contexts.
 
diff --git a/translations/zh-CN/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/about-supply-chain-security-for-your-enterprise.md b/translations/zh-CN/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/about-supply-chain-security-for-your-enterprise.md
index ee72a7d813..d0e0a0fefc 100644
--- a/translations/zh-CN/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/about-supply-chain-security-for-your-enterprise.md
+++ b/translations/zh-CN/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/about-supply-chain-security-for-your-enterprise.md
@@ -15,6 +15,6 @@ topics:
 
 You can allow users to identify their projects' dependencies by {% ifversion ghes %}enabling{% elsif ghae %}using{% endif %} the dependency graph for {% data variables.location.product_location %}. For more information, see "{% ifversion ghes %}[Enabling the dependency graph for your enterprise](/admin/code-security/managing-supply-chain-security-for-your-enterprise/enabling-the-dependency-graph-for-your-enterprise){% elsif ghae %}[About the dependency graph](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph){% endif %}."
 
-You can also allow users on {% data variables.location.product_location %} to find and fix vulnerabilities in their code dependencies by enabling {% data variables.product.prodname_dependabot_alerts %}{% ifversion ghes > 3.2 %} and {% data variables.product.prodname_dependabot_updates %}{% endif %}. For more information, see "[Enabling {% data variables.product.prodname_dependabot %} for your enterprise](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise)."
+You can also allow users on {% data variables.location.product_location %} to find and fix vulnerabilities in their code dependencies by enabling {% data variables.product.prodname_dependabot_alerts %}{% ifversion ghes %} and {% data variables.product.prodname_dependabot_updates %}{% endif %}. For more information, see "[Enabling {% data variables.product.prodname_dependabot %} for your enterprise](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise)."
 
 After you enable {% data variables.product.prodname_dependabot_alerts %}, you can view vulnerability data from the {% data variables.product.prodname_advisory_database %} on {% data variables.location.product_location %} and manually sync the data. For more information, see "[Viewing the vulnerability data for your enterprise](/admin/code-security/managing-supply-chain-security-for-your-enterprise/viewing-the-vulnerability-data-for-your-enterprise)."
diff --git a/translations/zh-CN/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/enabling-the-dependency-graph-for-your-enterprise.md b/translations/zh-CN/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/enabling-the-dependency-graph-for-your-enterprise.md
index d4d24029d2..eb2b304a79 100644
--- a/translations/zh-CN/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/enabling-the-dependency-graph-for-your-enterprise.md
+++ b/translations/zh-CN/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/enabling-the-dependency-graph-for-your-enterprise.md
@@ -16,7 +16,7 @@ topics:
 
 {% data reusables.dependabot.about-the-dependency-graph %} For more information, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)"
 
-After you enable the dependency graph for your enterprise, you can enable {% data variables.product.prodname_dependabot %} to detect insecure dependencies in your repository{% ifversion ghes > 3.2 %} and automatically fix the vulnerabilities{% endif %}. For more information, see "[Enabling {% data variables.product.prodname_dependabot %} for your enterprise](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise)."
+After you enable the dependency graph for your enterprise, you can enable {% data variables.product.prodname_dependabot %} to detect insecure dependencies in your repository{% ifversion ghes %} and automatically fix the vulnerabilities{% endif %}. For more information, see "[Enabling {% data variables.product.prodname_dependabot %} for your enterprise](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise)."
 
 {% ifversion ghes %}
 You can enable the dependency graph via the {% data variables.enterprise.management_console %} or the administrative shell. We recommend using the {% data variables.enterprise.management_console %} unless {% data variables.location.product_location %} uses clustering.
diff --git a/translations/zh-CN/content/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise.md b/translations/zh-CN/content/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise.md
index 8fa01e4e0d..d0b14cf91e 100644
--- a/translations/zh-CN/content/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise.md
+++ b/translations/zh-CN/content/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise.md
@@ -1,6 +1,6 @@
 ---
 title: Enabling Dependabot for your enterprise
-intro: 'You can allow users of {% data variables.location.product_location %} to find and fix vulnerabilities in code dependencies by enabling {% data variables.product.prodname_dependabot_alerts %}{% ifversion ghes > 3.2 %} and {% data variables.product.prodname_dependabot_updates %}{% endif %}.'
+intro: 'You can allow users of {% data variables.location.product_location %} to find and fix vulnerabilities in code dependencies by enabling {% data variables.product.prodname_dependabot_alerts %}{% ifversion ghes %} and {% data variables.product.prodname_dependabot_updates %}{% endif %}.'
 miniTocMaxHeadingLevel: 3
 shortTitle: Dependabot
 redirect_from:
@@ -26,7 +26,7 @@ topics:
 
 ## About {% data variables.product.prodname_dependabot %} for {% data variables.product.product_name %}
 
-{% data variables.product.prodname_dependabot %} helps users of {% data variables.location.product_location %} find and fix vulnerabilities in their dependencies.{% ifversion ghes > 3.2 %} You can enable {% data variables.product.prodname_dependabot_alerts %} to notify users about vulnerable dependencies and {% data variables.product.prodname_dependabot_updates %} to fix the vulnerabilities and keep dependencies updated to the latest version.
+{% data variables.product.prodname_dependabot %} helps users of {% data variables.location.product_location %} find and fix vulnerabilities in their dependencies.{% ifversion ghes %} You can enable {% data variables.product.prodname_dependabot_alerts %} to notify users about vulnerable dependencies and {% data variables.product.prodname_dependabot_updates %} to fix the vulnerabilities and keep dependencies updated to the latest version.
 
 ### About {% data variables.product.prodname_dependabot_alerts %}
 {% endif %}
@@ -51,7 +51,7 @@ When {% data variables.location.product_location %} receives information about a
 
 For repositories with {% data variables.product.prodname_dependabot_alerts %} enabled, scanning is triggered on any push to the default branch that contains a manifest file or lock file. Additionally, when a new vulnerability record is added to {% data variables.location.product_location %}, {% data variables.product.product_name %} scans all existing repositories on {% data variables.location.product_location %} and generates alerts for any repository that is vulnerable. For more information, see "[About {% data variables.product.prodname_dependabot_alerts %}](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)."
 
-{% ifversion ghes > 3.2 %}
+{% ifversion ghes %}
 ### About {% data variables.product.prodname_dependabot_updates %}
 
 {% data reusables.dependabot.beta-security-and-version-updates %}
@@ -124,7 +124,7 @@ After you enable {% data variables.product.prodname_dependabot_alerts %} for you
    ![Screenshot of the dropdown menu to enable updating vulnerable dependencies](/assets/images/enterprise/site-admin-settings/dependabot-updates-button.png)
 
 {% endif %}
-{% ifversion ghes > 3.2 %}
+{% ifversion ghes %}
 
 When you enable {% data variables.product.prodname_dependabot_alerts %}, you should consider also setting up {% data variables.product.prodname_actions %} for {% data variables.product.prodname_dependabot_security_updates %}. This feature allows developers to fix vulnerabilities in their dependencies. For more information, see "[Managing self-hosted runners for {% data variables.product.prodname_dependabot_updates %} on your enterprise](/admin/github-actions/enabling-github-actions-for-github-enterprise-server/managing-self-hosted-runners-for-dependabot-updates)."
 
diff --git a/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/configuring-host-keys-for-your-instance.md b/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/configuring-host-keys-for-your-instance.md
index 0930d0297d..6c4cc51477 100644
--- a/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/configuring-host-keys-for-your-instance.md
+++ b/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/configuring-host-keys-for-your-instance.md
@@ -2,7 +2,7 @@
 title: Configuring host keys for your instance
 shortTitle: Configure host keys
 intro: 'You can increase the security of {% data variables.location.product_location %} by configuring the algorithms that your instance uses to generate and advertise host keys for incoming SSH connections.'
-permissions: "Site administrators can configure the host keys for a {% data variables.product.product_name %} instance."
+permissions: 'Site administrators can configure the host keys for a {% data variables.product.product_name %} instance.'
 versions:
   ghes: '>= 3.6'
 type: how_to
diff --git a/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/configuring-ssh-connections-to-your-instance.md b/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/configuring-ssh-connections-to-your-instance.md
index c76cd8b27b..3d8a2df2fe 100644
--- a/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/configuring-ssh-connections-to-your-instance.md
+++ b/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/configuring-ssh-connections-to-your-instance.md
@@ -2,7 +2,7 @@
 title: Configuring SSH connections to your instance
 shortTitle: Configure SSH connections
 intro: 'You can increase the security of {% data variables.location.product_location %} by configuring the SSH algorithms that clients can use to establish a connection.'
-permissions: "Site administrators can configure SSH connections to a {% data variables.product.product_name %} instance."
+permissions: 'Site administrators can configure SSH connections to a {% data variables.product.product_name %} instance.'
 versions:
   ghes: '>= 3.6'
 type: how_to
diff --git a/translations/zh-CN/content/admin/enterprise-management/caching-repositories/about-repository-caching.md b/translations/zh-CN/content/admin/enterprise-management/caching-repositories/about-repository-caching.md
index 501700f870..814f55de38 100644
--- a/translations/zh-CN/content/admin/enterprise-management/caching-repositories/about-repository-caching.md
+++ b/translations/zh-CN/content/admin/enterprise-management/caching-repositories/about-repository-caching.md
@@ -1,26 +1,21 @@
 ---
-title: 关于存储库缓存
-intro: 您可以使用存储库缓存提高分散的团队和 CI 服务器场的 Git 读取操作性能。
+title: About repository caching
+intro: You can increase the performance of Git read operations for distributed teams and CI farms with repository caching.
 versions:
-  ghes: '>=3.3'
+  ghes: '*'
 type: overview
 topics:
   - Enterprise
-ms.openlocfilehash: 06a0dd3ba202c73f1ee035d61f7865fadd13b415
-ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
-ms.translationtype: HT
-ms.contentlocale: zh-CN
-ms.lasthandoff: 09/11/2022
-ms.locfileid: '145100053'
 ---
+
 {% data reusables.enterprise.repository-caching-release-phase %}
 
-如果您的团队和 CI 服务器场位于世界各地，则主要 {% data variables.product.prodname_ghe_server %} 实例的性能可能会降低。 虽然活动异地副本可以提高读取请求的性能，但这是以限制写入吞吐量为代价的。 要减少主实例上的负载并提高写入吞吐量性能，您可以配置存储库缓存，这是位于这些地理位置分散的客户端附近的存储库的异步只读镜像。 
+If you have teams and CI farms located around the world, you may experience reduced performance on your primary {% data variables.product.prodname_ghe_server %} instance. While active geo-replicas can improve the performance of read requests, this comes at the cost of limiting write throughput. To reduce load on your primary instance and improve write throughput performance, you can configure a repository cache, an asynchronous read-only mirror of repositories located near these geographically-distributed clients. 
 
-存储库缓存通过在 CI 场和分散的团队附近提供存储库数据，不再需要 {% data variables.product.product_name %} 通过长途网络链路多次传输相同的 Git 数据以服务于多个客户端。 例如，如果您的主实例位于北美，并且您在亚洲也拥有大量业务，那么在亚洲设置存储库缓存以供 CI 运行者使用将很有益。
+A repository cache eliminates the need for {% data variables.product.product_name %} to transmit the same Git data over a long-haul network link multiple times to serve multiple clients, by serving your repository data close to CI farms and distributed teams. For instance, if your primary instance is in North America and you also have a large presence in Asia, you will benefit from setting up the repository cache in Asia for use by CI runners there.
 
-存储库缓存侦听主实例（无论是单个实例还是异地复制的实例集），以查找对 Git 数据的更改。 CI 场和其他读取量大的使用者克隆并从存储库缓存（而不是主实例）中提取。 更改以定期间隔在网络上传播，每个缓存实例一次，而不是每个客户端一次。 Git 数据通常会在数据推送到主实例后的几分钟内在存储库缓存中可见。  {% ifversion ghes > 3.3 %}CI 系统可以使用 [`cache_sync` Webhook](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#cache_sync) 来响应缓存中可用的数据。{% endif %}
+The repository cache listens to the primary instance, whether that's a single instance or a geo-replicated set of instances, for changes to Git data. CI farms and other read-heavy consumers clone and fetch from the repository cache instead of the primary instance. Changes are propagated across the network, at periodic intervals, once per cache instance rather than once per client. Git data will typically be visible on the repository cache within several minutes after the data is pushed to the primary instance.  {% ifversion ghes > 3.3 %}The [`cache_sync` webhook](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#cache_sync) can be used by CI systems to react to data being available in the cache.{% endif %}
 
-您可以精细控制允许哪些存储库同步到存储库缓存。 Git 数据将仅复制到指定的位置。
+You have fine-grained control over which repositories are allowed to sync to the repository cache. Git data will only be replicated to the locations you specify.
 
-{% data reusables.enterprise.repository-caching-config-summary %} 有关详细信息，请参阅“[配置存储库缓存](/admin/enterprise-management/caching-repositories/configuring-a-repository-cache)”。
+{% data reusables.enterprise.repository-caching-config-summary %} For more information, see "[Configuring a repository cache](/admin/enterprise-management/caching-repositories/configuring-a-repository-cache)."
diff --git a/translations/zh-CN/content/admin/enterprise-management/caching-repositories/configuring-a-repository-cache.md b/translations/zh-CN/content/admin/enterprise-management/caching-repositories/configuring-a-repository-cache.md
index f7bed09686..26b4536eea 100644
--- a/translations/zh-CN/content/admin/enterprise-management/caching-repositories/configuring-a-repository-cache.md
+++ b/translations/zh-CN/content/admin/enterprise-management/caching-repositories/configuring-a-repository-cache.md
@@ -1,107 +1,105 @@
 ---
-title: 配置存储库缓存
-intro: 您可以通过创建新设备、将存储库缓存连接到主设备以及配置存储库网络到存储库缓存的副本来配置存储库缓存。
+title: Configuring a repository cache
+intro: 'You can configure a repository cache by creating a new appliance, connecting the repository cache to your primary appliance, and configuring replication of repository networks to the repository cache.'
 versions:
-  ghes: '>=3.3'
+  ghes: '*'
 type: how_to
 topics:
   - Enterprise
-ms.openlocfilehash: dced49e1e6795407e2e41f12275a310c3a98aaf1
-ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
-ms.translationtype: HT
-ms.contentlocale: zh-CN
-ms.lasthandoff: 09/10/2022
-ms.locfileid: '146332002'
 ---
+
 {% data reusables.enterprise.repository-caching-release-phase %}
 
-## 关于存储库缓存的配置
+## About configuration for repository caching
 
-{% data reusables.enterprise.repository-caching-config-summary %} 然后，您可以设置数据位置策略来控制将哪些存储库网络复制到存储库缓存。
+{% data reusables.enterprise.repository-caching-config-summary %} Then, you can set data location policies that govern which repository networks are replicated to the repository cache.
 
-群集不支持存储库缓存。
+Repository caching is not supported with clustering.
 
-## 存储库缓存的 DNS
+## DNS for repository caches
 
-主实例和存储库缓存应具有不同的 DNS 名称。 例如，如果主实例位于 `github.example.com`，则可以决定将缓存命名为 `europe-ci.github.example.com` 或 `github.asia.example.com`。
+The primary instance and repository cache should have different DNS names. For example, if your primary instance is at `github.example.com`, you might decide to name a cache `europe-ci.github.example.com` or `github.asia.example.com`.
 
-要让 CI 计算机从存储库缓存，而不是主实例中进行提取，可以使用 Git 的 `url.<base>.insteadOf` 配置设置。 有关详细信息，请参阅 Git 文档中的“[`git-config`](https://git-scm.com/docs/git-config#Documentation/git-config.txt-urlltbasegtinsteadOf)”。 
+To have your CI machines fetch from the repository cache instead of the primary instance, you can use Git's `url.<base>.insteadOf` configuration setting. For more information, see [`git-config`](https://git-scm.com/docs/git-config#Documentation/git-config.txt-urlltbasegtinsteadOf) in the Git documentation. 
 
-例如，CI 计算机的全局 `.gitconfig` 包含这些行。
+For example, the global `.gitconfig` for the CI machine would include these lines.
 
 ```
 [url "https://europe-ci.github.example.com/"]
-    insteadOf = https://github.example.com/
+	insteadOf = https://github.example.com/
 ```
 
-然后，当被告知提取 `https://github.example.com/myorg/myrepo` 时，Git 会改从 `https://europe-ci.github.example.com/myorg/myrepo` 中提取。
+Then, when told to fetch `https://github.example.com/myorg/myrepo`, Git will instead fetch from `https://europe-ci.github.example.com/myorg/myrepo`.
 
-## 配置存储库缓存
+## Configuring a repository cache
 
 {% ifversion ghes = 3.3 %}
-1. 在主 {% data variables.product.prodname_ghe_server %} 设备上，为存储库缓存启用功能标志。
+1. On your primary {% data variables.product.prodname_ghe_server %} appliance, enable the feature flag for repository caching.
    
    ```
    $ ghe-config cluster.cache-enabled true
    ```
 {%- endif %}
-1. 在所需平台上设置新的 {% data variables.product.prodname_ghe_server %} 设备。 此设备将是您的存储库缓存。 有关详细信息，请参阅“[设置 {% data variables.product.prodname_ghe_server %} 实例](/admin/guides/installation/setting-up-a-github-enterprise-server-instance)”。
+1. Set up a new {% data variables.product.prodname_ghe_server %} appliance on your desired platform. This appliance will be your repository cache. For more information, see "[Setting up a {% data variables.product.prodname_ghe_server %} instance](/admin/guides/installation/setting-up-a-github-enterprise-server-instance)."
 {% data reusables.enterprise_installation.replica-steps %}
-1. 使用 SSH 连接到存储库缓存的 IP 地址。
+1. Connect to the repository cache's IP address using SSH.
 
    ```shell
-   $ ssh -p 122 admin@<em>REPLICA IP</em>
+   $ ssh -p 122 admin@REPLICA-IP
    ```
 {%- ifversion ghes = 3.3 %}
-1. 在缓存副本上，为存储库缓存启用功能标志。
+1. On your cache replica, enable the feature flag for repository caching.
    
    ```
    $ ghe-config cluster.cache-enabled true
    ```
-{%- endif %} {% data reusables.enterprise_installation.generate-replication-key-pair %} {% data reusables.enterprise_installation.add-ssh-key-to-primary %}
-1. 要验证与主实例的连接并为存储库缓存启用副本模式，请再次运行 `ghe-repl-setup`。
+{%- endif %}
+{% data reusables.enterprise_installation.generate-replication-key-pair %}
+{% data reusables.enterprise_installation.add-ssh-key-to-primary %}
+1. To verify the connection to the primary and enable replica mode for the repository cache, run `ghe-repl-setup` again.
 
    ```shell
-   $ ghe-repl-setup <em>PRIMARY IP</em>
+   $ ghe-repl-setup PRIMARY-IP
    ```
 
-1. 为存储库缓存设置一个 `cache_location`，将 CACHE-LOCATION 替换为字母数字标识符，例如部署缓存的区域。 还要为此缓存设置数据中心名称；新缓存将尝试从同一数据中心的另一个缓存中播种。
+1. Set a `cache_location` for the repository cache, replacing *CACHE-LOCATION* with an alphanumeric identifier, such as the region where the cache is deployed. Also set a datacenter name for this cache; new caches will attempt to seed from another cache in the same datacenter.
 
    ```shell
-   $ ghe-repl-node --cache <em>CACHE-LOCATION</em> --datacenter <em>REPLICA-DC-NAME</em>
+   $ ghe-repl-node --cache CACHE-LOCATION --datacenter REPLICA-DC-NAME
    ```
 
-{% data reusables.enterprise_installation.replication-command %} {% data reusables.enterprise_installation.verify-replication-channel %}
-1. 要启用存储库网络到存储库缓存的复制，请设置数据位置策略。 有关详细信息，请参阅“[数据位置策略](#data-location-policies)”。
+{% data reusables.enterprise_installation.replication-command %}
+{% data reusables.enterprise_installation.verify-replication-channel %}
+1. To enable replication of repository networks to the repository cache, set a data location policy. For more information, see "[Data location policies](#data-location-policies)."
 
-## 数据位置策略
+## Data location policies
 
-可以通过用 `spokesctl cache-policy` 命令为存储库配置数据位置策略来控制数据局部性。 数据位置策略确定在哪些存储库缓存上复制哪些存储库网络。 默认情况下，在配置数据位置策略之前，不会在任何存储库缓存上复制任何存储库网络。
+You can control data locality by configuring data location policies for your repositories with the `spokesctl cache-policy` command. Data location policies determine which repository networks are replicated on which repository caches. By default, no repository networks will be replicated on any repository caches until a data location policy is configured.
 
-数据位置策略仅影响 Git 内容。 无论策略如何，数据库中的内容（如问题和拉取请求注释）都将复制到所有节点。
+Data location policies affect only Git content. Content in the database, such as issues and pull request comments, will be replicated to all nodes regardless of policy.
 
 {% note %}
 
-注意：数据位置策略与访问控制不同。 必须使用存储库角色来控制哪些用户可以访问存储库。 有关存储库角色的详细信息，请参阅“[组织的存储库角色](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)”。
+**Note:** Data location policies are not the same as access control. You must use repository roles to control which users may access a repository. For more information about repository roles, see "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)."
 
 {% endnote %} 
 
-可以配置一个策略来复制带有 `--default` 标志的所有网络。 例如，此命令将创建一个策略，以将每个存储库网络的单个副本复制到 `cache_location` 为“kansas”的存储库缓存集。
+You can configure a policy to replicate all networks with the `--default` flag. For example, this command will create a policy to replicate a single copy of every repository network to the set of repository caches whose `cache_location` is "kansas".
 
  ```
  $ ghe-spokesctl cache-policy set --default 1 kansas
  ```
 
-要为存储库网络配置复制，请指定作为网络根目录的存储库。 存储库网络包括一个存储库和存储库的所有分支。 如果不复制整个网络，则无法复制网络的一部分。
+To configure replication for a repository network, specify the repository that is the root of the network. A repository network includes a repository and all of the repository's forks. You cannot replicate part of a network without replicating the whole network.
 
 ```
 $ ghe-spokesctl cache-policy set <owner/repository> 1 kansas
 ```
 
-您可以通过为网络指定副本计数为零来覆盖复制所有网络并排除特定网络的策略。 例如，此命令指定位置“kansas”中的任何存储库缓存都不能包含该网络的任何副本。
+You can override a policy that replicates all networks and exclude specific networks by specifying a replica count of zero for the network. For example, this command specifies that any repository cache in location "kansas" cannot contain any copies of that network.
 
 ```
 $ ghe-spokesctl cache-policy set <owner/repository> 0 kansas
 ```
 
-不支持给定缓存位置中大于 1 的副本计数。
+Replica counts greater than one in a given cache location are not supported.
diff --git a/translations/zh-CN/content/admin/enterprise-management/caching-repositories/index.md b/translations/zh-CN/content/admin/enterprise-management/caching-repositories/index.md
index 10e6488910..f84a25d1cc 100644
--- a/translations/zh-CN/content/admin/enterprise-management/caching-repositories/index.md
+++ b/translations/zh-CN/content/admin/enterprise-management/caching-repositories/index.md
@@ -1,18 +1,13 @@
 ---
-title: 缓存存储库
-intro: 您可以使用存储库缓存来提高地理位置分散团队的性能，存储库缓存可提供靠近用户和 CI 客户端的只读镜像。
+title: Caching repositories
+intro: 'You can improve performance for your geographically-distributed team with repository caching, which provides read-only mirrors close to your users and CI clients.'
 versions:
-  ghes: '>=3.3'
+  ghes: '*'
 topics:
   - Enterprise
 children:
   - /about-repository-caching
   - /configuring-a-repository-cache
-ms.openlocfilehash: 4c019db4ea99bc2383c4496fb9632e8723a7a02b
-ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
-ms.translationtype: HT
-ms.contentlocale: zh-CN
-ms.lasthandoff: 09/11/2022
-ms.locfileid: '145098092'
 ---
+
 {% data reusables.enterprise.repository-caching-release-phase %}
diff --git a/translations/zh-CN/content/admin/enterprise-management/configuring-high-availability/about-geo-replication.md b/translations/zh-CN/content/admin/enterprise-management/configuring-high-availability/about-geo-replication.md
index 61d68ea486..99e8a4d951 100644
--- a/translations/zh-CN/content/admin/enterprise-management/configuring-high-availability/about-geo-replication.md
+++ b/translations/zh-CN/content/admin/enterprise-management/configuring-high-availability/about-geo-replication.md
@@ -1,6 +1,6 @@
 ---
-title: 关于 Geo-replication
-intro: '{% data variables.product.prodname_ghe_server %} 上的 Geo-replication 使用多个活动副本满足从异地分布式数据中心发出的请求。'
+title: About geo-replication
+intro: 'Geo-replication on {% data variables.product.prodname_ghe_server %} uses multiple active replicas to fulfill requests from geographically distributed data centers.'
 redirect_from:
   - /enterprise/admin/installation/about-geo-replication
   - /enterprise/admin/enterprise-management/about-geo-replication
@@ -11,32 +11,26 @@ type: overview
 topics:
   - Enterprise
   - High availability
-ms.openlocfilehash: 0e4e2feb161dd897172385bf25cf997268527fd3
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
-ms.translationtype: HT
-ms.contentlocale: zh-CN
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '146332806'
 ---
-多个活动副本可以提供到达最近副本的较短距离。 举例来说，一个在旧金山、纽约和伦敦均设有办事处的组织可以在靠近纽约的数据中心运行主设备，在靠近旧金山和伦敦的数据中心运行两个副本。 利用地理位置感知 DNS，用户可以转到距离最近的可用服务器，并更快地访问仓库数据。 如果将靠近旧金山的设备指定为主设备，则与伦敦的延迟会比较大，相比而言，将靠近纽约的设备指定为主设备有助于减小主机之间的延迟。
+Multiple active replicas can provide a shorter distance to the nearest replica. For example, an organization with offices in San Francisco, New York, and London could run the primary appliance in a datacenter near New York and two replicas in datacenters near San Francisco and London. Using geolocation-aware DNS, users can be directed to the closest server available and access repository data faster. Designating the appliance near New York as the primary helps reduce the latency between the hosts, compared to the appliance near San Francisco being the primary which has a higher latency to London.
 
-活动副本会将自身无法处理的请求委托主实例代为处理。 副本用作终止所有 SSL 连接的入口点。 与没有 Geo-replication 功能的双节点高可用性配置类似，主机之间的流量通过加密 VPN 连接发送。
+The active replica proxies requests that it can't process itself to the primary instance. The replicas function as a point of presence terminating all SSL connections. Traffic between hosts is sent through an encrypted VPN connection, similar to a two-node high availability configuration without geo-replication.
 
-Git 请求和特定的文件服务器请求（例如 LFS 和文件上传）可直接通过副本完成，无需从主设备加载任何数据。 Web 请求会始终传送到主设备，但在副本距离用户较近的情况下，由于 SSL 端接距离更近，请求速度更快。
+Git requests and specific file server requests, such as LFS and file uploads, can be served directly from the replica without loading any data from the primary. Web requests are always routed to the primary, but if the replica is closer to the user the requests are faster due to the closer SSL termination.
 
-为了让异地复制无缝运行，需要使用 Geo DNS，例如 [Amazon 的 Route 53 服务](http://docs.aws.amazon.com/Route53/latest/DeveloperGuide/routing-policy.html#routing-policy-geo)。 实例的主机名应解析到距离用户最近的副本。
+Geo DNS, such as [Amazon's Route 53 service](http://docs.aws.amazon.com/Route53/latest/DeveloperGuide/routing-policy.html#routing-policy-geo), is required for geo-replication to work seamlessly. The hostname for the instance should resolve to the replica that is closest to the user's location.
 
-## 限制
+## Limitations
 
-将请求写入副本需要将数据发送到主设备和所有副本。 这意味着所有写入操作的性能都受限于最慢的副本，虽然新的地理副本可以从现有共同位置地理副本（而不是从主设备）播种大部分数据。 {% ifversion ghes > 3.2 %}若要在不影响写入吞吐量的情况下减少分布式团队和大型 CI 服务器场导致的延迟和带宽，可以改为配置存储库缓存。 有关详细信息，请参阅“[关于存储库缓存](/admin/enterprise-management/caching-repositories/about-repository-caching)”。{% endif %}
+Writing requests to the replica requires sending the data to the primary and all replicas. This means that the performance of all writes is limited by the slowest replica, although new geo-replicas can seed the majority of their data from existing co-located geo-replicas, rather than from the primary. To reduce the latency and bandwidth caused by distributed teams and large CI farms without impacting write throughput, you can configure repository caching instead. For more information, see "[About repository caching](/admin/enterprise-management/caching-repositories/about-repository-caching)."
 
-Geo-replication 不会增大 {% data variables.product.prodname_ghe_server %} 实例的容量，也不会解决与 CPU 或内存资源不足相关的性能问题。 如果主设备处于脱机状态，则活动副本将无法满足任何读取或写入请求。 
+Geo-replication will not add capacity to a {% data variables.product.prodname_ghe_server %} instance or solve performance issues related to insufficient CPU or memory resources. If the primary appliance is offline, active replicas will be unable to serve any read or write requests. 
 
 {% data reusables.enterprise_installation.replica-limit %}
 
-## 监视 Geo-replication 配置
+## Monitoring a geo-replication configuration
 
 {% data reusables.enterprise_installation.monitoring-replicas %}
 
-## 延伸阅读
-- “[创建异地复制副本](/enterprise/admin/guides/installation/creating-a-high-availability-replica/#creating-geo-replication-replicas)”
+## Further reading
+- "[Creating geo-replication replicas](/enterprise/admin/guides/installation/creating-a-high-availability-replica/#creating-geo-replication-replicas)"
diff --git a/translations/zh-CN/content/admin/enterprise-management/configuring-high-availability/about-high-availability-configuration.md b/translations/zh-CN/content/admin/enterprise-management/configuring-high-availability/about-high-availability-configuration.md
index 3a4a751915..3d3d8b767c 100644
--- a/translations/zh-CN/content/admin/enterprise-management/configuring-high-availability/about-high-availability-configuration.md
+++ b/translations/zh-CN/content/admin/enterprise-management/configuring-high-availability/about-high-availability-configuration.md
@@ -13,12 +13,12 @@ topics:
   - High availability
   - Infrastructure
 shortTitle: About HA configuration
-ms.openlocfilehash: 921a1a935bbfa930c77e2c72d7856f00d54d6016
-ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.openlocfilehash: b54ca60c6cf1d79b9435ca8deedebec09ed39396
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: zh-CN
-ms.lasthandoff: 09/10/2022
-ms.locfileid: '146332742'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148108089'
 ---
 配置高可用性时，会自动设置将所有数据存储（Git 仓库、MySQL、Redis 和 Elasticsearch）单向、异步地从主设备复制到副本。 还会复制大多数 {% data variables.product.prodname_ghe_server %} 配置设置，包括 {% data variables.enterprise.management_console %} 密码。 有关详细信息，请参阅“[访问管理控制台](/admin/configuration/configuring-your-enterprise/accessing-the-management-console)”。
 
@@ -35,8 +35,8 @@ ms.locfileid: '146332742'
 
 高可用性配置不适用于：
 
-  - 横向扩展。虽然可以使用异地复制将流量分布在不同地理位置，但写入性能受限于主设备的速度和可用性。 有关详细信息，请参阅“[关于异地复制](/enterprise/admin/guides/installation/about-geo-replication/)”。{% ifversion ghes > 3.2 %}
-  - CI/CD 负载。 如果您有大量在地理位置上远离主实例的 CI 客户端，则配置仓库缓存可能会使您受益匪浅。 有关详细信息，请参阅“[关于存储库缓存](/admin/enterprise-management/caching-repositories/about-repository-caching)”。{% endif %}
+  - 横向扩展。虽然可以使用异地复制将流量分布在不同地理位置，但写入性能受限于主设备的速度和可用性。 有关详细信息，请参阅“[有关异地复制](/enterprise/admin/guides/installation/about-geo-replication/)”。
+  - CI/CD 负载。 如果您有大量在地理位置上远离主实例的 CI 客户端，则配置仓库缓存可能会使您受益匪浅。 有关详细信息，请参阅“[关于存储库缓存](/admin/enterprise-management/caching-repositories/about-repository-caching)”。
   - 备份主设备。 高可用性副本不会替代灾难恢复计划中的非现场备份。 某些形式的数据损坏或数据丢失可能会立即从主设备复制到副本。 为确保安全回滚到稳定的过去状态，必须通过历史快照执行定期备份。
   - 零停机时间升级。 为避免受控升级场景下出现数据丢失和裂脑的状况，请先将主设备置于维护模式并等待所有写入操作完成，然后再对副本进行升级。
 
diff --git a/translations/zh-CN/content/admin/enterprise-management/configuring-high-availability/creating-a-high-availability-replica.md b/translations/zh-CN/content/admin/enterprise-management/configuring-high-availability/creating-a-high-availability-replica.md
index b3f1c3ec05..e70b4f1225 100644
--- a/translations/zh-CN/content/admin/enterprise-management/configuring-high-availability/creating-a-high-availability-replica.md
+++ b/translations/zh-CN/content/admin/enterprise-management/configuring-high-availability/creating-a-high-availability-replica.md
@@ -39,7 +39,7 @@ shortTitle: Create HA replica
 
 This example configuration uses a primary and two replicas, which are located in three different geographic regions. While the three nodes can be in different networks, all nodes are required to be reachable from all the other nodes. At the minimum, the required administrative ports should be open to all the other nodes. For more information about the port requirements, see "[Network Ports](/enterprise/admin/guides/installation/network-ports/#administrative-ports)."
 
-{% data reusables.enterprise_clustering.network-latency %}{% ifversion ghes > 3.2 %} If latency is more than 70 milliseconds, we recommend cache replica nodes instead. For more information, see "[Configuring a repository cache](/admin/enterprise-management/caching-repositories/configuring-a-repository-cache)."{% endif %}
+{% data reusables.enterprise_clustering.network-latency %} If latency is more than 70 milliseconds, we recommend cache replica nodes instead. For more information, see "[Configuring a repository cache](/admin/enterprise-management/caching-repositories/configuring-a-repository-cache)."
 
 1. Create the first replica the same way you would for a standard two node configuration by running `ghe-repl-setup` on the first replica.
   ```shell
diff --git a/translations/zh-CN/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrade-requirements.md b/translations/zh-CN/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrade-requirements.md
index 24cfb85f46..5b9ed639d1 100644
--- a/translations/zh-CN/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrade-requirements.md
+++ b/translations/zh-CN/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrade-requirements.md
@@ -17,7 +17,6 @@ topics:
 {% note %}
 
 **Notes:**
-{% ifversion ghes < 3.3 %}- Features such as {% data variables.product.prodname_actions %}, {% data variables.product.prodname_registry %}, {% data variables.product.prodname_mobile %} and {% data variables.product.prodname_GH_advanced_security %} are available on {% data variables.product.prodname_ghe_server %} 3.0 or higher. We highly recommend upgrading to 3.0 or later releases to take advantage of critical security updates, bug fixes and feature enhancements.{% endif %}
 - Upgrade packages are available at [enterprise.github.com](https://enterprise.github.com/releases) for supported versions. Verify the availability of the upgrade packages you will need to complete the upgrade. If a package is not available, contact {% data variables.contact.contact_ent_support %} for assistance.
 - If you're using {% data variables.product.prodname_ghe_server %} Clustering, see "[Upgrading a cluster](/enterprise/admin/guides/clustering/upgrading-a-cluster/)" in the {% data variables.product.prodname_ghe_server %} Clustering Guide for specific instructions unique to clustering.
 - The release notes for {% data variables.product.prodname_ghe_server %} provide a comprehensive list of new features for every version of {% data variables.product.prodname_ghe_server %}. For more information, see the [releases page](https://enterprise.github.com/releases).
diff --git a/translations/zh-CN/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server.md b/translations/zh-CN/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server.md
index c1c8100472..b4203f0a1d 100644
--- a/translations/zh-CN/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server.md
+++ b/translations/zh-CN/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server.md
@@ -23,7 +23,6 @@ topics:
 shortTitle: Upgrading GHES
 ---
 
-{% ifversion ghes < 3.3 %}{% data reusables.enterprise.upgrade-ghes-for-features %}{% endif %}
 
 ## Preparing to upgrade
 
@@ -70,8 +69,7 @@ There are two types of snapshots:
 | Azure | VM | <https://docs.microsoft.com/azure/backup/backup-azure-vms-first-look-arm>
 | Hyper-V | VM | <https://docs.microsoft.com/windows-server/virtualization/hyper-v/manage/enable-or-disable-checkpoints-in-hyper-v>
 | Google Compute Engine | Disk | <https://cloud.google.com/compute/docs/disks/create-snapshots>
-| VMware | VM | <https://pubs.vmware.com/vsphere-50/topic/com.vmware.wssdk.pg.doc_50/PG_Ch11_VM_Manage.13.3.html>{% ifversion ghes < 3.3 %}
-| XenServer | VM | <https://docs.citrix.com/en-us/xencenter/current-release/vms-snapshots.html>{% endif %}
+| VMware | VM | <https://pubs.vmware.com/vsphere-50/topic/com.vmware.wssdk.pg.doc_50/PG_Ch11_VM_Manage.13.3.html>
 
 ## Upgrading with a hotpatch
 
diff --git a/translations/zh-CN/content/admin/github-actions/advanced-configuration-and-troubleshooting/backing-up-and-restoring-github-enterprise-server-with-github-actions-enabled.md b/translations/zh-CN/content/admin/github-actions/advanced-configuration-and-troubleshooting/backing-up-and-restoring-github-enterprise-server-with-github-actions-enabled.md
index 986fa1a462..bb63cf03cc 100644
--- a/translations/zh-CN/content/admin/github-actions/advanced-configuration-and-troubleshooting/backing-up-and-restoring-github-enterprise-server-with-github-actions-enabled.md
+++ b/translations/zh-CN/content/admin/github-actions/advanced-configuration-and-troubleshooting/backing-up-and-restoring-github-enterprise-server-with-github-actions-enabled.md
@@ -41,4 +41,4 @@ To restore a backup of {% data variables.location.product_location %} with {% da
    ```
 {% data reusables.actions.apply-configuration-and-enable %}
 1. After {% data variables.product.prodname_actions %} is configured and enabled, to restore the rest of the data from the backup, use the `ghe-restore` command. For more information, see "[Restoring a backup](/admin/configuration/configuring-backups-on-your-appliance#restoring-a-backup)."
-1. Re-register your self-hosted runners on the destination instance. For more information, see "[Adding self-hosted runners](/actions/hosting-your-own-runners/adding-self-hosted-runners)."
\ No newline at end of file
+1. Re-register your self-hosted runners on the destination instance. For more information, see "[Adding self-hosted runners](/actions/hosting-your-own-runners/adding-self-hosted-runners)."
diff --git a/translations/zh-CN/content/admin/github-actions/advanced-configuration-and-troubleshooting/troubleshooting-github-actions-for-your-enterprise.md b/translations/zh-CN/content/admin/github-actions/advanced-configuration-and-troubleshooting/troubleshooting-github-actions-for-your-enterprise.md
index c38c209a49..71088f9285 100644
--- a/translations/zh-CN/content/admin/github-actions/advanced-configuration-and-troubleshooting/troubleshooting-github-actions-for-your-enterprise.md
+++ b/translations/zh-CN/content/admin/github-actions/advanced-configuration-and-troubleshooting/troubleshooting-github-actions-for-your-enterprise.md
@@ -156,7 +156,7 @@ If any of these services are at or near 100% CPU utilization, or the memory is n
     When running `ghe-config-apply`, if you see output like `Failed to run nomad job '/etc/nomad-jobs/<name>.hcl'`, then the change has likely over-allocated CPU or memory resources. If this happens, edit the configuration files again and lower the allocated CPU or memory, then re-run `ghe-config-apply`.
 1. After the configuration is applied, run `ghe-actions-check` to verify that the {% data variables.product.prodname_actions %} services are operational.
 
-{% ifversion fpt or ghec or ghes > 3.2 %}
+{% ifversion fpt or ghec or ghes %}
 ## Troubleshooting failures when {% data variables.product.prodname_dependabot %} triggers existing workflows
 
 {% data reusables.dependabot.beta-security-and-version-updates %}
diff --git a/translations/zh-CN/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/index.md b/translations/zh-CN/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/index.md
index 8a37039a5e..da5758bbe5 100644
--- a/translations/zh-CN/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/index.md
+++ b/translations/zh-CN/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/index.md
@@ -12,11 +12,11 @@ children:
   - /enabling-github-actions-with-minio-gateway-for-nas-storage
   - /managing-self-hosted-runners-for-dependabot-updates
 shortTitle: Enable GitHub Actions
-ms.openlocfilehash: 675bbbe0ccbb68d676602b0553c8534f1601bcf6
-ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.openlocfilehash: 273e03407dd8c3c0a125e2c215a973c88aaf884b
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: zh-CN
-ms.lasthandoff: 09/10/2022
-ms.locfileid: '145100004'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148108108'
 ---
 
diff --git a/translations/zh-CN/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/about-github-actions-for-enterprises.md b/translations/zh-CN/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/about-github-actions-for-enterprises.md
index c8553798a2..921d01760d 100644
--- a/translations/zh-CN/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/about-github-actions-for-enterprises.md
+++ b/translations/zh-CN/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/about-github-actions-for-enterprises.md
@@ -12,13 +12,6 @@ topics:
   - Enterprise
 ---
 
-{% ifversion ghes < 3.3 %}
-{% note %}
-
-**Note:** {% data reusables.enterprise.upgrade-ghes-for-actions %}
-
-{% endnote %}
-{% endif %}
 
 ## About {% data variables.product.prodname_actions %} for enterprises
 
@@ -56,7 +49,6 @@ You can create your own unique automations, or you can use and adapt workflows f
 After you finish planning, you can follow the instructions for getting started with {% data variables.product.prodname_actions %}. For more information, see {% ifversion ghec %}"[Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_cloud %}](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-cloud)."{% elsif ghae %}"[Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_managed %}](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-ae)."{% endif %}
 {% endif %}
 
-
 ## Further reading
 
 - "[Understanding {% data variables.product.prodname_actions %}](/actions/learn-github-actions/understanding-github-actions)"{% ifversion ghec %}
diff --git a/translations/zh-CN/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server.md b/translations/zh-CN/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server.md
index 739cb96d5d..5b79fefc07 100644
--- a/translations/zh-CN/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server.md
+++ b/translations/zh-CN/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server.md
@@ -23,8 +23,6 @@ topics:
 
 This article explains how site administrators can configure {% data variables.product.prodname_ghe_server %} to use {% data variables.product.prodname_actions %}.
 
-{% data reusables.enterprise.upgrade-ghes-for-actions %}
-
 {% data reusables.actions.ghes-actions-not-enabled-by-default %} You'll need to determine whether your instance has adequate CPU and memory resources to handle the load from {% data variables.product.prodname_actions %} without causing performance loss, and possibly increase those resources. You'll also need to decide which storage provider you'll use for the blob storage required to store artifacts{% ifversion actions-caching %} and caches{% endif %} generated by workflow runs. Then, you'll enable {% data variables.product.prodname_actions %} for your enterprise, manage access permissions, and add self-hosted runners to run workflows.
 
 {% data reusables.actions.introducing-enterprise %}
@@ -33,7 +31,6 @@ This article explains how site administrators can configure {% data variables.pr
 
 ## Review hardware requirements
 
-
 {%- ifversion ghes < 3.6 %}
 
 The CPU and memory resources available to {% data variables.location.product_location %} determine the number of jobs that can be run concurrently without performance loss. {% data reusables.actions.minimum-hardware %}
@@ -50,14 +47,6 @@ The peak quantity of connected runners without performance loss depends on such
 
 {% endif %}
 
-{%- ifversion ghes = 3.2 %}
-
-{% data reusables.actions.hardware-requirements-3.2 %}
-
-Maximum concurrency was measured using multiple repositories, job duration of approximately 10 minutes, and 10 MB artifact uploads. You may experience different performance depending on the overall levels of activity on your instance.
-
-{%- endif %}
-
 {%- ifversion ghes = 3.3 %}
 
 {% data reusables.actions.hardware-requirements-3.3 %}
@@ -88,7 +77,6 @@ Maximum concurrency was measured using multiple repositories, job duration of ap
 
 {%- endif %}
 
-
 {%- ifversion ghes = 3.6 %}
 
 {% data reusables.actions.hardware-requirements-3.6 %}
@@ -114,8 +102,7 @@ For more information about minimum hardware requirements for {% data variables.l
 - [Google Cloud Platform](/admin/installation/installing-github-enterprise-server-on-google-cloud-platform#hardware-considerations)
 - [Hyper-V](/admin/installation/installing-github-enterprise-server-on-hyper-v#hardware-considerations)
 - [OpenStack KVM](/admin/installation/installing-github-enterprise-server-on-openstack-kvm#hardware-considerations)
-- [VMware](/admin/installation/installing-github-enterprise-server-on-vmware#hardware-considerations){% ifversion ghes < 3.3 %}
-- [XenServer](/admin/installation/installing-github-enterprise-server-on-xenserver#hardware-considerations){% endif %}
+- [VMware](/admin/installation/installing-github-enterprise-server-on-vmware#hardware-considerations)
 
 {% data reusables.enterprise_installation.about-adjusting-resources %}
 
diff --git a/translations/zh-CN/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-self-hosted-runners-for-your-enterprise.md b/translations/zh-CN/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-self-hosted-runners-for-your-enterprise.md
index 8fc4c6c049..0c3418282c 100644
--- a/translations/zh-CN/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-self-hosted-runners-for-your-enterprise.md
+++ b/translations/zh-CN/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-self-hosted-runners-for-your-enterprise.md
@@ -32,9 +32,7 @@ This guide shows you how to apply a centralized management approach to self-host
 1. Deploy a self-hosted runner for your enterprise
 1. Create a group to manage access to the runners available to your enterprise
 1. Optionally, further restrict the repositories that can use the runner
-{%- ifversion ghec or ghae or ghes > 3.2 %}
 1. Optionally, build custom tooling to automatically scale your self-hosted runners
-{% endif %}
 
 You'll also find additional information about how to monitor and secure your self-hosted runners,{% ifversion ghes or ghae %} how to access actions from {% data variables.product.prodname_dotcom_the_website %},{% endif %} and how to customize the software on your runner machines.
 
@@ -122,14 +120,10 @@ Optionally, organization owners can further restrict the access policy of the ru
 
 For more information, see "[Managing access to self-hosted runners using groups](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#changing-the-access-policy-of-a-self-hosted-runner-group)."
 
-{% ifversion ghec or ghae or ghes > 3.2 %}
-
 ## 5. Automatically scale your self-hosted runners
 
 Optionally, you can build custom tooling to automatically scale the self-hosted runners for {% ifversion ghec or ghae %}your enterprise{% elsif ghes %}{% data variables.location.product_location %}{% endif %}. For example, your tooling can respond to webhook events from {% data variables.location.product_location %} to automatically scale a cluster of runner machines. For more information, see "[Autoscaling with self-hosted runners](/actions/hosting-your-own-runners/autoscaling-with-self-hosted-runners)."
 
-{% endif %}
-
 ## Next steps
 
 - You can monitor self-hosted runners and troubleshoot common issues. For more information, see "[Monitoring and troubleshooting self-hosted runners](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners)."
diff --git a/translations/zh-CN/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise.md b/translations/zh-CN/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise.md
index 8ac0a99e29..625a34aa98 100644
--- a/translations/zh-CN/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise.md
+++ b/translations/zh-CN/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise.md
@@ -18,8 +18,6 @@ topics:
 
 ![Diagram of jobs running on self-hosted runners](/assets/images/help/images/actions-enterprise-overview.png)
 
-{% data reusables.enterprise.upgrade-ghes-for-actions %}
-
 Before you introduce {% data variables.product.prodname_actions %} to a large enterprise, you first need to plan your adoption and make decisions about how your enterprise will use {% data variables.product.prodname_actions %} to best support your unique needs.
 
 ## Governance and compliance
@@ -102,7 +100,7 @@ You may need to upgrade the CPU and memory resources for {% data variables.locat
 
 You also have to decide where to add each runner. You can add a self-hosted runner to an individual repository, or you can make the runner available to an entire organization or your entire enterprise. Adding runners at the organization or enterprise levels allows sharing of runners, which might reduce the size of your runner infrastructure. You can use policies to limit access to self-hosted runners at the organization and enterprise levels by assigning groups of runners to specific repositories or organizations. For more information, see "[Adding self-hosted runners](/actions/hosting-your-own-runners/adding-self-hosted-runners)" and "[Managing access to self-hosted runners using groups](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups)."
 
-{% ifversion ghec or ghes > 3.2 %}
+{% ifversion ghec or ghes %}
 You should consider using autoscaling to automatically increase or decrease the number of available self-hosted runners. For more information, see "[Autoscaling with self-hosted runners](/actions/hosting-your-own-runners/autoscaling-with-self-hosted-runners)."
 {% endif %}
 
diff --git a/translations/zh-CN/content/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect.md b/translations/zh-CN/content/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect.md
index 709907e154..79a2892040 100644
--- a/translations/zh-CN/content/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect.md
+++ b/translations/zh-CN/content/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect.md
@@ -31,7 +31,7 @@ Alternatively, if you want stricter control over which actions are allowed in yo
 
 {% data reusables.actions.github-connect-resolution %}
 
-If a user has already created an organization and repository in your enterprise that matches an organization and repository name on {% data variables.product.prodname_dotcom_the_website %}, the repository on your enterprise will be used instead of the {% data variables.product.prodname_dotcom_the_website %} repository. {% ifversion ghes < 3.3 or ghae %}A malicious user could take advantage of this behavior to run code as part of a workflow{% else %}For more information, see "[Automatic retirement of namespaces for actions accessed on {% data variables.product.prodname_dotcom_the_website%}](#automatic-retirement-of-namespaces-for-actions-accessed-on-githubcom)."
+If a user has already created an organization and repository in your enterprise that matches an organization and repository name on {% data variables.product.prodname_dotcom_the_website %}, the repository on your enterprise will be used instead of the {% data variables.product.prodname_dotcom_the_website %} repository. {% ifversion ghae %}A malicious user could take advantage of this behavior to run code as part of a workflow.{% else %}For more information, see "[Automatic retirement of namespaces for actions accessed on {% data variables.product.prodname_dotcom_the_website%}](#automatic-retirement-of-namespaces-for-actions-accessed-on-githubcom)."
 {% endif %}
 
 ## Enabling automatic access to all {% data variables.product.prodname_dotcom_the_website %} actions
@@ -46,8 +46,6 @@ Before enabling access to all actions from {% data variables.product.prodname_do
   ![Drop-down menu to actions from GitHub.com in workflows runs](/assets/images/enterprise/site-admin-settings/enable-marketplace-actions-drop-down-ae.png)
 1. {% data reusables.actions.enterprise-limit-actions-use %}
 
-{% ifversion ghes > 3.2 or ghae %}
-
 ## Automatic retirement of namespaces for actions accessed on {% data variables.product.prodname_dotcom_the_website %}
 
 When you enable {% data variables.product.prodname_github_connect %}, users see no change in behavior for existing workflows because {% data variables.product.prodname_actions %} searches {% data variables.location.product_location %} for each action before falling back to {% data variables.product.prodname_dotcom_the_website%}. This ensures that any custom versions of actions your enterprise has created are used in preference to their counterparts on {% data variables.product.prodname_dotcom_the_website%}.
@@ -67,5 +65,3 @@ After using an action from {% data variables.product.prodname_dotcom_the_website
    **Tip:** When you unretire a namespace, always create the new repository with that name as soon as possible. If a workflow calls the associated action on {% data variables.product.prodname_dotcom_the_website %} before you create the local repository, the namespace will be retired again. For actions used in workflows that run frequently, you may find that a namespace is retired again before you have time to create the local repository. In this case, you can temporarily disable the relevant workflows until you have created the new repository.
 
    {% endtip %}
-
-{% endif %}
diff --git a/translations/zh-CN/content/admin/github-actions/managing-access-to-actions-from-githubcom/manually-syncing-actions-from-githubcom.md b/translations/zh-CN/content/admin/github-actions/managing-access-to-actions-from-githubcom/manually-syncing-actions-from-githubcom.md
index e44a1c5cf1..7e1756c530 100644
--- a/translations/zh-CN/content/admin/github-actions/managing-access-to-actions-from-githubcom/manually-syncing-actions-from-githubcom.md
+++ b/translations/zh-CN/content/admin/github-actions/managing-access-to-actions-from-githubcom/manually-syncing-actions-from-githubcom.md
@@ -33,13 +33,11 @@ If your machine has access to both systems at the same time, you can do the sync
 
 The `actions-sync` tool can only download actions from {% data variables.product.prodname_dotcom_the_website %} that are stored in public repositories.
 
-{% ifversion ghes > 3.2 or ghae %}
 {% note %}
 
 **Note:** The `actions-sync` tool is intended for use in systems where {% data variables.product.prodname_github_connect %} is not enabled. If you run the tool on a system with {% data variables.product.prodname_github_connect %} enabled, you may see the error `The repository <repo_name> has been retired and cannot be reused`. This indicates that a workflow has used that action directly on {% data variables.product.prodname_dotcom_the_website %} and the namespace is retired on {% data variables.location.product_location %}. For more information, see "[Automatic retirement of namespaces for actions accessed on {% data variables.product.prodname_dotcom_the_website%}](/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect#automatic-retirement-of-namespaces-for-actions-accessed-on-githubcom)." 
 
 {% endnote %}
-{% endif %}
 
 ## Prerequisites
 
diff --git a/translations/zh-CN/content/admin/github-actions/managing-access-to-actions-from-githubcom/using-the-latest-version-of-the-official-bundled-actions.md b/translations/zh-CN/content/admin/github-actions/managing-access-to-actions-from-githubcom/using-the-latest-version-of-the-official-bundled-actions.md
index c75e4e6eef..585957f8c6 100644
--- a/translations/zh-CN/content/admin/github-actions/managing-access-to-actions-from-githubcom/using-the-latest-version-of-the-official-bundled-actions.md
+++ b/translations/zh-CN/content/admin/github-actions/managing-access-to-actions-from-githubcom/using-the-latest-version-of-the-official-bundled-actions.md
@@ -47,10 +47,8 @@ Once {% data variables.product.prodname_github_connect %} is configured, you can
 1. Configure your workflow's YAML to use `{% data reusables.actions.action-checkout %}`.
 1. Each time your workflow runs, the runner will use the specified version of `actions/checkout` from {% data variables.product.prodname_dotcom_the_website %}.
 
-   {% ifversion ghes > 3.2 or ghae %}
    {% note %}
 
    **Note:** The first time the `checkout` action is used from {% data variables.product.prodname_dotcom_the_website %}, the `actions/checkout` namespace is automatically retired on {% data variables.location.product_location %}. If you ever want to revert to using a local copy of the action, you first need to remove the namespace from retirement. For more information, see "[Automatic retirement of namespaces for actions accessed on {% data variables.product.prodname_dotcom_the_website%}](/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect#automatic-retirement-of-namespaces-for-actions-accessed-on-githubcom)."
 
    {% endnote %}
-   {% endif %}
diff --git a/translations/zh-CN/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-enterprise-managed-users.md b/translations/zh-CN/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-enterprise-managed-users.md
index a448aa318d..2015dcd47d 100644
--- a/translations/zh-CN/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-enterprise-managed-users.md
+++ b/translations/zh-CN/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-enterprise-managed-users.md
@@ -1,5 +1,5 @@
 ---
-title: About Enterprise Managed Users
+title: About {% data variables.product.prodname_emus %}
 shortTitle: About managed users
 intro: 'You can centrally manage identity and access for your enterprise members on {% data variables.product.prodname_dotcom %} from your identity provider.'
 redirect_from:
@@ -16,6 +16,7 @@ topics:
   - Authentication
   - Enterprise
   - SSO
+allowTitleToDifferFromFilename: true
 ---
 
 ## About {% data variables.product.prodname_emus %}
@@ -24,8 +25,6 @@ With {% data variables.product.prodname_emus %}, you can control the user accoun
 
 In your IdP, you can give each {% data variables.enterprise.prodname_managed_user %} the role of user, enterprise owner, or billing manager. {% data variables.enterprise.prodname_managed_users_caps %} can own organizations within your enterprise and can add other {% data variables.enterprise.prodname_managed_users %} to the organizations and teams within. For more information, see "[Roles in an enterprise](/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/roles-in-an-enterprise)" and "[About organizations](/organizations/collaborating-with-groups-in-organizations/about-organizations)."
 
-Organization membership can be managed manually, or you can update membership automatically as {% data variables.enterprise.prodname_managed_users %} are added to IdP groups that are connected to teams within the organization. When a {% data variables.enterprise.prodname_managed_user %} is manually added to an organization, unassigning them from the {% data variables.product.prodname_emu_idp_application %} application on your IdP will suspend the user but not remove them from the organization. For more information about managing organization and team membership automatically, see "[Managing team memberships with identity provider groups](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/managing-team-memberships-with-identity-provider-groups)."
-
 {% ifversion oidc-for-emu %}
 
 {% data reusables.enterprise-accounts.emu-cap-validates %} For more information, see "[About support for your IdP's Conditional Access Policy](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-support-for-your-idps-conditional-access-policy)."
@@ -46,6 +45,17 @@ To use {% data variables.product.prodname_emus %}, you need a separate type of e
 
 {% endnote %}
 
+## About organization membership management
+
+Organization memberships can be managed manually, or you can update memberships automatically using IdP groups. To manage organization memberships through your IdP, the members must be added to an IdP group, and the IdP group must be connected to a team within the organization. For more information about managing organization and team memberships automatically, see "[Managing team memberships with identity provider groups](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/managing-team-memberships-with-identity-provider-groups)."
+
+The way a member is added to an organization owned by your enterprise (through IdP groups or manually) determines how they must be removed from an organization. 
+
+- If a member was added to an organization manually, you must remove them manually. Unassigning them from the {% data variables.product.prodname_emu_idp_application %} application on your IdP will suspend the user but not remove them from the organization.
+- If a user became a member of an organization because they were added to IdP groups mapped to one or more teams in the organization, removing them from _all_ of the mapped IdP groups associated with the organization will remove them from the organization.
+
+To discover how a member was added to an organization, you can filter the member list by type. For more information, see "[Viewing people in your enterprise](/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise#filtering-by-member-type-in-an-enterprise-with-managed-users)."
+
 ## Identity provider support
 
 {% data variables.product.prodname_emus %} supports the following IdPs{% ifversion oidc-for-emu %} and authentication methods:
diff --git a/translations/zh-CN/content/admin/identity-and-access-management/using-ldap-for-enterprise-iam/using-ldap.md b/translations/zh-CN/content/admin/identity-and-access-management/using-ldap-for-enterprise-iam/using-ldap.md
index 1054fee109..29ea2a82d2 100644
--- a/translations/zh-CN/content/admin/identity-and-access-management/using-ldap-for-enterprise-iam/using-ldap.md
+++ b/translations/zh-CN/content/admin/identity-and-access-management/using-ldap-for-enterprise-iam/using-ldap.md
@@ -145,7 +145,13 @@ After you enable LDAP sync, a synchronization job will run at the specified time
 A synchronization job will also run at the specified time interval to perform the following operations on each team that has been mapped to an LDAP group:
 
 - If a team's corresponding LDAP group has been removed, remove all members from the team.
-- If LDAP member entries have been removed from the LDAP group, remove the corresponding users from the team. If the user is no longer a member of any team in the organization, remove the user from the organization. If the user loses access to any repositories as a result, delete any private forks the user has of those repositories.
+- If LDAP member entries have been removed from the LDAP group, remove the corresponding users from the team. If the user is no longer a member of any team in the organization and is not an owner of the organization, remove the user from the organization. If the user loses access to any repositories as a result, delete any private forks the user has of those repositories.
+
+  {% note %}
+
+  **Note:** LDAP Sync will not remove a user from an organization if the user is an owner of that organization. Another organization owner will need to manually remove the user instead.
+
+  {% endnote %}
 - If LDAP member entries have been added to the LDAP group, add the corresponding users to the team. If the user regains access to any repositories as a result, restore any private forks of the repositories that were deleted because the user lost access in the past 90 days.
 
 {% data reusables.enterprise_user_management.ldap-sync-nested-teams %}
diff --git a/translations/zh-CN/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/configuring-saml-single-sign-on-for-your-enterprise-using-okta.md b/translations/zh-CN/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/configuring-saml-single-sign-on-for-your-enterprise-using-okta.md
index ecb776e56d..709867b3de 100644
--- a/translations/zh-CN/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/configuring-saml-single-sign-on-for-your-enterprise-using-okta.md
+++ b/translations/zh-CN/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/configuring-saml-single-sign-on-for-your-enterprise-using-okta.md
@@ -15,12 +15,12 @@ topics:
   - Enterprise
 type: how_to
 shortTitle: Configure SAML SSO with Okta
-ms.openlocfilehash: 2772285f266a2593e8fc0900b39602325d30c46d
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: e9cbf6e70fb5e07f9cd2c5e27d9b952921e18fdc
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: zh-CN
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147094804'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148108690'
 ---
 {% data reusables.enterprise-accounts.emu-saml-note %}
 
diff --git a/translations/zh-CN/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/troubleshooting-saml-authentication.md b/translations/zh-CN/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/troubleshooting-saml-authentication.md
index 3688464fb7..34adc3917c 100644
--- a/translations/zh-CN/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/troubleshooting-saml-authentication.md
+++ b/translations/zh-CN/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/troubleshooting-saml-authentication.md
@@ -108,4 +108,4 @@ Ensure that you set the value for `Audience` on your IdP to the `EntityId` for {
 
 {% ifversion ghec %}
 {% data reusables.saml.authentication-loop %}
-{% endif %}
\ No newline at end of file
+{% endif %}
diff --git a/translations/zh-CN/content/admin/index.md b/translations/zh-CN/content/admin/index.md
index 2ecb51023a..210f340b53 100644
--- a/translations/zh-CN/content/admin/index.md
+++ b/translations/zh-CN/content/admin/index.md
@@ -105,14 +105,6 @@ featuredLinks:
     - '{% ifversion ghec %}/admin/monitoring-activity-in-your-enterprise/exploring-user-activity/managing-global-webhooks{% endif %}'
     - /billing/managing-your-license-for-github-enterprise/using-visual-studio-subscription-with-github-enterprise/setting-up-visual-studio-subscription-with-github-enterprise
     - /admin/enterprise-support/about-github-enterprise-support
-  videos:
-    - title: GitHub in the Enterprise – Maya Ross
-      href: 'https://www.youtube-nocookie.com/embed/1-i39RqaxRs'
-    - title: What's new for GitHub Enterprise – Jarryd McCree
-      href: 'https://www.youtube-nocookie.com/embed/ZZviWZgrqhM'
-    - title: Enforcing information security policy through GitHub Enterprise – Thomas Worley
-      href: 'https://www.youtube-nocookie.com/embed/DCu-ZTT7WTI'
-  videosHeading: GitHub Universe 2021 videos
 layout: product-landing
 versions:
   ghec: '*'
@@ -133,11 +125,11 @@ children:
   - /guides
   - /release-notes
   - /all-releases
-ms.openlocfilehash: ebd1473538d42928ff3d9abb3c0e2bd9f12767f5
-ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.openlocfilehash: 3980ad01e56bf1e38dd6473c5e5246c6d45350eb
+ms.sourcegitcommit: 3268914369fb29540e4d88ee5e56bc7a41f2a60e
 ms.translationtype: HT
 ms.contentlocale: zh-CN
-ms.lasthandoff: 09/11/2022
-ms.locfileid: '147881153'
+ms.lasthandoff: 10/26/2022
+ms.locfileid: '148111306'
 ---
 
diff --git a/translations/zh-CN/content/admin/installation/setting-up-a-github-enterprise-server-instance/index.md b/translations/zh-CN/content/admin/installation/setting-up-a-github-enterprise-server-instance/index.md
index b705dfa267..b5ce998435 100644
--- a/translations/zh-CN/content/admin/installation/setting-up-a-github-enterprise-server-instance/index.md
+++ b/translations/zh-CN/content/admin/installation/setting-up-a-github-enterprise-server-instance/index.md
@@ -18,14 +18,13 @@ children:
   - /installing-github-enterprise-server-on-hyper-v
   - /installing-github-enterprise-server-on-openstack-kvm
   - /installing-github-enterprise-server-on-vmware
-  - /installing-github-enterprise-server-on-xenserver
   - /setting-up-a-staging-instance
 shortTitle: Set up an instance
-ms.openlocfilehash: 23fe586f2c4baa87a2e2b388685bf8e42d5e10a4
-ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.openlocfilehash: 7c23ae31e8e976f2acc664f87fbff82ffe025a0e
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: zh-CN
-ms.lasthandoff: 09/11/2022
-ms.locfileid: '147881459'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148108088'
 ---
 
diff --git a/translations/zh-CN/content/admin/installation/setting-up-a-github-enterprise-server-instance/setting-up-a-staging-instance.md b/translations/zh-CN/content/admin/installation/setting-up-a-github-enterprise-server-instance/setting-up-a-staging-instance.md
index ecfcde73e0..6ae6322477 100644
--- a/translations/zh-CN/content/admin/installation/setting-up-a-github-enterprise-server-instance/setting-up-a-staging-instance.md
+++ b/translations/zh-CN/content/admin/installation/setting-up-a-github-enterprise-server-instance/setting-up-a-staging-instance.md
@@ -5,7 +5,7 @@ redirect_from:
   - /enterprise/admin/installation/setting-up-a-staging-instance
   - /admin/installation/setting-up-a-staging-instance
 versions:
-  ghes: "*"
+  ghes: '*'
 type: how_to
 topics:
   - Enterprise
diff --git a/translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/about-the-audit-log-for-your-enterprise.md b/translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/about-the-audit-log-for-your-enterprise.md
index fd9d8dacf6..82146c1824 100644
--- a/translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/about-the-audit-log-for-your-enterprise.md
+++ b/translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/about-the-audit-log-for-your-enterprise.md
@@ -46,9 +46,7 @@ As an enterprise owner{% ifversion ghes %} or site administrator{% endif %}, you
 {%- ifversion ghes %}
 - You can forward audit and system logs, from your enterprise to an third-party hosted monitoring system. For more information, see "[Log forwarding](/admin/monitoring-activity-in-your-enterprise/exploring-user-activity/log-forwarding)."
 {%- endif %}
-{%- ifversion ghec or ghes > 3.2 or ghae %}
 - You can use the Audit log API to view actions performed in your enterprise. For more information, see "[Using the audit log API for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/using-the-audit-log-api-for-your-enterprise)."
-{%- endif %}
 
 For a full list of audit log actions that may appear in your enterprise audit log, see "[Audit log actions for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise)."
 
diff --git a/translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise.md b/translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise.md
index 863a314cec..c4610e9a26 100644
--- a/translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise.md
+++ b/translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise.md
@@ -265,7 +265,6 @@ Action                        | Description
 | `config_entry.update` | A configuration setting was edited. These events are only visible in the site admin audit log. The type of events recorded relate to:</br>- Enterprise settings and policies</br>- Organization and repository permissions and settings</br>- Git, Git LFS, {% data variables.product.prodname_github_connect %}, {% data variables.product.prodname_registry %}, project, and code security settings.
 {%- endif %}
 
-{%- ifversion fpt or ghec or ghes > 3.2 or ghae %}
 ## `dependabot_alerts` category actions
 
 | Action | Description
@@ -285,9 +284,8 @@ Action                        | Description
 | Action | Description
 |--------|-------------
 | `dependabot_repository_access.repositories_updated` | The repositories that {% data variables.product.prodname_dependabot %} can access were updated.
-{%- endif %}
 
-{%- ifversion fpt or ghec or ghes > 3.2 %}
+{%- ifversion fpt or ghec or ghes %}
 ## `dependabot_security_updates` category actions
 
 | Action | Description
@@ -1341,7 +1339,7 @@ Before you'll see `git` category actions, you must enable Git events in the audi
 |--------|-------------
 | `staff.disable_repo`          | An organization{% ifversion ghes %}, repository or site{% else %} or repository{% endif %} administrator disabled access to a repository and all of its forks.
 | `staff.enable_repo`           | An organization{% ifversion ghes %}, repository or site{% else %} or repository{% endif %} administrator re-enabled access to a repository and all of its forks.
-{%- ifversion ghes > 3.2 or ghae %}
+{%- ifversion ghes or ghae %}
 | `staff.exit_fake_login`       | An enterprise owner{% ifversion ghes %} or site administrator{% endif %} ended an impersonation session on {% data variables.product.product_name %}.
 | `staff.fake_login`            | An enterprise owner{% ifversion ghes %} or site administrator{% endif %} signed into {% data variables.product.product_name %} as another user.
 {%- endif %}
diff --git a/translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/configuring-the-audit-log-for-your-enterprise.md b/translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/configuring-the-audit-log-for-your-enterprise.md
index 0bcdaf5744..5c4f84902a 100644
--- a/translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/configuring-the-audit-log-for-your-enterprise.md
+++ b/translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/configuring-the-audit-log-for-your-enterprise.md
@@ -1,8 +1,8 @@
 ---
 title: Configuring the audit log for your enterprise
-intro: "You can configure settings for your enterprise's audit log."
+intro: You can configure settings for your enterprise's audit log.
 shortTitle: Configure audit logs
-permissions: 'Enterprise owners can configure the audit log.'
+permissions: Enterprise owners can configure the audit log.
 versions:
   feature: audit-data-retention-tab
 type: how_to
@@ -53,4 +53,4 @@ Before you can enable Git events in the audit log, you must configure a retentio
    ![Screenshot of the checkbox to enable Git events in the audit log](/assets/images/help/enterprises/enable-git-events-checkbox.png)
 1. Click **Save**.
 
-{% endif %}
\ No newline at end of file
+{% endif %}
diff --git a/translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/using-the-audit-log-api-for-your-enterprise.md b/translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/using-the-audit-log-api-for-your-enterprise.md
index eb7ca4cae4..2d570ef443 100644
--- a/translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/using-the-audit-log-api-for-your-enterprise.md
+++ b/translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/using-the-audit-log-api-for-your-enterprise.md
@@ -1,6 +1,6 @@
 ---
 title: Using the audit log API for your enterprise
-intro: 'You can programmatically retrieve enterprise events with the{% ifversion ghec or ghes > 3.2 %} REST or{% endif %} GraphQL API.'
+intro: 'You can programmatically retrieve enterprise events with the REST or GraphQL API.'
 shortTitle: Audit log API
 permissions: 'Enterprise owners {% ifversion ghes %}and site administrators {% endif %}can use the audit log API.'
 miniTocMaxHeadingLevel: 3
@@ -18,7 +18,7 @@ topics:
 
 ## Using the audit log API
 
-You can interact with the audit log using the GraphQL API{% ifversion ghec or ghes > 3.2 or ghae %} or the REST API{% endif %}. 
+You can interact with the audit log using the GraphQL API or the REST API. 
 
 Timestamps and date fields in the API response are measured in [UTC epoch milliseconds](http://en.wikipedia.org/wiki/Unix_time).
 
@@ -106,7 +106,6 @@ This query uses the [AuditEntry](/graphql/reference/interfaces#auditentry) inter
 
 For more query examples, see the [platform-samples repository](https://github.com/github/platform-samples/blob/master/graphql/queries).
 
-{% ifversion ghec or ghes > 3.2 or ghae %}
 ## Querying the audit log REST API
 
 To ensure your intellectual property is secure, and you maintain compliance for your enterprise, you can use the audit log REST API to keep copies of your audit log data and monitor:
@@ -137,5 +136,3 @@ curl -H "Authorization: Bearer TOKEN" \
 --request GET \
 "https://api.github.com/enterprises/avocado-corp/audit-log?phrase=action:pull_request+created:>=2022-01-01+actor:octocat"
 ```
-
-{% endif %}
diff --git a/translations/zh-CN/content/admin/overview/about-github-for-enterprises.md b/translations/zh-CN/content/admin/overview/about-github-for-enterprises.md
index 3678330829..4fc01bf2aa 100644
--- a/translations/zh-CN/content/admin/overview/about-github-for-enterprises.md
+++ b/translations/zh-CN/content/admin/overview/about-github-for-enterprises.md
@@ -1,6 +1,6 @@
 ---
 title: About GitHub for enterprises
-intro: "Businesses can use {% data variables.product.prodname_dotcom %}'s enterprise products to improve their entire software development lifecycle."
+intro: 'Businesses can use {% data variables.product.prodname_dotcom %}''s enterprise products to improve their entire software development lifecycle.'
 versions:
   ghec: '*'
   ghes: '*'
diff --git a/translations/zh-CN/content/admin/overview/about-upgrades-to-new-releases.md b/translations/zh-CN/content/admin/overview/about-upgrades-to-new-releases.md
index bdda51ba2f..34b2bfeba4 100644
--- a/translations/zh-CN/content/admin/overview/about-upgrades-to-new-releases.md
+++ b/translations/zh-CN/content/admin/overview/about-upgrades-to-new-releases.md
@@ -9,15 +9,13 @@ type: overview
 topics:
   - Enterprise
   - Upgrades
-ms.openlocfilehash: 196745ee4ededaf78bd5afe876e4afa09141e930
-ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.openlocfilehash: b3a2d340ef73ffe92f2117caf38a84e76ba0c8d1
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: zh-CN
-ms.lasthandoff: 09/11/2022
-ms.locfileid: '145099943'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148108039'
 ---
-{% ifversion ghes < 3.3 %}{% data reusables.enterprise.upgrade-ghes-for-features %}{% endif %}
-
 {% data reusables.enterprise.constantly-improving %}{% ifversion ghae %}{% data variables.product.prodname_ghe_managed %} 是一项完全管理的服务，因此 {% data variables.product.company_short %} 可完成企业的升级过程。{% endif %}
 
 功能版本包括新的功能和功能升级，通常每季度进行一次。 {% ifversion ghae %}{% data variables.product.company_short %} 会将您的企业升级到最新的功能版本。 您的企业如有任何计划内的停机，都会提前通知您。{% endif %}
diff --git a/translations/zh-CN/content/admin/packages/migrating-your-enterprise-to-the-container-registry-from-the-docker-registry.md b/translations/zh-CN/content/admin/packages/migrating-your-enterprise-to-the-container-registry-from-the-docker-registry.md
index 9305406cc8..9a64fab4c6 100644
--- a/translations/zh-CN/content/admin/packages/migrating-your-enterprise-to-the-container-registry-from-the-docker-registry.md
+++ b/translations/zh-CN/content/admin/packages/migrating-your-enterprise-to-the-container-registry-from-the-docker-registry.md
@@ -2,9 +2,9 @@
 title: Migrating your enterprise to the Container registry from the Docker registry
 intro: 'You can migrate Docker images previously stored in the Docker registry on {% data variables.location.product_location %} to the {% data variables.product.prodname_container_registry %}.'
 product: '{% data reusables.gated-features.packages %}'
-permissions: "Enterprise owners can migrate Docker images to the {% data variables.product.prodname_container_registry %}."
+permissions: 'Enterprise owners can migrate Docker images to the {% data variables.product.prodname_container_registry %}.'
 versions:
-  feature: 'docker-ghcr-enterprise-migration'
+  feature: docker-ghcr-enterprise-migration
 shortTitle: Migrate to Container registry
 topics:
   - Containers
diff --git a/translations/zh-CN/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-projects-in-your-enterprise.md b/translations/zh-CN/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-projects-in-your-enterprise.md
new file mode 100644
index 0000000000..a462a49406
--- /dev/null
+++ b/translations/zh-CN/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-projects-in-your-enterprise.md
@@ -0,0 +1,70 @@
+---
+title: 在企业中为项目实施策略
+intro: '可以为企业组织内的 {% data variables.projects.projects_v2_and_v1 %} 实施策略，或者允许在每个组织中设置策略。'
+permissions: Enterprise owners can enforce policies for projects in an enterprise.
+redirect_from:
+  - /articles/enforcing-project-board-settings-for-organizations-in-your-business-account
+  - /articles/enforcing-project-board-policies-for-organizations-in-your-enterprise-account
+  - /articles/enforcing-project-board-policies-in-your-enterprise-account
+  - /github/setting-up-and-managing-your-enterprise-account/enforcing-project-board-policies-in-your-enterprise-account
+  - /github/setting-up-and-managing-your-enterprise/enforcing-project-board-policies-in-your-enterprise-account
+  - /github/setting-up-and-managing-your-enterprise/setting-policies-for-organizations-in-your-enterprise-account/enforcing-project-board-policies-in-your-enterprise-account
+  - /admin/policies/enforcing-policies-for-your-enterprise/enforcing-project-board-policies-in-your-enterprise
+versions:
+  ghec: '*'
+  ghes: '*'
+  ghae: '*'
+type: how_to
+topics:
+  - Enterprise
+  - Policies
+  - Projects
+shortTitle: Project board policies
+ms.openlocfilehash: 2bb72b21094fadea8f584eb4749ed0cea69619ee
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: zh-CN
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148108021'
+---
+## 关于用于企业中的项目的策略
+
+可以实施策略来控制企业成员管理 {% data variables.projects.projects_v2_and_v1 %} 的方式，也可以允许组织所有者在组织级别管理 {% data variables.projects.projects_v2_and_v1 %} 的策略。{% ifversion project-visibility-policy %}
+
+某些策略同时应用于 {% data variables.product.prodname_projects_v2 %}（新项目体验）和 {% data variables.product.prodname_projects_v1 %}（以前的体验），而某些策略仅应用于 {% data variables.product.prodname_projects_v1 %}。 有关每种体验的详细信息，请参阅“[关于 {% data variables.product.prodname_projects_v2 %}](/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)”和“[关于 {% data variables.product.prodname_projects_v1 %}](/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)”。
+{% else %}有关详细信息，请参阅“[关于项目板](/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)”。{% endif %}
+
+## 为组织范围项目实施策略
+
+在企业拥有的所有组织中，可以启用或禁用组织范围的项目板，或允许所有者在组织级别管理设置。
+
+{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.policies-tab %} {% data reusables.enterprise-accounts.projects-tab %}
+4. 在“Organization projects”（组织项目）下，审查有关更改设置的信息。 {% data reusables.enterprise-accounts.view-current-policy-config-orgs %}
+5. 在“Organization projects”（组织项目）下，使用下拉菜单并选择策略。
+  ![带有组织项目板策略选项的下拉菜单](/assets/images/help/business-accounts/organization-projects-policy-drop-down.png)
+
+{% ifversion project-visibility-policy %}
+## 为项目的可见性更改实施策略
+
+在企业拥有的所有组织中，你可以启用或禁用具有项目管理权限的人员更改项目可见性的能力，也可以允许所有者在组织级别管理设置。
+
+{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.policies-tab %} {% data reusables.enterprise-accounts.projects-tab %}
+1. 在“项目可见性更改权限”下，检查有关更改设置的信息。 {% data reusables.enterprise-accounts.view-current-policy-config-orgs %}
+1. 选择下拉菜单，然后单击策略。
+
+   ![用于配置“项目可见性更改权限”策略的下拉菜单的屏幕截图](/assets/images/help/business-accounts/project-visibility-change-drop-down.png){% endif %}
+
+{% ifversion projects-v1 %}
+## 为 {% data variables.product.prodname_projects_v1 %} 实施策略
+
+某些策略仅应用于 {% data variables.product.prodname_projects_v1 %}。
+
+### 为存储库项目实施策略
+
+在企业拥有的所有组织中，可以启用或禁用存储库级别项目，或允许所有者在组织级别管理设置。
+
+{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.policies-tab %} {% data reusables.enterprise-accounts.projects-tab %}
+4. 在“Repository projects”（仓库项目）下，审查有关更改设置的信息。 {% data reusables.enterprise-accounts.view-current-policy-config-orgs %}
+5. 在“Repository projects”（仓库项目）下，使用下拉菜单并选择策略。
+
+   ![带有存储库项目板策略选项的下拉菜单](/assets/images/help/business-accounts/repository-projects-policy-drop-down.png){% endif %}
diff --git a/translations/zh-CN/content/admin/policies/index.md b/translations/zh-CN/content/admin/policies/index.md
index 1321a88c56..7036f99838 100644
--- a/translations/zh-CN/content/admin/policies/index.md
+++ b/translations/zh-CN/content/admin/policies/index.md
@@ -14,11 +14,11 @@ children:
   - /enforcing-policies-for-your-enterprise
   - /enforcing-policy-with-pre-receive-hooks
 shortTitle: Set policies
-ms.openlocfilehash: 075d4f949435539c9c45ae651aedb0878f3317db
-ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d
+ms.openlocfilehash: 6fae4d9a9aa9c137be114b51eb90d79eb16d71df
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: zh-CN
-ms.lasthandoff: 09/11/2022
-ms.locfileid: '147400368'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148108127'
 ---
 
diff --git a/translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise/index.md b/translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise/index.md
index 400e09e79c..d7213bee10 100644
--- a/translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise/index.md
+++ b/translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise/index.md
@@ -33,11 +33,11 @@ children:
   - /managing-projects-using-jira
   - /continuous-integration-using-jenkins
 shortTitle: Manage organizations
-ms.openlocfilehash: 5d1430bc4efff03e6cddfe81f3c018d4f2064155
-ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d
+ms.openlocfilehash: 333d9b8d50bcdb86f709a447fee5a4078353dfe2
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: zh-CN
-ms.lasthandoff: 09/11/2022
-ms.locfileid: '147884243'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148108126'
 ---
 
diff --git a/translations/zh-CN/content/admin/user-management/managing-users-in-your-enterprise/impersonating-a-user.md b/translations/zh-CN/content/admin/user-management/managing-users-in-your-enterprise/impersonating-a-user.md
index 1af123b3ed..3e5816df56 100644
--- a/translations/zh-CN/content/admin/user-management/managing-users-in-your-enterprise/impersonating-a-user.md
+++ b/translations/zh-CN/content/admin/user-management/managing-users-in-your-enterprise/impersonating-a-user.md
@@ -3,7 +3,7 @@ title: 模拟用户
 intro: 您可以出于故障排除、取消阻止和其他合法原因而模拟用户并代表用户执行操作。
 permissions: Enterprise owners can impersonate users within their enterprise.
 versions:
-  ghes: '>3.2'
+  ghes: '*'
   ghae: '*'
 type: how_to
 topics:
@@ -11,12 +11,12 @@ topics:
   - Enterprise
   - User account
 shortTitle: Impersonate a user
-ms.openlocfilehash: 8e237c6ace7e7feb4badefcbd863b0974c983732
-ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.openlocfilehash: df0513c3ca2931378e656f228939540dd5ea5816
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: zh-CN
-ms.lasthandoff: 09/10/2022
-ms.locfileid: '145098959'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148108174'
 ---
 ## 关于用户模拟
 
diff --git a/translations/zh-CN/content/admin/user-management/managing-users-in-your-enterprise/index.md b/translations/zh-CN/content/admin/user-management/managing-users-in-your-enterprise/index.md
index 3bf94a262e..9b4229a632 100644
--- a/translations/zh-CN/content/admin/user-management/managing-users-in-your-enterprise/index.md
+++ b/translations/zh-CN/content/admin/user-management/managing-users-in-your-enterprise/index.md
@@ -36,11 +36,11 @@ children:
   - /customizing-user-messages-for-your-enterprise
   - /rebuilding-contributions-data
 shortTitle: Manage users
-ms.openlocfilehash: 9ec6d7dc6822e71ff72542dd6b67ded031a1c44d
-ms.sourcegitcommit: ac00e2afa6160341c5b258d73539869720b395a4
+ms.openlocfilehash: 763277882c2af96505c2a6d4c236c05475ab9f3f
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: zh-CN
-ms.lasthandoff: 09/09/2022
-ms.locfileid: '147876023'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148007883'
 ---
 
diff --git a/translations/zh-CN/content/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise.md b/translations/zh-CN/content/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise.md
index 0596124afa..9fed0e1cbb 100644
--- a/translations/zh-CN/content/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise.md
+++ b/translations/zh-CN/content/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise.md
@@ -1,7 +1,7 @@
 ---
 title: Viewing people in your enterprise
 intro: 'To audit access to enterprise-owned resources or user license usage, enterprise owners can view every administrator and member of the enterprise.'
-permissions: 'Enterprise owners can view the people in an enterprise.'
+permissions: Enterprise owners can view the people in an enterprise.
 redirect_from:
   - /github/setting-up-and-managing-your-enterprise-account/viewing-people-in-your-enterprise-account
   - /articles/viewing-people-in-your-enterprise-account
@@ -116,7 +116,7 @@ If you use {% data variables.product.prodname_vss_ghe %}, the list of pending in
 
 ## Viewing suspended members in an {% data variables.enterprise.prodname_emu_enterprise %}
 
-If your enterprise uses {% data variables.product.prodname_emus %}, you can also view suspended users. Suspended users are members who have been deprovisioned after being unassigned from the {% data variables.product.prodname_emu_idp_application %} application or deleted from the identity provider. For more information, see "[About Enterprise Managed Users](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/about-enterprise-managed-users)."
+If your enterprise uses {% data variables.product.prodname_emus %}, you can view suspended users. Suspended users are members who have been deprovisioned after being unassigned from the {% data variables.product.prodname_emu_idp_application %} application or deleted from the identity provider. For more information, see "[About {% data variables.product.prodname_emus %}](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/about-enterprise-managed-users)."
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.people-tab %}
@@ -129,6 +129,21 @@ If your enterprise uses {% data variables.product.prodname_emus %}, you can also
 
 You can view a list of all dormant users {% ifversion ghes or ghae %} who have not been suspended and {% endif %}who are not site administrators. {% data reusables.enterprise-accounts.dormant-user-activity-threshold %} For more information, see "[Managing dormant users](/admin/user-management/managing-users-in-your-enterprise/managing-dormant-users)."
 
+{% ifversion filter-by-enterprise-member-type %}
+## Filtering by member type{% ifversion ghec %} in an {% data variables.enterprise.prodname_emu_enterprise %}{% endif %}
+
+{% ifversion ghec %}If your enterprise uses {% data variables.product.prodname_emus %}, you{% elsif ghes or ghae %}You{% endif %} can filter the member list of an organization by type to determine if memberships are managed through an IdP or managed directly. Memberships managed through an IdP were added through an IdP group, and the IdP group was connected to a team within the organization. Memberships managed directly were added to the organization manually. The way a membership is mananaged in an organization determines how it must be removed. You can use this filter to determine how members were added to an organization, so you know how to remove them.{% ifversion ghec %} For more information, see "[About {% data variables.product.prodname_emus %}](/enterprise-cloud@latest/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/about-enterprise-managed-users#about-organization-membership-management)."{% endif %}
+
+{% data reusables.enterprise-accounts.access-enterprise %}
+1. Under "Organizations," in the search bar, begin typing the organization's name until the organization appears in the search results, then click the name of the organization.
+   ![Screenshot of the search field for organizations](/assets/images/help/enterprises/organization-search.png)
+1. Under the organization name, click {% octicon "person" aria-label="The Person icon" %} **People**.
+   ![Screenshot of the People tab](/assets/images/help/enterprises/emu-organization-people-tab.png)
+1. Above the list of members, click **Type**, then select the type of members you want to view.
+   ![Screenshot of the "Type" button](/assets/images/help/enterprises/filter-by-member-type.png)
+
+{% endif %}
+
 {% ifversion ghec or ghes %}
 ## Viewing members without an email address from a verified domain
 
diff --git a/translations/zh-CN/content/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on.md b/translations/zh-CN/content/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on.md
index c0787f5ae1..b2c8f13f0b 100644
--- a/translations/zh-CN/content/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on.md
+++ b/translations/zh-CN/content/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on.md
@@ -24,13 +24,15 @@ If you can't access {% data variables.product.product_name %}, contact your loca
 
 {% endif %}
 
-{% ifversion fpt or ghec %}
+{% ifversion ghec %}
 
 {% data reusables.saml.dotcom-saml-explanation %} Organization owners can invite your personal account on {% data variables.product.prodname_dotcom %} to join their organization that uses SAML SSO, which allows you to contribute to the organization and retain your existing identity and contributions on {% data variables.product.prodname_dotcom %}.
 
 If you're a member of an {% data variables.enterprise.prodname_emu_enterprise %}, you will instead use a new account that is provisioned for you and controlled by your enterprise. {% data reusables.enterprise-accounts.emu-more-info-account %}
 
-When you access private resources within an organization that uses SAML SSO, {% data variables.product.prodname_dotcom %} will redirect you to the organization's SAML IdP to authenticate. After you successfully authenticate with your account on the IdP, the IdP redirects you back to {% data variables.product.prodname_dotcom %}, where you can access the organization's resources.
+When you attempt to access most resources within an organization that uses SAML SSO, {% data variables.product.prodname_dotcom %} will redirect you to the organization's SAML IdP to authenticate. After you successfully authenticate with your account on the IdP, the IdP redirects you back to {% data variables.product.prodname_dotcom %}, where you can access the organization's resources.
+
+{% data reusables.saml.resources-without-sso %}
 
 {% data reusables.saml.outside-collaborators-exemption %}
 
diff --git a/translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token.md b/translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token.md
index 88febb34fe..2a8409c383 100644
--- a/translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token.md
+++ b/translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token.md
@@ -1,6 +1,6 @@
 ---
 title: Creating a personal access token
-intro: You can create a {% data variables.product.pat_generic %} to use in place of a password with the command line or with the API.
+intro: 'You can create a {% data variables.product.pat_generic %} to use in place of a password with the command line or with the API.'
 redirect_from:
   - /articles/creating-an-oauth-token-for-command-line-use
   - /articles/creating-an-access-token-for-command-line-use
@@ -17,7 +17,7 @@ versions:
 topics:
   - Identity
   - Access management
-shortTitle: Create a {% data variables.product.pat_generic %}
+shortTitle: 'Create a {% data variables.product.pat_generic %}'
 ---
 
 {% warning %}
@@ -112,9 +112,9 @@ If you selected an organization as the resource owner and the organization requi
 {% ifversion pat-v2 %}1. In the left sidebar, under **{% octicon "key" aria-label="The key icon" %} {% data variables.product.pat_generic_caps %}s**, click **Tokens (classic)**.{% else %}{% data reusables.user-settings.personal_access_tokens %}{% endif %}
 {% ifversion pat-v2%}1. Select **Generate new token**, then click **Generate new token (classic)**.{% else %}{% data reusables.user-settings.generate_new_token %}{% endif %}
 5. Give your token a descriptive name.
-   ![Token description field](/assets/images/help/settings/token_description.png){% ifversion fpt or ghes > 3.2 or ghae or ghec %}
+   ![Token description field](/assets/images/help/settings/token_description.png)
 6. To give your token an expiration, select the **Expiration** drop-down menu, then click a default or use the calendar picker.
-   ![Token expiration field](/assets/images/help/settings/token_expiration.png){% endif %}
+   ![Token expiration field](/assets/images/help/settings/token_expiration.png)
 7. Select the scopes you'd like to grant this token. To use your token to access repositories from the command line, select **repo**. A token with no assigned scopes can only access public information. For more information, see "[Available scopes](/apps/building-oauth-apps/scopes-for-oauth-apps#available-scopes)".
    {% ifversion fpt or ghes or ghec %}
    ![Selecting token scopes](/assets/images/help/settings/token_scopes.gif)
@@ -143,5 +143,5 @@ Instead of manually entering your {% data variables.product.pat_generic %} for e
 
 ## Further reading
 
-- "[About authentication to GitHub](/github/authenticating-to-github/about-authentication-to-github)"{% ifversion fpt or ghae or ghes > 3.2 or ghec %}
-- "[Token expiration and revocation](/github/authenticating-to-github/keeping-your-account-and-data-secure/token-expiration-and-revocation)"{% endif %}
+- "[About authentication to GitHub](/github/authenticating-to-github/about-authentication-to-github)"
+- "[Token expiration and revocation](/github/authenticating-to-github/keeping-your-account-and-data-secure/token-expiration-and-revocation)"
diff --git a/translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/reviewing-your-security-log.md b/translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/reviewing-your-security-log.md
index 477a01b0a1..ca865d3bdf 100644
--- a/translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/reviewing-your-security-log.md
+++ b/translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/reviewing-your-security-log.md
@@ -109,7 +109,7 @@ An overview of some of the most common actions that are recorded as events in th
 | Action | Description
 |------------------|-------------------
 | `create` | Triggered when you [grant access to an {% data variables.product.prodname_oauth_app %}](/github/authenticating-to-github/keeping-your-account-and-data-secure/authorizing-oauth-apps).
-| `destroy` | Triggered when you [revoke an {% data variables.product.prodname_oauth_app %}'s access to your account](/articles/reviewing-your-authorized-integrations){% ifversion fpt or ghae or ghes > 3.2 or ghec %} and when [authorizations are revoked or expire](/github/authenticating-to-github/keeping-your-account-and-data-secure/token-expiration-and-revocation).{% else %}.{% endif %}
+| `destroy` | Triggered when you [revoke an {% data variables.product.prodname_oauth_app %}'s access to your account](/articles/reviewing-your-authorized-integrations) and when [authorizations are revoked or expire](/github/authenticating-to-github/keeping-your-account-and-data-secure/token-expiration-and-revocation).
 
 {% ifversion fpt or ghec %}
 
diff --git a/translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/token-expiration-and-revocation.md b/translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/token-expiration-and-revocation.md
index 877fedd33b..4b4832b39c 100644
--- a/translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/token-expiration-and-revocation.md
+++ b/translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/token-expiration-and-revocation.md
@@ -14,7 +14,7 @@ redirect_from:
   - /github/authenticating-to-github/keeping-your-account-and-data-secure/token-expiration-and-revocation
 ---
 
-When a token {% ifversion fpt or ghae or ghes > 3.2 or ghec %}has expired or {% endif %} has been revoked, it can no longer be used to authenticate Git and API requests. It is not possible to restore an expired or revoked token, you or the application will need to create a new token.
+When a token has expired or has been revoked, it can no longer be used to authenticate Git and API requests. It is not possible to restore an expired or revoked token, you or the application will need to create a new token.
 
 This article explains the possible reasons your {% data variables.product.product_name %} token might be revoked or expire.
 
@@ -24,11 +24,9 @@ This article explains the possible reasons your {% data variables.product.produc
 
 {% endnote %}
 
-{% ifversion fpt or ghae or ghes > 3.2 or ghec %}
 ## Token revoked after reaching its expiration date
 
 When you create a {% data variables.product.pat_generic %}, we recommend that you set an expiration for your token. Upon reaching your token's expiration date, the token is automatically revoked. For more information, see "[Creating a {% data variables.product.pat_generic %}](/github/authenticating-to-github/keeping-your-account-and-data-secure/creating-a-personal-access-token)."
-{% endif %}
 
 {% ifversion fpt or ghec %}
 ## Token revoked when pushed to a public repository or public gist
diff --git a/translations/zh-CN/content/authentication/managing-commit-signature-verification/signing-commits.md b/translations/zh-CN/content/authentication/managing-commit-signature-verification/signing-commits.md
index e9b3200e36..5ddd3f123f 100644
--- a/translations/zh-CN/content/authentication/managing-commit-signature-verification/signing-commits.md
+++ b/translations/zh-CN/content/authentication/managing-commit-signature-verification/signing-commits.md
@@ -1,6 +1,6 @@
 ---
-title: Signing commits
-intro: You can sign commits locally using GPG{% ifversion ssh-commit-verification %}, SSH,{% endif %} or S/MIME.
+title: 对提交签名
+intro: '可以使用 GPG{% ifversion ssh-commit-verification %}、SSH、{% endif %} 或 S/MIME 在本地对提交进行签名。'
 redirect_from:
   - /articles/signing-commits-and-tags-using-gpg
   - /articles/signing-commits-using-gpg
@@ -15,42 +15,48 @@ versions:
 topics:
   - Identity
   - Access management
+ms.openlocfilehash: 8550393cc31571756099ac364698434f38b02cfa
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: zh-CN
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148106747'
 ---
 {% data reusables.gpg.desktop-support-for-commit-signing %}
 
 {% tip %}
 
-**Tips:**
+**提示：**
 
-To configure your Git client to sign commits by default for a local repository, in Git versions 2.0.0 and above, run `git config commit.gpgsign true`. To sign all commits by default in any local repository on your computer, run `git config --global commit.gpgsign true`.
+若要将 Git 客户端配置为默认对本地存储库的提交进行签名，请在 Git 版本 2.0.0 及更高版本中，运行 `git config commit.gpgsign true`。 要在计算机上的任何本地存储库中默认对所有提交进行签名，请运行 `git config --global commit.gpgsign true`。
 
-To store your GPG key passphrase so you don't have to enter it every time you sign a commit, we recommend using the following tools:
-  - For Mac users, the [GPG Suite](https://gpgtools.org/) allows you to store your GPG key passphrase in the Mac OS Keychain.
-  - For Windows users, the [Gpg4win](https://www.gpg4win.org/) integrates with other Windows tools.
+要存储 GPG 密钥密码，以便无需在每次对提交签名时输入该密码，我们建议使用以下工具：
+  - 对于 Mac 用户，[GPG Suite](https://gpgtools.org/) 支持在 Mac OS 密钥链中存储 GPG 密钥密码。
+  - 对于 Windows 用户，[Gpg4win](https://www.gpg4win.org/) 将与其他 Windows 工具集成。
 
-You can also manually configure [gpg-agent](http://linux.die.net/man/1/gpg-agent) to save your GPG key passphrase, but this doesn't integrate with Mac OS Keychain like ssh-agent and requires more setup.
+你也可以手动配置 [gpg-agent](http://linux.die.net/man/1/gpg-agent) 以保存 GPG 密钥密码，但这不会与 Mac OS 密钥链（如 ssh 代理）集成，并且需要更多设置。
 
 {% endtip %}
 
-If you have multiple keys or are attempting to sign commits or tags with a key that doesn't match your committer identity, you should [tell Git about your signing key](/articles/telling-git-about-your-signing-key).
+如果你有多个密钥或尝试使用与你的提交者标识不匹配的密钥对提交或标记进行签名，应[将签名密钥告知 Git](/articles/telling-git-about-your-signing-key)。
 
-1. When committing changes in your local branch, add the -S flag to the git commit command:
+1. 当本地分支中的提交更改时，请将 S 标志添加到 git commit 命令：
   ```shell
   $ git commit -S -m "YOUR_COMMIT_MESSAGE"
   # Creates a signed commit
   ```
-2. If you're using GPG, after you create your commit, provide the passphrase you set up when you [generated your GPG key](/articles/generating-a-new-gpg-key).
-3. When you've finished creating commits locally, push them to your remote repository on {% data variables.product.product_name %}:
+2. 如果使用 GPG，创建提交后，请提供[生成 GPG 密钥](/articles/generating-a-new-gpg-key)时设置的密码。
+3. 在本地完成创建提交后，将其推送到 {% data variables.product.product_name %} 上的远程仓库：
   ```shell
   $ git push
   # Pushes your local commits to the remote repository
   ```
-4. On {% data variables.product.product_name %}, navigate to your pull request.
+4. 在 {% data variables.product.product_name %} 上，导航到您的拉取请求。
 {% data reusables.repositories.review-pr-commits %}
-5. To view more detailed information about the verified signature, click Verified.
-![Signed commit](/assets/images/help/commits/gpg-signed-commit-verified-without-details.png)
+5. 要查看关于已验证签名的更多详细信息，请单击 Verified（已验证）。
+![已签名提交](/assets/images/help/commits/gpg-signed-commit-verified-without-details.png)
 
-## Further reading
+## 延伸阅读
 
-* "[Telling Git about your signing key](/articles/telling-git-about-your-signing-key)"
-* "[Signing tags](/articles/signing-tags)"
+* “[将签名密钥告知 Git](/articles/telling-git-about-your-signing-key)”
+* [对标记签名](/articles/signing-tags)
diff --git a/translations/zh-CN/content/authentication/managing-commit-signature-verification/signing-tags.md b/translations/zh-CN/content/authentication/managing-commit-signature-verification/signing-tags.md
index e5371adbc6..c019e0bdba 100644
--- a/translations/zh-CN/content/authentication/managing-commit-signature-verification/signing-tags.md
+++ b/translations/zh-CN/content/authentication/managing-commit-signature-verification/signing-tags.md
@@ -1,6 +1,6 @@
 ---
-title: Signing tags
-intro: You can sign tags locally using GPG{% ifversion ssh-commit-verification %}, SSH,{% endif %} or S/MIME.
+title: 对标记签名
+intro: '可以使用 GPG{% ifversion ssh-commit-verification %}、SSH、{% endif %} 或 S/MIME 在本地对标记进行签名。'
 redirect_from:
   - /articles/signing-tags-using-gpg
   - /articles/signing-tags
@@ -14,23 +14,29 @@ versions:
 topics:
   - Identity
   - Access management
+ms.openlocfilehash: 22bdc1c5095a8fa82d2ac406a19dc633f8f44fc6
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: zh-CN
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148106675'
 ---
 {% data reusables.gpg.desktop-support-for-commit-signing %}
 
-1. To sign a tag, add `-s` to your `git tag` command.
+1. 若要对标记进行签名，请将 `-s` 添加到 `git tag` 命令。
   ```shell
   $ git tag -s MYTAG
   # Creates a signed tag
   ```
-2. Verify your signed tag by running `git tag -v [tag-name]`.
+2. 通过运行 `git tag -v [tag-name]` 验证已签名的标记。
   ```shell
   $ git tag -v MYTAG
   # Verifies the signed tag
   ```
 
-## Further reading
+## 延伸阅读
 
-- "[Viewing your repository's tags](/articles/viewing-your-repositorys-tags)"
-- "[Telling Git about your signing key](/articles/telling-git-about-your-signing-key)"
-- "[Associating an email with your GPG key](/articles/associating-an-email-with-your-gpg-key)"
-- "[Signing commits](/articles/signing-commits)"
+- [查看存储库的标记](/articles/viewing-your-repositorys-tags)
+- “[将签名密钥告知 Git](/articles/telling-git-about-your-signing-key)”
+- [将电子邮件与 GPG 密钥关联](/articles/associating-an-email-with-your-gpg-key)
+- [对提交签名](/articles/signing-commits)
diff --git a/translations/zh-CN/content/billing/index.md b/translations/zh-CN/content/billing/index.md
index 1b6614c340..54fb7a87a5 100644
--- a/translations/zh-CN/content/billing/index.md
+++ b/translations/zh-CN/content/billing/index.md
@@ -54,11 +54,11 @@ children:
   - /managing-billing-for-github-marketplace-apps
   - /managing-billing-for-git-large-file-storage
   - /setting-up-paid-organizations-for-procurement-companies
-ms.openlocfilehash: 816bfb699135974a180ccf350aa04bc36dfbf25a
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: 977d170024ddec1d49f51723b654ee7171915e94
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: zh-CN
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147110896'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148108175'
 ---
 
diff --git a/translations/zh-CN/content/billing/managing-billing-for-github-codespaces/index.md b/translations/zh-CN/content/billing/managing-billing-for-github-codespaces/index.md
index b565c2a921..839d5dc496 100644
--- a/translations/zh-CN/content/billing/managing-billing-for-github-codespaces/index.md
+++ b/translations/zh-CN/content/billing/managing-billing-for-github-codespaces/index.md
@@ -11,3 +11,4 @@ children:
   - /viewing-your-github-codespaces-usage
   - /managing-spending-limits-for-github-codespaces
 ---
+
diff --git a/translations/zh-CN/content/billing/managing-billing-for-github-codespaces/viewing-your-github-codespaces-usage.md b/translations/zh-CN/content/billing/managing-billing-for-github-codespaces/viewing-your-github-codespaces-usage.md
index 9652fd43bd..68d34a6ab0 100644
--- a/translations/zh-CN/content/billing/managing-billing-for-github-codespaces/viewing-your-github-codespaces-usage.md
+++ b/translations/zh-CN/content/billing/managing-billing-for-github-codespaces/viewing-your-github-codespaces-usage.md
@@ -54,4 +54,4 @@ Enterprise owners and billing managers can view {% data variables.product.prodna
 
 ## Further reading
 
-- "[Listing the codespaces in your organization](/codespaces/managing-codespaces-for-your-organization/listing-the-codespaces-in-your-organization)"
\ No newline at end of file
+- "[Listing the codespaces in your organization](/codespaces/managing-codespaces-for-your-organization/listing-the-codespaces-in-your-organization)"
diff --git a/translations/zh-CN/content/billing/managing-billing-for-your-github-account/about-per-user-pricing.md b/translations/zh-CN/content/billing/managing-billing-for-your-github-account/about-per-user-pricing.md
index 5f06513eaa..57706ab231 100644
--- a/translations/zh-CN/content/billing/managing-billing-for-your-github-account/about-per-user-pricing.md
+++ b/translations/zh-CN/content/billing/managing-billing-for-your-github-account/about-per-user-pricing.md
@@ -72,9 +72,12 @@ In addition to licensed seats, your bill may include other charges, such as {% d
 - Enterprise owners who are a member or owner of at least one organization in the enterprise
 - Organization members, including owners
 - Outside collaborators on private or internal repositories owned by your organization, excluding forks
+- Dormant users
+
+If your enterprise does not use {% data variables.product.prodname_emus %}, you will also be billed for each of the following accounts:
+
 - Anyone with a pending invitation to become an organization owner or member
 - Anyone with a pending invitation to become an outside collaborator on private or internal repositories owned by your organization, excluding forks
-- Dormant users
 
 {% note %}
 
diff --git a/translations/zh-CN/content/code-security/adopting-github-advanced-security-at-scale/index.md b/translations/zh-CN/content/code-security/adopting-github-advanced-security-at-scale/index.md
index 2f22978ee2..df0e66c5f8 100644
--- a/translations/zh-CN/content/code-security/adopting-github-advanced-security-at-scale/index.md
+++ b/translations/zh-CN/content/code-security/adopting-github-advanced-security-at-scale/index.md
@@ -18,11 +18,11 @@ children:
   - /phase-4-create-internal-documentation
   - /phase-5-rollout-and-scale-code-scanning
   - /phase-6-rollout-and-scale-secret-scanning
-ms.openlocfilehash: c5624ca33d347e1be1c7bfc9a687f1c06bb828ed
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: 5430d24ecf8979f5421c6f3fea9f10ad3f580e4c
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: zh-CN
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147145343'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148108726'
 ---
 
diff --git a/translations/zh-CN/content/code-security/adopting-github-advanced-security-at-scale/introduction-to-adopting-github-advanced-security-at-scale.md b/translations/zh-CN/content/code-security/adopting-github-advanced-security-at-scale/introduction-to-adopting-github-advanced-security-at-scale.md
index f0c1a40280..6d1d8c8c2d 100644
--- a/translations/zh-CN/content/code-security/adopting-github-advanced-security-at-scale/introduction-to-adopting-github-advanced-security-at-scale.md
+++ b/translations/zh-CN/content/code-security/adopting-github-advanced-security-at-scale/introduction-to-adopting-github-advanced-security-at-scale.md
@@ -14,12 +14,12 @@ redirect_from:
   - /admin/advanced-security/deploying-github-advanced-security-in-your-enterprise
   - /admin/code-security/managing-github-advanced-security-for-your-enterprise/deploying-github-advanced-security-in-your-enterprise
 miniTocMaxHeadingLevel: 2
-ms.openlocfilehash: 0993205a2f51262c0766062995caa1c2e2714742
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: f42a461b3c53565725d6909680fa8e6a202c0439
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: zh-CN
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147145342'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148108723'
 ---
 ## 关于以下文章
 
diff --git a/translations/zh-CN/content/code-security/adopting-github-advanced-security-at-scale/phase-1-align-on-your-rollout-strategy-and-goals.md b/translations/zh-CN/content/code-security/adopting-github-advanced-security-at-scale/phase-1-align-on-your-rollout-strategy-and-goals.md
index 60a8e6e756..7380e9be79 100644
--- a/translations/zh-CN/content/code-security/adopting-github-advanced-security-at-scale/phase-1-align-on-your-rollout-strategy-and-goals.md
+++ b/translations/zh-CN/content/code-security/adopting-github-advanced-security-at-scale/phase-1-align-on-your-rollout-strategy-and-goals.md
@@ -9,12 +9,12 @@ topics:
   - Advanced Security
 shortTitle: 1. Align on strategy
 miniTocMaxHeadingLevel: 3
-ms.openlocfilehash: 63154ac960e4b3a9d29f41e72cd925230838069c
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: b2677cf11c300ad657f9bd6b8862fb1f292c2fb7
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: zh-CN
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147145335'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148108718'
 ---
 {% note %}
 
diff --git a/translations/zh-CN/content/code-security/adopting-github-advanced-security-at-scale/phase-2-preparing-to-enable-at-scale.md b/translations/zh-CN/content/code-security/adopting-github-advanced-security-at-scale/phase-2-preparing-to-enable-at-scale.md
index ed53b104ab..8a17f81542 100644
--- a/translations/zh-CN/content/code-security/adopting-github-advanced-security-at-scale/phase-2-preparing-to-enable-at-scale.md
+++ b/translations/zh-CN/content/code-security/adopting-github-advanced-security-at-scale/phase-2-preparing-to-enable-at-scale.md
@@ -9,12 +9,12 @@ topics:
   - Advanced Security
 shortTitle: 2. Preparation
 miniTocMaxHeadingLevel: 3
-ms.openlocfilehash: a34711765e8beb6d57215c0c8fd16519e975539d
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: 79368897c125ff23541520a253a34a2aae8c7c27
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: zh-CN
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147145333'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148108722'
 ---
 {% note %}
 
diff --git a/translations/zh-CN/content/code-security/adopting-github-advanced-security-at-scale/phase-3-pilot-programs.md b/translations/zh-CN/content/code-security/adopting-github-advanced-security-at-scale/phase-3-pilot-programs.md
index 2fce6887bc..c77f15e18a 100644
--- a/translations/zh-CN/content/code-security/adopting-github-advanced-security-at-scale/phase-3-pilot-programs.md
+++ b/translations/zh-CN/content/code-security/adopting-github-advanced-security-at-scale/phase-3-pilot-programs.md
@@ -9,12 +9,12 @@ topics:
   - Advanced Security
 shortTitle: 3. Pilot programs
 miniTocMaxHeadingLevel: 3
-ms.openlocfilehash: 3df893158c402b9180260ddd1c82c96f62b84717
-ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d
+ms.openlocfilehash: d56427173580558a192d0709ae700cbd497e2935
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: zh-CN
-ms.lasthandoff: 09/11/2022
-ms.locfileid: '147145334'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148108125'
 ---
 {% note %}
 
diff --git a/translations/zh-CN/content/code-security/adopting-github-advanced-security-at-scale/phase-4-create-internal-documentation.md b/translations/zh-CN/content/code-security/adopting-github-advanced-security-at-scale/phase-4-create-internal-documentation.md
index 7f84284d7f..3213f1b96f 100644
--- a/translations/zh-CN/content/code-security/adopting-github-advanced-security-at-scale/phase-4-create-internal-documentation.md
+++ b/translations/zh-CN/content/code-security/adopting-github-advanced-security-at-scale/phase-4-create-internal-documentation.md
@@ -9,12 +9,12 @@ topics:
   - Advanced Security
 shortTitle: 4. Create internal documentation
 miniTocMaxHeadingLevel: 3
-ms.openlocfilehash: e9852eacc95b98eca5358aafb9a9b13811888f15
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: caf35f06c3f836ea7532b7c5e9dfb419ba8c325b
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: zh-CN
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147145331'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148108124'
 ---
 {% note %}
 
diff --git a/translations/zh-CN/content/code-security/adopting-github-advanced-security-at-scale/phase-5-rollout-and-scale-code-scanning.md b/translations/zh-CN/content/code-security/adopting-github-advanced-security-at-scale/phase-5-rollout-and-scale-code-scanning.md
index 48763c37a1..007c88e662 100644
--- a/translations/zh-CN/content/code-security/adopting-github-advanced-security-at-scale/phase-5-rollout-and-scale-code-scanning.md
+++ b/translations/zh-CN/content/code-security/adopting-github-advanced-security-at-scale/phase-5-rollout-and-scale-code-scanning.md
@@ -9,12 +9,12 @@ topics:
   - Advanced Security
 shortTitle: 5. Rollout code scanning
 miniTocMaxHeadingLevel: 3
-ms.openlocfilehash: 69c5a4e88c5490cbd7dcddca902426862047dff5
-ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.openlocfilehash: abbcdf4c1e4a231a568e8d8cd488877ebdf2fd9f
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: zh-CN
-ms.lasthandoff: 09/11/2022
-ms.locfileid: '147145332'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148108123'
 ---
 {% note %}
 
diff --git a/translations/zh-CN/content/code-security/adopting-github-advanced-security-at-scale/phase-6-rollout-and-scale-secret-scanning.md b/translations/zh-CN/content/code-security/adopting-github-advanced-security-at-scale/phase-6-rollout-and-scale-secret-scanning.md
index 4afdef662c..7cf84a8886 100644
--- a/translations/zh-CN/content/code-security/adopting-github-advanced-security-at-scale/phase-6-rollout-and-scale-secret-scanning.md
+++ b/translations/zh-CN/content/code-security/adopting-github-advanced-security-at-scale/phase-6-rollout-and-scale-secret-scanning.md
@@ -1,6 +1,6 @@
 ---
-title: 第 6 阶段：推出和缩放机密扫描
-intro: '在最后阶段，重点关注推出 {% data variables.product.prodname_secret_scanning %}。 {% data variables.product.prodname_secret_scanning_caps %} 是一个比 {% data variables.product.prodname_code_scanning %} 更简单的推出工具，因为它所需的配置更少，但务必制定处理新旧结果的策略。'
+title: 'Phase 6: Rollout and scale secret scanning'
+intro: 'For the final phase, you will focus on the rollout of {% data variables.product.prodname_secret_scanning %}. {% data variables.product.prodname_secret_scanning_caps %} is a more straightforward tool to rollout than {% data variables.product.prodname_code_scanning %}, as it involves less configuration, but it''s critical to have a strategy for handling new and old results.'
 versions:
   ghes: '*'
   ghae: '*'
@@ -9,103 +9,98 @@ topics:
   - Advanced Security
 shortTitle: 6. Rollout secret scanning
 miniTocMaxHeadingLevel: 3
-ms.openlocfilehash: 791ce9924ac9f2cb918db4e1c416a8755b790bf5
-ms.sourcegitcommit: 74d6918dae0cf489c86eee049fb0f061a63df44c
-ms.translationtype: HT
-ms.contentlocale: zh-CN
-ms.lasthandoff: 07/15/2022
-ms.locfileid: '147145330'
 ---
+
 {% note %}
 
-本文是大规模采用 {% data variables.product.prodname_GH_advanced_security %} 系列的一部分。 有关本系列的上一篇文章，请参阅“[第 5 阶段：推出和缩放代码扫描](/code-security/adopting-github-advanced-security-at-scale/phase-5-rollout-and-scale-code-scanning)”。
+This article is part of a series on adopting {% data variables.product.prodname_GH_advanced_security %} at scale. For the previous article in this series, see "[Phase 5: Rollout and scale code scanning](/code-security/adopting-github-advanced-security-at-scale/phase-5-rollout-and-scale-code-scanning)."
 
 {% endnote %}
 
-可以为组织中的各个存储库或所有存储库启用机密扫描。 有关详细信息，请参阅“[管理存储库的安全和分析设置](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-security-and-analysis-settings-for-your-repository)”或“[管理组织的安全和分析设置](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)”。
+You can enable secret scanning for individual repositories or for all repositories in an organization. For more information, see "[Managing security and analysis settings for your repository](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-security-and-analysis-settings-for-your-repository)" or "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)."
 
-本文介绍了一个修正流程，该流程重点阐述为组织中的所有存储库启用 {% data variables.product.prodname_secret_scanning %}。 即使采用更加交错的方法来为各个存储库启用 {% data variables.product.prodname_secret_scanning %}，仍然可以应用本文中描述的原则。 
+This article explains a high-level process focusing on enabling {% data variables.product.prodname_secret_scanning %} for all repositories in an organization. The principles described in this article can still be applied even if you take a more staggered approach of enabling {% data variables.product.prodname_secret_scanning %} for individual repositories. 
 
-### <a name="1-focus-on-newly-committed-secrets"></a>1. 重点关注新提交的机密
+### 1. Focus on newly committed secrets
 
-启用 {% data variables.product.prodname_secret_scanning %} 时，应重点关注修复机密扫描检测到的所有新提交的凭据。 如果注重清理已提交的凭据，开发人员可能会继续意外推送新的凭据，这意味着总机密数将保持在同一水平，而不是按预期减少。 因此，必须在专注于撤销任何当前机密之前阻止泄露新凭据。
+When you enable {% data variables.product.prodname_secret_scanning %}, you should focus on remediating any newly committed credentials detected by secret scanning. If you focus on cleaning up committed credentials, developers could continue to accidentally push new credentials, which means your total secret count will stay around the same level, not decrease as intended. This is why it is essential to stop new credentials being leaked before focusing on revoking any current secrets.
 
-可以通过多种方法处理新提交的凭据，其中的示例方法如下：
+There are a few approaches for tackling newly committed credentials, but one example approach would be:
 
-1. **通知**：使用 webhook 确保正确的团队尽快看到所有新的机密警报。 创建、解决或重新开启机密警报时会触发 webhook。 然后，可以分析 webhook 有效负载，并将其集成到你和你的团队所用的任何工具中，例如 Slack、Teams、Splunk 或电子邮件。 有关详细信息，请参阅“[关于 Webhook](/developers/webhooks-and-events/webhooks/about-webhooks)”和“[Webhook 事件和有效负载](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#secret_scanning_alert)”。
-2. **跟进**：创建适用于所有机密类型的大致修正过程。 例如，可以联系提交机密的开发人员及其在该项目中的技术负责人，强调向 GitHub 提交机密的危险，并要求其撤销并更新检测到的机密。
+1. **Notify**: Use webhooks to ensure that any new secret alerts are seen by the right teams as quickly as possible. A webhook fires when a secret alert is either created, resolved, or reopened. You can then parse the webhook payload, and integrate it into any tools you and your team use such Slack, Teams, Splunk, or email. For more information, see "[About webhooks](/developers/webhooks-and-events/webhooks/about-webhooks)" and "[Webhook events and payloads](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#secret_scanning_alert)."
+2. **Follow Up**: Create a high-level remediation process that works for all secret types. For example, you could contact the developer who committed the secret and their technical lead on that project, highlighting the dangers of committing secrets to GitHub, and asking the them to revoke, and update the detected secret.
 
   {% note %}
   
-  **注意：** 你可以自动执行此步骤。 对于拥有数百存储库的大型企业和组织，手动跟进不可持续。 可以将自动化整合到第一步中定义的 webhook 流程。 Webhook 有效负载包含有关所泄露机密的存储库和组织信息。 使用此信息可以联系存储库上的当前维护人员，并创建电子邮件/消息发送给负责人或开启问题。
+  **Note:** You can automate this step. For large enterprises and organizations with hundreds of repositories, manually following up is unsustainable. You could incorporate automation into the webhook process defined in the first step. The webhook payload contains repository and organization information about the leaked secret. Using this information, you can contact the current maintainers on the repository and create an email/message to the responsible people or open an issue.
   
   {% endnote %} 
-3. **培训**：创建分配给提交机密的开发人员的内部培训文档。 在本培训文档中，你可以说明提交机密所带来的风险，并引导其查阅有关在开发中安全使用机密的最佳做法信息。 如果开发人员没有借鉴经验并继续提交机密，你可以创建升级过程，但培训通常效果很好。
+3. **Educate**: Create an internal training document assigned to the developer who committed the secret. Within this training document, you can explain the risks created by committing secrets and direct them to your best practice information about using secrets securely in development. If the a developer doesn't learn from the experience and continues to commit secrets, you could create an escalation process, but education usually works well.
 
-对泄露的任意新机密重复最后两个步骤。 此过程可鼓励开发人员负责安全地管理代码中使用的机密，并使你能够估计新提交机密的减少量。
+Repeat the last two steps for any new secrets leaked. This process encourages developers to take responsibility for managing the secrets used in their code securely, and allows you to measure the reduction in newly committed secrets.
 
 {% note %}
 
-**注意**：更先进的组织可能希望对某些类型的机密执行自动修复。 可以将名为 [GitHub 机密扫描器自动修复器](https://github.com/NickLiffen/GSSAR) 的开源计划部署到 AWS、Azure 或 GCP 环境中，并根据定义的最关键内容进行修改以自动撤销某些类型的机密。 这也是一种以更自动化的方式处理提交的新机密的绝佳方式。
+**Note:** More advanced organizations may want to perform auto-remediation of certain types of secrets. There is an open-source initiative called [GitHub Secret Scanner Auto Remediator](https://github.com/NickLiffen/GSSAR) which you can deploy into your AWS, Azure, or GCP environment and tailor to automatically revoke certain types of secrets based on what you define as the most critical. This is also an excellent way to react to new secrets being committed with a more automated approach.
 
 {% endnote %}
 
-### <a name="2-remediate-previously-committed-secrets-starting-with-the-most-critical"></a>2. 修复之前提交的机密，从最关键的机密开始
+### 2. Remediate previously committed secrets, starting with the most critical
 
-建立监视、通知和修复新发布机密的流程后，可以开始处理引入 {% data variables.product.prodname_GH_advanced_security %} 之前提交的机密。
+After you have established a process to monitor, notify and remediate newly published secrets, you can start work on secrets committed before {% data variables.product.prodname_GH_advanced_security %} was introduced.
 
-如何定义最关键的机密将取决于贵组织的流程和集成。 例如，如果不使用 Slack，则公司可能不会担心 Slack 入站 Webhook 机密。 你可能会发现从注重贵组织的前五种最关键凭据类型着手会很有用。
+How you define your most critical secrets will depend on your organization's processes and integrations. For example, a company likely isn’t worried about a Slack Incoming Webhook secret if they don’t use Slack. You may find it useful to start by focusing on the top five most critical credential types for your organization.
 
-确定机密类型后，可以执行以下操作：
+Once you have decided on the secret types, you can do the following:
 
-1. 定义修复每种机密类型的流程。 每种机密类型的实际程序通常截然不同。 在文档或内部知识库中记录每种机密的过程。
+1. Define a process for remediating each type of secret. The actual procedure for each secret type is often drastically different. Write down the process for each type of secret in a document or internal knowledge base.
   
   {% note %}
   
-  **注意**：创建撤消机密的流程时，请尝试将撤消机密的责任交给维护存储库的团队而不是中央团队。 GHAS 的原则之一是开发人员对安全负责并负责解决安全问题，尤其是在开发人员引发这些问题的情况下。
+  **Note:** When you create the process for revoking secrets, try and give the responsibility for revoking secrets to the team maintaining the repository instead of a central team. One of the principles of GHAS is developers taking ownership of security and having the responsibility of fixing security issues, especially if they have created them.
 
   {% endnote %}
 
-2. 创建团队将遵循的撤销凭据流程后，你可以整理有关机密类型的信息以及与所泄露机密相关的其他元数据，以便识别出将接收新流程的人员。
+2. When you have created the process that teams will follow for revoking credentials, you can collate information about the types of secrets and other metadata associated with the leaked secrets so you can discern who to communicate the new process to.
   
   {% ifversion not ghae %}
   
-  可以使用安全概述来收集此信息。 有关使用安全概述的详细信息，请参阅“[在安全概述中筛选警报](/code-security/security-overview/filtering-alerts-in-the-security-overview)”。
+  You can use the security overview to collect this information. For more information about using the security overview, see "[Filtering alerts in the security overview](/code-security/security-overview/filtering-alerts-in-the-security-overview)."
   
   {% endif %}
   
-  建议收集的信息包括：
+  Some information you may want to collect includes:
   
-    - 组织
-    - 存储库
-    - 机密类型
-    - 机密值
-    - 要联系的存储库维护人员
+    - Organization
+    - Repository
+    - Secret type
+    - Secret value
+    - Maintainers on repository to contact
   
   {% note %}
   
-  **注意：** 如果泄露的该类型机密很少，请使用 UI。 如果泄露的机密达到数百个，请使用 API 收集信息。 有关详细信息，请参阅“[机密扫描 REST API](/rest/reference/secret-scanning)”。
+  **Note:** Use the UI if you have few secrets leaked of that type. If you have hundreds of leaked secrets, use the API to collect information. For more information, see "[Secret scanning REST API](/rest/reference/secret-scanning)."
     
   {% endnote %}
 
-3. 收集有关所泄露机密的信息后，为维护受每种机密类型影响的存储库的用户创建有针对性的沟通计划。 可以使用电子邮件、消息，甚至在受影响的存储库中创建 GitHub 问题。 如果可以使用这些工具提供的 API 以自动方式发送通信，你可以轻松地跨多种机密类型进行缩放。
+3. After you collect information about leaked secrets, create a targeted communication plan for the users who maintain the repositories affected by each secret type. You could use email, messaging, or even create GitHub issues in the affected repositories. If you can use APIs provided by these tools to send out the communications in an automated manner, this will make it easier for you to scale across multiple secret types.
 
-### <a name="3-expand-the-program-to-include-more-secret-types-and-custom-patterns"></a>3. 扩展程序以包含更多机密类型和自定义模式
+### 3. Expand the program to include more secret types and custom patterns
 
-现在，你可以将五种最关键的机密类型扩展为更全面的列表，并重点关注培训。 你可以针对指定为目标的各种机密类型重复上一步，以修复先前提交的机密。
+You can now expand beyond the five most critical secret types into a more comprehensive list, with an additional focus on education. You can repeat the previous step, remediating previously committed secrets, for the different secret types you have targeted.
 
-你还可以包含更多早期阶段整理的自定义模式，并邀请安全团队和开发团队提交更多模式，以建立针对新建的机密类型提交新模式的流程。 有关详细信息，请参阅“[为机密扫描定义自定义模式](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning)”。
+You can also include more of the custom patterns collated in the earlier phases and invite security teams and developer teams to submit more patterns, establishing a process for submitting new patterns as new secret types are created. For more information, see "[Defining custom patterns for secret scanning](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning)."
 
 {% ifversion secret-scanning-push-protection %}
 
-你还可以通过机密扫描启用推送保护。 启用后，机密扫描会检查推送是否存在高可信度机密并阻止推送。 有关详细信息，请参阅“[使用机密扫描保护推送](/code-security/secret-scanning/protecting-pushes-with-secret-scanning#using-secret-scanning-as-a-push-protection-from-the-command-line)”。
+You can also enable push protection with secret scanning. Once enabled, secret scanning checks pushes for high-confidence secrets and blocks the push. For more information, see "[Protecting pushes with secret scanning](/code-security/secret-scanning/protecting-pushes-with-secret-scanning#using-secret-scanning-as-a-push-protection-from-the-command-line)."
 
 {% endif %}
 
-继续为其他机密类型生成修正流程时，请开始创建可与组织中所有 GitHub 开发人员共享的主动培训材料。 到目前为止，很多重点关注都是被动的。 最好一开始就将重点关注转变为主动，并鼓励开发人员不将凭据推送到 GitHub。 可以通过多种方式实现这一目标，不过创建简洁文档来说明风险和原因将会奠定很好的基础。
+As you continue to build your remediation processes for other secret types, start to create proactive training material that can be shared with all developers of GitHub in your organization. Until this point, a lot of the focus has been reactive. It is an excellent idea to shift focus to being proactive and encourage developers not to push credentials to GitHub in the first place. This can be achieved in multiple ways but creating a short document explaining the risks and reasons would be a great place to start.
 
 {% note %}
 
-本文是大规模采用 {% data variables.product.prodname_GH_advanced_security %} 系列的最后一篇。 如果有疑问或需要支持，请参阅“[大规模采用 {% data variables.product.prodname_GH_advanced_security %} 简介](/code-security/adopting-github-advanced-security-at-scale/introduction-to-adopting-github-advanced-security-at-scale#github-support-and-professional-services)”中有关 {% data variables.contact.github_support %} 和 {% data variables.product.prodname_professional_services_team %} 的部分。
+This is the final article of a series on adopting {% data variables.product.prodname_GH_advanced_security %} at scale. If you have questions or need support, see the section on {% data variables.contact.github_support %} and {% data variables.product.prodname_professional_services_team %} in "[Introduction to adopting {% data variables.product.prodname_GH_advanced_security %} at scale](/code-security/adopting-github-advanced-security-at-scale/introduction-to-adopting-github-advanced-security-at-scale#github-support-and-professional-services)."
 
 {% endnote %}
diff --git a/translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning.md b/translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning.md
index e7a4e2b032..bfb8740fb1 100644
--- a/translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning.md
+++ b/translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning.md
@@ -73,9 +73,7 @@ By default, the {% data variables.product.prodname_codeql_workflow %} uses the `
 
 If you scan on push, then the results appear in the **Security** tab for your repository. For more information, see "[Managing code scanning alerts for your repository](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository#viewing-the-alerts-for-a-repository)."
 
-{% ifversion fpt or ghes > 3.2 or ghae or ghec %}
 Additionally, when an `on:push` scan returns results that can be mapped to an open pull request, these alerts will automatically appear on the pull request in the same places as other pull request alerts. The alerts are identified by comparing the existing analysis of the head of the branch to the analysis for the target branch. For more information on {% data variables.product.prodname_code_scanning %} alerts in pull requests, see "[Triaging {% data variables.product.prodname_code_scanning %} alerts in pull requests](/code-security/secure-coding/triaging-code-scanning-alerts-in-pull-requests)."
-{% endif %}
 
 ### Scanning pull requests
 
@@ -85,9 +83,7 @@ For more information about the `pull_request` event, see "[Events that trigger w
 
 If you scan pull requests, then the results appear as alerts in a pull request check. For more information, see "[Triaging code scanning alerts in pull requests](/code-security/secure-coding/triaging-code-scanning-alerts-in-pull-requests)."
 
-{% ifversion fpt or ghes > 3.2 or ghae or ghec %}
- Using the `pull_request` trigger, configured to scan the pull request's merge commit rather than the head commit, will produce more efficient and accurate results than scanning the head of the branch on each push. However, if you use a CI/CD system that cannot be configured to trigger on pull requests, you can still use the `on:push` trigger and {% data variables.product.prodname_code_scanning %} will map the results to open pull requests on the branch and add the alerts as annotations on the pull request. For more information, see "[Scanning on push](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning#scanning-on-push)."
-{% endif %}
+Using the `pull_request` trigger, configured to scan the pull request's merge commit rather than the head commit, will produce more efficient and accurate results than scanning the head of the branch on each push. However, if you use a CI/CD system that cannot be configured to trigger on pull requests, you can still use the `on:push` trigger and {% data variables.product.prodname_code_scanning %} will map the results to open pull requests on the branch and add the alerts as annotations on the pull request. For more information, see "[Scanning on push](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning#scanning-on-push)."
 
 ### Defining the severities causing pull request check failure
 
diff --git a/translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-the-codeql-workflow-for-compiled-languages.md b/translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-the-codeql-workflow-for-compiled-languages.md
index 9135c91197..1220575d5d 100644
--- a/translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-the-codeql-workflow-for-compiled-languages.md
+++ b/translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-the-codeql-workflow-for-compiled-languages.md
@@ -41,7 +41,7 @@ For general information about configuring {% data variables.product.prodname_cod
 ##  About autobuild for {% data variables.product.prodname_codeql %}
 
 {% data variables.product.prodname_code_scanning_capc %} works by running queries against one or more databases. Each database contains a representation of all of the code in a single language in your repository.   
-For the compiled languages C/C++, C#, and Java, the process of populating this database involves building the code and extracting data. {% data reusables.code-scanning.analyze-go %}
+For the compiled languages C/C++, C#,{% ifversion codeql-go-autobuild %} Go,{% endif %} and Java, the process of populating this database involves building the code and extracting data. {% data reusables.code-scanning.analyze-go %}
 
 {% data reusables.code-scanning.autobuild-compiled-languages %}
 
@@ -90,6 +90,20 @@ The `autobuild` process attempts to autodetect a suitable build method for C# us
 If `autobuild` detects multiple solution or project files at the same (shortest) depth from the top level directory, it will attempt to build all of them.
 3. Invoke a script that looks like a build script—_build_ and _build.sh_ (in that order, for Linux) or _build.bat_, _build.cmd_, _and build.exe_ (in that order, for Windows).
 
+### Go
+
+| Supported system type | System name |
+|----|----|
+| Operating system | Windows, macOS, and Linux |
+| Build system | Go modules, `dep` and Glide, as well as build scripts including Makefiles and Ninja scripts |
+
+The `autobuild` process attempts to autodetect a suitable way to install the dependencies needed by a Go repository before extracting all `.go` files:
+
+1. Invoke `make`, `ninja`, `./build` or `./build.sh` (in that order) until one of these commands succeeds and a subsequent `go list ./...` also succeeds, indicating that the needed dependencies have been installed.
+2. If none of those commands succeeded, look for `go.mod`, `Gopkg.toml` or `glide.yaml`, and run `go get` (unless vendoring is in use), `dep ensure -v` or `glide install` respectively to try to install dependencies.
+3. Finally, if configurations files for these dependency managers are not found, rearrange the repository directory structure suitable for addition to `GOPATH`, and use `go get` to install dependencies. The directory structure reverts to normal after extraction completes.
+4. Extract all Go code in the repository, similar to running `go build ./...`.
+
 ### Java
 
 | Supported system type | System name |
@@ -107,12 +121,12 @@ The `autobuild` process tries to determine the build system for Java codebases b
 
 {% data reusables.code-scanning.autobuild-add-build-steps %} For information on how to edit the workflow file, see  "[Configuring {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/configuring-code-scanning#editing-a-code-scanning-workflow)."
 
-After removing the `autobuild` step, uncomment the `run` step and add build commands that are suitable for your repository. The workflow `run` step runs command-line programs using the operating system's shell. You can modify these commands and add more commands to customize the build process. 
+After removing the `autobuild` step, uncomment the `run` step and add build commands that are suitable for your repository. The workflow `run` step runs command-line programs using the operating system's shell. You can modify these commands and add more commands to customize the build process.
 
 ``` yaml
 - run: |
-  make bootstrap
-  make release
+    make bootstrap
+    make release
 ```
 
 For more information about the `run` keyword, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepsrun)."
diff --git a/translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository.md b/translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository.md
index 56ea5e3cc3..d4e421b540 100644
--- a/translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository.md
+++ b/translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository.md
@@ -153,12 +153,9 @@ The names of the {% data variables.product.prodname_code_scanning %} analysis ch
 
 When the {% data variables.product.prodname_code_scanning %} jobs complete, {% data variables.product.prodname_dotcom %} works out whether any alerts were added by the pull request and adds the "{% data variables.product.prodname_code_scanning_capc %} results / TOOL NAME" entry to the list of checks. After {% data variables.product.prodname_code_scanning %} has been performed at least once, you can click **Details** to view the results of the analysis.
 
-{% ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4  %}
-<!--Troubleshooting section no longer relevant-->
-{% elsif ghes < 3.5 or ghae %}
-If you used a pull request to add {% data variables.product.prodname_code_scanning %} to the repository, you will initially see {% ifversion ghes > 3.2 or ghae %}an "Analysis not found"{% elsif ghes = 3.2 %}a "Missing analysis"{% endif %} message when you click **Details** on the "{% data variables.product.prodname_code_scanning_capc %} results / TOOL NAME" check.
+{% ifversion ghes < 3.5 or ghae %}
+If you used a pull request to add {% data variables.product.prodname_code_scanning %} to the repository, you will initially see an "Analysis not found" message when you click **Details** on the "{% data variables.product.prodname_code_scanning_capc %} results / TOOL NAME" check.
 
-{% ifversion ghes > 3.2 or ghae %}
   ![Analysis not found for commit message](/assets/images/enterprise/3.4/repository/code-scanning-analysis-not-found.png)
 
 The table lists one or more categories. Each category relates to specific analyses, for the same tool and commit, performed on a different language or a different part of the code. For each category, the table shows the two analyses that {% data variables.product.prodname_code_scanning %} attempted to compare to determine which alerts were introduced or fixed in the pull request.
@@ -167,13 +164,8 @@ For example, in the screenshot above, {% data variables.product.prodname_code_sc
 
 ### Reasons for the "Analysis not found" message
 
-{% elsif ghes = 3.2 %}
-  ![Missing analysis for commit message](/assets/images/enterprise/3.2/repository/code-scanning-missing-analysis.png)
 
-### Reasons for the "Missing analysis" message
-{% endif %}
-
-After {% data variables.product.prodname_code_scanning %} has analyzed the code in a pull request, it needs to compare the analysis of the topic branch (the branch you used to create the pull request) with the analysis of the base branch (the branch into which you want to merge the pull request). This allows {% data variables.product.prodname_code_scanning %} to compute which alerts are newly introduced by the pull request, which alerts were already present in the base branch, and whether any existing alerts are fixed by the changes in the pull request. Initially, if you use a pull request to add {% data variables.product.prodname_code_scanning %} to a repository, the base branch has not yet been analyzed, so it's not possible to compute these details. In this case, when you click through from the results check on the pull request you will see the {% ifversion ghes > 3.2 or ghae %}"Analysis not found"{% elsif ghes = 3.2 %}"Missing analysis for base commit SHA-HASH"{% endif %} message.
+After {% data variables.product.prodname_code_scanning %} has analyzed the code in a pull request, it needs to compare the analysis of the topic branch (the branch you used to create the pull request) with the analysis of the base branch (the branch into which you want to merge the pull request). This allows {% data variables.product.prodname_code_scanning %} to compute which alerts are newly introduced by the pull request, which alerts were already present in the base branch, and whether any existing alerts are fixed by the changes in the pull request. Initially, if you use a pull request to add {% data variables.product.prodname_code_scanning %} to a repository, the base branch has not yet been analyzed, so it's not possible to compute these details. In this case, when you click through from the results check on the pull request you will see the "Analysis not found" message.
 
 There are other situations where there may be no analysis for the latest commit to the base branch for a pull request. These include:
 
diff --git a/translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/triaging-code-scanning-alerts-in-pull-requests.md b/translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/triaging-code-scanning-alerts-in-pull-requests.md
index ec6da4e48a..acf7f647a3 100644
--- a/translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/triaging-code-scanning-alerts-in-pull-requests.md
+++ b/translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/triaging-code-scanning-alerts-in-pull-requests.md
@@ -35,9 +35,7 @@ In repositories where {% data variables.product.prodname_code_scanning %} is con
 
 If you have write permission for the repository, you can see any existing {% data variables.product.prodname_code_scanning %} alerts on the **Security** tab. For information about repository alerts, see "[Managing {% data variables.product.prodname_code_scanning %} alerts for your repository](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository)."
 
-{% ifversion fpt or ghes > 3.2 or ghae or ghec %}
 In repositories where {% data variables.product.prodname_code_scanning %} is configured to scan each time code is pushed, {% data variables.product.prodname_code_scanning %} will also map the results to any open pull requests and add the alerts as annotations in the same places as other pull request checks. For more information, see "[Scanning on push](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning#scanning-on-push)."
-{% endif %}
 
 If your pull request targets a protected branch that uses {% data variables.product.prodname_code_scanning %}, and the repository owner has configured required status checks, then the "{% data variables.product.prodname_code_scanning_capc %} results" check must pass before you can merge the pull request. For more information, see "[About protected branches](/github/administering-a-repository/about-protected-branches#require-status-checks-before-merging)."
 
@@ -49,10 +47,9 @@ There are many options for configuring {% data variables.product.prodname_code_s
 
 For all configurations of {% data variables.product.prodname_code_scanning %}, the check that contains the results of {% data variables.product.prodname_code_scanning %} is: **{% data variables.product.prodname_code_scanning_capc %} results**. The results for each analysis tool used are shown separately. Any new alerts caused by changes in the pull request are shown as annotations. 
 
-{% ifversion fpt or ghes > 3.2 or ghae or ghec %} To see the full set of alerts for the analyzed branch, click **View all branch alerts**. This opens the full alert view where you can filter all the alerts on the branch by type, severity, tag, etc. For more information, see "[Managing code scanning alerts for your repository](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository#filtering-and-searching-for-code-scanning-alerts)."
+To see the full set of alerts for the analyzed branch, click **View all branch alerts**. This opens the full alert view where you can filter all the alerts on the branch by type, severity, tag, etc. For more information, see "[Managing code scanning alerts for your repository](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository#filtering-and-searching-for-code-scanning-alerts)."
 
 ![{% data variables.product.prodname_code_scanning_capc %} results check on a pull request](/assets/images/help/repository/code-scanning-results-check.png)
-{% endif %}
 
 ### {% data variables.product.prodname_code_scanning_capc %} results check failures
 
diff --git a/translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/troubleshooting-the-codeql-workflow.md b/translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/troubleshooting-the-codeql-workflow.md
index 658d44b582..11529ccbee 100644
--- a/translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/troubleshooting-the-codeql-workflow.md
+++ b/translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/troubleshooting-the-codeql-workflow.md
@@ -49,7 +49,7 @@ To produce more detailed logging output, you can enable step debug logging. For
 ## Creating {% data variables.product.prodname_codeql %} debugging artifacts
 
 You can obtain artifacts to help you debug {% data variables.product.prodname_codeql %}.
-The debug artifacts will be uploaded to the workflow run as an artifact named `debug-artifacts`. The data contains the {% data variables.product.prodname_codeql %} logs, {% data variables.product.prodname_codeql %} database(s), and any SARIF file(s) produced by the workflow. 
+The debug artifacts will be uploaded to the workflow run as an artifact named `debug-artifacts`. The data contains the {% data variables.product.prodname_codeql %} logs, {% data variables.product.prodname_codeql %} database(s), and any SARIF file(s) produced by the workflow.
 
 These artifacts will help you debug problems with {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %}. If you contact GitHub support, they might ask for this data.
 
@@ -59,11 +59,10 @@ These artifacts will help you debug problems with {% data variables.product.prod
 
 ### Creating {% data variables.product.prodname_codeql %} debugging artifacts by re-running jobs with debug logging enabled
 
-You can create {% data variables.product.prodname_codeql %} debugging artifacts by enabling debug logging and re-running the jobs. For more information about re-running {% data variables.product.prodname_actions %} workflows and jobs, see "[Re-running workflows and jobs](/actions/managing-workflow-runs/re-running-workflows-and-jobs)." 
+You can create {% data variables.product.prodname_codeql %} debugging artifacts by enabling debug logging and re-running the jobs. For more information about re-running {% data variables.product.prodname_actions %} workflows and jobs, see "[Re-running workflows and jobs](/actions/managing-workflow-runs/re-running-workflows-and-jobs)."
 
 You need to ensure that you select **Enable debug logging** . This option enables runner diagnostic logging and step debug logging for the run. You'll then be able to download `debug-artifacts` to investigate further. You do not need to modify the workflow file when creating {% data variables.product.prodname_codeql %} debugging artifacts by re-running jobs.
 
-
 {% endif %}
 
 {% ifversion fpt or ghec or ghes > 3.3 or ghae > 3.3 %}
@@ -87,7 +86,7 @@ If an automatic build of code for a compiled language within your project fails,
 
 - Remove the `autobuild` step from your {% data variables.product.prodname_code_scanning %} workflow and add specific build steps. For information about editing the workflow, see  "[Configuring {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/configuring-code-scanning#editing-a-code-scanning-workflow)." For more information about replacing the `autobuild` step, see "[Configuring the {% data variables.product.prodname_codeql %} workflow for compiled languages](/code-security/secure-coding/configuring-the-codeql-workflow-for-compiled-languages#adding-build-steps-for-a-compiled-language)."
 
-- If your workflow doesn't explicitly specify the languages to analyze, {% data variables.product.prodname_codeql %} implicitly detects the supported languages in your code base. In this configuration, out of the compiled languages C/C++, C#, and Java, {% data variables.product.prodname_codeql %} only analyzes the language with the most source files. Edit the workflow and add a matrix specifying the languages you want to analyze. The default CodeQL analysis workflow uses such a matrix.
+- If your workflow doesn't explicitly specify the languages to analyze, {% data variables.product.prodname_codeql %} implicitly detects the supported languages in your code base. In this configuration, out of the compiled languages C/C++, C#,{% ifversion codeql-go-autobuild %} Go,{% endif %} and Java, {% data variables.product.prodname_codeql %} only analyzes the language with the most source files. Edit the workflow and add a matrix specifying the languages you want to analyze. The default CodeQL analysis workflow uses such a matrix.
 
   The following extracts from a workflow show how you can use a matrix within the job strategy to specify languages, and then reference each language within the "Initialize {% data variables.product.prodname_codeql %}" step:
 
@@ -131,14 +130,15 @@ If your workflow fails with an error `No source code was seen during the build`
   ```
 
    For more information, see the workflow extract in "[Automatic build for a compiled language fails](#automatic-build-for-a-compiled-language-fails)" above.
-1. Your {% data variables.product.prodname_code_scanning %} workflow is analyzing a compiled language (C, C++, C#, or Java), but the code was not compiled. By default, the {% data variables.product.prodname_codeql %} analysis workflow contains an `autobuild` step, however, this step represents a best effort process, and may not succeed in building your code, depending on your specific build environment. Compilation may also fail if you have removed the `autobuild` step and did not include build steps manually.  For more information about specifying build steps, see "[Configuring the {% data variables.product.prodname_codeql %} workflow for compiled languages](/code-security/secure-coding/configuring-the-codeql-workflow-for-compiled-languages#adding-build-steps-for-a-compiled-language)."
-1. Your workflow is analyzing a compiled language (C, C++, C#, or Java), but portions of your build are cached to improve performance (most likely to occur with build systems like Gradle or Bazel). Since {% data variables.product.prodname_codeql %} observes the activity of the compiler to understand the data flows in a repository, {% data variables.product.prodname_codeql %} requires a complete build to take place in order to perform analysis. 
-1. Your workflow is analyzing a compiled language (C, C++, C#, or Java), but compilation does not occur between the `init` and `analyze` steps in the workflow. {% data variables.product.prodname_codeql %} requires that your build happens in between these two steps in order to observe the activity of the compiler and perform analysis. 
-1. Your compiled code (in C, C++, C#, or Java) was compiled successfully, but {% data variables.product.prodname_codeql %} was unable to detect the compiler invocations. The most common causes are:
 
-   * Running your build process in a separate container to {% data variables.product.prodname_codeql %}. For more information, see "[Running CodeQL code scanning in a container](/code-security/secure-coding/running-codeql-code-scanning-in-a-container)."
-   * Building using a distributed build system external to GitHub Actions, using a daemon process.
-   * {% data variables.product.prodname_codeql %} isn't aware of the specific compiler you are using.
+1. Your {% data variables.product.prodname_code_scanning %} workflow is analyzing a compiled language (C, C++, C#,{% ifversion codeql-go-autobuild %} Go,{% endif %} or Java), but the code was not compiled. By default, the {% data variables.product.prodname_codeql %} analysis workflow contains an `autobuild` step, however, this step represents a best effort process, and may not succeed in building your code, depending on your specific build environment. Compilation may also fail if you have removed the `autobuild` step and did not include build steps manually.  For more information about specifying build steps, see "[Configuring the {% data variables.product.prodname_codeql %} workflow for compiled languages](/code-security/secure-coding/configuring-the-codeql-workflow-for-compiled-languages#adding-build-steps-for-a-compiled-language)."
+1. Your workflow is analyzing a compiled language (C, C++, C#,{% ifversion codeql-go-autobuild %} Go,{% endif %} or Java), but portions of your build are cached to improve performance (most likely to occur with build systems like Gradle or Bazel). Since {% data variables.product.prodname_codeql %} observes the activity of the compiler to understand the data flows in a repository, {% data variables.product.prodname_codeql %} requires a complete build to take place in order to perform analysis.
+1. Your workflow is analyzing a compiled language (C, C++, C#,{% ifversion codeql-go-autobuild %} Go,{% endif %} or Java), but compilation does not occur between the `init` and `analyze` steps in the workflow. {% data variables.product.prodname_codeql %} requires that your build happens in between these two steps in order to observe the activity of the compiler and perform analysis.
+1. Your compiled code (in C, C++, C#,{% ifversion codeql-go-autobuild %} Go,{% endif %} or Java) was compiled successfully, but {% data variables.product.prodname_codeql %} was unable to detect the compiler invocations. The most common causes are:
+
+   - Running your build process in a separate container to {% data variables.product.prodname_codeql %}. For more information, see "[Running CodeQL code scanning in a container](/code-security/secure-coding/running-codeql-code-scanning-in-a-container)."
+   - Building using a distributed build system external to GitHub Actions, using a daemon process.
+   - {% data variables.product.prodname_codeql %} isn't aware of the specific compiler you are using.
 
   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.
   
@@ -151,9 +151,10 @@ If your workflow fails with an error `No source code was seen during the build`
 
   If you encounter another problem with your specific compiler or configuration, contact {% data variables.contact.contact_support %}.
 
-For more information about specifying build steps, see "[Configuring the {% data variables.product.prodname_codeql %} workflow for compiled languages](/code-security/secure-coding/configuring-the-codeql-workflow-for-compiled-languages#adding-build-steps-for-a-compiled-language)." 
+For more information about specifying build steps, see "[Configuring the {% data variables.product.prodname_codeql %} workflow for compiled languages](/code-security/secure-coding/configuring-the-codeql-workflow-for-compiled-languages#adding-build-steps-for-a-compiled-language)."
 
 {% ifversion fpt or ghes > 3.1  or ghae or ghec %}
+
 ## Lines of code scanned are lower than expected
 
 For compiled languages like C/C++, C#, Go, and Java, {% data variables.product.prodname_codeql %} only scans files that are built during the analysis. Therefore the number of lines of code scanned will be lower than expected if some of the source code isn't compiled correctly. This can happen for several reasons:
@@ -163,12 +164,13 @@ For compiled languages like C/C++, C#, Go, and Java, {% data variables.product.p
 
 If your {% data variables.product.prodname_codeql %} analysis scans fewer lines of code than expected, there are several approaches you can try to make sure all the necessary source files are compiled.
 
-### Replace the `autobuild` step 
+### Replace the `autobuild` step
 
 Replace the `autobuild` step with the same build commands you would use in production. This makes sure that {% data variables.product.prodname_codeql %} knows exactly how to compile all of the source files you want to scan.
-For more information, see "[Configuring the {% data variables.product.prodname_codeql %} workflow for compiled languages](/code-security/secure-coding/configuring-the-codeql-workflow-for-compiled-languages#adding-build-steps-for-a-compiled-language)." 
+For more information, see "[Configuring the {% data variables.product.prodname_codeql %} workflow for compiled languages](/code-security/secure-coding/configuring-the-codeql-workflow-for-compiled-languages#adding-build-steps-for-a-compiled-language)."
 
 ### Inspect the copy of the source files in the {% data variables.product.prodname_codeql %} database
+
 You may be able to understand why some source files haven't been analyzed by inspecting the copy of the source code included with the {% data variables.product.prodname_codeql %} database. To obtain the database from your Actions workflow, modify the `init` step of your {% data variables.product.prodname_codeql %} workflow file and set `debug: true`.
 
 ```yaml
@@ -188,12 +190,13 @@ The artifact will contain an archived copy of the source files scanned by {% dat
 
 ## Extraction errors in the database
 
-The {% data variables.product.prodname_codeql %} team constantly works on critical extraction errors to make sure that all source files can be scanned. However, the {% data variables.product.prodname_codeql %} extractors do occasionally generate errors during database creation. {% data variables.product.prodname_codeql %} provides information about extraction errors and warnings generated during database creation in a log file. 
+The {% data variables.product.prodname_codeql %} team constantly works on critical extraction errors to make sure that all source files can be scanned. However, the {% data variables.product.prodname_codeql %} extractors do occasionally generate errors during database creation. {% data variables.product.prodname_codeql %} provides information about extraction errors and warnings generated during database creation in a log file.
 The extraction diagnostics information gives an indication of overall database health. Most extractor errors do not significantly impact the analysis. A small number of extractor errors is healthy and typically indicates a good state of analysis.
 
 However, if you see extractor errors in the overwhelming majority of files that were compiled during database creation, you should look into the errors in more detail to try to understand why some source files weren't extracted properly.
 
 {% else %}
+
 ## Portions of my repository were not analyzed using `autobuild`
 
 The {% data variables.product.prodname_codeql %} `autobuild` feature uses heuristics to build the code in a repository, however, sometimes this approach results in incomplete analysis of a repository. For example, when multiple `build.sh` commands exist in a single repository, the analysis may not complete since the `autobuild` step will only execute one of the commands. The solution is to replace the `autobuild` step with build steps which build all of the source code which you wish to analyze. For more information, see "[Configuring the {% data variables.product.prodname_codeql %} workflow for compiled languages](/code-security/secure-coding/configuring-the-codeql-workflow-for-compiled-languages#adding-build-steps-for-a-compiled-language)."
@@ -201,7 +204,7 @@ The {% data variables.product.prodname_codeql %} `autobuild` feature uses heuris
 
 ## The build takes too long
 
-If your build with {% data variables.product.prodname_codeql %} analysis takes too long to run, there are several approaches you can try to reduce the build time. 
+If your build with {% data variables.product.prodname_codeql %} analysis takes too long to run, there are several approaches you can try to reduce the build time.
 
 ### Increase the memory or cores
 
@@ -225,7 +228,7 @@ If your analysis is still too slow to be run during `push` or `pull_request` eve
 
 ### Check which query suites the workflow runs
 
-By default, there are three main query suites available for each language. If you have optimized the CodeQL database build and the process is still too long, you could reduce the number of queries you run. The default query suite is run automatically; it contains the fastest security queries with the lowest rates of false positive results. 
+By default, there are three main query suites available for each language. If you have optimized the CodeQL database build and the process is still too long, you could reduce the number of queries you run. The default query suite is run automatically; it contains the fastest security queries with the lowest rates of false positive results.
 
 You may be running extra queries or query suites in addition to the default queries. Check whether the workflow defines an additional query suite or additional queries to run using the `queries` element. You can experiment with disabling the additional query suite or queries. For more information, see "[Configuring {% data variables.product.prodname_code_scanning %}](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning#using-queries-in-ql-packs)."
 
@@ -237,6 +240,7 @@ You may be running extra queries or query suites in addition to the default quer
 {% endif %}
 
 {% ifversion fpt or ghec %}
+
 ## Results differ between analysis platforms
 
 If you are analyzing code written in Python, you may see different results depending on whether you run the {% data variables.product.prodname_codeql_workflow %} on Linux, macOS, or Windows.
@@ -256,11 +260,13 @@ On very large projects, {% data variables.product.prodname_codeql %} may run out
 {% else %}If you encounter this issue, try increasing the memory on the runner.{% endif %}
 
 {% ifversion fpt or ghec %}
+
 ## Error: 403 "Resource not accessible by integration" when using {% data variables.product.prodname_dependabot %}
 
 {% data variables.product.prodname_dependabot %} is considered untrusted when it triggers a workflow run, and the workflow will run with read-only scopes. Uploading {% data variables.product.prodname_code_scanning %} results for a branch usually requires the `security_events: write` scope. However, {% data variables.product.prodname_code_scanning %} always allows the uploading of results when the `pull_request` event triggers the action run. This is why, for {% data variables.product.prodname_dependabot %} branches, we recommend you use the `pull_request` event instead of the `push` event.
 
 A simple approach is to run on pushes to the default branch and any other important long-running branches, as well as pull requests opened against this set of branches:
+
 ```yaml
 on:
   push:
@@ -270,7 +276,9 @@ on:
     branches:
       - main
 ```
+
 An alternative approach is to run on all pushes except for {% data variables.product.prodname_dependabot %} branches:
+
 ```yaml
 on:
   push:
@@ -282,6 +290,7 @@ on:
 ### Analysis still failing on the default branch
 
 If the {% data variables.product.prodname_codeql_workflow %} still fails on a commit made on the default branch, you need to check:
+
 - whether {% data variables.product.prodname_dependabot %} authored the commit
 - whether the pull request that includes the commit has been merged using `@dependabot squash and merge`
 
diff --git a/translations/zh-CN/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/about-codeql-code-scanning-in-your-ci-system.md b/translations/zh-CN/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/about-codeql-code-scanning-in-your-ci-system.md
index 370ce281d8..6390bcc50e 100644
--- a/translations/zh-CN/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/about-codeql-code-scanning-in-your-ci-system.md
+++ b/translations/zh-CN/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/about-codeql-code-scanning-in-your-ci-system.md
@@ -49,21 +49,12 @@ redirect_from:
 Use the {% data variables.product.prodname_codeql_cli %} to analyze:
 
 - Dynamic languages, for example, JavaScript and Python.
-- Compiled languages, for example, C/C++, C# and Java.
+- Compiled languages, for example, C/C++, C#,{% ifversion codeql-go-autobuild %} Go,{% endif %} and Java.
 - Codebases written in a mixture of languages.
 
 For more information, see "[Installing {% data variables.product.prodname_codeql_cli %} in your CI system](/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system/installing-codeql-cli-in-your-ci-system)."
 
 {% data reusables.code-scanning.licensing-note %}
 
-{% ifversion ghes = 3.2 %}
-<!-- Content for GHES 3.2 only. CodeQL CLI 2.6.2, which introduces full feature parity between CodeQL CLI and CodeQL runner, is officially recommended for GHES 3.0+ -->
-
-Since version 2.6.3, the {% data variables.product.prodname_codeql_cli %} has had full feature parity with the {% data variables.product.prodname_codeql_runner %}.
-
-{% data reusables.code-scanning.deprecation-codeql-runner %}
-
-{% endif %}
 
 <!--Content for GHES 3.1 only. Both CodeQL CLI and CodeQL runner are available -->
-
diff --git a/translations/zh-CN/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-cli-in-your-ci-system.md b/translations/zh-CN/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-cli-in-your-ci-system.md
index 1a0e74ad50..09f10cd3f0 100644
--- a/translations/zh-CN/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-cli-in-your-ci-system.md
+++ b/translations/zh-CN/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-cli-in-your-ci-system.md
@@ -78,8 +78,8 @@ You can display the command-line help for any command using the <nobr>`--help`</
 | <nobr>`--command`</nobr> | | Recommended. Use to specify the build command or script that invokes the build process for the codebase. Commands are run from the current folder or, where it is defined, from <nobr>`--source-root`</nobr>. Not needed for Python and JavaScript/TypeScript analysis. |
 | <nobr>`--db-cluster`</nobr> | | Optional. Use in multi-language codebases to generate one database for each language specified by <nobr>`--language`</nobr>.
 | <nobr>`--no-run-unnecessary-builds`</nobr> | | Recommended. Use to suppress the build command for languages where the {% data variables.product.prodname_codeql_cli %} does not need to monitor the build (for example, Python and JavaScript/TypeScript).
-| <nobr>`--source-root`</nobr> | | Optional. Use if you run the CLI outside the checkout root of the repository. By default, the `database create` command assumes that the current directory is the root directory for the source files, use this option to specify a different location. |{% ifversion fpt or ghec or ghes > 3.2 or ghae %}
-| <nobr>`--codescanning-config`</nobr> | | Optional (Advanced). Use if you have a configuration file that specifies how to create the {% data variables.product.prodname_codeql %} databases and what queries to run in later steps. For more information, see "[Using a custom configuration file](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning#using-a-custom-configuration-file)" and "[database create](https://codeql.github.com/docs/codeql-cli/manual/database-create/#cmdoption-codeql-database-create-codescanning-config)." |{% endif %}
+| <nobr>`--source-root`</nobr> | | Optional. Use if you run the CLI outside the checkout root of the repository. By default, the `database create` command assumes that the current directory is the root directory for the source files, use this option to specify a different location. |
+| <nobr>`--codescanning-config`</nobr> | | Optional (Advanced). Use if you have a configuration file that specifies how to create the {% data variables.product.prodname_codeql %} databases and what queries to run in later steps. For more information, see "[Using a custom configuration file](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning#using-a-custom-configuration-file)" and "[database create](https://codeql.github.com/docs/codeql-cli/manual/database-create/#cmdoption-codeql-database-create-codescanning-config)." |
 
 For more information, see [Creating {% data variables.product.prodname_codeql %} databases](https://codeql.github.com/docs/codeql-cli/creating-codeql-databases/) in the documentation for the {% data variables.product.prodname_codeql_cli %}.
 
diff --git a/translations/zh-CN/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-runner-in-your-ci-system.md b/translations/zh-CN/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-runner-in-your-ci-system.md
index e9d72e176b..c02304f43a 100644
--- a/translations/zh-CN/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-runner-in-your-ci-system.md
+++ b/translations/zh-CN/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-runner-in-your-ci-system.md
@@ -115,7 +115,7 @@ $ /path/to-runner/codeql-runner-linux init --config-file .github/codeql/codeql-c
 
 ## Configuring {% data variables.product.prodname_code_scanning %} for compiled languages
 
-For the compiled languages C/C++, C#, and Java, {% data variables.product.prodname_codeql %} builds the code before analyzing it. {% data reusables.code-scanning.analyze-go %}
+For the compiled languages C/C++, C#,{% ifversion codeql-go-autobuild %} Go,{% endif %} and Java, {% data variables.product.prodname_codeql %} builds the code before analyzing it. {% data reusables.code-scanning.analyze-go %}
 
 For many common build systems, the {% data variables.product.prodname_codeql_runner %} can build the code automatically. To attempt to build the code automatically, run `autobuild` between the `init` and `analyze` steps. Note that if your repository requires a specific version of a build tool, you may need to install the build tool manually first. 
 
diff --git a/translations/zh-CN/content/code-security/dependabot/dependabot-alerts/about-dependabot-alerts.md b/translations/zh-CN/content/code-security/dependabot/dependabot-alerts/about-dependabot-alerts.md
index fa3ad2ded3..7b93d6bb64 100644
--- a/translations/zh-CN/content/code-security/dependabot/dependabot-alerts/about-dependabot-alerts.md
+++ b/translations/zh-CN/content/code-security/dependabot/dependabot-alerts/about-dependabot-alerts.md
@@ -76,7 +76,7 @@ For information about access requirements for actions related to {% data variabl
 
 When {% data variables.product.product_name %} identifies a vulnerable dependency{% ifversion GH-advisory-db-supports-malware %} or malware{% endif %}, we generate a {% data variables.product.prodname_dependabot %} alert and display it {% ifversion fpt or ghec or ghes %} on the Security tab for the repository and{% endif %} in the repository's dependency graph. The alert includes {% ifversion fpt or ghec or ghes %}a link to the affected file in the project, and {% endif %}information about a fixed version. {% data variables.product.product_name %} may also notify the maintainers of affected repositories about the new alert according to their notification preferences. For more information, see "[Configuring notifications for {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/configuring-notifications-for-dependabot-alerts)."
 
-{% ifversion fpt or ghec or ghes > 3.2 %}
+{% ifversion fpt or ghec or ghes %}
 For repositories where {% data variables.product.prodname_dependabot_security_updates %} are enabled, the alert may also contain a link to a pull request to update the manifest or lock file to the minimum version that resolves the vulnerability. For more information, see "[About {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)."
 {% endif %}
 
@@ -98,7 +98,7 @@ By default, we notify people with admin permissions in the affected repositories
 
 You can also see all the {% data variables.product.prodname_dependabot_alerts %} that correspond to a particular advisory in the {% data variables.product.prodname_advisory_database %}. {% data reusables.security-advisory.link-browsing-advisory-db %}
 
-{% ifversion fpt or ghec or ghes > 3.2 %}
+{% ifversion fpt or ghec or ghes %}
 ## Further reading
 
 - "[About {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)"
diff --git a/translations/zh-CN/content/code-security/dependabot/dependabot-alerts/browsing-security-advisories-in-the-github-advisory-database.md b/translations/zh-CN/content/code-security/dependabot/dependabot-alerts/browsing-security-advisories-in-the-github-advisory-database.md
deleted file mode 100644
index 663dc63e1b..0000000000
--- a/translations/zh-CN/content/code-security/dependabot/dependabot-alerts/browsing-security-advisories-in-the-github-advisory-database.md
+++ /dev/null
@@ -1,188 +0,0 @@
----
-title: Browsing security advisories in the GitHub Advisory Database
-intro: 'You can browse the {% data variables.product.prodname_advisory_database %} to find advisories for security risks in open source projects that are hosted on {% data variables.product.company_short %}.'
-shortTitle: Browse Advisory Database
-miniTocMaxHeadingLevel: 3
-redirect_from:
-  - /github/managing-security-vulnerabilities/browsing-security-vulnerabilities-in-the-github-advisory-database
-  - /code-security/supply-chain-security/browsing-security-vulnerabilities-in-the-github-advisory-database
-  - /code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/browsing-security-vulnerabilities-in-the-github-advisory-database
-  - /code-security/dependabot/dependabot-alerts/browsing-security-vulnerabilities-in-the-github-advisory-database
-versions:
-  fpt: '*'
-  ghec: '*'
-  ghes: '*'
-  ghae: '*'
-type: how_to
-topics:
-  - Security advisories
-  - Alerts
-  - Dependabot
-  - Vulnerabilities
-  - CVEs
----
-<!--Marketing-LINK: From /features/security/software-supply-chain page "Browsing security vulnerabilities in the GitHub Advisory Database".-->
-
-## About the {% data variables.product.prodname_advisory_database %}
-
-The {% data variables.product.prodname_advisory_database %} contains a list of known security vulnerabilities {% ifversion GH-advisory-db-supports-malware %}and malware, {% endif %}grouped in two categories: {% data variables.product.company_short %}-reviewed advisories and unreviewed advisories.
-
-{% data reusables.repositories.tracks-vulnerabilities %}
-
-## About types of security advisories
-
-{% data reusables.advisory-database.beta-malware-advisories %}
-
-Each advisory in the {% data variables.product.prodname_advisory_database %} is for a vulnerability in open source projects{% ifversion GH-advisory-db-supports-malware %} or for malicious open source software{% endif %}. 
-
-{% data reusables.repositories.a-vulnerability-is %} Vulnerabilities in code are usually introduced by accident and fixed soon after they are discovered. You should update your code to use the fixed version of the dependency as soon as it is available.
-
-{% ifversion GH-advisory-db-supports-malware %}
-
-In contrast, malicious software, or malware, is code that is intentionally designed to perform unwanted or harmful functions. The malware may target hardware, software, confidential data, or users of any application that uses the malware. You need to remove the malware from your project and find an alternative, more secure replacement for the dependency.
-
-{% endif %}
-
-### {% data variables.product.company_short %}-reviewed advisories
-
-{% data variables.product.company_short %}-reviewed advisories are security vulnerabilities{% ifversion GH-advisory-db-supports-malware %} or malware{% endif %} that have been mapped to packages in ecosystems we support. We carefully review each advisory for validity and ensure that they have a full description, and contain both ecosystem and package information.
-
-Generally, we name our supported ecosystems after the software programming language's associated package registry. We review advisories if they are for a vulnerability in a package that comes from a supported registry.
-
-- Composer (registry: https://packagist.org/){% ifversion GH-advisory-db-erlang-support %}
-- Erlang (registry: https://hex.pm/){% endif %}
-- Go (registry: https://pkg.go.dev/)
-{%- ifversion fpt or ghec or ghes > 3.6 or ghae > 3.6 %}
-- GitHub Actions (https://github.com/marketplace?type=actions/) {% endif %}
-- Maven (registry: https://repo.maven.apache.org/maven2)
-- npm (registry: https://www.npmjs.com/)
-- NuGet (registry: https://www.nuget.org/)
-- pip (registry: https://pypi.org/){% ifversion dependency-graph-dart-support %}
-- pub (registry: https://pub.dev/packages/registry){% endif %}
-- RubyGems (registry: https://rubygems.org/)
-- Rust (registry: https://crates.io/)
-
-If you have a suggestion for a new ecosystem we should support, please open an [issue](https://github.com/github/advisory-database/issues) for discussion.
-
-If you enable {% data variables.product.prodname_dependabot_alerts %} for your repositories, you are automatically notified when a new {% data variables.product.company_short %}-reviewed advisory reports a vulnerability {% ifversion GH-advisory-db-supports-malware %}or malware{% endif %} for a package you depend on. For more information, see "[About {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)."
-
-### Unreviewed advisories
-
-Unreviewed advisories are security vulnerabilites that we publish automatically into the {% data variables.product.prodname_advisory_database %}, directly from the National Vulnerability Database feed. 
-
-{% data variables.product.prodname_dependabot %} doesn't create {% data variables.product.prodname_dependabot_alerts %} for unreviewed advisories as this type of advisory isn't checked for validity or completion.
-
-## About information in security advisories
-
-Each security advisory contains information about the vulnerability{% ifversion GH-advisory-db-supports-malware %} or malware,{% endif %} which may include the description, severity, affected package, package ecosystem, affected versions and patched versions, impact, and optional information such as references, workarounds, and credits. In addition, advisories from the National Vulnerability Database list contain a link to the CVE record, where you can read more details about the vulnerability, its CVSS scores, and its qualitative severity level. For more information, see the "[National Vulnerability Database](https://nvd.nist.gov/)" from the National Institute of Standards and Technology.
-
-The severity level is one of four possible levels defined in the "[Common Vulnerability Scoring System (CVSS), Section 5](https://www.first.org/cvss/specification-document)."
-- Low
-- Medium/Moderate
-- High
-- Critical
-
-The {% data variables.product.prodname_advisory_database %} uses the CVSS levels described above. If {% data variables.product.company_short %} obtains a CVE, the {% data variables.product.prodname_advisory_database %} uses CVSS version 3.1. If the CVE is imported, the {% data variables.product.prodname_advisory_database %} supports both CVSS versions 3.0 and 3.1.
-
-{% data reusables.repositories.github-security-lab %}
-
-## Accessing an advisory in the {% data variables.product.prodname_advisory_database %}
-
-1. Navigate to https://github.com/advisories.
-2. Optionally, to filter the list, use any of the drop-down menus.
-  ![Dropdown filters](/assets/images/help/security/advisory-database-dropdown-filters.png)
-   {% tip %}
-
-   **Tip:** You can use the sidebar on the left to explore  {% data variables.product.company_short %}-reviewed and unreviewed advisories separately.
-
-   {% endtip %}
-3. Click an advisory to view details. By default, you will see {% data variables.product.company_short %}-reviewed advisories for security vulnerabilities. {% ifversion GH-advisory-db-supports-malware %}To show malware advisories, use `type:malware` in the search bar.{% endif %}
-
-
-{% note %}
-
-The database is also accessible using the GraphQL API. {% ifversion GH-advisory-db-supports-malware %}By default, queries will return {% data variables.product.company_short %}-reviewed advisories for security vulnerabilities unless you specify `type:malware`.{% endif %} For more information, see the "[`security_advisory` webhook event](/webhooks/event-payloads/#security_advisory)."
-
-{% endnote %}
-
-## Editing an advisory in the {% data variables.product.prodname_advisory_database %}
-You can suggest improvements to any advisory in the {% data variables.product.prodname_advisory_database %}. For more information, see "[Editing security advisories in the {% data variables.product.prodname_advisory_database %}](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/editing-security-advisories-in-the-github-advisory-database)."
-
-## Searching the {% data variables.product.prodname_advisory_database %}
-
-You can search the database, and use qualifiers to narrow your search. For example, you can search for advisories created on a certain date, in a specific ecosystem, or in a particular library.
-
-{% data reusables.time_date.date_format %} {% data reusables.time_date.time_format %}
-
-{% data reusables.search.date_gt_lt %}
-
-| Qualifier  | Example |
-| ------------- | ------------- |
-| `type:reviewed`| [**type:reviewed**](https://github.com/advisories?query=type%3Areviewed) will show {% data variables.product.company_short %}-reviewed advisories for security vulnerabilities. |
-{% ifversion GH-advisory-db-supports-malware %}| `type:malware` | [**type:malware**](https://github.com/advisories?query=type%3Amalware) will show {% data variables.product.company_short %}-reviewed advisories for malware. |
-{% endif %}| `type:unreviewed`| [**type:unreviewed**](https://github.com/advisories?query=type%3Aunreviewed) will show unreviewed advisories. |
-| `GHSA-ID`| [**GHSA-49wp-qq6x-g2rf**](https://github.com/advisories?query=GHSA-49wp-qq6x-g2rf) will show the advisory with this {% data variables.product.prodname_advisory_database %} ID. |
-| `CVE-ID`| [**CVE-2020-28482**](https://github.com/advisories?query=CVE-2020-28482) will show the advisory with this CVE ID number. |
-| `ecosystem:ECOSYSTEM`| [**ecosystem:npm**](https://github.com/advisories?utf8=%E2%9C%93&query=ecosystem%3Anpm) will show only advisories affecting NPM packages. |
-| `severity:LEVEL`| [**severity:high**](https://github.com/advisories?utf8=%E2%9C%93&query=severity%3Ahigh) will show only advisories with a high severity level. |
-| `affects:LIBRARY`| [**affects:lodash**](https://github.com/advisories?utf8=%E2%9C%93&query=affects%3Alodash) will show only advisories affecting the lodash library. |
-| `cwe:ID`| [**cwe:352**](https://github.com/advisories?query=cwe%3A352) will show only advisories with this CWE number. |
-| `credit:USERNAME`| [**credit:octocat**](https://github.com/advisories?query=credit%3Aoctocat) will show only advisories credited to the "octocat" user account. |
-| `sort:created-asc`| [**sort:created-asc**](https://github.com/advisories?utf8=%E2%9C%93&query=sort%3Acreated-asc) will sort by the oldest advisories first. |
-| `sort:created-desc`| [**sort:created-desc**](https://github.com/advisories?utf8=%E2%9C%93&query=sort%3Acreated-desc) will sort by the newest advisories first. |
-| `sort:updated-asc`| [**sort:updated-asc**](https://github.com/advisories?utf8=%E2%9C%93&query=sort%3Aupdated-asc) will sort by the least recently updated first. |
-| `sort:updated-desc`| [**sort:updated-desc**](https://github.com/advisories?utf8=%E2%9C%93&query=sort%3Aupdated-desc) will sort by the most recently updated first. |
-| `is:withdrawn`| [**is:withdrawn**](https://github.com/advisories?utf8=%E2%9C%93&query=is%3Awithdrawn) will show only advisories that have been withdrawn. |
-| `created:YYYY-MM-DD`| [**created:2021-01-13**](https://github.com/advisories?utf8=%E2%9C%93&query=created%3A2021-01-13) will show only advisories created on this date. |
-| `updated:YYYY-MM-DD`| [**updated:2021-01-13**](https://github.com/advisories?utf8=%E2%9C%93&query=updated%3A2021-01-13) will show only advisories updated on this date. |
-
-## Viewing your vulnerable repositories
-
-For any {% data variables.product.company_short %}-reviewed advisory in the {% data variables.product.prodname_advisory_database %}, you can see which of your repositories are affected by that security vulnerability{% ifversion GH-advisory-db-supports-malware %} or malware{% endif %}. To see a vulnerable repository, you must have access to {% data variables.product.prodname_dependabot_alerts %} for that repository. For more information, see "[About {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies#access-to-dependabot-alerts)."
-
-1. Navigate to https://github.com/advisories.
-2. Click an advisory.
-3. At the top of the advisory page, click **Dependabot alerts**.
-   ![Dependabot alerts](/assets/images/help/security/advisory-database-dependabot-alerts.png)
-4. Optionally, to filter the list, use the search bar or the drop-down menus. The "Organization" drop-down menu allows you to filter the {% data variables.product.prodname_dependabot_alerts %} per owner (organization or user).
-   ![Search bar and drop-down menus to filter alerts](/assets/images/help/security/advisory-database-dependabot-alerts-filters.png)
-5. For more details about the advisory, and for advice on how to fix the vulnerable repository, click the repository name.
-
-{% ifversion security-advisories-ghes-ghae %}
-## Accessing the local advisory database on {% data variables.location.product_location %}
-
-If your site administrator has enabled {% data variables.product.prodname_github_connect %} for {% data variables.location.product_location %}, you can also browse reviewed advisories locally. For more information, see "[About {% data variables.product.prodname_github_connect %}](/admin/configuration/configuring-github-connect/about-github-connect)".
-
-You can use your local advisory database to check whether a specific security vulnerability is included, and therefore whether you'd get alerts for vulnerable dependencies. You can also view any vulnerable repositories. 
-
-1. Navigate to `https://HOSTNAME/advisories`.
-2. Optionally, to filter the list, use any of the drop-down menus.
-  ![Dropdown filters](/assets/images/help/security/advisory-database-dropdown-filters.png)
-   {% note %}
-
-   **Note:** Only reviewed advisories will be listed. Unreviewed advisories can be viewed in the {% data variables.product.prodname_advisory_database %} on {% data variables.product.prodname_dotcom_the_website %}. For more information, see "[Accessing an advisory in the GitHub Advisory Database](#accessing-an-advisory-in-the-github-advisory-database)". 
-
-   {% endnote %}
-3. Click an advisory to view details.{% ifversion GH-advisory-db-supports-malware %} By default, you will see {% data variables.product.company_short %}-reviewed advisories for security vulnerabilities. To show malware advisories, use `type:malware` in the search bar.{% endif %}
-
-You can also suggest improvements to any advisory directly from your local advisory database. For more information, see "[Editing advisories from {% data variables.location.product_location %}](/code-security/dependabot/dependabot-alerts/editing-security-advisories-in-the-github-advisory-database#editing-advisories-from-your-github-enterprise-server-instance)".
-
-### Viewing vulnerable repositories for {% data variables.location.product_location %}
-
-{% data reusables.repositories.enable-security-alerts %}
-
-In the local advisory database, you can see which repositories are affected by each security vulnerability{% ifversion GH-advisory-db-supports-malware %} or malware{% endif %}. To see a vulnerable repository, you must have access to {% data variables.product.prodname_dependabot_alerts %} for that repository. For more information, see "[About {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies#access-to-dependabot-alerts)."
-
-1. Navigate to `https://HOSTNAME/advisories`.
-2. Click an advisory.
-3. At the top of the advisory page, click **Dependabot alerts**.
-   ![Dependabot alerts](/assets/images/help/security/advisory-database-dependabot-alerts.png)
-4. Optionally, to filter the list, use the search bar or the drop-down menus. The "Organization" drop-down menu allows you to filter the {% data variables.product.prodname_dependabot_alerts %} per owner (organization or user).
-   ![Search bar and drop-down menus to filter alerts](/assets/images/help/security/advisory-database-dependabot-alerts-filters.png)
-5. For more details about the advisory, and for advice on how to fix the vulnerable repository, click the repository name.
-
-{% endif %}
-
-## Further reading
-
-- MITRE's [definition of "vulnerability"](https://www.cve.org/ResourcesSupport/Glossary#vulnerability)
diff --git a/translations/zh-CN/content/code-security/dependabot/dependabot-alerts/editing-security-advisories-in-the-github-advisory-database.md b/translations/zh-CN/content/code-security/dependabot/dependabot-alerts/editing-security-advisories-in-the-github-advisory-database.md
deleted file mode 100644
index 688f003461..0000000000
--- a/translations/zh-CN/content/code-security/dependabot/dependabot-alerts/editing-security-advisories-in-the-github-advisory-database.md
+++ /dev/null
@@ -1,55 +0,0 @@
----
-title: Editing security advisories in the GitHub Advisory Database
-intro: 'You can submit improvements to any advisory published in the {% data variables.product.prodname_advisory_database %}.'
-redirect_from:
-  - /code-security/security-advisories/editing-security-advisories-in-the-github-advisory-database
-  - /code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/editing-security-advisories-in-the-github-advisory-database
-versions:
-  fpt: '*'
-  ghec: '*'
-  ghes: '*'
-  ghae: '*'
-type: how_to
-topics:
-  - Security advisories
-  - Alerts
-  - Dependabot
-  - Vulnerabilities
-  - CVEs
-shortTitle: Edit Advisory Database
----
-
-## About editing advisories in the {% data variables.product.prodname_advisory_database %}
-Security advisories in the {% data variables.product.prodname_advisory_database %} at [github.com/advisories](https://github.com/advisories) are considered global advisories. Anyone can suggest improvements on any global security advisory in the {% data variables.product.prodname_advisory_database %}. You can edit or add any detail, including additionally affected ecosystems, severity level or description of who is impacted. The {% data variables.product.prodname_security %} curation team will review the submitted improvements and publish them onto the {% data variables.product.prodname_advisory_database %} if accepted.
-{% ifversion fpt or ghec %}
-Only repository owners and administrators can edit repository-level security advisories. For more information, see "[Editing a repository security advisory](/code-security/security-advisories/editing-a-security-advisory)."{% endif %}
-
-## Editing advisories in the GitHub Advisory Database
-
-1. Navigate to https://github.com/advisories.
-1. Select the security advisory you would like to contribute to.
-1. On the right-hand side of the page, click the **Suggest improvements for this vulnerability** link.
-   
-   ![Screenshot of the suggest improvements link](/assets/images/help/security/suggest-improvements-to-advisory.png)
-
-1. In the "Improve security advisory" form, make the desired improvements. You can edit or add any detail.{% ifversion fpt or ghec %} For information about correctly specifying information on the form, including affected versions, see "[Best practices for writing repository security advisories](/code-security/repository-security-advisories/best-practices-for-writing-repository-security-advisories)."{% endif %}{% ifversion security-advisories-reason-for-change %}
-1. Under **Reason for change**, explain why you want to make this improvement. If you include links to supporting material this will help our reviewers.
-   
-   ![Screenshot of the reason for change field](/assets/images/help/security/security-advisories-suggest-improvement-reason.png){% endif %}
-
-1. When you finish editing the advisory, click **Submit improvements**.
-1. Once you submit your improvements, a pull request containing your changes will be created for review in [github/advisory-database](https://github.com/github/advisory-database) by the {% data variables.product.prodname_security %} curation team. If the advisory originated from a {% data variables.product.prodname_dotcom %} repository, we will also tag the original publisher for optional commentary. You can view the pull request and get notifications when it is updated or closed.
-
-You can also open a pull request directly on an advisory file in the [github/advisory-database](https://github.com/github/advisory-database) repository. For more information, see the [contribution guidelines](https://github.com/github/advisory-database/blob/main/CONTRIBUTING.md). 
-
-{% ifversion security-advisories-ghes-ghae %}
-## Editing advisories from {% data variables.location.product_location %}
-
-If you have {% data variables.product.prodname_github_connect %} enabled for {% data variables.location.product_location %}, you will be able to see advisories by adding `/advisories` to the instance url. 
-
-1. Navigate to `https://HOSTNAME/advisories`.
-2. Select the security advisory you would like to contribute to.
-3. On the right-hand side of the page, click the **Suggest improvements for this vulnerability on Github.com.** link. A new tab opens with the same security advisory on {% data variables.product.prodname_dotcom_the_website %}.
-![Suggest improvements link](/assets/images/help/security/suggest-improvements-to-advisory-on-github-com.png)
-4. Edit the advisory, following steps four through six in "[Editing advisories in the GitHub Advisory Database](#editing-advisories-in-the-github-advisory-database)" above.
-{% endif %}
diff --git a/translations/zh-CN/content/code-security/dependabot/dependabot-alerts/index.md b/translations/zh-CN/content/code-security/dependabot/dependabot-alerts/index.md
index 087f5864a1..87831d91fb 100644
--- a/translations/zh-CN/content/code-security/dependabot/dependabot-alerts/index.md
+++ b/translations/zh-CN/content/code-security/dependabot/dependabot-alerts/index.md
@@ -15,8 +15,6 @@ topics:
   - Repositories
   - Dependencies
 children:
-  - /browsing-security-advisories-in-the-github-advisory-database
-  - /editing-security-advisories-in-the-github-advisory-database
   - /about-dependabot-alerts
   - /configuring-dependabot-alerts
   - /viewing-and-updating-dependabot-alerts
diff --git a/translations/zh-CN/content/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts.md b/translations/zh-CN/content/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts.md
index 28df5d5e99..94166566bd 100644
--- a/translations/zh-CN/content/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts.md
+++ b/translations/zh-CN/content/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts.md
@@ -26,13 +26,13 @@ topics:
 {% data reusables.dependabot.beta-security-and-version-updates %}
 {% data reusables.dependabot.enterprise-enable-dependabot %}
 
-Your repository's {% data variables.product.prodname_dependabot_alerts %} tab lists all open and closed {% data variables.product.prodname_dependabot_alerts %}{% ifversion fpt or ghec or ghes > 3.2 %} and corresponding {% data variables.product.prodname_dependabot_security_updates %}{% endif %}. You can{% ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4 %} filter alerts by package, ecosystem, or manifest. You can {% endif %} sort the list of alerts, and you can click into specific alerts for more details. {% ifversion dependabot-bulk-alerts %}You can also dismiss or reopen alerts, either one by one or by selecting multiple alerts at once.{% else %}You can also dismiss or reopen alerts. {% endif %} For more information, see "[About {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)." 
+Your repository's {% data variables.product.prodname_dependabot_alerts %} tab lists all open and closed {% data variables.product.prodname_dependabot_alerts %}{% ifversion fpt or ghec or ghes %} and corresponding {% data variables.product.prodname_dependabot_security_updates %}{% endif %}. You can{% ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4 %} filter alerts by package, ecosystem, or manifest. You can {% endif %} sort the list of alerts, and you can click into specific alerts for more details. {% ifversion dependabot-bulk-alerts %}You can also dismiss or reopen alerts, either one by one or by selecting multiple alerts at once.{% else %}You can also dismiss or reopen alerts. {% endif %} For more information, see "[About {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)." 
 
-{% ifversion fpt or ghec or ghes > 3.2 %}
+{% ifversion fpt or ghec or ghes %}
 You can enable automatic security updates for any repository that uses {% data variables.product.prodname_dependabot_alerts %} and the dependency graph. For more information, see "[About {% data variables.product.prodname_dependabot_security_updates %}](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-dependabot-security-updates)."
 {% endif %}
 
-{% ifversion fpt or ghec or ghes > 3.2 %}
+{% ifversion fpt or ghec or ghes %}
 ## About updates for vulnerable dependencies in your repository
 
 {% data variables.product.product_name %} generates {% data variables.product.prodname_dependabot_alerts %} when we detect that your codebase is using dependencies with known security risks. For repositories where {% data variables.product.prodname_dependabot_security_updates %} are enabled, when {% data variables.product.product_name %} detects a vulnerable dependency in the default branch, {% data variables.product.prodname_dependabot %} creates a pull request to fix it. The pull request will upgrade the dependency to the minimum possible secure version needed to avoid the vulnerability.
@@ -144,16 +144,16 @@ For supported languages, {% data variables.product.prodname_dependabot %} detect
 ### Fixing vulnerable dependencies
 
 1. View the details for an alert. For more information, see "[Viewing {% data variables.product.prodname_dependabot_alerts %}](#viewing-dependabot-alerts)" (above).
-{% ifversion fpt or ghec or ghes > 3.2 %}
+{% ifversion fpt or ghec or ghes %}
 1. If you have {% data variables.product.prodname_dependabot_security_updates %} enabled, there may be a link to a pull request that will fix the dependency. Alternatively, you can click **Create {% data variables.product.prodname_dependabot %} security update** at the top of the alert details page to create a pull request.
   ![Create {% data variables.product.prodname_dependabot %} security update button](/assets/images/help/repository/create-dependabot-security-update-button-ungrouped.png)
 1. Optionally, if you do not use {% data variables.product.prodname_dependabot_security_updates %}, you can use the information on the page to decide which version of the dependency to upgrade to and create a pull request to update the dependency to a secure version.
-{% elsif ghes < 3.3 or ghae %}
+{% elsif ghae %}
 1. You can use the information on the page to decide which version of the dependency to upgrade to and create a pull request to the manifest or lock file to a secure version.
 {% endif %}
 1. When you're ready to update your dependency and resolve the vulnerability, merge the pull request. 
 
-{% ifversion fpt or ghec or ghes > 3.2 %}
+{% ifversion fpt or ghec or ghes %}
    Each pull request raised by {% data variables.product.prodname_dependabot %} includes information on commands you can use to control {% data variables.product.prodname_dependabot %}. For more information, see "[Managing pull requests for dependency updates](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/managing-pull-requests-for-dependency-updates#managing-dependabot-pull-requests-with-comment-commands)."
 {% endif %}
 
diff --git a/translations/zh-CN/content/code-security/dependabot/dependabot-security-updates/configuring-dependabot-security-updates.md b/translations/zh-CN/content/code-security/dependabot/dependabot-security-updates/configuring-dependabot-security-updates.md
index 320c6a0c45..0e0910c214 100644
--- a/translations/zh-CN/content/code-security/dependabot/dependabot-security-updates/configuring-dependabot-security-updates.md
+++ b/translations/zh-CN/content/code-security/dependabot/dependabot-security-updates/configuring-dependabot-security-updates.md
@@ -13,7 +13,7 @@ redirect_from:
 versions:
   fpt: '*'
   ghec: '*'
-  ghes: '>3.2'
+  ghes: '*'
 type: how_to
 topics:
   - Dependabot
diff --git a/translations/zh-CN/content/code-security/dependabot/dependabot-security-updates/index.md b/translations/zh-CN/content/code-security/dependabot/dependabot-security-updates/index.md
index 5ab4f3bdf8..ef6cfa41b7 100644
--- a/translations/zh-CN/content/code-security/dependabot/dependabot-security-updates/index.md
+++ b/translations/zh-CN/content/code-security/dependabot/dependabot-security-updates/index.md
@@ -5,7 +5,7 @@ allowTitleToDifferFromFilename: true
 versions:
   fpt: '*'
   ghec: '*'
-  ghes: '>3.2'
+  ghes: '*'
 topics:
   - Repositories
   - Dependabot
@@ -16,11 +16,11 @@ shortTitle: Dependabot security updates
 children:
   - /about-dependabot-security-updates
   - /configuring-dependabot-security-updates
-ms.openlocfilehash: 046ef28084ce31c1a4178355f5db6644b5ba0f12
-ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.openlocfilehash: e18b6331f762a81b82c759de5fdbc6eeed300308
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: zh-CN
-ms.lasthandoff: 09/11/2022
-ms.locfileid: '145101115'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148108055'
 ---
 
diff --git a/translations/zh-CN/content/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file.md b/translations/zh-CN/content/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file.md
index 38b4b62926..eaefe0047a 100644
--- a/translations/zh-CN/content/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file.md
+++ b/translations/zh-CN/content/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file.md
@@ -11,7 +11,7 @@ miniTocMaxHeadingLevel: 3
 versions:
   fpt: '*'
   ghec: '*'
-  ghes: '>3.2'
+  ghes: '*'
 type: reference
 topics:
   - Dependabot
diff --git a/translations/zh-CN/content/code-security/dependabot/dependabot-version-updates/customizing-dependency-updates.md b/translations/zh-CN/content/code-security/dependabot/dependabot-version-updates/customizing-dependency-updates.md
index 770f25b958..4ec0f0cac8 100644
--- a/translations/zh-CN/content/code-security/dependabot/dependabot-version-updates/customizing-dependency-updates.md
+++ b/translations/zh-CN/content/code-security/dependabot/dependabot-version-updates/customizing-dependency-updates.md
@@ -1,6 +1,6 @@
 ---
-title: 自定义依赖项更新
-intro: '您可以自定义 {% data variables.product.prodname_dependabot %} 如何维护依赖项。'
+title: Customizing dependency updates
+intro: 'You can customize how {% data variables.product.prodname_dependabot %} maintains your dependencies.'
 permissions: 'People with write permissions to a repository can configure {% data variables.product.prodname_dependabot %} for the repository.'
 redirect_from:
   - /github/administering-a-repository/customizing-dependency-updates
@@ -9,7 +9,7 @@ redirect_from:
 versions:
   fpt: '*'
   ghec: '*'
-  ghes: '>3.2'
+  ghes: '*'
 type: how_to
 topics:
   - Dependabot
@@ -20,40 +20,36 @@ topics:
   - Pull requests
   - Vulnerabilities
 shortTitle: Customize updates
-ms.openlocfilehash: 6cb6db974fe880bccc76c89447dc077e0617df9a
-ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
-ms.translationtype: HT
-ms.contentlocale: zh-CN
-ms.lasthandoff: 09/11/2022
-ms.locfileid: '145101104'
 ---
-{% data reusables.dependabot.beta-security-and-version-updates %} {% data reusables.dependabot.enterprise-enable-dependabot %}
 
-## 关于自定义依赖项更新
+{% data reusables.dependabot.beta-security-and-version-updates %}
+{% data reusables.dependabot.enterprise-enable-dependabot %}
 
-启用版本更新后，可以通过向 dependabot.yml 文件添加更多选项来自定义 {% data variables.product.prodname_dependabot %} 维护依赖项的方式。 例如，可以：
+## About customizing dependency updates
 
-- 指定星期几打开版本更新的拉取请求：`schedule.day`
-- 为每个包管理器设置审阅者、被分派人和标签：`reviewers`、`assignees` 和 `labels`
-- 为每个清单文件的更改定义版本控制策略：`versioning-strategy`
-- 更改为版本更新打开的最大拉取请求数（默认值为 5）：`open-pull-requests-limit`
-- 打开版本更新的拉取请求以定位特定分支，而不是默认分支：`target-branch`
+After you've enabled version updates, you can customize how {% data variables.product.prodname_dependabot %} maintains your dependencies by adding further options to the *dependabot.yml* file. For example, you could:
 
-有关配置选项的详细信息，请参阅“[dependabot.yml 文件的配置选项](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/configuration-options-for-dependency-updates)”。
+- Specify which day of the week to open pull requests for version updates: `schedule.day`
+- Set reviewers, assignees, and labels for each package manager: `reviewers`, `assignees`, and `labels`
+- Define a versioning strategy for changes to each manifest file: `versioning-strategy`
+- Change the maximum number of open pull requests for version updates from the default of 5: `open-pull-requests-limit`
+- Open pull requests for version updates to target a specific branch, instead of the default branch: `target-branch`
 
-更新存储库中的 dependabot.yml 文件后，{% data variables.product.prodname_dependabot %} 会使用新配置即刻进行检查。 几分钟内，你将在 {% data variables.product.prodname_dependabot %} 选项卡上看到更新的依赖项列表，如果存储库有很多依赖项，可能需要更长时间。 您可能还会看到针对版本更新的新拉取请求。 有关详细信息，请参阅“[列出为版本更新配置的依赖项](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/listing-dependencies-configured-for-version-updates)”。
+For more information about the configuration options, see "[Configuration options for the dependabot.yml file](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/configuration-options-for-dependency-updates)."
 
-## 配置更改对安全更新的影响
+When you update the *dependabot.yml* file in your repository, {% data variables.product.prodname_dependabot %} runs an immediate check with the new configuration. Within minutes you will see an updated list of dependencies on the **{% data variables.product.prodname_dependabot %}** tab, this may take longer if the repository has many dependencies. You may also see new pull requests for version updates. For more information, see "[Listing dependencies configured for version updates](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/listing-dependencies-configured-for-version-updates)."
 
-如果自定义 dependabot.yml 文件，可能会注意到针对安全更新提出的拉取请求发生了一些变化。 这些拉取请求始终由依赖项的安全通告触发，而不是由 {% data variables.product.prodname_dependabot %} 时间表触发。 但是，它们会从 dependabot.yml 文件继承相关的配置设置，除非为版本更新指定不同的目标分支。
+## Impact of configuration changes on security updates
 
-有关示例，请参阅下面的“[设置自定义标签](#setting-custom-labels)”。
+If you customize the *dependabot.yml* file, you may notice some changes to the pull requests raised for security updates. These pull requests are always triggered by a security advisory for a dependency, rather than by the {% data variables.product.prodname_dependabot %} schedule. However, they inherit relevant configuration settings from the *dependabot.yml* file unless you specify a different target branch for version updates.
 
-## 修改计划
+For an example, see "[Setting custom labels](#setting-custom-labels)" below.
 
-设置 `daily` 更新计划后，{% data variables.product.prodname_dependabot %} 会默认在 05:00 UTC 检查新版本。 可以使用 `schedule.time` 指定检查更新的备用时间（格式：`hh:mm`）。
+## Modifying scheduling
 
-下面的示例 dependabot.yml 文件扩展了 npm 配置，以指定 {% data variables.product.prodname_dependabot %} 应何时检查依赖项的版本更新。
+When you set a `daily` update schedule, by default, {% data variables.product.prodname_dependabot %} checks for new versions at 05:00 UTC. You can use `schedule.time` to specify an alternative time of day to check for updates (format: `hh:mm`).
+
+The example *dependabot.yml* file below expands the npm configuration to specify when {% data variables.product.prodname_dependabot %} should check for version updates to dependencies.
 
 ```yaml
 # dependabot.yml file with
@@ -70,13 +66,13 @@ updates:
       time: "02:00"
 ```
 
-## 设置审查者和受理人
+## Setting reviewers and assignees
 
-默认情况下，{% data variables.product.prodname_dependabot %} 会提出没有任何审查者或受理人的拉取请求。
+By default, {% data variables.product.prodname_dependabot %} raises pull requests without any reviewers or assignees.
 
-可以使用 `reviewers` 和 `assignees` 为针对包管理器提出的所有拉取请求指定审阅者和被分派人。 指定一个团队时，必须使用完整的团队名称，就像 @mentioning 团队（包括组织）一样。
+You can use `reviewers` and `assignees`  to specify reviewers and assignees for all pull requests raised for a package manager. When you specify a team, you must use the full team name, as if you were @mentioning the team (including the organization).
 
-下面的示例 dependabot.yml 文件更改了 npm 配置，使所有通过 npm 的版本和安全更新打开的拉取请求都有两个审阅者和一个被分派人。
+The example *dependabot.yml* file below changes the npm configuration so that all pull requests opened with version and security updates for npm will have two reviewers and one assignee.
 
 ```yaml
 # dependabot.yml file with
@@ -88,7 +84,7 @@ updates:
   - package-ecosystem: "npm"
     directory: "/"
     schedule:
-      interval: "daily"
+      interval: "weekly"
     # Raise all npm pull requests with reviewers
     reviewers:
       - "my-org/team-name"
@@ -98,17 +94,17 @@ updates:
       - "user-name"
 ```
 
-## 设置自定义标签
+## Setting custom labels
 
 {% data reusables.dependabot.default-labels %}
 
-可以使用 `labels` 替代默认标签，并为针对包管理器提出的所有拉取请求指定替代标签。 无法在 dependabot.yml 文件中创建新标签，因此，存储库中必须已存在替代标签。
+You can use `labels` to override the default labels and specify alternative labels for all pull requests raised for a package manager. You can't create new labels in the *dependabot.yml* file, so the alternative labels must already exist in the repository.
 
-下面的示例 dependabot.yml 文件更改了 npm 配置，使所有通过 npm 的版本和安全更新打开的拉取请求都有自定义标签。 它还会更改 Docker 配置，以针对自定义分支检查版本更新，并针对自定义分支使用自定义标签提出拉取请求。 Docker 的变更不会影响安全更新拉取请求，因为安全更新始终针对默认分支进行。
+The example *dependabot.yml* file below changes the npm configuration so that all pull requests opened with version and security updates for npm will have custom labels. It also changes the Docker configuration to check for version updates against a custom branch and to raise pull requests with custom labels against that custom branch. The changes to Docker will not affect security update pull requests because security updates are always made against the default branch.
 
 {% note %}
 
-只有：新版 `target-branch` 必须包含要更新的 Dockerfile，，此变更将导致 Docker 版本更新被禁用。
+**Note:** The new `target-branch` must contain a Dockerfile to update, otherwise this change will have the effect of disabling version updates for Docker.
 
 {% endnote %}
 
@@ -122,7 +118,7 @@ updates:
   - package-ecosystem: "npm"
     directory: "/"
     schedule:
-      interval: "daily"
+      interval: "weekly"
     # Raise all npm pull requests with custom labels
     labels:
       - "npm dependencies"
@@ -132,7 +128,7 @@ updates:
   - package-ecosystem: "docker"
     directory: "/"
     schedule:
-      interval: "daily"
+      interval: "weekly"
     # Raise pull requests for Docker version updates
     # against the "develop" branch. The Docker configuration
     # no longer affects security update pull requests.
@@ -143,6 +139,6 @@ updates:
       - "triage-board"
 ```
 
-## 更多示例
+## More examples
 
-有关详细信息，请参阅“[dependabot.yml 文件的配置选项](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/configuration-options-for-dependency-updates)”。
+For more examples, see "[Configuration options for the dependabot.yml file](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/configuration-options-for-dependency-updates)."
diff --git a/translations/zh-CN/content/code-security/dependabot/dependabot-version-updates/index.md b/translations/zh-CN/content/code-security/dependabot/dependabot-version-updates/index.md
index 23ecb96bb8..02426a36ad 100644
--- a/translations/zh-CN/content/code-security/dependabot/dependabot-version-updates/index.md
+++ b/translations/zh-CN/content/code-security/dependabot/dependabot-version-updates/index.md
@@ -8,7 +8,7 @@ redirect_from:
 versions:
   fpt: '*'
   ghec: '*'
-  ghes: '>3.2'
+  ghes: '*'
 topics:
   - Repositories
   - Dependabot
@@ -22,11 +22,11 @@ children:
   - /customizing-dependency-updates
   - /configuration-options-for-the-dependabot.yml-file
 shortTitle: Dependabot version updates
-ms.openlocfilehash: 7eec75884da9fed388c7f882fe870d993606cb00
-ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.openlocfilehash: 7d926dd11d8d97511a66109273e30aa018f2707a
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: zh-CN
-ms.lasthandoff: 09/11/2022
-ms.locfileid: '145101103'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148108782'
 ---
 
diff --git a/translations/zh-CN/content/code-security/dependabot/dependabot-version-updates/listing-dependencies-configured-for-version-updates.md b/translations/zh-CN/content/code-security/dependabot/dependabot-version-updates/listing-dependencies-configured-for-version-updates.md
index 695d4088e8..e44e45c3e1 100644
--- a/translations/zh-CN/content/code-security/dependabot/dependabot-version-updates/listing-dependencies-configured-for-version-updates.md
+++ b/translations/zh-CN/content/code-security/dependabot/dependabot-version-updates/listing-dependencies-configured-for-version-updates.md
@@ -1,6 +1,6 @@
 ---
-title: 列出为版本更新配置的依赖项
-intro: '您可以查看由 {% data variables.product.prodname_dependabot %} 监视更新的依赖项。'
+title: Listing dependencies configured for version updates
+intro: 'You can view the dependencies that {% data variables.product.prodname_dependabot %} monitors for updates.'
 redirect_from:
   - /github/administering-a-repository/listing-dependencies-configured-for-version-updates
   - /code-security/supply-chain-security/listing-dependencies-configured-for-version-updates
@@ -8,7 +8,7 @@ redirect_from:
 versions:
   fpt: '*'
   ghec: '*'
-  ghes: '>3.2'
+  ghes: '*'
 type: how_to
 topics:
   - Repositories
@@ -16,28 +16,27 @@ topics:
   - Version updates
   - Dependencies
 shortTitle: List configured dependencies
-ms.openlocfilehash: 8028c10c39d4b045206954fc38ed805b5432e553
-ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
-ms.translationtype: HT
-ms.contentlocale: zh-CN
-ms.lasthandoff: 09/10/2022
-ms.locfileid: '145101102'
 ---
-{% data reusables.dependabot.beta-security-and-version-updates %} {% data reusables.dependabot.enterprise-enable-dependabot %}
 
-## 查看由 {% data variables.product.prodname_dependabot %} 监视的依赖项
+{% data reusables.dependabot.beta-security-and-version-updates %}
+{% data reusables.dependabot.enterprise-enable-dependabot %}
 
-启用版本更新后，可以使用存储库依赖关系图中的“{% data variables.product.prodname_dependabot %}”选项卡确认配置是否正确。 有关详细信息，请参阅“[配置 {% data variables.product.prodname_dependabot %} 版本更新](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/enabling-and-disabling-dependabot-version-updates)”。
+## Viewing dependencies monitored by {% data variables.product.prodname_dependabot %}
 
-{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.accessing-repository-graphs %} {% data reusables.repositories.click-dependency-graph %} {% data reusables.dependabot.click-dependabot-tab %}
-1. 或者，要查看为包管理器监视的文件，请单击关联的 {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}。
-  ![受监视的依赖项文件](/assets/images/help/dependabot/monitored-dependency-files.png)
+After you've enabled version updates, you can confirm that your configuration is correct using the **{% data variables.product.prodname_dependabot %}** tab in the dependency graph for the repository. For more information, see "[Configuring {% data variables.product.prodname_dependabot %} version updates](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/enabling-and-disabling-dependabot-version-updates)."
 
-如果缺少任何依赖项，请检查日志文件是否有错误。 如果缺少任何包管理器，请审查配置文件。
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.accessing-repository-graphs %}
+{% data reusables.repositories.click-dependency-graph %}
+{% data reusables.dependabot.click-dependabot-tab %}
+1. Optionally, to view the files monitored for a package manager, click the associated {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}.
+  ![Monitored dependency files](/assets/images/help/dependabot/monitored-dependency-files.png)
 
-## 查看 {% data variables.product.prodname_dependabot %} 日志文件
+If any dependencies are missing, check the log files for errors. If any package managers are missing, review the configuration file.
 
-1. 在“{% data variables.product.prodname_dependabot %}”选项卡上，单击“上次检查时间之前”，查看上次检查版本更新期间 {% data variables.product.prodname_dependabot %} 生成的日志文件 。
-  ![查看日志文件](/assets/images/help/dependabot/last-checked-link.png)
-2. （可选）若要重新运行版本检查，请单击“检查更新”。
-  ![检查更新](/assets/images/help/dependabot/check-for-updates.png)
+## Viewing {% data variables.product.prodname_dependabot %} log files
+
+1. On the **{% data variables.product.prodname_dependabot %}** tab, click **Last checked *TIME* ago** to see the log file that {% data variables.product.prodname_dependabot %} generated during the last check for version updates.
+  ![View log file](/assets/images/help/dependabot/last-checked-link.png)
+2. Optionally, to rerun the version check, click **Check for updates**.
+  ![Check for updates](/assets/images/help/dependabot/check-for-updates.png)
diff --git a/translations/zh-CN/content/code-security/dependabot/index.md b/translations/zh-CN/content/code-security/dependabot/index.md
index ff5cbea002..757cd057ed 100644
--- a/translations/zh-CN/content/code-security/dependabot/index.md
+++ b/translations/zh-CN/content/code-security/dependabot/index.md
@@ -1,7 +1,7 @@
 ---
-title: 使用 Dependabot 确保供应链安全
+title: Keeping your supply chain secure with Dependabot
 shortTitle: Dependabot
-intro: '通过 {% data variables.product.prodname_dependabot %}，监视项目{% ifversion fpt or ghec or ghes > 3.2 %}中使用的依赖项中的漏洞，并使依赖项保持最新{% endif %}。'
+intro: 'Monitor vulnerabilities in dependencies used in your project{% ifversion fpt or ghec or ghes %} and keep your dependencies up-to-date{% endif %} with {% data variables.product.prodname_dependabot %}.'
 allowTitleToDifferFromFilename: true
 versions:
   fpt: '*'
@@ -19,11 +19,5 @@ children:
   - /dependabot-security-updates
   - /dependabot-version-updates
   - /working-with-dependabot
-ms.openlocfilehash: 82b385ab7177adfe568344c0dc04357ffafeb0b3
-ms.sourcegitcommit: 80842b4e4c500daa051eff0ccd7cde91c2d4bb36
-ms.translationtype: HT
-ms.contentlocale: zh-CN
-ms.lasthandoff: 09/12/2022
-ms.locfileid: '145101101'
 ---
 
diff --git a/translations/zh-CN/content/code-security/dependabot/working-with-dependabot/automating-dependabot-with-github-actions.md b/translations/zh-CN/content/code-security/dependabot/working-with-dependabot/automating-dependabot-with-github-actions.md
index 4d727384fd..05fcb40b26 100644
--- a/translations/zh-CN/content/code-security/dependabot/working-with-dependabot/automating-dependabot-with-github-actions.md
+++ b/translations/zh-CN/content/code-security/dependabot/working-with-dependabot/automating-dependabot-with-github-actions.md
@@ -6,7 +6,7 @@ miniTocMaxHeadingLevel: 3
 versions:
   fpt: '*'
   ghec: '*'
-  ghes: '>3.2'
+  ghes: '*'
   ghae: '*'
 type: how_to
 topics:
diff --git a/translations/zh-CN/content/code-security/dependabot/working-with-dependabot/index.md b/translations/zh-CN/content/code-security/dependabot/working-with-dependabot/index.md
index f0aded10ac..16f88857ac 100644
--- a/translations/zh-CN/content/code-security/dependabot/working-with-dependabot/index.md
+++ b/translations/zh-CN/content/code-security/dependabot/working-with-dependabot/index.md
@@ -5,7 +5,7 @@ intro: '有关使用 {% data variables.product.prodname_dependabot %} 的指导
 versions:
   fpt: '*'
   ghec: '*'
-  ghes: '>3.2'
+  ghes: '*'
 topics:
   - Repositories
   - Dependabot
@@ -20,11 +20,11 @@ children:
   - /managing-encrypted-secrets-for-dependabot
   - /troubleshooting-the-detection-of-vulnerable-dependencies
   - /troubleshooting-dependabot-errors
-ms.openlocfilehash: ae4f4cd7f4f748487420c2804eae67d561455099
-ms.sourcegitcommit: 80842b4e4c500daa051eff0ccd7cde91c2d4bb36
+ms.openlocfilehash: efab6caf0c9384c9e72cc5ed1fe64bd500cede45
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: zh-CN
-ms.lasthandoff: 09/12/2022
-ms.locfileid: '145109551'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148108075'
 ---
 
diff --git a/translations/zh-CN/content/code-security/dependabot/working-with-dependabot/keeping-your-actions-up-to-date-with-dependabot.md b/translations/zh-CN/content/code-security/dependabot/working-with-dependabot/keeping-your-actions-up-to-date-with-dependabot.md
index 3bac5cecf3..d6ffb64685 100644
--- a/translations/zh-CN/content/code-security/dependabot/working-with-dependabot/keeping-your-actions-up-to-date-with-dependabot.md
+++ b/translations/zh-CN/content/code-security/dependabot/working-with-dependabot/keeping-your-actions-up-to-date-with-dependabot.md
@@ -1,6 +1,6 @@
 ---
-title: 使用 Dependabot 保持操作的最新状态
-intro: '您可以使用 {% data variables.product.prodname_dependabot %} 来确保您使用的操作更新到最新版本。'
+title: Keeping your actions up to date with Dependabot
+intro: 'You can use {% data variables.product.prodname_dependabot %} to keep the actions you use updated to the latest versions.'
 redirect_from:
   - /github/administering-a-repository/keeping-your-actions-up-to-date-with-github-dependabot
   - /github/administering-a-repository/keeping-your-actions-up-to-date-with-dependabot
@@ -9,7 +9,7 @@ redirect_from:
 versions:
   fpt: '*'
   ghec: '*'
-  ghes: '>3.2'
+  ghes: '*'
 type: how_to
 topics:
   - Repositories
@@ -17,38 +17,33 @@ topics:
   - Version updates
   - Actions
 shortTitle: Auto-update actions
-ms.openlocfilehash: b7de2100ad191dbcb66f4853779e5f048ca33a84
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
-ms.translationtype: HT
-ms.contentlocale: zh-CN
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '146027961'
 ---
+
 {% data reusables.dependabot.beta-security-and-version-updates %}
 
 {% data reusables.dependabot.enterprise-enable-dependabot %}
 
-## 关于操作的 {% data variables.product.prodname_dependabot_version_updates %}
+## About {% data variables.product.prodname_dependabot_version_updates %} for actions
 
-操作通常使用漏洞修复和新功能进行更新，以使自动化流程更可靠、更快速、更安全。 为 {% data variables.product.prodname_actions %} 启用 {% data variables.product.prodname_dependabot_version_updates %} 时，{% data variables.product.prodname_dependabot %} 将帮助确保存储库 workflow.yml 文件中操作的引用保持最新。 对于文件中的每个操作，{% data variables.product.prodname_dependabot %} 根据最新版本检查操作的引用（通常是与操作关联的版本号或提交标识符）。 如果操作有更新的版本，{% data variables.product.prodname_dependabot %} 将向你发送拉取请求，要求将工作流程文件中的引用更新到最新版本。 有关 {% data variables.product.prodname_dependabot_version_updates %} 的详细信息，请参阅[关于 {% data variables.product.prodname_dependabot_version_updates %}](/github/administering-a-repository/about-dependabot-version-updates)。 有关为 {% data variables.product.prodname_actions %} 配置工作流程的更多信息，请参阅[了解 {% data variables.product.prodname_actions %}](/actions/learn-github-actions)。
+Actions are often updated with bug fixes and new features to make automated processes more reliable, faster, and safer. When you enable {% data variables.product.prodname_dependabot_version_updates %} for {% data variables.product.prodname_actions %}, {% data variables.product.prodname_dependabot %} will help ensure that references to actions in a repository's *workflow.yml* file are kept up to date. For each action in the file, {% data variables.product.prodname_dependabot %} checks the action's reference (typically a version number or commit identifier associated with the action) against the latest version. If a more recent version of the action is available, {% data variables.product.prodname_dependabot %} will send you a pull request that updates the reference in the workflow file to the latest version. For more information about {% data variables.product.prodname_dependabot_version_updates %}, see "[About {% data variables.product.prodname_dependabot_version_updates %}](/github/administering-a-repository/about-dependabot-version-updates)." For more information about configuring workflows for {% data variables.product.prodname_actions %}, see "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)."
   
 {% data reusables.actions.workflow-runs-dependabot-note %}
 
-## 为操作启用 {% data variables.product.prodname_dependabot_version_updates %}
+## Enabling {% data variables.product.prodname_dependabot_version_updates %} for actions
 
-可配置 {% data variables.product.prodname_dependabot_version_updates %} 来维护你的操作以及所依赖的库和包。 
+You can configure {% data variables.product.prodname_dependabot_version_updates %} to maintain your actions as well as the libraries and packages you depend on. 
 
-1. 如果你已经为其他生态系统或包管理器启用 {% data variables.product.prodname_dependabot_version_updates %}，只需打开现有的 dependabot.yml 文件。 否则，在存储库的 `.github` 目录中创建一个 dependabot.yml 配置文件。 有关详细信息，请参阅“[配置 Dependabot 版本更新](/code-security/dependabot/dependabot-version-updates/configuring-dependabot-version-updates#enabling-dependabot-version-updates)”。
-1. 指定 `"github-actions"` 为要监视的 `package-ecosystem`。
-1. 设置 `directory` 为 `"/"`，检查 `.github/workflows` 中的工作流文件。
-1. 设置 `schedule.interval` 以指定检查新版本的频率。
-{% data reusables.dependabot.check-in-dependabot-yml %} 如果已编辑现有文件，请保存所做的更改。
+1. If you have already enabled {% data variables.product.prodname_dependabot_version_updates %} for other ecosystems or package managers, simply open the existing *dependabot.yml* file. Otherwise, create a *dependabot.yml* configuration file in the `.github` directory of your repository. For more information, see "[Configuring Dependabot version updates](/code-security/dependabot/dependabot-version-updates/configuring-dependabot-version-updates#enabling-dependabot-version-updates)."
+1. Specify `"github-actions"` as a `package-ecosystem` to monitor.
+1. Set the `directory` to `"/"` to check for workflow files in `.github/workflows`.
+1. Set a `schedule.interval` to specify how often to check for new versions.
+{% data reusables.dependabot.check-in-dependabot-yml %} If you have edited an existing file, save your changes.
 
-您也可以在复刻上启用 {% data variables.product.prodname_dependabot_version_updates %}。 有关详细信息，请参阅[配置 {% data variables.product.prodname_dependabot %} 版本更新](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/enabling-and-disabling-dependabot-version-updates#enabling-version-updates-on-forks)。
+You can also enable {% data variables.product.prodname_dependabot_version_updates %} on forks. For more information, see "[Configuring {% data variables.product.prodname_dependabot %} version updates](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/enabling-and-disabling-dependabot-version-updates#enabling-version-updates-on-forks)."
 
-### 例如用于 {% data variables.product.prodname_actions %} 的 dependabot.yml 文件
+### Example *dependabot.yml* file for {% data variables.product.prodname_actions %}
 
-下面的示例 dependabot.yml 文件配置 {% data variables.product.prodname_actions %} 的版本更新。 `directory` 必须设置为 `"/"` 以检查 `.github/workflows` 中的工作流文件。 `schedule.interval` 设置为 `"daily"`。 在该文件被检入或更新后，{% data variables.product.prodname_dependabot %} 将检查您的操作的新版本。 {% data variables.product.prodname_dependabot %} 在发现任何过时的操作时，将会提出版本更新的拉取请求。 在初始版本更新后，{% data variables.product.prodname_dependabot %} 将继续每天检查一次过时的操作。
+The example *dependabot.yml* file below configures version updates for {% data variables.product.prodname_actions %}. The `directory` must be set to `"/"` to check for workflow files in `.github/workflows`. The `schedule.interval` is set to `"weekly"`. After this file has been checked in or updated, {% data variables.product.prodname_dependabot %} checks for new versions of your actions. {% data variables.product.prodname_dependabot %} will raise pull requests for version updates for any outdated actions that it finds. After the initial version updates, {% data variables.product.prodname_dependabot %} will continue to check for outdated versions of actions once a week.
 
 ```yaml
 # Set update schedule for GitHub Actions
@@ -59,14 +54,14 @@ updates:
   - package-ecosystem: "github-actions"
     directory: "/"
     schedule:
-      # Check for updates to GitHub Actions every weekday
-      interval: "daily"
+      # Check for updates to GitHub Actions every week
+      interval: "weekly"
 ```
 
-## 为操作配置 {% data variables.product.prodname_dependabot_version_updates %}
+## Configuring {% data variables.product.prodname_dependabot_version_updates %} for actions
 
-为操作启用 {% data variables.product.prodname_dependabot_version_updates %} 时，必须指定 `package-ecosystem`、`directory` 和 `schedule.interval` 的值。 您可以设置更多可选属性来进一步自定义版本更新。 有关详细信息，请参阅[dependabot.yml 文件的配置选项](/github/administering-a-repository/configuration-options-for-dependency-updates)。
+When enabling {% data variables.product.prodname_dependabot_version_updates %} for actions, you must specify values for `package-ecosystem`, `directory`, and `schedule.interval`. There are many more optional properties that you can set to further customize your version updates. For more information, see "[Configuration options for the dependabot.yml file](/github/administering-a-repository/configuration-options-for-dependency-updates)."
 
-## 延伸阅读
+## Further reading
 
-- [关于 GitHub Actions](/actions/getting-started-with-github-actions/about-github-actions)
+- "[About GitHub Actions](/actions/getting-started-with-github-actions/about-github-actions)"
diff --git a/translations/zh-CN/content/code-security/dependabot/working-with-dependabot/managing-encrypted-secrets-for-dependabot.md b/translations/zh-CN/content/code-security/dependabot/working-with-dependabot/managing-encrypted-secrets-for-dependabot.md
index 7b75165e76..d3c87a52e1 100644
--- a/translations/zh-CN/content/code-security/dependabot/working-with-dependabot/managing-encrypted-secrets-for-dependabot.md
+++ b/translations/zh-CN/content/code-security/dependabot/working-with-dependabot/managing-encrypted-secrets-for-dependabot.md
@@ -8,7 +8,7 @@ redirect_from:
 versions:
   fpt: '*'
   ghec: '*'
-  ghes: '>3.2'
+  ghes: '*'
 type: how_to
 topics:
   - Dependabot
diff --git a/translations/zh-CN/content/code-security/dependabot/working-with-dependabot/troubleshooting-dependabot-errors.md b/translations/zh-CN/content/code-security/dependabot/working-with-dependabot/troubleshooting-dependabot-errors.md
index b2903374c3..2c35207247 100644
--- a/translations/zh-CN/content/code-security/dependabot/working-with-dependabot/troubleshooting-dependabot-errors.md
+++ b/translations/zh-CN/content/code-security/dependabot/working-with-dependabot/troubleshooting-dependabot-errors.md
@@ -1,6 +1,6 @@
 ---
-title: 排查 Dependabot 错误
-intro: '有时，{% data variables.product.prodname_dependabot %} 无法提出拉取请求以更新依赖项。 您可以查看错误并取消阻止 {% data variables.product.prodname_dependabot %}。'
+title: Troubleshooting Dependabot errors
+intro: 'Sometimes {% data variables.product.prodname_dependabot %} is unable to raise a pull request to update your dependencies. You can review the error and unblock {% data variables.product.prodname_dependabot %}.'
 shortTitle: Troubleshoot errors
 miniTocMaxHeadingLevel: 3
 redirect_from:
@@ -11,7 +11,7 @@ redirect_from:
 versions:
   fpt: '*'
   ghec: '*'
-  ghes: '>3.2'
+  ghes: '*'
 type: how_to
 topics:
   - Dependabot
@@ -22,77 +22,72 @@ topics:
   - Troubleshooting
   - Errors
   - Dependencies
-ms.openlocfilehash: ad3449768246ea8659ddffe4957fd3d6801edd2c
-ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794
-ms.translationtype: HT
-ms.contentlocale: zh-CN
-ms.lasthandoff: 09/09/2022
-ms.locfileid: '147861658'
 ---
+
 {% data reusables.dependabot.beta-security-and-version-updates %}
 
 {% data reusables.dependabot.enterprise-enable-dependabot %}
 
-## 关于 {% data variables.product.prodname_dependabot %} 错误
+## About {% data variables.product.prodname_dependabot %} errors
 
 {% data reusables.dependabot.pull-request-introduction %}
 
-如果有任何因素阻止 {% data variables.product.prodname_dependabot %} 提出拉取请求，则报告为错误。
+If anything prevents {% data variables.product.prodname_dependabot %} from raising a pull request, this is reported as an error.
 
-## 使用 {% data variables.product.prodname_dependabot_security_updates %} 调查错误
+## Investigating errors with {% data variables.product.prodname_dependabot_security_updates %}
 
-当 {% data variables.product.prodname_dependabot %} 被阻止创建拉取请求以修复 {% data variables.product.prodname_dependabot %} 警报时，它会在警报上发布错误消息。 {% data variables.product.prodname_dependabot_alerts %} 视图显示尚未解决的所有警报列表。 若要访问警报视图，请单击存储库“安全”选项卡上的“{% data variables.product.prodname_dependabot_alerts %}” 。 如果旨在修复有漏洞依赖项的拉取请求已生成，则警报将包括指向该拉取请求的链接。
+When {% data variables.product.prodname_dependabot %} is blocked from creating a pull request to fix a {% data variables.product.prodname_dependabot %} alert, it posts the error message on the alert. The {% data variables.product.prodname_dependabot_alerts %} view shows a list of any alerts that have not been resolved yet. To access the alerts view, click **{% data variables.product.prodname_dependabot_alerts %}** on the **Security** tab for the repository. Where a pull request that will fix the vulnerable dependency has been generated, the alert includes a link to that pull request.
 
-![{% data variables.product.prodname_dependabot_alerts %} 视图显示拉取请求链接](/assets/images/help/dependabot/dependabot-alert-pr-link.png)
+![{% data variables.product.prodname_dependabot_alerts %} view showing a pull request link](/assets/images/help/dependabot/dependabot-alert-pr-link.png)
 
-有多个原因可能导致警报中没有拉取请求链接：
+There are several reasons why an alert may have no pull request link:
 
-1. {% data variables.product.prodname_dependabot_security_updates %} 未对仓库启用。
+1. {% data variables.product.prodname_dependabot_security_updates %} are not enabled for the repository.
 {% ifversion GH-advisory-db-supports-malware %}
-1. 警报适用于恶意软件，并且包没有安全版本。
+1. The alert is for malware and there is no secure version of the package.
 {% endif %}
-1. 警报针对未在锁文件中显式定义的间接或过渡依赖项。
-1. 某个错误阻止了 {% data variables.product.prodname_dependabot %} 创建拉取请求。
+1. The alert is for an indirect or transitive dependency that is not explicitly defined in a lock file.
+1. An error blocked {% data variables.product.prodname_dependabot %} from creating a pull request.
 
-如果某个错误阻止了 {% data variables.product.prodname_dependabot %} 创建拉取请求，您可以通过单击警报来显示错误详情。
+If an error blocked {% data variables.product.prodname_dependabot %} from creating a pull request, you can display details of the error by clicking the alert.
 
-## 使用 {% data variables.product.prodname_dependabot_version_updates %} 调查错误
+## Investigating errors with {% data variables.product.prodname_dependabot_version_updates %}
 
-当 {% data variables.product.prodname_dependabot %} 被阻止创建拉取请求以更新生态系统中的依赖项时，它将在清单文件中发布错误图标。 由 {% data variables.product.prodname_dependabot %} 管理的清单文件列于 {% data variables.product.prodname_dependabot %} 选项卡上。若要访问此选项卡，请在存储库的“见解”选项卡上单击“依赖项关系图”，然后单击“{% data variables.product.prodname_dependabot %}”选项卡  。
+When {% data variables.product.prodname_dependabot %} is blocked from creating a pull request to update a dependency in an ecosystem, it posts the error icon on the manifest file. The manifest files that are managed by {% data variables.product.prodname_dependabot %} are listed on the {% data variables.product.prodname_dependabot %} tab. To access this tab, on the **Insights** tab for the repository click **Dependency graph**, and then click the **{% data variables.product.prodname_dependabot %}** tab.
 
-![{% data variables.product.prodname_dependabot %} 视图显示错误](/assets/images/help/dependabot/dependabot-tab-view-error.png)
+![{% data variables.product.prodname_dependabot %} view showing an error](/assets/images/help/dependabot/dependabot-tab-view-error.png)
 
 {% ifversion fpt or ghec %}
 
-若要查看任何清单文件的日志文件，请单击“上次检查时间以前”链接。 当您显示一个带有错误符号的清单(例如上面截图中的 Maven）的日志文件时，也会显示任何错误。
+To see the log file for any manifest file, click the **Last checked TIME ago** link. When you display the log file for a manifest that's shown with an error symbol (for example, Maven in the screenshot above), any errors are also displayed.
 
-![{% data variables.product.prodname_dependabot %} 版本更新错误和日志 ](/assets/images/help/dependabot/dependabot-version-update-error.png)
+![{% data variables.product.prodname_dependabot %} version update error and log ](/assets/images/help/dependabot/dependabot-version-update-error.png)
 
 {% else %}
 
-若要查看任何清单文件的日志，请单击“上次检查时间以前”链接，然后单击“查看日志” 。
+To see the logs for any manifest file, click the **Last checked TIME ago** link, and then click **View logs**.
 
-![{% data variables.product.prodname_dependabot %} 版本更新错误和日志 ](/assets/images/enterprise/3.3/dependabot/dependabot-version-update-error.png)
+![{% data variables.product.prodname_dependabot %} version update error and log ](/assets/images/enterprise/3.3/dependabot/dependabot-version-update-error.png)
 
 {% endif %}
 
-## 了解 {% data variables.product.prodname_dependabot %} 错误
+## Understanding {% data variables.product.prodname_dependabot %} errors
 
-安全更新拉取请求用于将有漏洞依赖项升级到包含漏洞修复的最低版本。 而版本更新拉取请求用于将依赖项升级到包清单文件和 {% data variables.product.prodname_dependabot %} 配置文件允许的最新版本。 因此，某些错误特定于一种类型的更新。
+Pull requests for security updates act to upgrade a vulnerable dependency to the minimum version that includes a fix for the vulnerability. In contrast, pull requests for version updates act to upgrade a dependency to the latest version allowed by the package manifest and {% data variables.product.prodname_dependabot %} configuration files. Consequently, some errors are specific to one type of update.
 
-### {% data variables.product.prodname_dependabot %} 无法将依赖项更新到无漏洞版本
+### {% data variables.product.prodname_dependabot %} cannot update DEPENDENCY to a non-vulnerable version
 
-仅限安全更新。 {% data variables.product.prodname_dependabot %} 无法创建拉取请求以将有漏洞依赖项更新到安全版本，而又不破坏此存储库依赖项关系图中的其他依赖项。
+**Security updates only.** {% data variables.product.prodname_dependabot %} cannot create a pull request to update the vulnerable dependency to a secure version without breaking other dependencies in the dependency graph for this repository.
 
-每个具有依赖项的应用程序都有一个依赖关系图，即应用程序直接或间接依赖的每个包版本的定向非循环图。 每次更新依赖项时，必须解决此图，否则将无法构建应用程序。 当生态系统具有深刻而复杂的依赖关系图（例如 npm 和 RubyGems）时，如果不升级整个生态系统，往往难以升级单个依赖项。
+Every application that has dependencies has a dependency graph, that is, a directed acyclic graph of every package version that the application directly or indirectly depends on. Every time a dependency is updated, this graph must resolve otherwise the application won't build. When an ecosystem has a deep and complex dependency graph, for example, npm and RubyGems, it is often impossible to upgrade a single dependency without upgrading the whole ecosystem.
 
-避免这个问题的最佳办法是跟上最新发布的版本，例如启用版本更新。 这增加了通过不破坏依赖关系图的简单升级解决一个依赖项中的漏洞的可能性。 有关详细信息，请参阅“[配置 {% data variables.product.prodname_dependabot %} 版本更新](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/enabling-and-disabling-dependabot-version-updates)”。{% ifversion dependabot-security-updates-unlock-transitive-dependencies %}
+The best way to avoid this problem is to stay up to date with the most recently released versions, for example, by enabling version updates. This increases the likelihood that a vulnerability in one dependency can be resolved by a simple upgrade that doesn't break the dependency graph. For more information, see "[Configuring {% data variables.product.prodname_dependabot %} version updates](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/enabling-and-disabling-dependabot-version-updates)."{% ifversion dependabot-security-updates-unlock-transitive-dependencies %}
 
-### {% data variables.product.prodname_dependabot %} 尝试在没有警报的情况下更新依赖项
+### {% data variables.product.prodname_dependabot %} tries to update dependencies without an alert
 
-仅限安全更新。 {% data variables.product.prodname_dependabot %} 更新显式定义的可传递依赖项，这些依赖项对于所有生态系统而言易受攻击。 对于 npm，{% data variables.product.prodname_dependabot %} 会引发拉取请求，如果这是修复可传递依赖项的唯一方法，则该请求还会更新父依赖项。
+**Security updates only.** {% data variables.product.prodname_dependabot %} updates explicitly defined transitive dependencies that are vulnerable for all ecosystems. For npm, {% data variables.product.prodname_dependabot %} will raise a pull request that also updates the parent dependency if it's the only way to fix the transitive dependency.
 
-例如，在 `A` 版本 `~2.0.0` 上有一个依赖项的项目在 `B` 版本 `~1.0.0`（已解析为 `1.0.1`）上有一个可传递依赖项。
+For example, a project with a dependency on `A` version `~2.0.0` which has a transitive dependency on `B` version `~1.0.0` which has resolved to `1.0.1`.
 ```
 my project
 |
@@ -100,59 +95,59 @@ my project
        |
        --> B (1.0.1) [~1.0.0]
 ```       
-如果针对 `B` 版本 `<2.0.0` 发布安全漏洞，而修补程序在 `2.0.0` 上可用，则 {% data variables.product.prodname_dependabot %} 将尝试更新 `B`，但会发现无法更新，因为 `A` 具有限制，仅允许较低的易受攻击版本。 为了修复漏洞，{% data variables.product.prodname_dependabot %} 将查找允许使用固定版本的 `B` 的依赖项 `A` 的更新。 
+If a security vulnerability is released for `B` versions `<2.0.0` and a patch is available at `2.0.0` then  {% data variables.product.prodname_dependabot %} will attempt to update `B` but will find that it's not possible due to the restriction in place by `A` which only allows lower vulnerable versions. To fix the vulnerability, {% data variables.product.prodname_dependabot %} will look for updates to dependency `A` which allow the fixed version of `B` to be used. 
 
-{% data variables.product.prodname_dependabot %} 会自动生成一个拉取请求以同时升级父级和子级可传递依赖项。{% endif %}
+{% data variables.product.prodname_dependabot %} automatically generates a pull request that upgrades both the locked parent and child transitive dependencies.{% endif %}
 
-### {% data variables.product.prodname_dependabot %} 无法更新到所需的版本，因为已经为最新版本打开了拉取请求
+### {% data variables.product.prodname_dependabot %} cannot update to the required version as there is already an open pull request for the latest version
 
-仅限安全更新。 {% data variables.product.prodname_dependabot %} 不会创建拉取请求以将有漏洞依赖项更新到安全版本，因为已存在更新此依赖项的打开拉取请求。 如果在一个依赖项中检测到漏洞，但已经存在将该依赖项更新到最新版本的打开拉取请求时，您将会看到此错误。
+**Security updates only.** {% data variables.product.prodname_dependabot %} will not create a pull request to update the vulnerable dependency to a secure version because there is already an open pull request to update this dependency. You will see this error when a vulnerability is detected in a single dependency and there's already an open pull request to update the dependency to the latest version.
 
-有两个选项：您可以查看打开的拉取请求，确认更改安全后合并它，或者关闭该拉取请求并触发新的安全更新拉取请求。 有关详细信息，请参阅“[手动触发 {% data variables.product.prodname_dependabot %} 拉取请求](#triggering-a-dependabot-pull-request-manually)”。
+There are two options: you can review the open pull request and merge it as soon as you are confident that the change is safe, or close that pull request and trigger a new security update pull request. For more information, see "[Triggering a {% data variables.product.prodname_dependabot %} pull request manually](#triggering-a-dependabot-pull-request-manually)."
 
-### {% data variables.product.prodname_dependabot %} 在更新过程中超时
+### {% data variables.product.prodname_dependabot %} timed out during its update
 
-{% data variables.product.prodname_dependabot %} 评估所需更新和准备拉取请求所用的时间超过了允许的最大时间。 此错误通常只出现在具有许多清单文件的大型存储库中，例如具有数百个 package.json 文件的 npm 或 yarn 单存储库项目。 对 Composer 生态系统的更新也需要较长的时间来评估，可能会超时。
+{% data variables.product.prodname_dependabot %} took longer than the maximum time allowed to assess the update required and prepare a pull request. This error is usually seen only for large repositories with many manifest files, for example, npm or yarn monorepo projects with hundreds of *package.json* files. Updates to the Composer ecosystem also take longer to assess and may time out.
 
-此错误难以解决。 如果版本更新超时，可以使用 `allow` 参数来指定更新最重要的依赖项，或者使用 `ignore` 参数从更新中排除某些依赖项。 更新配置可能使 {% data variables.product.prodname_dependabot %} 能够在规定时间内检查版本更新并生成请求。
+This error is difficult to address. If a version update times out, you could specify the most important dependencies to update using the `allow` parameter or, alternatively, use the `ignore` parameter to exclude some dependencies from updates. Updating your configuration might allow {% data variables.product.prodname_dependabot %} to review the version update and generate the pull request in the time available.
 
-如果安全更新超时，您可以通过保持依赖项更新（例如，启用版本更新）来减少更新需要。 有关详细信息，请参阅“[配置 {% data variables.product.prodname_dependabot %} 版本更新](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/enabling-and-disabling-dependabot-version-updates)”。
+If a security update times out, you can reduce the chances of this happening by keeping the dependencies updated, for example, by enabling version updates. For more information, see "[Configuring {% data variables.product.prodname_dependabot %} version updates](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/enabling-and-disabling-dependabot-version-updates)."
 
-### {% data variables.product.prodname_dependabot %} 无法再打开拉取请求
+### {% data variables.product.prodname_dependabot %} cannot open any more pull requests
 
-{% data variables.product.prodname_dependabot %} 生成的打开拉取请求数量存在限制。 如果达到此限制，将无法打开新的拉取请求，并报告此错误。 解决此错误的最佳方法是审查并合并一些打开的拉取请求。
+There's a limit on the number of open pull requests {% data variables.product.prodname_dependabot %} will generate. When this limit is reached, no new pull requests are opened and this error is reported. The best way to resolve this error is to review and merge some of the open pull requests.
 
-安全性和版本更新拉取请求有各自的限制，因此打开版本更新拉取请求不会阻止安全更新拉取请求的创建。 安全更新拉取请求的限制是 10。 默认情况下，版本更新的限制为 5，但你可以使用配置文件中的 `open-pull-requests-limit` 参数来更改它。 有关详细信息，请参阅“[dependabot.yml 文件的配置选项](/github/administering-a-repository/configuration-options-for-dependency-updates#open-pull-requests-limit)”。
+There are separate limits for security and version update pull requests, so that open version update pull requests cannot block the creation of a security update pull request. The limit for security update pull requests is 10. By default, the limit for version updates is 5 but you can change this using the `open-pull-requests-limit` parameter in the configuration file. For more information, see "[Configuration options for the dependabot.yml file](/github/administering-a-repository/configuration-options-for-dependency-updates#open-pull-requests-limit)."
 
-解决此错误的最佳方法是合并或关闭一些现有拉取请求，然后手动触发新的拉取请求。 有关详细信息，请参阅“[手动触发 {% data variables.product.prodname_dependabot %} 拉取请求](#triggering-a-dependabot-pull-request-manually)”。
+The best way to resolve this error is to merge or close some of the existing pull requests and trigger a new pull request manually. For more information, see "[Triggering a {% data variables.product.prodname_dependabot %} pull request manually](#triggering-a-dependabot-pull-request-manually)."
 
-### {% data variables.product.prodname_dependabot %} 无法解析或访问您的依赖项
+### {% data variables.product.prodname_dependabot %} can't resolve or access your dependencies
 
-如果 {% data variables.product.prodname_dependabot %} 尝试检查是否需要更新仓库中的依赖项引用，但无法访问一个或多个依赖项文件，则操作将失败，并返回错误消息“{% data variables.product.prodname_dependabot %} can't resolve your LANGUAGE dependency files（无法解析语言依赖项文件）”。 API 错误类型为 `git_dependencies_not_reachable`
+If {% data variables.product.prodname_dependabot %} attempts to check whether dependency references need to be updated in a repository, but can't access one or more of the referenced files, the operation will fail with the error message "{% data variables.product.prodname_dependabot %} can't resolve your LANGUAGE dependency files." The API error type is `git_dependencies_not_reachable`.
 
-同样，如果 {% data variables.product.prodname_dependabot %} 不能访问依赖项所在的私有包注册表，则会产生以下错误之一：
+Similarly, if {% data variables.product.prodname_dependabot %} can't access a private package registry in which a dependency is located, one of the following errors is generated:
 
-*   “Dependabot 无法访问专用包注册表中的依赖项”<br>
-   （API 错误类型：`private_source_not_reachable`）
-*   “Dependabot 无法对专用包注册表进行身份验证”<br>
-   （API 错误类型：`private_source_authentication_failure`）
-*   “Dependabot 在等待专用包注册表时超时”<br>
-   （API 错误类型：`private_source_timed_out`）
-*   “Dependabot 无法验证专用包注册表的证书”<br>
-   （API 错误类型：`private_source_certificate_failure`）
+*	"Dependabot can't reach a dependency in a private package registry"<br>
+   (API error type: `private_source_not_reachable`)
+*	"Dependabot can't authenticate to a private package registry"<br>
+   (API error type:`private_source_authentication_failure`)
+*	"Dependabot timed out while waiting for a private package registry"<br>
+   (API error type:`private_source_timed_out`)
+*	"Dependabot couldn't validate the certificate for a private package registry"<br>
+   (API error type:`private_source_certificate_failure`)
 
-要让 {% data variables.product.prodname_dependabot %} 成功更新依赖项引用，请确保所有引用依赖项都托管在可访问的位置。 
+To allow {% data variables.product.prodname_dependabot %} to update the dependency references successfully, make sure that all of the referenced dependencies are hosted at accessible locations. 
 
-仅限版本更新。 {% data reusables.dependabot.private-dependencies-note %} 此外，{% data variables.product.prodname_dependabot %} 不支持所有包管理器的 {% data variables.product.prodname_dotcom %} 私有依赖项。 有关详细信息，请参阅“[关于 Dependabot 版本更新](/github/administering-a-repository/about-dependabot-version-updates#supported-repositories-and-ecosystems)”。
+**Version updates only.** {% data reusables.dependabot.private-dependencies-note %} Additionally, {% data variables.product.prodname_dependabot %} doesn't support private {% data variables.product.prodname_dotcom %} dependencies for all package managers. For more information, see "[About Dependabot version updates](/github/administering-a-repository/about-dependabot-version-updates#supported-repositories-and-ecosystems)."
 
-## 手动触发 {% data variables.product.prodname_dependabot %} 拉取请求
+## Triggering a {% data variables.product.prodname_dependabot %} pull request manually
 
-如果取消阻止了 {% data variables.product.prodname_dependabot %}，您可以手动触发新的尝试来创建拉取请求。
+If you unblock {% data variables.product.prodname_dependabot %}, you can manually trigger a fresh attempt to create a pull request.
 
-- 安全更新 - 显示 {% data variables.product.prodname_dependabot %} 警报，查看你修复的错误，然后单击“创建 {% data variables.product.prodname_dependabot %} 安全更新” 。
-- 版本更新 - 在存储库的“见解”选项卡上单击“依赖项关系图”，然后单击“Dependabot”选项卡   。单击“上次检查时间之前”，查看上次检查版本更新期间 {% data variables.product.prodname_dependabot %} 生成的日志文件。 单击“检查更新”。
+- **Security updates**—display the {% data variables.product.prodname_dependabot %} alert that shows the error you have fixed and click **Create {% data variables.product.prodname_dependabot %} security update**.
+- **Version updates**—on the **Insights** tab for the repository click **Dependency graph**, and then click the **Dependabot** tab. Click **Last checked *TIME* ago** to see the log file that {% data variables.product.prodname_dependabot %} generated during the last check for version updates. Click **Check for updates**.
 
-## 延伸阅读
+## Further reading
 
-- “[依赖项关系图疑难解答](/code-security/supply-chain-security/understanding-your-software-supply-chain/troubleshooting-the-dependency-graph)”。
-- “[漏洞依赖项检测疑难解答](/code-security/dependabot/working-with-dependabot/troubleshooting-the-detection-of-vulnerable-dependencies)”
+- "[Troubleshooting the dependency graph](/code-security/supply-chain-security/understanding-your-software-supply-chain/troubleshooting-the-dependency-graph)"
+- "[Troubleshooting the detection of vulnerable dependencies](/code-security/dependabot/working-with-dependabot/troubleshooting-the-detection-of-vulnerable-dependencies)"
diff --git a/translations/zh-CN/content/code-security/dependabot/working-with-dependabot/troubleshooting-the-detection-of-vulnerable-dependencies.md b/translations/zh-CN/content/code-security/dependabot/working-with-dependabot/troubleshooting-the-detection-of-vulnerable-dependencies.md
index 7974d9e6ee..725554270a 100644
--- a/translations/zh-CN/content/code-security/dependabot/working-with-dependabot/troubleshooting-the-detection-of-vulnerable-dependencies.md
+++ b/translations/zh-CN/content/code-security/dependabot/working-with-dependabot/troubleshooting-the-detection-of-vulnerable-dependencies.md
@@ -34,13 +34,13 @@ topics:
 *   {% data variables.product.prodname_advisory_database %} is one of the data sources that {% data variables.product.prodname_dotcom %} uses to identify vulnerable dependencies{% ifversion GH-advisory-db-supports-malware %} and malware{% endif %}. It's a free, curated database of security advisories for common package ecosystems on {% data variables.product.prodname_dotcom %}. It includes both data reported directly to {% data variables.product.prodname_dotcom %} from {% data variables.product.prodname_security_advisories %}, as well as official feeds and community sources. This data is reviewed and curated by {% data variables.product.prodname_dotcom %} to ensure that false or unactionable information is not shared with the development community. {% data reusables.security-advisory.link-browsing-advisory-db %}
 *   The dependency graph parses all known package manifest files in a user’s repository. For example, for npm it will parse the _package-lock.json_ file. It constructs a graph of all of the repository’s dependencies and public dependents. This happens when you enable the dependency graph and when anyone pushes to the default branch, and it includes commits that makes changes to a supported manifest format. For more information, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)" and "[Troubleshooting the dependency graph](/code-security/supply-chain-security/understanding-your-software-supply-chain/troubleshooting-the-dependency-graph)."
 *   {% data variables.product.prodname_dependabot %} scans any push, to the default branch, that contains a manifest file. When a new advisory is added, it scans all existing repositories and generates an alert for each repository that is affected. {% data variables.product.prodname_dependabot_alerts %} are aggregated at the repository level, rather than creating one alert per advisory. For more information, see "[About {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)."
-*   {% ifversion fpt or ghec or ghes > 3.2 %}{% data variables.product.prodname_dependabot_security_updates %} are triggered when you receive an alert about a vulnerable dependency in your repository. Where possible, {% data variables.product.prodname_dependabot %} creates a pull request in your repository to upgrade the vulnerable dependency to the minimum possible secure version needed to avoid the vulnerability. For more information, see "[About {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)" and "[Troubleshooting {% data variables.product.prodname_dependabot %} errors](/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors)."
+*   {% ifversion fpt or ghec or ghes %}{% data variables.product.prodname_dependabot_security_updates %} are triggered when you receive an alert about a vulnerable dependency in your repository. Where possible, {% data variables.product.prodname_dependabot %} creates a pull request in your repository to upgrade the vulnerable dependency to the minimum possible secure version needed to avoid the vulnerability. For more information, see "[About {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)" and "[Troubleshooting {% data variables.product.prodname_dependabot %} errors](/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors)."
   
     {% endif %}{% data variables.product.prodname_dependabot %} doesn't scan repositories on a schedule, but rather when something changes. For example, a scan is triggered when a new dependency is added ({% data variables.product.prodname_dotcom %} checks for this on every push), or when a new advisory is added to the database{% ifversion ghes or ghae %} and synchronized to {% data variables.location.product_location %}{% endif %}. For more information, see "[About {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies#detection-of-insecure-dependencies)."
 
 ## Do {% data variables.product.prodname_dependabot_alerts %} only relate to insecure dependencies in manifests and lockfiles?
 
-{% data variables.product.prodname_dependabot_alerts %} advise you about dependencies you should update, including transitive dependencies, where the version can be determined from a manifest or a lockfile. {% ifversion fpt or ghec or ghes > 3.2 %}{% data variables.product.prodname_dependabot_security_updates %} only suggest a change where {% data variables.product.prodname_dependabot %} can directly "fix" the dependency, that is, when these are:
+{% data variables.product.prodname_dependabot_alerts %} advise you about dependencies you should update, including transitive dependencies, where the version can be determined from a manifest or a lockfile. {% ifversion fpt or ghec or ghes %}{% data variables.product.prodname_dependabot_security_updates %} only suggest a change where {% data variables.product.prodname_dependabot %} can directly "fix" the dependency, that is, when these are:
 * Direct dependencies explicitly declared in a manifest or lockfile
 * Transitive dependencies declared in a lockfile{% endif %}
 
@@ -84,7 +84,7 @@ The {% data variables.product.prodname_dependabot_alerts %} count in {% data var
 **Check**: If there is a discrepancy in the totals you are seeing, check that you are not comparing alert numbers with dependency numbers. Also check that you are viewing all alerts and not a subset of filtered alerts.
 {% endif %}
 
-{% ifversion fpt or ghec or ghes > 3.2 %}
+{% ifversion fpt or ghec or ghes %}
 ## Can Dependabot ignore specific dependencies?
 
 You can configure {% data variables.product.prodname_dependabot %} to ignore specific dependencies in the configuration file, which will prevent security and version updates for those dependencies. If you only wish to use security updates, you will need to override the default behavior with a configuration file. For more information, see "[Overriding the default behavior with a configuration file](/code-security/dependabot/dependabot-security-updates/configuring-dependabot-security-updates#overriding-the-default-behavior-with-a-configuration-file)" to prevent version updates from being activated. For information about ignoring dependencies, see "[`ignore`](/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#ignore)."
@@ -95,5 +95,5 @@ You can configure {% data variables.product.prodname_dependabot %} to ignore spe
 - "[About {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)"
 - "[Viewing and updating {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts)"
 - "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)"
-- "[Troubleshooting the dependency graph](/code-security/supply-chain-security/understanding-your-software-supply-chain/troubleshooting-the-dependency-graph)"{% ifversion fpt or ghec or ghes > 3.2 %}
+- "[Troubleshooting the dependency graph](/code-security/supply-chain-security/understanding-your-software-supply-chain/troubleshooting-the-dependency-graph)"{% ifversion fpt or ghec or ghes %}
 - "[Troubleshooting {% data variables.product.prodname_dependabot %} errors](/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors)"{% endif %}
diff --git a/translations/zh-CN/content/code-security/getting-started/adding-a-security-policy-to-your-repository.md b/translations/zh-CN/content/code-security/getting-started/adding-a-security-policy-to-your-repository.md
index 97d1cfae98..9c14fe91d4 100644
--- a/translations/zh-CN/content/code-security/getting-started/adding-a-security-policy-to-your-repository.md
+++ b/translations/zh-CN/content/code-security/getting-started/adding-a-security-policy-to-your-repository.md
@@ -1,6 +1,6 @@
 ---
-title: 将安全策略添加到存储库
-intro: 您可以为仓库添加安全政策，说明如何报告项目中的安全漏洞。
+title: Adding a security policy to your repository
+intro: You can give instructions for how to report a security vulnerability in your project by adding a security policy to your repository.
 redirect_from:
   - /articles/adding-a-security-policy-to-your-repository
   - /github/managing-security-vulnerabilities/adding-a-security-policy-to-your-repository
@@ -17,47 +17,49 @@ topics:
   - Repositories
   - Health
 shortTitle: Add a security policy
-ms.openlocfilehash: f081d6e6bd99f604e7e86bc094f76de9041adf4b
-ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
-ms.translationtype: HT
-ms.contentlocale: zh-CN
-ms.lasthandoff: 09/10/2022
-ms.locfileid: '145084382'
 ---
-## 关于安全政策
 
-要向人们提供报告项目中安全漏洞的说明，{% ifversion fpt or ghes or ghec %}可以将 _SECURITY.md_ 文件添加到存储库的根目录、`docs` 或 `.github` 文件夹。{% else %}可以将 _SECURITY.md_ 文件添加到存储库的根目录或 `docs` 文件夹。{% endif %}当有人在你的存储库中创建问题时，他们将会看到一个指向你的项目的安全策略的链接。
+## About security policies
+
+To give people instructions for reporting security vulnerabilities in your project,{% ifversion fpt or ghes or ghec %} you can add a _SECURITY.md_ file to your repository's root, `docs`, or `.github` folder.{% else %} you can add a _SECURITY.md_ file to your repository's root, or `docs` folder.{% endif %} When someone creates an issue in your repository, they will see a link to your project's security policy.
 
 {% ifversion not ghae %}
 <!-- no public repos in GHAE -->
-你可以为组织或个人帐户创建默认的安全政策。 有关详细信息，请参阅[创建默认社区运行状况文件](/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file)。
+You can create a default security policy for your organization or personal account. For more information, see "[Creating a default community health file](/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file)."
 {% endif %}
 
 {% tip %}
 
-提示：为帮助人们查找安全策略，可以从存储库中的其他位置（如 README 文件）链接到 SECURITY.md 文件。 有关详细信息，请参阅“[关于 README](/articles/about-readmes)”。
+**Tip:** To help people find your security policy, you can link to your _SECURITY.md_ file from other places in your repository, such as your README file. For more information, see "[About READMEs](/articles/about-readmes)."
 
 {% endtip %}
 
-{% ifversion fpt or ghec %} 当有人报告项目中的安全漏洞后，可以使用 {% data variables.product.prodname_security_advisories %} 披露、修复和发布关于该漏洞的信息。 有关 {% data variables.product.prodname_dotcom %} 中报告和披露漏洞的过程的详细信息，请参阅“[关于安全漏洞的协调披露](/code-security/security-advisories/about-coordinated-disclosure-of-security-vulnerabilities#about-reporting-and-disclosing-vulnerabilities-in-projects-on-github)”。 有关 {% data variables.product.prodname_security_advisories %} 的详细信息，请参阅“[关于 {% data variables.product.prodname_security_advisories %}](/github/managing-security-vulnerabilities/about-github-security-advisories)”。
+{% ifversion fpt or ghec %}
+After someone reports a security vulnerability in your project, you can use {% data variables.product.prodname_security_advisories %} to disclose, fix, and publish information about the vulnerability. For more information about the process of reporting and disclosing vulnerabilities in {% data variables.product.prodname_dotcom %}, see "[About coordinated disclosure of security vulnerabilities](/code-security/security-advisories/about-coordinated-disclosure-of-security-vulnerabilities#about-reporting-and-disclosing-vulnerabilities-in-projects-on-github)." For more information about repository security advisories, see "[About repository security advisories](/github/managing-security-vulnerabilities/about-github-security-advisories)."
 
-{% data reusables.repositories.github-security-lab %} {% endif %} {% ifversion ghes or ghae %}
+{% data reusables.repositories.github-security-lab %}
+{% endif %}
+{% ifversion ghes or ghae %}
 <!-- alternative to the content about GitHub Security Advisories in the dotcom article -->
-通过创建明确的安全报告说明，用户可以轻松地使用您喜欢的通信通道报告仓库中发现的任何安全漏洞。
+By making security reporting instructions clearly available, you make it easy for your users to report any security vulnerabilities they find in your repository using your preferred communication channel.
 {% endif %}
 
-## 将安全策略添加到存储库
+## Adding a security policy to your repository
 
-{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %}
-3. 在左边栏中，单击“安全策略”。
-  ![“安全策略”选项卡](/assets/images/help/security/security-policy-tab.png)
-4. 单击“开始设置”。
-  ![“开始设置”按钮](/assets/images/help/security/start-setup-security-policy-button.png)
-5. 在新的 SECURITY.md 文件中，添加关于项目受支持版本以及如何报告漏洞的信息。
-{% data reusables.files.write_commit_message %} {% data reusables.files.choose-commit-email %} {% data reusables.files.choose_commit_branch %} {% data reusables.files.propose_file_change %}
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.sidebar-security %}
+3. In the left sidebar, click **Security policy**.
+  ![Security policy tab](/assets/images/help/security/security-policy-tab.png)
+4. Click **Start setup**.
+  ![Start setup button](/assets/images/help/security/start-setup-security-policy-button.png)
+5. In the new _SECURITY.md_ file, add information about supported versions of your project and how to report a vulnerability.
+{% data reusables.files.write_commit_message %}
+{% data reusables.files.choose-commit-email %}
+{% data reusables.files.choose_commit_branch %}
+{% data reusables.files.propose_file_change %}
 
-## 延伸阅读
+## Further reading
 
-- [保护存储库](/code-security/getting-started/securing-your-repository){% ifversion not ghae %}
-- [设置项目的健康贡献](/communities/setting-up-your-project-for-healthy-contributions){% endif %}{% ifversion fpt or ghec %}
+- "[Securing your repository](/code-security/getting-started/securing-your-repository)"{% ifversion not ghae %}
+- "[Setting up your project for healthy contributions](/communities/setting-up-your-project-for-healthy-contributions)"{% endif %}{% ifversion fpt or ghec %}
 - [{% data variables.product.prodname_security %}]({% data variables.product.prodname_security_link %}){% endif %}
diff --git a/translations/zh-CN/content/code-security/getting-started/github-security-features.md b/translations/zh-CN/content/code-security/getting-started/github-security-features.md
index 5e7ed85861..081272149c 100644
--- a/translations/zh-CN/content/code-security/getting-started/github-security-features.md
+++ b/translations/zh-CN/content/code-security/getting-started/github-security-features.md
@@ -28,10 +28,10 @@ Make it easy for your users to confidentially report security vulnerabilities th
 {% ifversion fpt or ghec %}
 ### Security advisories
 
-Privately discuss and fix security vulnerabilities in your repository's code. You can then publish a security advisory to alert your community to the vulnerability and encourage community members to upgrade. For more information, see "[About {% data variables.product.prodname_security_advisories %}](/github/managing-security-vulnerabilities/about-github-security-advisories)."
+Privately discuss and fix security vulnerabilities in your repository's code. You can then publish a security advisory to alert your community to the vulnerability and encourage community members to upgrade. For more information, see "[About repository security advisories](/github/managing-security-vulnerabilities/about-github-security-advisories)."
 
 {% endif %}
-{% ifversion fpt or ghec or ghes > 3.2 %}
+{% ifversion fpt or ghec or ghes %}
 
 ### {% data variables.product.prodname_dependabot_alerts %} and security updates
 
@@ -39,7 +39,7 @@ View alerts about dependencies that are known to contain security vulnerabilitie
 and "[About {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)."
 {% endif %}
 
-{% ifversion ghes < 3.3 or ghae %}
+{% ifversion ghae %}
 ### {% data variables.product.prodname_dependabot_alerts %}
 
 {% data reusables.dependabot.dependabot-alerts-beta %}
@@ -47,7 +47,7 @@ and "[About {% data variables.product.prodname_dependabot_security_updates %}](/
 View alerts about dependencies that are known to contain security vulnerabilities, and manage these alerts. For more information, see "[About {% data variables.product.prodname_dependabot_alerts %}](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)."
 {% endif %}
 
-{% ifversion fpt or ghec or ghes > 3.2 %}
+{% ifversion fpt or ghec or ghes %}
 ### {% data variables.product.prodname_dependabot %} version updates
 
 Use {% data variables.product.prodname_dependabot %} to automatically raise pull requests to keep your dependencies up-to-date. This helps reduce your exposure to older versions of dependencies. Using newer versions makes it easier to apply patches if security vulnerabilities are discovered, and also makes it easier for {% data variables.product.prodname_dependabot_security_updates %} to successfully raise pull requests to upgrade vulnerable dependencies. For more information, see "[About {% data variables.product.prodname_dependabot_version_updates %}](/github/administering-a-repository/about-dependabot-version-updates)."
diff --git a/translations/zh-CN/content/code-security/getting-started/securing-your-organization.md b/translations/zh-CN/content/code-security/getting-started/securing-your-organization.md
index e00a81e612..63cff8ac9b 100644
--- a/translations/zh-CN/content/code-security/getting-started/securing-your-organization.md
+++ b/translations/zh-CN/content/code-security/getting-started/securing-your-organization.md
@@ -56,7 +56,7 @@ Dependency review is an {% data variables.product.prodname_advanced_security %}
 {% 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.location.product_location %} and you enable {% data variables.product.prodname_advanced_security %} for the organization (see below).{% endif %}
 
-{% ifversion fpt or ghec or ghes > 3.2 %}
+{% ifversion fpt or ghec or ghes %}
 ## Managing {% data variables.product.prodname_dependabot_security_updates %}
 
 For any repository that uses {% data variables.product.prodname_dependabot_alerts %}, you can enable {% data variables.product.prodname_dependabot_security_updates %} to raise pull requests with security updates when vulnerabilities are detected. You can also enable or disable {% data variables.product.prodname_dependabot_security_updates %} for all repositories across your organization.
@@ -123,9 +123,9 @@ For more information, see "[Managing security and analysis settings for your org
 {% 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
-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 {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts),"{% 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)."
+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 {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts),"{% endif %} {% ifversion fpt or ghec or ghes %}"[Managing pull requests for dependency updates](/code-security/supply-chain-security/managing-pull-requests-for-dependency-updates)," {% endif %}"[Managing {% data variables.product.prodname_code_scanning %} for your repository](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository)," and "[Managing alerts from {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/managing-alerts-from-secret-scanning)."
 
-{% ifversion fpt or ghec %}If you have a security vulnerability, you can create a security advisory to privately discuss and fix the vulnerability. For more information, see "[About {% data variables.product.prodname_security_advisories %}](/code-security/security-advisories/about-github-security-advisories)" and "[Creating a security advisory](/code-security/security-advisories/creating-a-security-advisory)."
+{% 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 repository security advisories](/code-security/security-advisories/about-github-security-advisories)" and "[Creating a security advisory](/code-security/security-advisories/creating-a-security-advisory)."
 {% endif %}
 
 {% ifversion ghes or ghec or ghae %}You{% elsif fpt %}Organizations that use {% data variables.product.prodname_ghe_cloud %}{% endif %} can view, filter, and sort security alerts for repositories owned by {% ifversion ghes or ghec or ghae %}your{% elsif fpt %}their{% endif %} organization in the security overview. For more information, see{% ifversion ghes or ghec or ghae %} "[About the security overview](/code-security/security-overview/about-the-security-overview)."{% elsif fpt %} "[About the security overview](/enterprise-cloud@latest/code-security/security-overview/about-the-security-overview)" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% endif %}
diff --git a/translations/zh-CN/content/code-security/getting-started/securing-your-repository.md b/translations/zh-CN/content/code-security/getting-started/securing-your-repository.md
index 919f1b2fdd..3e84f7c163 100644
--- a/translations/zh-CN/content/code-security/getting-started/securing-your-repository.md
+++ b/translations/zh-CN/content/code-security/getting-started/securing-your-repository.md
@@ -86,8 +86,7 @@ Dependency review is a {% data variables.product.prodname_GH_advanced_security %
 
 {% endif %}
 
-
-{% ifversion fpt or ghec or ghes > 3.2 %}
+{% ifversion fpt or ghec or ghes %}
 
 ## Managing {% data variables.product.prodname_dependabot_security_updates %}
 
@@ -132,7 +131,7 @@ You can set up {% data variables.product.prodname_code_scanning %} to automatica
 {% 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 {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts),"{% 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)."
+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 {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts),"{% endif %} {% ifversion fpt or ghec or ghes %}"[Managing pull requests for dependency updates](/code-security/supply-chain-security/managing-pull-requests-for-dependency-updates)," {% endif %}"[Managing {% data variables.product.prodname_code_scanning %} for your repository](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository)," and "[Managing alerts from {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/managing-alerts-from-secret-scanning)."
 
-{% ifversion fpt or ghec %}If you have a security vulnerability, you can create a security advisory to privately discuss and fix the vulnerability. For more information, see "[About {% data variables.product.prodname_security_advisories %}](/code-security/security-advisories/about-github-security-advisories)" and "[Creating a security advisory](/code-security/security-advisories/creating-a-security-advisory)."
+{% 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 repository 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/zh-CN/content/code-security/index.md b/translations/zh-CN/content/code-security/index.md
index 86c2e3d488..e9d02c2953 100644
--- a/translations/zh-CN/content/code-security/index.md
+++ b/translations/zh-CN/content/code-security/index.md
@@ -1,7 +1,7 @@
 ---
-title: 代码安全
+title: Code security
 shortTitle: Code security
-intro: '在你的 {% data variables.product.prodname_dotcom %} 工作流中建立安全与功能，以使你的代码库中不含秘密和漏洞{% ifversion not ghae %}，并维护你的软件供应链{% endif %}。'
+intro: 'Build security into your {% data variables.product.prodname_dotcom %} workflow with features to keep secrets and vulnerabilities out of your codebase{% ifversion not ghae %}, and to maintain your software supply chain{% endif %}.'
 introLinks:
   overview: /code-security/getting-started/github-security-features
 featuredLinks:
@@ -53,16 +53,10 @@ children:
   - /adopting-github-advanced-security-at-scale
   - /secret-scanning
   - /code-scanning
-  - /repository-security-advisories
+  - /security-advisories
   - /supply-chain-security
   - /dependabot
   - /security-overview
   - /guides
-ms.openlocfilehash: 90d3ad046a6531849edd8e783db265866f118d90
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
-ms.translationtype: HT
-ms.contentlocale: zh-CN
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147145237'
 ---
 
diff --git a/translations/zh-CN/content/code-security/repository-security-advisories/about-coordinated-disclosure-of-security-vulnerabilities.md b/translations/zh-CN/content/code-security/repository-security-advisories/about-coordinated-disclosure-of-security-vulnerabilities.md
deleted file mode 100644
index fcb65554af..0000000000
--- a/translations/zh-CN/content/code-security/repository-security-advisories/about-coordinated-disclosure-of-security-vulnerabilities.md
+++ /dev/null
@@ -1,76 +0,0 @@
----
-title: 关于安全漏洞的协调披露
-intro: 漏洞披露是安全报告者与仓库维护者之间的协调工作。
-redirect_from:
-  - /code-security/security-advisories/about-coordinated-disclosure-of-security-vulnerabilities
-miniTocMaxHeadingLevel: 3
-versions:
-  fpt: '*'
-  ghec: '*'
-type: overview
-topics:
-  - Security advisories
-  - Vulnerabilities
-shortTitle: Coordinated disclosure
-ms.openlocfilehash: a5d4445525b46536cbfd3301cccb78140589de22
-ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
-ms.translationtype: HT
-ms.contentlocale: zh-CN
-ms.lasthandoff: 09/11/2022
-ms.locfileid: '145084365'
----
-## 关于披露行业漏洞
-
-{% data reusables.security-advisory.disclosing-vulnerabilities %}
-
-漏洞的初始报告是私下发布的，并且只有在维护者确认问题后才会公布全部详细信息，最好提供补救或修补程序，有时会延迟，以便有更多的时间安装修补程序。 有关详细信息，请参阅 OWASP 备忘单系列网站上的“[关于漏洞披露的 OWASP 备忘单系列](https://cheatsheetseries.owasp.org/cheatsheets/Vulnerability_Disclosure_Cheat_Sheet.html#commercial-and-open-source-software)”。
-
-### 漏洞报告者的最佳实践
-
-私下向维护者报告漏洞是一项良好的做法。 如果可能，作为漏洞报告者，我们建议您避免：
-- 公开披露漏洞而不给维护者补救的机会。
-- 绕过维护者。
-- 在代码的修复版可用之前披露漏洞。
-- 在没有公共奖励方案的情况下，报告某个问题时期望得到补偿。
-
-漏洞报告者如果已尝试联系维护者但未收到回复，或与已联系他们但被要求等待很久才能披露，则在一段时间后公开披露漏洞是可以接受的。 
-
-我们建议漏洞报告者在报告过程中明确说明其披露政策的条款。 即使漏洞报告者不遵守严格的政策，最好在预期漏洞披露的时间表上对维护者设定明确的期望。 有关披露策略的示例，请参阅 GitHub 安全实验室网站上的“[安全实验室披露策略](https://securitylab.github.com/advisories#policy)”。
-
-### 维护者最佳实践
-
-作为维护者，最佳做法是明确说明您想如何和在何处收到关于漏洞的报告。 如果此信息不可明确，但漏洞报告者不知道如何联系您，可能寻求从 git 提交历史记录中提取开发人员电子邮件地址，以尝试找到适当的安全联系人。 这可能导致摩擦、丢失报告或发布未解决的报告。
-
-维护者应及时披露漏洞。 如果您的仓库存在安全漏洞，我们建议您：
-- 在响应和披露中，将漏洞视为安全问题，而不是简单的错误。 例如，您需要明确提及问题在发布说明中是一个安全漏洞。
-- 即使没有即时的调查资源，也应尽快确认收到漏洞报告。 这传递了这样一个信息：您可以快速响应并采取行动，并为您与漏洞报告者之间的其余互动设定了积极的基调。
-- 当您验证报告的影响和真实性时，请让漏洞报告者参与。 漏洞报告者可能已经花时间考虑了各种情景中的漏洞，其中一些情况您自己可能都没有考虑过。
-- 以你认为合适的方式解决这个问题，认真考虑漏洞报告者提出的任何关切和建议。 通常，漏洞报告者会了解没有安全研究背景时容易错过的某些角落案例和补救旁路。
-- 始终将漏洞的发现归功于漏洞报告者。
-- 目标是尽快发布修复。
-- 确保您在披露漏洞时让更广泛的生态系统意识到问题及其补救措施。 在项目当前开发分支中修复已识别的安全问题，但提交或后续版本未明确标记为安全修复或发布的情况并不少见。 这可能给下游消费者造成问题。
-
-发布安全漏洞的详细信息不会使维护者看起来很糟糕。 安全漏洞在软件中随处可见。用户会信任那些在其守则中明确制定了安全漏洞披露程序的维护者。
-
-## 关于在 {% data variables.product.prodname_dotcom %} 上报告和披露项目中的漏洞
-
-在 {% data variables.product.prodname_dotcom_the_website %} 上报告和披露项目漏洞的流程如下：
-
- 如果您是要报告漏洞的漏洞报告者（例如安全研究人员），请先检查相关仓库是否有安全策略。 有关详细信息，请参阅“[关于安全策略](/code-security/getting-started/adding-a-security-policy-to-your-repository#about-security-policies)”。 如果有的话，请先了解该流程，然后再联系该仓库的安全团队。 
- 
- 如果没有安全策略，与维护者建立私人通信手段的最有效办法是制造一个要求优先安全联系的问题。 值得注意的是，这个问题将立即公开可见，所以它不应该包括任何有关漏洞的信息。 建立通信后，您可以建议维护者制定安全策略以供将来使用。
-
-{% note %}
-
-注意：如果我们收到 npm 包中的恶意软件报告，我们会尝试私下与你联系（仅适用于 npm）。 如果您不及时解决问题，我们将予以披露。 有关详细信息，请参阅 npm Docs 网站上的“[报告 npm 包中的恶意软件](https://docs.npmjs.com/reporting-malware-in-an-npm-package)”。
-
-{% endnote %}
-
- 如果您在 {% data variables.product.prodname_dotcom_the_website %} 中发现了安全漏洞，请通过我们协调的披露流程报告该漏洞。 有关详细信息，请参阅“[{% data variables.product.prodname_dotcom %}  安全 Bug 赏金](https://bounty.github.com/)”网站。
-
- 如果您是维护者， 您可以在管道开始时通过为您的仓库设置安全策略来掌控这一过程，或者以其他方式使安全报告说明清楚可用，例如在项目的 README 文件中。 有关添加安全策略的信息，请参阅“[关于安全策略](/code-security/getting-started/adding-a-security-policy-to-your-repository#about-security-policies)”。 如果没有安全策略，漏洞报告者可能会尝试向您发送电子邮件或以其他方式私下与您联系。 或者，有人可能会开一个（公共）议题讨论安全问题的细节。
-
- 作为维护者，要在您的代码中披露漏洞，请先在 {% data variables.product.prodname_dotcom %} 中软件包的仓库内创建安全通告。 {% data reusables.security-advisory.security-advisory-overview %}有关详细信息，请参阅“[关于存储库的 {% data variables.product.prodname_security_advisories %}](/code-security/repository-security-advisories/about-github-security-advisories-for-repositories)”。
-
-
- 要开始使用，请参阅“[创建存储库安全公告](/code-security/repository-security-advisories/creating-a-repository-security-advisory)”。
diff --git a/translations/zh-CN/content/code-security/repository-security-advisories/about-github-security-advisories-for-repositories.md b/translations/zh-CN/content/code-security/repository-security-advisories/about-github-security-advisories-for-repositories.md
deleted file mode 100644
index 38131ce26b..0000000000
--- a/translations/zh-CN/content/code-security/repository-security-advisories/about-github-security-advisories-for-repositories.md
+++ /dev/null
@@ -1,66 +0,0 @@
----
-title: 关于存储库的 GitHub 安全公告
-intro: '您可以使用 {% data variables.product.prodname_security_advisories %} 来私下讨论、修复和发布有关仓库中安全漏洞的信息。'
-redirect_from:
-  - /articles/about-maintainer-security-advisories
-  - /github/managing-security-vulnerabilities/about-maintainer-security-advisories
-  - /github/managing-security-vulnerabilities/about-github-security-advisories
-  - /code-security/security-advisories/about-github-security-advisories
-versions:
-  fpt: '*'
-  ghec: '*'
-type: overview
-topics:
-  - Security advisories
-  - Vulnerabilities
-  - CVEs
-shortTitle: Repository security advisories
-ms.openlocfilehash: 5c8ad99a2bee30f52a185fa15421bc6b23429fbf
-ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
-ms.translationtype: HT
-ms.contentlocale: zh-CN
-ms.lasthandoff: 09/10/2022
-ms.locfileid: '145084364'
----
-{% data reusables.repositories.security-advisory-admin-permissions %}
-
-{% data reusables.security-advisory.security-researcher-cannot-create-advisory %}
-
-## 关于 {% data variables.product.prodname_security_advisories %}
-
-{% data reusables.security-advisory.disclosing-vulnerabilities %} 更多信息请参阅“[关于协调披露安全漏洞](/code-security/repository-security-advisories/about-coordinated-disclosure-of-security-vulnerabilities)”。
-
-{% data reusables.security-advisory.security-advisory-overview %}
-
-通过 {% data variables.product.prodname_security_advisories %}，您可以：
-
-1. 创建安全通告草稿，并使用草稿私下讨论漏洞对项目的影响。 有关详细信息，请参阅“[创建存储库安全公告](/code-security/repository-security-advisories/creating-a-repository-security-advisory)”。
-2. 在临时私有复刻中私下协作以修复漏洞。
-3. 在补丁发布后发布通告向社区提醒漏洞。 有关详细信息，请参阅“[发布存储库安全性公告](/code-security/repository-security-advisories/publishing-a-repository-security-advisory)”。
-
-{% data reusables.repositories.security-advisories-republishing %}
-
-您可以向为安全通告做出贡献的个人提供积分。 有关详细信息，请参阅“[编辑存储库安全性公告](/code-security/repository-security-advisories/editing-a-repository-security-advisory#about-credits-for-security-advisories)”。
-
-{% data reusables.repositories.security-guidelines %}
-
-如果您在仓库中创建了安全通告，安全通告将保留在您的仓库中。 我们在 [github.com/advantores](https://github.com/advisories) 上的 {% data variables.product.prodname_advisory_database %} 发布任何由依赖关系图支持的生态系统的安全公告。 任何人都可以提交对 {% data variables.product.prodname_advisory_database %} 中发布的公告的更改。 有关详细信息，请参阅“[在 {% data variables.product.prodname_advisory_database %} 中编辑安全公告](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/editing-security-advisories-in-the-github-advisory-database)”。
-
-如果安全通告是专门针对 npm 的，我们也会向 npm 安全通告发布该通告。 有关详细信息，请参阅 [npmjs.com/advisories](https://www.npmjs.com/advisories)。
-
-{% data reusables.repositories.github-security-lab %}
-
-## CVE 识别号
-
-{% data variables.product.prodname_security_advisories %} 基于通用漏洞披露 (CVE) 列表而构建。 在 {% data variables.product.prodname_dotcom %} 上的安全通告表是符合 CVE 描述格式的标准化表格。 
-
-{% data variables.product.prodname_dotcom %} 是 CVE 编号颁发机构 (CNA)，被授权分配 CVE 标识号。 有关详细信息，请参阅 CVE 网站上的[关于 CVE](https://www.cve.org/About/Overview) 和 [CVE 编号机构](https://www.cve.org/ProgramOrganization/CNAs)。
-
-在 {% data variables.product.prodname_dotcom %} 上为公共仓库创建安全通告时，您可以选择为安全漏洞提供现有的 CVE 标识号。 {% data reusables.repositories.request-security-advisory-cve-id %}
-
-在您发布了安全通告并且 {% data variables.product.prodname_dotcom %} 为漏洞分配 CVE 标识号后，{% data variables.product.prodname_dotcom %} 会将 CVE 发布到 MITRE 数据库。
-有关详细信息，请参阅“[发布存储库安全性公告](/code-security/repository-security-advisories/publishing-a-repository-security-advisory)”。
-
-## 对于发布的安全通告的 {% data variables.product.prodname_dependabot_alerts %}
-
-{% data reusables.repositories.github-reviews-security-advisories %}
diff --git a/translations/zh-CN/content/code-security/repository-security-advisories/adding-a-collaborator-to-a-repository-security-advisory.md b/translations/zh-CN/content/code-security/repository-security-advisories/adding-a-collaborator-to-a-repository-security-advisory.md
deleted file mode 100644
index c34e7c9224..0000000000
--- a/translations/zh-CN/content/code-security/repository-security-advisories/adding-a-collaborator-to-a-repository-security-advisory.md
+++ /dev/null
@@ -1,50 +0,0 @@
----
-title: 将协作者添加到存储库安全通告
-intro: 您可以添加其他用户或团队与您协作处理安全通告。
-redirect_from:
-  - /articles/adding-a-collaborator-to-a-maintainer-security-advisory
-  - /github/managing-security-vulnerabilities/adding-a-collaborator-to-a-maintainer-security-advisory
-  - /github/managing-security-vulnerabilities/adding-a-collaborator-to-a-security-advisory
-  - /code-security/security-advisories/adding-a-collaborator-to-a-security-advisory
-versions:
-  fpt: '*'
-  ghec: '*'
-type: how_to
-topics:
-  - Security advisories
-  - Vulnerabilities
-  - Collaboration
-shortTitle: Add collaborators
-ms.openlocfilehash: 6fa4062fab8e4ffc59724ceb0ba3b6b536871df9
-ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
-ms.translationtype: HT
-ms.contentlocale: zh-CN
-ms.lasthandoff: 09/10/2022
-ms.locfileid: '147877165'
----
-对安全通告具有管理员权限的人员可向安全通告添加协作者。
-
-{% data reusables.security-advisory.repository-level-advisory-note %}
-
-## 添加协作者到安全通告
-
-协作者对安全通告具有写入权限。 有关详细信息，请参阅[存储库安全通告的权限级别](/code-security/repository-security-advisories/permission-levels-for-repository-security-advisories)。
-
-{% note %}
-
-{% data reusables.repositories.security-advisory-collaborators-public-repositories %} 有关删除安全通告协作者的更多信息，请参阅[从存储库安全通告删除协作者](/code-security/repository-security-advisories/removing-a-collaborator-from-a-repository-security-advisory)。
-
-{% endnote %}
-
-{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %} {% data reusables.repositories.sidebar-advisories %}
-4. 在“Security Advisories（安全通告）”列表中，单击要向其添加协作者的安全通告。
-5. 在页面右侧的“Collaborators（协作者）”下，键入要添加到安全通告的用户或团队名称。
-  ![用于输入用户或团队名称的字段](/assets/images/help/security/add-collaborator-field.png)
-6. 单击“添加”。
-  ![“添加”按钮](/assets/images/help/security/security-advisory-add-collaborator-button.png)
-
-## 延伸阅读
-
-- [存储库安全通告的权限级别](/code-security/repository-security-advisories/permission-levels-for-repository-security-advisories)
-- [在临时专用分支中协作以解决存储库安全漏洞](/code-security/repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability)
-- [从存储库安全通告删除协作者](/code-security/repository-security-advisories/removing-a-collaborator-from-a-repository-security-advisory)。
diff --git a/translations/zh-CN/content/code-security/repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability.md b/translations/zh-CN/content/code-security/repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability.md
deleted file mode 100644
index ee4d7a6f98..0000000000
--- a/translations/zh-CN/content/code-security/repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability.md
+++ /dev/null
@@ -1,90 +0,0 @@
----
-title: 在临时专用分支中协作以解决存储库安全漏洞
-intro: 您可以创建临时私有复刻，以私下协作修复仓库中的安全漏洞。
-redirect_from:
-  - /articles/collaborating-in-a-temporary-private-fork-to-resolve-a-security-vulnerability
-  - /github/managing-security-vulnerabilities/collaborating-in-a-temporary-private-fork-to-resolve-a-security-vulnerability
-  - /code-security/security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-security-vulnerability
-versions:
-  fpt: '*'
-  ghec: '*'
-type: how_to
-topics:
-  - Security advisories
-  - Vulnerabilities
-  - Collaboration
-  - Forks
-shortTitle: Temporary private forks
-ms.openlocfilehash: c03892c3ad1bd7345a7a066c9a9564858db4b84d
-ms.sourcegitcommit: ac00e2afa6160341c5b258d73539869720b395a4
-ms.translationtype: HT
-ms.contentlocale: zh-CN
-ms.lasthandoff: 09/09/2022
-ms.locfileid: '147876029'
----
-{% data reusables.security-advisory.repository-level-advisory-note %}
-
-## 先决条件
-
-在临时私有复刻中进行协作之前，必须创建维护员通告草稿。 有关详细信息，请参阅“[创建存储库安全通告](/code-security/repository-security-advisories/creating-a-repository-security-advisory)”。
-
-## 创建临时私有复刻
-
-任何对安全通告有管理权限的人都可以创建临时私有复刻。
-
-为保证漏洞相关信息的安全，集成系统（包括 CI）无法访问临时私有复刻。
-
-{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %} {% data reusables.repositories.sidebar-advisories %}
-4. 在“Security Advisories（安全通告）”列表中，单击要在其中创建临时私有复刻的安全通告。
-  ![列表中的安全通告](/assets/images/help/security/security-advisory-in-list.png)
-5. 单击“新建临时专用分支”。
-  ![“新建临时专用分支”按钮](/assets/images/help/security/new-temporary-private-fork-button.png)
-
-## 将协作者添加到临时私有复刻
-
-对安全通告具有管理员权限的任何人都可以向安全通告添加其他协作者，而安全通告的协作者可以访问临时私有复刻。 有关详细信息，请参阅“[将协作者添加到存储库安全通告](/code-security/repository-security-advisories/adding-a-collaborator-to-a-repository-security-advisory)”。
-
-## 将更改添加到临时私有复刻
-
-任何对安全通告有写入权限的人都可以向临时私有复刻添加更改。
-
-{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %} {% data reusables.repositories.sidebar-advisories %}
-4. 在“Security Advisories（安全通告）”列表中，单击要向其添加更改的安全通告。
-  ![列表中的安全通告](/assets/images/help/security/security-advisory-in-list.png)
-5. 在 {% data variables.product.product_name %} 上或在本地添加更改：
-   - 若要在 {% data variables.product.product_name %} 上添加更改，请在“向此通告添加更改”下单击“临时专用分支”。 然后，创建新分支并编辑文件。 有关详细信息，请参阅“[在存储库中创建和删除分支](/articles/creating-and-deleting-branches-within-your-repository)”和“[编辑文件](/repositories/working-with-files/managing-files/editing-files)”。
-   - 要在本地添加更改，请按照“克隆并创建新分支”和“进行更改，然后推送”下的说明进行操作。
-   ![“向此通告添加更改”框](/assets/images/help/security/add-changes-to-this-advisory-box.png)
-
-## 从临时私有复刻创建拉取请求
-
-任何对安全通告有写入权限的人都可以从临时私有复刻创建拉取请求。
-
-{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %} {% data reusables.repositories.sidebar-advisories %}
-4. 在“Security Advisories（安全通告）”列表中，单击要在其中创建拉取请求的安全通告。
-  ![列表中的安全通告](/assets/images/help/security/security-advisory-in-list.png)
-5. 在分支名称的右侧，单击“比较和拉取请求”。
-  ![“比较和拉取请求”按钮](/assets/images/help/security/security-advisory-compare-and-pr.png) {% data reusables.repositories.pr-title-description %} {% data reusables.repositories.create-pull-request %}
-
-{% data reusables.repositories.merge-all-pulls-together %} 有关详细信息，请参阅“[合并安全通告中的更改](#merging-changes-in-a-security-advisory)”。
-
-## 合并安全通告中的更改
-
-对安全通告具有管理员权限的任何人都可合并安全通告中的更改。
-
-{% data reusables.repositories.merge-all-pulls-together %}
-
-在合并安全通告中的更改之前，临时私有复刻中每个打开的拉取请求必须为可合并状态。 不存在合并冲突，并且必须满足分支保护要求。 为保证漏洞相关信息的安全，不在临时私有复刻的拉取请求上运行状态检查。 有关详细信息，请参阅“[关于受保护的分支](/articles/about-protected-branches)”。
-
-{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %} {% data reusables.repositories.sidebar-advisories %}
-4. 在“Security Advisories（安全通告）”列表中，单击要合并其更改的安全通告。
-  ![列表中的安全通告](/assets/images/help/security/security-advisory-in-list.png)
-5. 若要合并临时专用分支中所有打开的拉取请求，请单击“合并拉取请求”。
-  ![“合并拉取请求”按钮](/assets/images/help/security/merge-pull-requests-button.png)
-
-合并安全通告中的更改后，您可以发布安全通告，以提醒您的社区有关项目早期版本中安全漏洞的信息。 有关详细信息，请参阅“[发布存储库安全通告](/code-security/repository-security-advisories/publishing-a-repository-security-advisory)”。
-
-## 延伸阅读
-
-- “[存储库安全通告的权限级别](/code-security/repository-security-advisories/permission-levels-for-repository-security-advisories)”
-- “[发布存储库安全通告](/code-security/repository-security-advisories/publishing-a-repository-security-advisory)”
diff --git a/translations/zh-CN/content/code-security/repository-security-advisories/creating-a-repository-security-advisory.md b/translations/zh-CN/content/code-security/repository-security-advisories/creating-a-repository-security-advisory.md
deleted file mode 100644
index e8e16abe8c..0000000000
--- a/translations/zh-CN/content/code-security/repository-security-advisories/creating-a-repository-security-advisory.md
+++ /dev/null
@@ -1,44 +0,0 @@
----
-title: 创建存储库安全公告
-intro: 您可以创建安全通告草稿，以私下讨论和修复开源项目中的安全漏洞。
-redirect_from:
-  - /articles/creating-a-maintainer-security-advisory
-  - /github/managing-security-vulnerabilities/creating-a-maintainer-security-advisory
-  - /github/managing-security-vulnerabilities/creating-a-security-advisory
-  - /code-security/security-advisories/creating-a-security-advisory
-versions:
-  fpt: '*'
-  ghec: '*'
-type: how_to
-topics:
-  - Security advisories
-  - Vulnerabilities
-shortTitle: Create repository advisories
-ms.openlocfilehash: d4b47f84b20873e97b18106448b768288fff3039
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
-ms.translationtype: HT
-ms.contentlocale: zh-CN
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '145099741'
----
-任何对仓库有管理员权限的人都可以创建安全通告。
-
-{% data reusables.security-advisory.security-researcher-cannot-create-advisory %}
-
-## 创建安全通知
-
-{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %} {% data reusables.repositories.sidebar-advisories %}
-4. 单击“新建安全公告草稿”。
-  ![“打开公告草稿”按钮](/assets/images/help/security/security-advisory-new-draft-security-advisory-button.png)
-5. 键入安全通告的标题。
-{% data reusables.repositories.security-advisory-edit-details %} {% data reusables.repositories.security-advisory-edit-severity %} {% data reusables.repositories.security-advisory-edit-cwe-cve %} {% data reusables.repositories.security-advisory-edit-description %}
-11. 单击“创建安全公告草稿”。
-  ![“创建安全公告”按钮](/assets/images/help/security/security-advisory-create-security-advisory-button.png)
-
-## 后续步骤
-
-- 评论安全通告草稿，与团队讨论漏洞。
-- 添加协作者到安全通告。 有关详细信息，请参阅“[将协作者添加到存储库安全公告](/code-security/repository-security-advisories/adding-a-collaborator-to-a-repository-security-advisory)”。
-- 在临时私有复刻中私下协作以修复漏洞。 有关详细信息，请参阅“[在临时专用分支中协作以解决存储库安全漏洞](/code-security/repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability)”。
-- 添加因对安全通告做出贡献而应获得积分的个人。 有关详细信息，请参阅“[编辑存储库安全公告](/code-security/repository-security-advisories/editing-a-repository-security-advisory#about-credits-for-security-advisories)”。
-- 发布安全通告以向社区提醒安全漏洞。 有关详细信息，请参阅“[发布存储库安全公告](/code-security/repository-security-advisories/publishing-a-repository-security-advisory)”。
diff --git a/translations/zh-CN/content/code-security/repository-security-advisories/editing-a-repository-security-advisory.md b/translations/zh-CN/content/code-security/repository-security-advisories/editing-a-repository-security-advisory.md
deleted file mode 100644
index 916fc277c0..0000000000
--- a/translations/zh-CN/content/code-security/repository-security-advisories/editing-a-repository-security-advisory.md
+++ /dev/null
@@ -1,48 +0,0 @@
----
-title: 编辑存储库安全通告
-intro: 如果需要更新详细信息或更正错误，可以编辑存储库安全公告的元数据和说明。
-redirect_from:
-  - /github/managing-security-vulnerabilities/editing-a-security-advisory
-  - /code-security/security-advisories/editing-a-security-advisory
-versions:
-  fpt: '*'
-  ghec: '*'
-type: how_to
-topics:
-  - Security advisories
-  - Vulnerabilities
-shortTitle: Edit repository advisories
-ms.openlocfilehash: 2ea2f588374d83be677589b4f3bf4e74a7fc6e91
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
-ms.translationtype: HT
-ms.contentlocale: zh-CN
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '145099739'
----
-对存储库安全通告具有管理员权限的人员可以编辑安全通告。
-
-{% data reusables.security-advisory.repository-level-advisory-note %}
-
-## 关于安全通告的积分
-
-您可以向帮助发现、报告或修复安全漏洞的人提供积分。 如果您向某人提供积分，他们可以选择接受或拒绝积分。
-
-如果某人接受积分，则其用户名将显示在安全通告的“Credits（积分）”部分。 拥有仓库读取权限的任何人都可以看到通告和接受其积分的人。
-
-如果您认为您应该获得安全通告积分，请联系通告的创建者并让他们编辑通告以包含您的贡献积分。 只有通告创建者才可计入您的功劳积分，因此请不要就安全通告的积分一事联系 GitHub 支持。
-
-## 编辑安全通告
-
-{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %} {% data reusables.repositories.sidebar-advisories %}
-4. 在“Security Advisories（安全通告）”列表中，单击您要编辑的安全通告。
-5. 在安全通告详细信息的右上角，单击 {% octicon "pencil" aria-label="The edit icon" %}。
-  ![安全通告的“编辑”按钮](/assets/images/help/security/security-advisory-edit-button.png) {% data reusables.repositories.security-advisory-edit-details %} {% data reusables.repositories.security-advisory-edit-severity %} {% data reusables.repositories.security-advisory-edit-cwe-cve %} {% data reusables.repositories.security-advisory-edit-description %}
-11. （可选）编辑安全通告的“Credits（积分）”。
-  ![安全公告的额度](/assets/images/help/security/security-advisory-credits.png)
-12. 单击“更新安全公告”。
-  ![“更新安全公告”按钮](/assets/images/help/security/update-advisory-button.png)
-13. “Credits（积分）”部分列出的人员将会收到邀请他们接受积分的电子邮件或 web 通知。 如果某人接受，则其用户名将在安全通告发布后公开可见。
-
-## 延伸阅读
-
-- [撤消存储库安全公告](/code-security/repository-security-advisories/withdrawing-a-repository-security-advisory)
diff --git a/translations/zh-CN/content/code-security/repository-security-advisories/index.md b/translations/zh-CN/content/code-security/repository-security-advisories/index.md
deleted file mode 100644
index 97a4f73515..0000000000
--- a/translations/zh-CN/content/code-security/repository-security-advisories/index.md
+++ /dev/null
@@ -1,36 +0,0 @@
----
-title: 管理项目中针对漏洞的存储库安全公告
-shortTitle: Repository security advisories
-intro: 使用存储库安全公告讨论、修正和披露存储库中的安全漏洞。
-redirect_from:
-  - /articles/managing-security-vulnerabilities-in-your-project
-  - /github/managing-security-vulnerabilities/managing-security-vulnerabilities-in-your-project
-  - /code-security/security-advisories
-versions:
-  fpt: '*'
-  ghec: '*'
-topics:
-  - Security advisories
-  - Vulnerabilities
-  - Repositories
-  - CVEs
-children:
-  - /about-coordinated-disclosure-of-security-vulnerabilities
-  - /about-github-security-advisories-for-repositories
-  - /permission-levels-for-repository-security-advisories
-  - /creating-a-repository-security-advisory
-  - /adding-a-collaborator-to-a-repository-security-advisory
-  - /removing-a-collaborator-from-a-repository-security-advisory
-  - /collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability
-  - /publishing-a-repository-security-advisory
-  - /editing-a-repository-security-advisory
-  - /withdrawing-a-repository-security-advisory
-  - /best-practices-for-writing-repository-security-advisories
-ms.openlocfilehash: 43efe7ceaf307da4a8a7c02c45f744a4967b05b0
-ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
-ms.translationtype: HT
-ms.contentlocale: zh-CN
-ms.lasthandoff: 09/10/2022
-ms.locfileid: '145099738'
----
-
diff --git a/translations/zh-CN/content/code-security/repository-security-advisories/permission-levels-for-repository-security-advisories.md b/translations/zh-CN/content/code-security/repository-security-advisories/permission-levels-for-repository-security-advisories.md
deleted file mode 100644
index 7989a14730..0000000000
--- a/translations/zh-CN/content/code-security/repository-security-advisories/permission-levels-for-repository-security-advisories.md
+++ /dev/null
@@ -1,50 +0,0 @@
----
-title: 存储库安全公告的权限级别
-intro: 你在存储库安全公告中可以执行的操作取决于你是公告的管理员还是对其有写入权限。
-redirect_from:
-  - /articles/permission-levels-for-maintainer-security-advisories
-  - /github/managing-security-vulnerabilities/permission-levels-for-maintainer-security-advisories
-  - /github/managing-security-vulnerabilities/permission-levels-for-security-advisories
-  - /code-security/security-advisories/permission-levels-for-security-advisories
-versions:
-  fpt: '*'
-  ghec: '*'
-type: reference
-topics:
-  - Security advisories
-  - Vulnerabilities
-  - Permissions
-shortTitle: Permission levels
-ms.openlocfilehash: 9c2ad0d30b98b79786df09a224766bd826cb84f6
-ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
-ms.translationtype: HT
-ms.contentlocale: zh-CN
-ms.lasthandoff: 09/10/2022
-ms.locfileid: '145099740'
----
-本文仅适用于存储库级别的安全公告。 任何人都可以在 [github.com/advisories](https://github.com/advisories) 上的 {% data variables.product.prodname_advisory_database %} 中提供全局安全公告内容。 对全局公告的编辑不会改变或影响公告在存储库中的显示方式。  有关详细信息，请参阅“[在 {% data variables.product.prodname_advisory_database %} 中编辑安全公告](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/editing-security-advisories-in-the-github-advisory-database)”。
-
-## 权限概述
-
-{% data reusables.repositories.security-advisory-admin-permissions %} 有关将协作者添加到安全公告的详细信息，请参阅“[将协作者添加到存储库安全公告](/code-security/repository-security-advisories/adding-a-collaborator-to-a-repository-security-advisory)”。
-
-操作 | 写入权限 | 管理员权限 |
------- | ----------------- | ----------------- |
-查看安全通告草稿 | X | X |
-将协作者添加到安全公告（请参阅“[将协作者添加到存储库安全公告](/code-security/repository-security-advisories/adding-a-collaborator-to-a-repository-security-advisory)”） | | X |
-编辑和删除安全通告中的任何评论 | X | X |
-在安全公告中创建临时专用分支（请参阅“[在临时专用分支中协作以解决存储库安全漏洞](/code-security/repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability)”） | | X |
-在安全公告中添加对临时专用分支的更改（请参阅“[在临时专用分支中协作以解决存储库安全漏洞](/code-security/repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability)”） | X | X |
-在临时专用分支中创建拉取请求（请参阅“[在临时专用分支中协作以解决存储库安全漏洞](/code-security/repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability)”） | X | X |
-合并安全公告中的更改（请参阅“[在临时专用分支中协作以解决存储库安全漏洞](/code-security/repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability)”） | | X |
-在安全公告中添加和编辑元数据（请参阅“[发布存储库安全公告](/code-security/repository-security-advisories/publishing-a-repository-security-advisory)”） | X | X |
-添加和删除安全公告的积分（请参阅“[编辑存储库安全公告](/code-security/repository-security-advisories/editing-a-repository-security-advisory)”） | X | X |
-关闭安全通告草稿 | | X |
-发布安全公告（请参阅“[发布存储库安全公告](/code-security/repository-security-advisories/publishing-a-repository-security-advisory)”） | | X |
-
-## 延伸阅读
-
-- [将协作者添加到存储库安全公告](/code-security/repository-security-advisories/adding-a-collaborator-to-a-repository-security-advisory)
-- [在临时专用分支中协作以解决存储库安全漏洞](/code-security/repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability)
-- [从存储库安全公告删除协作者](/code-security/repository-security-advisories/removing-a-collaborator-from-a-repository-security-advisory)
-- [撤消存储库安全公告](/code-security/repository-security-advisories/withdrawing-a-repository-security-advisory)
diff --git a/translations/zh-CN/content/code-security/repository-security-advisories/publishing-a-repository-security-advisory.md b/translations/zh-CN/content/code-security/repository-security-advisories/publishing-a-repository-security-advisory.md
deleted file mode 100644
index 854a6e5ce5..0000000000
--- a/translations/zh-CN/content/code-security/repository-security-advisories/publishing-a-repository-security-advisory.md
+++ /dev/null
@@ -1,101 +0,0 @@
----
-title: 发布存储库安全公告
-intro: 您可以发布安全通告，向社区提醒项目中的安全漏洞。
-redirect_from:
-  - /articles/publishing-a-maintainer-security-advisory
-  - /github/managing-security-vulnerabilities/publishing-a-maintainer-security-advisory
-  - /github/managing-security-vulnerabilities/publishing-a-security-advisory
-  - /code-security/security-advisories/publishing-a-security-advisory
-versions:
-  fpt: '*'
-  ghec: '*'
-type: how_to
-topics:
-  - Security advisories
-  - Vulnerabilities
-  - CVEs
-  - Repositories
-shortTitle: Publish repository advisories
-ms.openlocfilehash: f3e3bfdb6b44ec1c86bb903c66271b854f4fb041
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
-ms.translationtype: HT
-ms.contentlocale: zh-CN
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '145099737'
----
-<!--Marketing-LINK: From /features/security/software-supply-chain page "Publishing a security advisory".-->
-
-对安全通告具有管理员权限的任何人都可发布安全通告。
-
-{% data reusables.security-advisory.repository-level-advisory-note %}
-
-## 先决条件
-
-在发布安全通告或申请 CVE 标识号之前，必须创建安全通告草稿，并提供受安全漏洞影响的项目版本的相关信息。 有关详细信息，请参阅“[创建存储库安全公告](/code-security/repository-security-advisories/creating-a-repository-security-advisory)”。
-
-如果您已创建安全通告，但尚未提供有关安全漏洞影响的项目版本的详细信息，则可以编辑安全通告。 有关详细信息，请参阅“[编辑存储库安全公告](/code-security/repository-security-advisories/editing-a-repository-security-advisory)”。
-
-## 关于发布安全通告
-
-发布安全通告时，会通知您的社区关于该安全通告解决的安全漏洞。 发布安全通告使您的社区能够更轻松地更新包依赖项和研究安全漏洞的影响。
-
-{% data reusables.repositories.security-advisories-republishing %}
-
-在发布安全通告之前，您可以私下协作在临时私有复刻中修复漏洞。 有关详细信息，请参阅“[在临时专用分支中协作以解决存储库安全漏洞问题](/code-security/repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability)”。
-
-{% warning %}
-
-警告：只要可能，你都应该始终在发布安全公告之前向该公告添加修复版本。 否则，通告将在没有修复版本的情况下发布，并且 {% data variables.product.prodname_dependabot %} 将向您的用户提醒有关问题，而不需提供任何安全版本来更新。
-
-我们建议您在以下不同情况下采取以下步骤：
-
-- 如果修复版本即将可用，请尽可能等到修复版本准备好后再发布。
-- 如果修复版本正在开发中，但尚不可用，请在通告中提及，等发布后再编辑通告。
-- 如果您不打算修复问题，请在通告中明确说明，以免用户联系您询问何时进行修复。 在这种情况下，列入用户可用于缓解这一问题的步骤会有帮助。
-
-{% endwarning %}
-
-从公共仓库发布通告草稿时，每个人都可以看到：
-
-- 通告数据的当前版本。
-- 积分用户已接受的任何通告积分。
-  
-{% note %}
-
-注意：公众无权查看公告的编辑历史记录，只能看到已发布的版本。
-
-{% endnote %}
-
-发布安全通告后，安全通告的 URL 将与发布安全通告之前保持相同。 对仓库具有读取权限的任何人都能看到安全通告。 安全通告的协作者可以继续查看安全通告中过去的对话，包括完整的评论流，除非有管理员权限的人从安全通告删除该协作者。 
-
-如果需要更新或更正已发布的安全通告中的信息，可以编辑安全通告。 有关详细信息，请参阅“[编辑存储库安全公告](/code-security/repository-security-advisories/editing-a-repository-security-advisory)”。
-
-## 发布安全通告
-
-发布安全通告会删除该安全通告的临时私有复刻。
-
-{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %} {% data reusables.repositories.sidebar-advisories %}
-4. 在“Security Advisories（安全通告）”列表中，单击您要发布的安全通告。
-  ![列表中的安全公告](/assets/images/help/security/security-advisory-in-list.png)
-5. 单击页面底部的“发布公告”。
-  ![“发布公告”按钮](/assets/images/help/security/publish-advisory-button.png)
-  
-## 对于发布的安全通告的 {% data variables.product.prodname_dependabot_alerts %}
-
-{% data reusables.repositories.github-reviews-security-advisories %}
-
-## 申请 CVE 识别号（可选）
-
-{% data reusables.repositories.request-security-advisory-cve-id %} 有关详细信息，请参阅“[关于存储库的 {% data variables.product.prodname_security_advisories %}](/code-security/repository-security-advisories/about-github-security-advisories-for-repositories#cve-identification-numbers)”。
-
-{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %} {% data reusables.repositories.sidebar-advisories %}
-4. 在“Security Advisories（安全通告）”列表中，单击要为其申请 CVE 识别号的安全通告。
-  ![列表中的安全公告](/assets/images/help/security/security-advisory-in-list.png)
-5. 使用“发布公告”下拉菜单，然后单击“申请 CVE” 。
-  ![下拉列表中的“申请 CVE”](/assets/images/help/security/security-advisory-drop-down-request-cve.png)
-6. 单击“申请 CVE”。
-  ![“申请 CVE”按钮](/assets/images/help/security/security-advisory-request-cve-button.png)
-
-## 延伸阅读
-
-- [撤消存储库安全公告](/code-security/repository-security-advisories/withdrawing-a-repository-security-advisory)
diff --git a/translations/zh-CN/content/code-security/repository-security-advisories/removing-a-collaborator-from-a-repository-security-advisory.md b/translations/zh-CN/content/code-security/repository-security-advisories/removing-a-collaborator-from-a-repository-security-advisory.md
deleted file mode 100644
index a4be39e75b..0000000000
--- a/translations/zh-CN/content/code-security/repository-security-advisories/removing-a-collaborator-from-a-repository-security-advisory.md
+++ /dev/null
@@ -1,42 +0,0 @@
----
-title: 删除存储库安全公告中的协作者
-intro: 协作者从存储库安全公告中删除后，将失去对安全公告的讨论和元数据的读取和写入权限。
-redirect_from:
-  - /github/managing-security-vulnerabilities/removing-a-collaborator-from-a-security-advisory
-  - /code-security/security-advisories/removing-a-collaborator-from-a-security-advisory
-versions:
-  fpt: '*'
-  ghec: '*'
-type: how_to
-topics:
-  - Security advisories
-  - Vulnerabilities
-  - Collaboration
-shortTitle: Remove collaborators
-ms.openlocfilehash: ced0edd0614304c0d33ddd40dce3c6a24a9ffcfd
-ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
-ms.translationtype: HT
-ms.contentlocale: zh-CN
-ms.lasthandoff: 09/10/2022
-ms.locfileid: '145099732'
----
-对安全通告具有管理员权限的人员可从安全通告删除协作者。
-
-{% data reusables.security-advisory.repository-level-advisory-note %}
-
-## 从安全通告删除协作者
-
-{% data reusables.repositories.security-advisory-collaborators-public-repositories %}
-
-{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %} {% data reusables.repositories.sidebar-advisories %}
-4. 在“Security Advisories（安全通告）”列表中，单击要从中删除协作者的安全通告。
-  ![列表中的安全公告](/assets/images/help/security/security-advisory-in-list.png)
-5. 在页面右侧的“Collaborators（协作者）”下，键入要从安全通告删除的用户或团队名称。
-  ![安全公告协作者](/assets/images/help/security/security-advisory-collaborator.png)
-6. 在要移除的协作者旁边，单击“X”图标。
-  ![用于删除安全公告协作者的 X 图标](/assets/images/help/security/security-advisory-remove-collaborator-x.png)
-
-## 延伸阅读
-
-- [存储库安全公告的权限级别](/code-security/repository-security-advisories/permission-levels-for-repository-security-advisories)
-- [将协作者添加到存储库安全公告](/code-security/repository-security-advisories/adding-a-collaborator-to-a-repository-security-advisory)
diff --git a/translations/zh-CN/content/code-security/repository-security-advisories/withdrawing-a-repository-security-advisory.md b/translations/zh-CN/content/code-security/repository-security-advisories/withdrawing-a-repository-security-advisory.md
deleted file mode 100644
index fffe33bf89..0000000000
--- a/translations/zh-CN/content/code-security/repository-security-advisories/withdrawing-a-repository-security-advisory.md
+++ /dev/null
@@ -1,28 +0,0 @@
----
-title: 撤销存储库安全通告
-intro: 你可以撤销已发布的存储库安全公告。
-redirect_from:
-  - /github/managing-security-vulnerabilities/withdrawing-a-security-advisory
-  - /code-security/security-advisories/withdrawing-a-security-advisory
-versions:
-  fpt: '*'
-  ghec: '*'
-type: how_to
-topics:
-  - Security advisories
-  - Vulnerabilities
-shortTitle: Withdraw repository advisories
-ms.openlocfilehash: 1d85afddaadbd25c5b24ab945dac998b7842ae23
-ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
-ms.translationtype: HT
-ms.contentlocale: zh-CN
-ms.lasthandoff: 09/10/2022
-ms.locfileid: '145099724'
----
-{% data reusables.security-advisory.repository-level-advisory-note %}
-
-如果错误地发布了安全通告，可以联系 {% data variables.contact.contact_support %} 撤销。
-
-## 延伸阅读
-
-- “[编辑存储库安全通告](/code-security/repository-security-advisories/editing-a-repository-security-advisory)”
diff --git a/translations/zh-CN/content/code-security/secret-scanning/about-secret-scanning.md b/translations/zh-CN/content/code-security/secret-scanning/about-secret-scanning.md
index b9dce9457c..f1c959c882 100644
--- a/translations/zh-CN/content/code-security/secret-scanning/about-secret-scanning.md
+++ b/translations/zh-CN/content/code-security/secret-scanning/about-secret-scanning.md
@@ -110,6 +110,6 @@ monitor results from {% data variables.product.prodname_secret_scanning %} acros
 - "[Keeping your account and data secure](/github/authenticating-to-github/keeping-your-account-and-data-secure)"
 {%- ifversion fpt or ghec %}
 - "[Managing encrypted secrets for your codespaces](/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces)"{% endif %}
-{%- ifversion fpt or ghec or ghes > 3.2 %}
+{%- ifversion fpt or ghec or ghes %}
 - "[Managing encrypted secrets for Dependabot](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/managing-encrypted-secrets-for-dependabot)"{% endif %}
 - "[Encrypted secrets](/actions/security-guides/encrypted-secrets)"
diff --git a/translations/zh-CN/content/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning.md b/translations/zh-CN/content/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning.md
index 03bf9dd95a..3b0a2bf172 100644
--- a/translations/zh-CN/content/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning.md
+++ b/translations/zh-CN/content/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning.md
@@ -15,35 +15,12 @@ topics:
   - Secret scanning
 ---
 
-{% ifversion ghes < 3.3 %}
-{% note %}
-
-**Note:** Custom patterns for {% data variables.product.prodname_secret_scanning %} is currently in beta and is subject to change.
-
-{% endnote %}
-{% endif %}
 
 ## About custom patterns for {% data variables.product.prodname_secret_scanning %}
 
 You can define custom patterns to identify secrets that are not detected by the default patterns supported by {% data variables.product.prodname_secret_scanning %}. For example, you might have a secret pattern that is internal to your organization. For details of the supported secrets and service providers, see "[{% data variables.product.prodname_secret_scanning_caps %} patterns](/code-security/secret-scanning/secret-scanning-patterns)."
 
-You can define custom patterns for your enterprise, organization, or repository. {% data variables.product.prodname_secret_scanning_caps %} supports up to 
-{%- ifversion fpt or ghec or ghes > 3.3 or ghae > 3.3 %} 500 custom patterns for each organization or enterprise account, and up to 100 custom patterns per repository.
-{%- elsif ghes = 3.2 %} 20 custom patterns for each organization or enterprise account, and per repository.
-{%- else %} 100 custom patterns for each organization or enterprise account, and 20 per repository.
-{%- endif %}
-
-{% ifversion ghes < 3.3 %}
-{% note %}
-
-**Note:** During the beta, there are some limitations when using custom patterns for {% data variables.product.prodname_secret_scanning %}:
-
-* There is no dry-run functionality.
-* You cannot edit custom patterns after they're created. To change a pattern, you must delete it and recreate it.
-* There is no API for creating, editing, or deleting custom patterns. However, results for custom patterns are returned in the [secret scanning alerts API](/rest/reference/secret-scanning).
-
-{% endnote %}
-{% endif %}
+You can define custom patterns for your enterprise, organization, or repository. {% data variables.product.prodname_secret_scanning_caps %} supports up to 500 custom patterns for each organization or enterprise account, and up to 100 custom patterns per repository.
 
 ## Regular expression syntax for custom patterns
 
@@ -160,7 +137,7 @@ Before defining a custom pattern, you must ensure that you enable secret scannin
 1. Under "Code security and analysis", click **Security features**.{% else %}
 {% data reusables.enterprise-accounts.advanced-security-policies %}
 {% data reusables.enterprise-accounts.advanced-security-security-features %}{% endif %}
-1. Under "Secret scanning custom patterns", click {% ifversion ghes = 3.2 %}**New custom pattern**{% else %}**New pattern**{% endif %}.
+1. Under "Secret scanning custom patterns", click **New pattern**.
 {% data reusables.advanced-security.secret-scanning-add-custom-pattern-details %}
 {%- ifversion secret-scanning-custom-enterprise-36 or custom-pattern-dry-run-ga %}
 1. When you're ready to test your new custom pattern, to identify matches in the enterprise without creating alerts, click **Save and dry run**.
@@ -172,7 +149,6 @@ Before defining a custom pattern, you must ensure that you enable secret scannin
 
 After your pattern is created, {% data variables.product.prodname_secret_scanning %} scans for any secrets in repositories within your enterprise's organizations with {% data variables.product.prodname_GH_advanced_security %} enabled, including their entire Git history on all branches. Organization owners and repository administrators will be alerted to any secrets found, and can review the alert in the repository where the secret is found. For more information on viewing {% data variables.product.prodname_secret_scanning %} alerts, see "[Managing alerts from {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/managing-alerts-from-secret-scanning)."
 
-{% ifversion fpt or ghes > 3.2 or ghec or ghae %}
 ## Editing a custom pattern
 
 When you save a change to a custom pattern, this closes all the {% data variables.product.prodname_secret_scanning %} alerts that were created using the previous version of the pattern.
@@ -184,7 +160,6 @@ When you save a change to a custom pattern, this closes all the {% data variable
 3. When you're ready to test your edited custom pattern, to identify matches without creating alerts, click **Save and dry run**.
 {%- endif %}
 4. When you have reviewed and tested your changes, click **Save changes**.
-{% endif %}
 
 ## Removing a custom pattern
 
@@ -192,13 +167,8 @@ When you save a change to a custom pattern, this closes all the {% data variable
 
    * For a repository or organization, display the "Security & analysis" settings for the repository or organization where the custom pattern was created. For more information, see "[Defining a custom pattern for a repository](#defining-a-custom-pattern-for-a-repository)" or "[Defining a custom pattern for an organization](#defining-a-custom-pattern-for-an-organization)" above.
    * For an enterprise, under "Policies" display the "Advanced Security" area, and then click **Security features**.  For more information, see "[Defining a custom pattern for an enterprise account](#defining-a-custom-pattern-for-an-enterprise-account)" above.
-{%- ifversion ghec or ghes > 3.2 or ghae %}
 1. To the right of the custom pattern you want to remove, click {% octicon "trash" aria-label="The trash icon" %}.
 1. Review the confirmation, and select a method for dealing with any open alerts relating to the custom pattern.
 1. Click **Yes, delete this pattern**.
 
-   ![Confirming deletion of a custom {% data variables.product.prodname_secret_scanning %} pattern ](/assets/images/help/repository/secret-scanning-confirm-deletion-custom-pattern.png)
-{%- elsif ghes = 3.2 %}
-1. To the right of the custom pattern you want to remove, click **Remove**.
-1. Review the confirmation, and click **Remove custom pattern**.
-{%- endif %}
+   ![Confirming deletion of a custom {% data variables.product.prodname_secret_scanning %} pattern ](/assets/images/help/repository/secret-scanning-confirm-deletion-custom-pattern.png)
\ No newline at end of file
diff --git a/translations/zh-CN/content/code-security/secret-scanning/protecting-pushes-with-secret-scanning.md b/translations/zh-CN/content/code-security/secret-scanning/protecting-pushes-with-secret-scanning.md
index e7ef382b5d..78b23e2fe1 100644
--- a/translations/zh-CN/content/code-security/secret-scanning/protecting-pushes-with-secret-scanning.md
+++ b/translations/zh-CN/content/code-security/secret-scanning/protecting-pushes-with-secret-scanning.md
@@ -137,4 +137,4 @@ If you confirm a secret is real and that you intend to fix it later, you should
 
 1. Click **Allow secret**.
 
-{% endif %}
\ No newline at end of file
+{% endif %}
diff --git a/translations/zh-CN/content/code-security/security-overview/about-the-security-overview.md b/translations/zh-CN/content/code-security/security-overview/about-the-security-overview.md
index 69e55a8adc..c763b80753 100644
--- a/translations/zh-CN/content/code-security/security-overview/about-the-security-overview.md
+++ b/translations/zh-CN/content/code-security/security-overview/about-the-security-overview.md
@@ -67,17 +67,23 @@ The security overview displays active alerts raised by security features. If the
 
 At the organization-level, the security overview displays aggregate and repository-specific security information for repositories owned by your organization. You can filter information by security features at the organization-level.
 
+Organization owners and security managers for organizations have access to the organization-level security overview. {% ifversion ghec or ghes > 3.6 or ghae > 3.6 %}Organization members can access the organization-level security overview to view results for repositories where they have admin privileges or have been granted access to security alerts. For more information on managing security alert access, see "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)".{% endif %}
+
 {% ifversion ghec or ghes > 3.4 or ghae > 3.4 %}
 ### About the enterprise-level security overview
 At the enterprise-level, the security overview displays aggregate and repository-specific security information for your enterprise. You can view repositories owned by your enterprise that have security alerts, view all security alerts, or security feature-specific alerts from across your enterprise.
 
-Organization owners and security managers for organizations in your enterprise also have limited access to the enterprise-level security overview. They can only view repositories and alerts for the organizations that they have full access to.
+Organization owners and security managers for organizations in your enterprise have access to the enterprise-level security overview. They can view repositories and alerts for the organizations that they have full access to.
+
+Enterprise owners can only see alerts for organizations that they are an owner or a security manager of.{% ifversion ghec or ghes > 3.5 or ghae > 3.5 %} Enterprise owners can join an organization as an organization owner to see all of its alerts in the enterprise-level security overview. For more information, see "[Managing your role in an organization owned by your enterprise](/admin/user-management/managing-organizations-in-your-enterprise/managing-your-role-in-an-organization-owned-by-your-enterprise)."{% endif %}
 
 {% elsif fpt %}
 ### About the enterprise-level security overview
 At the enterprise-level, the security overview displays aggregate and repository-specific information for an enterprise. For more information, see "[About the enterprise-level security overview](/enterprise-cloud@latest/code-security/security-overview/about-the-security-overview#about-the-enterprise-level-security-overview)" in the {% data variables.product.prodname_ghe_cloud %} documentation.
 {% endif %}
 
+{% ifversion ghes < 3.7 or ghae < 3.7 %}
 ### About the team-level security overview
 At the team-level, the security overview displays repository-specific security information for repositories that the team has admin privileges for. For more information, see "[Managing team access to an organization repository](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository)."
 {% endif %}
+{% endif %}
diff --git a/translations/zh-CN/content/code-security/supply-chain-security/end-to-end-supply-chain/securing-code.md b/translations/zh-CN/content/code-security/supply-chain-security/end-to-end-supply-chain/securing-code.md
index 882ad462dc..28d368418f 100644
--- a/translations/zh-CN/content/code-security/supply-chain-security/end-to-end-supply-chain/securing-code.md
+++ b/translations/zh-CN/content/code-security/supply-chain-security/end-to-end-supply-chain/securing-code.md
@@ -47,7 +47,7 @@ As a first step, you want to make a complete inventory of your dependencies. The
 
 ### Automatic detection of vulnerabilities in dependencies
 
-{% data variables.product.prodname_dependabot %} can help you by monitoring your dependencies and notifying you when they contain a known vulnerability. {% ifversion fpt or ghec or ghes > 3.2 %}You can even enable {% data variables.product.prodname_dependabot %} to automatically raise pull requests that update the dependency to a secure version.{% endif %} For more information, see "[About {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)"{% ifversion fpt or ghec or ghes > 3.2 %} and "[About Dependabot security updates](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-dependabot-security-updates)"{% endif %}.
+{% data variables.product.prodname_dependabot %} can help you by monitoring your dependencies and notifying you when they contain a known vulnerability. {% ifversion fpt or ghec or ghes %}You can even enable {% data variables.product.prodname_dependabot %} to automatically raise pull requests that update the dependency to a secure version.{% endif %} For more information, see "[About {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)"{% ifversion fpt or ghec or ghes %} and "[About Dependabot security updates](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-dependabot-security-updates)"{% endif %}.
 
 ### Assessment of exposure to risk from a vulnerable dependency
 
@@ -81,15 +81,13 @@ If your organization uses {% data variables.product.prodname_GH_advanced_securit
 You can configure {% data variables.product.prodname_secret_scanning %} to check for secrets issued by many service providers and to notify you when any are detected. You can also define custom patterns to detect additional secrets at the repository, organization, or enterprise level. For more information, see "[About secret scanning](/code-security/secret-scanning/about-secret-scanning)" and "[Secret scanning patterns](/code-security/secret-scanning/secret-scanning-patterns)."
 {% endif %}
 
-{% ifversion fpt or ghec or ghes > 3.2 or ghae %}
 ### Secure storage of secrets you use in {% data variables.product.product_name %}
-{% endif %}
 
 {% ifversion fpt or ghec %}
 Besides your code, you probably need to use secrets in other places. For example, to allow {% data variables.product.prodname_actions %} workflows, {% data variables.product.prodname_dependabot %}, or your {% data variables.product.prodname_github_codespaces %} development environment to communicate with other systems. For more information on how to securely store and use secrets, see "[Encrypted secrets in Actions](/actions/security-guides/encrypted-secrets)," "[Managing encrypted secrets for Dependabot](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/managing-encrypted-secrets-for-dependabot)," and "[Managing encrypted secrets for your codespaces](/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces)."
 {% endif %}
 
-{% ifversion ghes > 3.2 or ghae %}
+{% ifversion ghes or ghae %}
 Besides your code, you probably need to use secrets in other places. For example, to allow {% data variables.product.prodname_actions %} workflows{% ifversion ghes %} or {% data variables.product.prodname_dependabot %}{% endif %} to communicate with other systems. For more information on how to securely store and use secrets, see "[Encrypted secrets in Actions](/actions/security-guides/encrypted-secrets){% ifversion ghes %}" and "[Managing encrypted secrets for Dependabot](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/managing-encrypted-secrets-for-dependabot)."{% else %}."{% endif %}
 {% endif %}
 
diff --git a/translations/zh-CN/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review.md b/translations/zh-CN/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review.md
index 7a13366bbb..3e83d7902b 100644
--- a/translations/zh-CN/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review.md
+++ b/translations/zh-CN/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review.md
@@ -19,8 +19,6 @@ redirect_from:
   - /code-security/supply-chain-security/about-dependency-review
 ---
 
-{% data reusables.dependency-review.beta %}
-
 ## About dependency review
 
 {% data reusables.dependency-review.feature-overview %}  
diff --git a/translations/zh-CN/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-supply-chain-security.md b/translations/zh-CN/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-supply-chain-security.md
index 33e8c19950..8e83dd646e 100644
--- a/translations/zh-CN/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-supply-chain-security.md
+++ b/translations/zh-CN/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-supply-chain-security.md
@@ -1,6 +1,6 @@
 ---
 title: About supply chain security
-intro: '{% data variables.product.product_name %} helps you secure your supply chain, from understanding the dependencies in your environment, to knowing about vulnerabilities in those dependencies{% ifversion fpt or ghec or ghes > 3.2 %}, and patching them{% endif %}.'
+intro: '{% data variables.product.product_name %} helps you secure your supply chain, from understanding the dependencies in your environment, to knowing about vulnerabilities in those dependencies{% ifversion fpt or ghec or ghes %}, and patching them{% endif %}.'
 miniTocMaxHeadingLevel: 3
 shortTitle: Supply chain security
 redirect_from:
@@ -27,13 +27,13 @@ With the accelerated use of open source, most projects depend on hundreds of ope
 
 You add dependencies directly to your supply chain when you specify them in a manifest file or a lockfile. Dependencies can also be included transitively, that is, even if you don’t specify a particular dependency, but a dependency of yours uses it, then you’re also dependent on that dependency.
 
-{% data variables.product.product_name %} offers a range of features to help you understand the dependencies in your environment{% ifversion ghes < 3.3 or ghae %} and know about vulnerabilities in those dependencies{% endif %}{% ifversion fpt or ghec or ghes > 3.2 %}, know about vulnerabilities in those dependencies, and patch them{% endif %}. 
+{% data variables.product.product_name %} offers a range of features to help you understand the dependencies in your environment{% ifversion ghae %} and know about vulnerabilities in those dependencies{% endif %}{% ifversion fpt or ghec or ghes %}, know about vulnerabilities in those dependencies, and patch them{% endif %}. 
 
 The supply chain features on {% data variables.product.product_name %} are:
 - **Dependency graph**
 - **Dependency review**
 - **{% data variables.product.prodname_dependabot_alerts %} **
-{% ifversion fpt or ghec or ghes > 3.2 %}- **{% data variables.product.prodname_dependabot_updates %}**
+{% ifversion fpt or ghec or ghes %}- **{% data variables.product.prodname_dependabot_updates %}**
   - **{% data variables.product.prodname_dependabot_security_updates %}**
   - **{% data variables.product.prodname_dependabot_version_updates %}**{% endif %}
 
@@ -43,7 +43,7 @@ Other supply chain features on {% data variables.product.prodname_dotcom %} rely
 
 - Dependency review uses the dependency graph to identify dependency changes and help you understand the security impact of these changes when you review pull requests.
 - {% data variables.product.prodname_dependabot %} cross-references dependency data provided by the dependency graph with the list of advisories published in the {% data variables.product.prodname_advisory_database %}, scans your dependencies and generates {% data variables.product.prodname_dependabot_alerts %} when a potential vulnerability {% ifversion GH-advisory-db-supports-malware %}or malware{% endif %} is detected.
-{% ifversion fpt or ghec or ghes > 3.2 %}- {% data variables.product.prodname_dependabot_security_updates %} use the dependency graph and  {% data variables.product.prodname_dependabot_alerts %} to help you update dependencies with known vulnerabilities in your repository.
+{% ifversion fpt or ghec or ghes %}- {% data variables.product.prodname_dependabot_security_updates %} use the dependency graph and  {% data variables.product.prodname_dependabot_alerts %} to help you update dependencies with known vulnerabilities in your repository.
 
 {% data variables.product.prodname_dependabot_version_updates %} don't use the dependency graph and rely on the semantic versioning of dependencies instead. {% data variables.product.prodname_dependabot_version_updates %} help you keep your dependencies updated, even when they don’t have any vulnerabilities.
 {% endif %}
@@ -79,9 +79,9 @@ For more information about dependency review, see "[About dependency review](/co
 
 ### What is Dependabot
 
-{% data variables.product.prodname_dependabot %} keeps your dependencies up to date by informing you of any security vulnerabilities in your dependencies{% ifversion fpt or ghec or ghes > 3.2 %}, and automatically opens pull requests to upgrade your dependencies to the next available secure version when a {% data variables.product.prodname_dependabot %} alert is triggered, or to the latest version when a release is published{% else %} so that you can update that dependency{% endif %}.
+{% data variables.product.prodname_dependabot %} keeps your dependencies up to date by informing you of any security vulnerabilities in your dependencies{% ifversion fpt or ghec or ghes %}, and automatically opens pull requests to upgrade your dependencies to the next available secure version when a {% data variables.product.prodname_dependabot %} alert is triggered, or to the latest version when a release is published{% else %} so that you can update that dependency{% endif %}.
 
-{% ifversion fpt or ghec or ghes > 3.2 %}
+{% ifversion fpt or ghec or ghes %}
 The term "{% data variables.product.prodname_dependabot %}" encompasses the following features:
 - {% data variables.product.prodname_dependabot_alerts %}—Displayed notification on the **Security** tab for the repository, and in the repository's dependency graph. The alert includes a link to the affected file in the project, and information about a fixed version.
 - {% data variables.product.prodname_dependabot_updates %}:
@@ -117,7 +117,7 @@ The term "{% data variables.product.prodname_dependabot %}" encompasses the foll
 
 For more information, see "[About {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-alerts-for-vulnerable-dependencies)."
 
-{% ifversion fpt or ghec or ghes > 3.2 %}
+{% ifversion fpt or ghec or ghes %}
 #### What are Dependabot updates
 
 There are two types of {% data variables.product.prodname_dependabot_updates %}: {% data variables.product.prodname_dependabot %} _security_ updates and _version_ updates. {% data variables.product.prodname_dependabot %} generates automatic pull requests to update your dependencies in both cases, but there are several differences.
@@ -166,7 +166,7 @@ Any repository type:
 - **Dependency graph** and **{% data variables.product.prodname_dependabot_alerts %}**—not enabled by default. Both features are configured at an enterprise level by the enterprise owner. For more information, see {% ifversion ghes %}"[Enabling the dependency graph for your enterprise](/admin/code-security/managing-supply-chain-security-for-your-enterprise/enabling-the-dependency-graph-for-your-enterprise)" and {% endif %}"[Enabling {% data variables.product.prodname_dependabot %} for your enterprise](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise)."
 - **Dependency review**—available when dependency graph is enabled for {% data variables.location.product_location %} and {% data variables.product.prodname_advanced_security %} is enabled for the organization or repository. For more information, see "[About {% data variables.product.prodname_GH_advanced_security %}](/get-started/learning-about-github/about-github-advanced-security)."
 {% endif %}
-{% ifversion ghes > 3.2 %}
+{% ifversion ghes %}
 - **{% data variables.product.prodname_dependabot_security_updates %}**—not enabled by default. You can enable {% data variables.product.prodname_dependabot_security_updates %} for any repository that uses {% data variables.product.prodname_dependabot_alerts %} and the dependency graph. For information about enabling security updates, see "[Configuring {% data variables.product.prodname_dependabot_security_updates %}](/code-security/dependabot/dependabot-security-updates/configuring-dependabot-security-updates)."
 - **{% data variables.product.prodname_dependabot_version_updates %}**—not enabled by default. People with write permissions to a repository can enable {% data variables.product.prodname_dependabot_version_updates %}. For information about enabling version updates, see "[Configuring {% data variables.product.prodname_dependabot_version_updates %}](/code-security/dependabot/dependabot-version-updates/configuring-dependabot-version-updates)."
 {% endif %}
diff --git a/translations/zh-CN/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph.md b/translations/zh-CN/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph.md
index 15849448f0..42541c3ef9 100644
--- a/translations/zh-CN/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph.md
+++ b/translations/zh-CN/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph.md
@@ -79,11 +79,7 @@ The recommended formats explicitly define which versions are used for all direct
 {%- ifversion github-actions-in-dependency-graph %}
 | {% data variables.product.prodname_actions %} workflows<sup>[†]</sup> | YAML | `.yml`, `.yaml` | `.yml`, `.yaml` |
 {%- endif %}
-{%- ifversion fpt or ghec or ghes > 3.2 or ghae %}
 | Go modules | Go | `go.sum` | `go.mod`, `go.sum` |
-{%- elsif ghes = 3.2 %}
-| Go modules | Go | `go.mod` | `go.mod` |
-{%- endif %}
 | Maven | Java, Scala |  `pom.xml`  | `pom.xml`  |
 | npm | JavaScript |            `package-lock.json` | `package-lock.json`, `package.json`|
 | pip             | Python                    | `requirements.txt`, `pipfile.lock` | `requirements.txt`, `pipfile`, `pipfile.lock`, `setup.py`<sup>[‡]</sup> |
diff --git a/translations/zh-CN/content/code-security/supply-chain-security/understanding-your-software-supply-chain/configuring-dependency-review.md b/translations/zh-CN/content/code-security/supply-chain-security/understanding-your-software-supply-chain/configuring-dependency-review.md
index 06bb91f769..460c0bb236 100644
--- a/translations/zh-CN/content/code-security/supply-chain-security/understanding-your-software-supply-chain/configuring-dependency-review.md
+++ b/translations/zh-CN/content/code-security/supply-chain-security/understanding-your-software-supply-chain/configuring-dependency-review.md
@@ -4,7 +4,7 @@ intro: You can use dependency review to catch vulnerabilities before they are ad
 shortTitle: Configure dependency review
 versions:
   fpt: '*'
-  ghes: '>= 3.2'
+  ghes: '*'
   ghae: '*'
   ghec: '*'
 type: how_to
@@ -16,8 +16,6 @@ topics:
   - Pull requests
 ---
 
-{% data reusables.dependency-review.beta %}
-
 ## About dependency review
 
 {% data reusables.dependency-review.feature-overview %}   
@@ -46,8 +44,7 @@ Dependency review is available when dependency graph is enabled for {% data vari
 {% data reusables.repositories.sidebar-settings %}
 {% data reusables.repositories.navigate-to-code-security-and-analysis %}
 1. Under "Configure security and analysis features", check if the dependency graph is enabled. 
-1. If dependency graph is enabled, click **Enable** next to "{% data variables.product.prodname_GH_advanced_security %}" to enable {% data variables.product.prodname_advanced_security %}, including dependency review. The enable button is disabled if your enterprise has no available licenses for {% data variables.product.prodname_advanced_security %}.{% ifversion ghes < 3.3 %}
-  ![Screenshot of "Code security and analysis" features"](/assets/images/enterprise/3.2/repository/code-security-and-analysis-enable-ghas-3.2.png){% endif %}{% ifversion ghes > 3.2 %}
+1. If dependency graph is enabled, click **Enable** next to "{% data variables.product.prodname_GH_advanced_security %}" to enable {% data variables.product.prodname_advanced_security %}, including dependency review. The enable button is disabled if your enterprise has no available licenses for {% data variables.product.prodname_advanced_security %}.{% ifversion ghes %}
     ![Screenshot of "Code security and analysis" features"](/assets/images/enterprise/3.4/repository/code-security-and-analysis-enable-ghas-3.4.png){% endif %}
 
 {% endif %}
diff --git a/translations/zh-CN/content/code-security/supply-chain-security/understanding-your-software-supply-chain/troubleshooting-the-dependency-graph.md b/translations/zh-CN/content/code-security/supply-chain-security/understanding-your-software-supply-chain/troubleshooting-the-dependency-graph.md
index 34240ebf9d..c1879f3d31 100644
--- a/translations/zh-CN/content/code-security/supply-chain-security/understanding-your-software-supply-chain/troubleshooting-the-dependency-graph.md
+++ b/translations/zh-CN/content/code-security/supply-chain-security/understanding-your-software-supply-chain/troubleshooting-the-dependency-graph.md
@@ -1,6 +1,6 @@
 ---
-title: 依赖关系图疑难排解
-intro: 如果依赖项关系图报告的依赖项信息不符合你的预期，则需要考虑许多因素，你可以检查各种问题。
+title: Troubleshooting the dependency graph
+intro: 'If the dependency information reported by the dependency graph is not what you expected, there are a number of points to consider, and various things you can check.'
 shortTitle: Troubleshoot dependency graph
 versions:
   fpt: '*'
@@ -16,56 +16,51 @@ topics:
   - Dependency graph
   - CVEs
   - Repositories
-ms.openlocfilehash: 51a1da4eff062263aeca52de02b764385e7e1184
-ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d
-ms.translationtype: HT
-ms.contentlocale: zh-CN
-ms.lasthandoff: 09/11/2022
-ms.locfileid: '146458242'
 ---
+
 {% data reusables.dependabot.result-discrepancy %}
 
-## 依赖项图是否只查找清单和锁文件中的依赖项？
+## Does the dependency graph only find dependencies in manifests and lockfiles?
 
-依赖项关系图{% ifversion dependency-submission-api %}自动{% endif %}包含在环境中明确声明的依赖项的信息。 也就是说，在清单或锁定文件中指定的依赖项。 依赖项图通常还包括过渡依赖项，即使它们没有在锁定文件中指定，也可以通过查看清单文件中的依赖项来实现。
+The dependency graph {% ifversion dependency-submission-api %}automatically{% endif %} includes information on dependencies that are explicitly declared in your environment. That is, dependencies that are specified in a manifest or a lockfile. The dependency graph generally also includes transitive dependencies, even when they aren't specified in a lockfile, by looking at the dependencies of the dependencies in a manifest file.
 
-依赖项关系图不会{% ifversion dependency-submission-api %}自动{% endif %}包含“松散”依赖项。 “宽松”依赖项是指从另一个来源复制并直接或在存档文件（例如 ZIP 或 JAR 文件）中检入仓库的单个文件，而不是在包管理器的清单或锁定文件中引用的文件。 
+The dependency graph doesn't {% ifversion dependency-submission-api %}automatically{% endif %} include "loose" dependencies. "Loose" dependencies are individual files that are copied from another source and checked into the repository directly or within an archive (such as a ZIP or JAR file), rather than being referenced by in a package manager’s manifest or lockfile. 
 
-{% ifversion dependency-submission-api %}但是，可以使用依赖项提交 API（测试版）将依赖项添加到项目的依赖项关系图中，即使依赖项未在清单或锁定文件中声明，例如在生成项目时解析的依赖项。 依赖项关系图将显示按生态系统分组的提交依赖项，但与从清单或锁定文件解析的依赖项是分开的。 有关依赖项提交 API 的详细信息，请参阅“[使用依赖项提交 API](/code-security/supply-chain-security/understanding-your-software-supply-chain/using-the-dependency-submission-api)”。{% endif %}
+{% ifversion dependency-submission-api %}However, you can use the Dependency submission API (beta) to add dependencies to a project's dependency graph, even if the dependencies are not declared in a manifest or lock file, such as dependencies resolved when a project is built. The dependency graph will display the submitted dependencies grouped by ecosystem, but separately from the dependencies parsed from manifest or lock files. For more information on the Dependency submission API, see "[Using the Dependency submission API](/code-security/supply-chain-security/understanding-your-software-supply-chain/using-the-dependency-submission-api)."{% endif %}
 
-检查：是否在存储库清单或锁定文件中未指定组件的依赖项？
+**Check**: Is the missing dependency for a component that's not specified in the repository's manifest or lockfile?
 
-## 依赖项图是否检测使用变量指定的依赖项？
+## Does the dependency graph detect dependencies specified using variables?
 
-依赖项图在清单被推送到 {% data variables.product.prodname_dotcom %} 时分析它们。 因此，依赖项图无法访问项目的构建环境，从而无法解析清单中使用的变量。 如果在清单中使用变量指定名称，或指定依赖项的版本（更常见），则该依赖项不会{% ifversion dependency-submission-api %}自动{% endif %}包括在依赖项关系图中。
+The dependency graph analyzes manifests as they’re pushed to {% data variables.product.prodname_dotcom %}. The dependency graph doesn't, therefore, have access to the build environment of the project, so it can't resolve variables used within manifests. If you use variables within a manifest to specify the name, or more commonly the version of a dependency, then that dependency will not {% ifversion dependency-submission-api %}automatically{% endif %} be included in the dependency graph.
 
-{% ifversion dependency-submission-api %}但是，可以使用依赖项提交 API（测试版）将依赖项添加到项目的依赖项关系图中，即使仅当生成项目时才解析依赖项。 有关依赖项提交 API 的详细信息，请参阅“[使用依赖项提交 API](/code-security/supply-chain-security/understanding-your-software-supply-chain/using-the-dependency-submission-api)”。{% endif %}
+{% ifversion dependency-submission-api %}However, you can use the Dependency submission API (beta) to add dependencies to a project's dependency graph, even if the dependencies are only resolved when a project is built. For more information on the Dependency submission API, see "[Using the Dependency submission API](/code-security/supply-chain-security/understanding-your-software-supply-chain/using-the-dependency-submission-api)."{% endif %}
 
-检查：在清单中缺少的依赖项是否使用变量声明其名称或版本？
+**Check**: Is the missing dependency declared in the manifest by using a variable for its name or version?
 
-## 是否存在影响依赖项图数据的限制？
+## Are there limits which affect the dependency graph data?
 
-是的，依赖项图有两个限制类别：
+Yes, the dependency graph has two categories of limits:
 
-1. 处理限制
+1. **Processing limits**
 
-    这会影响 {% data variables.product.prodname_dotcom %} 中显示的依赖项图，还会阻止 {% data variables.product.prodname_dependabot_alerts %} 的创建。
+    These affect the dependency graph displayed within {% data variables.product.prodname_dotcom %} and also prevent {% data variables.product.prodname_dependabot_alerts %} being created.
 
-    仅为企业帐户处理大小超过 0.5 MB 的清单。 对于其他帐户，将忽略超过 0.5 MB 的清单，并且不会创建 {% data variables.product.prodname_dependabot_alerts %}。
+    Manifests over 0.5 MB in size are only processed for enterprise accounts. For other accounts, manifests over 0.5 MB are ignored and will not create {% data variables.product.prodname_dependabot_alerts %}.
 
-    默认情况下， {% data variables.product.prodname_dotcom %} 对每个仓库处理的清单不会超过 20 个。 对于超出此限制的清单，不会创建 {% data variables.product.prodname_dependabot_alerts %}。 如果您需要提高限值，请联系 {% data variables.contact.contact_support %}。 
+    By default, {% data variables.product.prodname_dotcom %} will not process more than 20 manifests per repository. {% data variables.product.prodname_dependabot_alerts %} are not created for manifests beyond this limit. If you need to increase the limit, contact {% data variables.contact.contact_support %}. 
 
-2. 可视化限制
+2. **Visualization limits**
 
-    这会影响 {% data variables.product.prodname_dotcom %} 中依赖项图的显示内容。 但是，它们不会影响 {% data variables.product.prodname_dependabot_alerts %} 的创建。
+    These affect what's displayed in the dependency graph within {% data variables.product.prodname_dotcom %}. However, they don't affect the {% data variables.product.prodname_dependabot_alerts %} that are created.
 
-    仓库依赖项图的依赖项视图只显示 100 个清单。 通常这就足够了，因为它明显高于上述处理限制。 处理限制超过 100 的情况下，对于任何未在 {% data variables.product.prodname_dotcom %} 中显示的任何清单，仍会创建 {% data variables.product.prodname_dependabot_alerts %}。
+    The Dependencies view of the dependency graph for a repository only displays 100 manifests. Typically this is adequate as it is significantly higher than the processing limit described above. In situations where the processing limit is over 100, {% data variables.product.prodname_dependabot_alerts %} are still created for any manifests that are not shown within {% data variables.product.prodname_dotcom %}.
 
-检查：在超过 0.5 MB 的清单文件或包含大量清单的存储库中是否存在缺少的依赖项？
+**Check**: Is the missing dependency in a manifest file that's over 0.5 MB, or in a repository with a large number of manifests?
 
-## 延伸阅读
+## Further reading
 
-- “[关于依赖项关系图](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph)”
-- “[管理存储库的安全性和分析设置](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)”
-- “[漏洞依赖项检测疑难解答](/code-security/dependabot/working-with-dependabot/troubleshooting-the-detection-of-vulnerable-dependencies)”{% ifversion fpt or ghec or ghes > 3.2 %}
-- “[排查 {% data variables.product.prodname_dependabot %} 错误](/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors)”{% endif %}
+- "[About the dependency graph](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph)"
+- "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)"
+- "[Troubleshooting the detection of vulnerable dependencies](/code-security/dependabot/working-with-dependabot/troubleshooting-the-detection-of-vulnerable-dependencies)"{% ifversion fpt or ghec or ghes %}
+- "[Troubleshooting {% data variables.product.prodname_dependabot %} errors](/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors)"{% endif %}
diff --git a/translations/zh-CN/content/codespaces/codespaces-reference/allowing-your-codespace-to-access-a-private-image-registry.md b/translations/zh-CN/content/codespaces/codespaces-reference/allowing-your-codespace-to-access-a-private-image-registry.md
index 40094b5db2..fe7c29fd82 100644
--- a/translations/zh-CN/content/codespaces/codespaces-reference/allowing-your-codespace-to-access-a-private-image-registry.md
+++ b/translations/zh-CN/content/codespaces/codespaces-reference/allowing-your-codespace-to-access-a-private-image-registry.md
@@ -30,7 +30,7 @@ If you publish a container image to {% data variables.packages.prodname_ghcr_or_
 
 By default, when you publish a container image to {% data variables.packages.prodname_ghcr_or_npm_registry %}, the image inherits the access setting of the repository from which the image was published. For example, if the repository is public, the image is also public. If the repository is private, the image is also private, but is accessible from the repository.
 
-This behavior is controlled by the **Inherit access from repo** option. **Inherit access from repo** is selected by default when publishing via {% data variables.product.prodname_actions %}, but not when publishing directly to {% data variables.packages.prodname_ghcr_or_npm_registry %} using a % data variables.product.pat_generic %}.
+This behavior is controlled by the **Inherit access from repo** option. **Inherit access from repo** is selected by default when publishing via {% data variables.product.prodname_actions %}, but not when publishing directly to {% data variables.packages.prodname_ghcr_or_npm_registry %} using a {% data variables.product.pat_generic %}.
 
 If the **Inherit access from repo** option was not selected when the image was published, you can manually add the repository to the published container image's access controls. For more information, see "[Configuring a package's access control and visibility](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility#inheriting-access-for-a-container-image-from-a-repository)."
 
diff --git a/translations/zh-CN/content/codespaces/customizing-your-codespace/changing-the-machine-type-for-your-codespace.md b/translations/zh-CN/content/codespaces/customizing-your-codespace/changing-the-machine-type-for-your-codespace.md
index 5aca361ee0..f985434f1b 100644
--- a/translations/zh-CN/content/codespaces/customizing-your-codespace/changing-the-machine-type-for-your-codespace.md
+++ b/translations/zh-CN/content/codespaces/customizing-your-codespace/changing-the-machine-type-for-your-codespace.md
@@ -105,4 +105,4 @@ You can use the `gh codespace edit --machine MACHINE-TYPE-NAME` {% data variable
 - "[Codespaces machines](/rest/codespaces/machines)" in the REST API documentation
 - [`gh codespace edit`](https://cli.github.com/manual/gh_codespace_edit) in the {% data variables.product.prodname_cli %} manual
 
-{% endcli %}
\ No newline at end of file
+{% endcli %}
diff --git a/translations/zh-CN/content/codespaces/developing-in-codespaces/creating-a-codespace.md b/translations/zh-CN/content/codespaces/developing-in-codespaces/creating-a-codespace.md
index 559ed6dc38..f0e477786b 100644
--- a/translations/zh-CN/content/codespaces/developing-in-codespaces/creating-a-codespace.md
+++ b/translations/zh-CN/content/codespaces/developing-in-codespaces/creating-a-codespace.md
@@ -153,4 +153,4 @@ For full details of the options for this command, see [the {% data variables.pro
 
 ## Further reading
 - "[Opening an existing codespace](/codespaces/developing-in-codespaces/opening-an-existing-codespace)"
-- "[Adding an 'Open in GitHub Codespaces' badge](/codespaces/setting-up-your-project-for-codespaces/adding-a-codespaces-badge)"
\ No newline at end of file
+- "[Adding an 'Open in GitHub Codespaces' badge](/codespaces/setting-up-your-project-for-codespaces/adding-a-codespaces-badge)"
diff --git a/translations/zh-CN/content/codespaces/developing-in-codespaces/deleting-a-codespace.md b/translations/zh-CN/content/codespaces/developing-in-codespaces/deleting-a-codespace.md
index 5a9bb4271a..92bf5d8295 100644
--- a/translations/zh-CN/content/codespaces/developing-in-codespaces/deleting-a-codespace.md
+++ b/translations/zh-CN/content/codespaces/developing-in-codespaces/deleting-a-codespace.md
@@ -124,4 +124,4 @@ You can also use the REST API to delete codespaces for your organization. For mo
 
 ## Further reading
 - "[Codespaces lifecycle](/codespaces/developing-in-codespaces/codespaces-lifecycle)"
-- "[Configuring automatic deletion of your codespaces](/codespaces/customizing-your-codespace/configuring-automatic-deletion-of-your-codespaces)"
\ No newline at end of file
+- "[Configuring automatic deletion of your codespaces](/codespaces/customizing-your-codespace/configuring-automatic-deletion-of-your-codespaces)"
diff --git a/translations/zh-CN/content/codespaces/developing-in-codespaces/developing-in-a-codespace.md b/translations/zh-CN/content/codespaces/developing-in-codespaces/developing-in-a-codespace.md
index 680e4301c4..ed9f3b5c99 100644
--- a/translations/zh-CN/content/codespaces/developing-in-codespaces/developing-in-a-codespace.md
+++ b/translations/zh-CN/content/codespaces/developing-in-codespaces/developing-in-a-codespace.md
@@ -53,4 +53,4 @@ For more information on using {% data variables.product.prodname_vscode_shortnam
 
 ### Using the {% data variables.product.prodname_vscode_command_palette %}
 
-The {% data variables.product.prodname_vscode_command_palette %} allows you to access and manage many features for {% data variables.product.prodname_github_codespaces %} and {% data variables.product.prodname_vscode_shortname %}. For more information, see "[Using the {% data variables.product.prodname_vscode_command_palette_shortname %} in {% data variables.product.prodname_github_codespaces %}](/codespaces/codespaces-reference/using-the-vs-code-command-palette-in-codespaces)."
\ No newline at end of file
+The {% data variables.product.prodname_vscode_command_palette %} allows you to access and manage many features for {% data variables.product.prodname_github_codespaces %} and {% data variables.product.prodname_vscode_shortname %}. For more information, see "[Using the {% data variables.product.prodname_vscode_command_palette_shortname %} in {% data variables.product.prodname_github_codespaces %}](/codespaces/codespaces-reference/using-the-vs-code-command-palette-in-codespaces)."
diff --git a/translations/zh-CN/content/codespaces/guides.md b/translations/zh-CN/content/codespaces/guides.md
index 9ade56462a..0d4b1d4901 100644
--- a/translations/zh-CN/content/codespaces/guides.md
+++ b/translations/zh-CN/content/codespaces/guides.md
@@ -15,6 +15,8 @@ includeGuides:
   - /codespaces/setting-up-your-project-for-codespaces/setting-up-your-python-project-for-codespaces
   - /codespaces/setting-up-your-project-for-codespaces/setting-up-your-dotnet-project-for-codespaces
   - /codespaces/setting-up-your-project-for-codespaces/setting-up-your-java-project-for-codespaces
+  - /codespaces/setting-up-your-project-for-codespaces/setting-a-minimum-specification-for-codespace-machines
+  - /codespaces/setting-up-your-project-for-codespaces/automatically-opening-files-in-the-codespaces-for-a-repository
   - /codespaces/setting-up-your-project-for-codespaces/adding-a-codespaces-badge
   - /codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project
   - /codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account
diff --git a/translations/zh-CN/content/codespaces/managing-codespaces-for-your-organization/enabling-github-codespaces-for-your-organization.md b/translations/zh-CN/content/codespaces/managing-codespaces-for-your-organization/enabling-github-codespaces-for-your-organization.md
index 25d134cf2a..4564093716 100644
--- a/translations/zh-CN/content/codespaces/managing-codespaces-for-your-organization/enabling-github-codespaces-for-your-organization.md
+++ b/translations/zh-CN/content/codespaces/managing-codespaces-for-your-organization/enabling-github-codespaces-for-your-organization.md
@@ -1,9 +1,9 @@
 ---
 title: Enabling GitHub Codespaces for your organization
 shortTitle: 'Enable {% data variables.product.prodname_codespaces %}'
-intro: "You can control which users in your organization can use {% data variables.product.prodname_github_codespaces %} at the organization's expense."
+intro: 'You can control which users in your organization can use {% data variables.product.prodname_github_codespaces %} at the organization''s expense.'
 product: '{% data reusables.gated-features.codespaces %}'
-permissions: "To alter an organization's billing settings, you must be an organization owner."
+permissions: 'To alter an organization''s billing settings, you must be an organization owner.'
 redirect_from:
   - /codespaces/managing-codespaces-for-your-organization/managing-user-permissions-for-your-organization
   - /codespaces/managing-codespaces-for-your-organization/enabling-codespaces-for-your-organization
diff --git a/translations/zh-CN/content/codespaces/managing-codespaces-for-your-organization/listing-the-codespaces-in-your-organization.md b/translations/zh-CN/content/codespaces/managing-codespaces-for-your-organization/listing-the-codespaces-in-your-organization.md
index 68ef8f119d..996b22f228 100644
--- a/translations/zh-CN/content/codespaces/managing-codespaces-for-your-organization/listing-the-codespaces-in-your-organization.md
+++ b/translations/zh-CN/content/codespaces/managing-codespaces-for-your-organization/listing-the-codespaces-in-your-organization.md
@@ -1,7 +1,7 @@
 ---
 title: Listing the codespaces in your organization
 shortTitle: List organization codespaces
-intro: 'You can list all of the currently active or stopped codespaces for your organization.'
+intro: You can list all of the currently active or stopped codespaces for your organization.
 product: '{% data reusables.gated-features.codespaces %}'
 permissions: 'To list all of the current codespaces for your organization, you must be an organization owner.'
 versions:
@@ -51,4 +51,4 @@ gh codespace list --org ORGANIZATION --user USER
 
 You can use the `/orgs/{org}/codespaces` API endpoint as an alternative method of listing the current codespaces for an organization. This returns more information than {% data variables.product.prodname_cli %}; for example, the machine type details.
 
-For more information about this endpoint, see "[Codespaces organizations](/rest/codespaces/organizations#list-codespaces-for-the-organization)."
\ No newline at end of file
+For more information about this endpoint, see "[Codespaces organizations](/rest/codespaces/organizations#list-codespaces-for-the-organization)."
diff --git a/translations/zh-CN/content/codespaces/overview.md b/translations/zh-CN/content/codespaces/overview.md
index b193cde66d..e0494d19cb 100644
--- a/translations/zh-CN/content/codespaces/overview.md
+++ b/translations/zh-CN/content/codespaces/overview.md
@@ -44,4 +44,4 @@ For information on pricing, storage, and usage for {% data variables.product.pro
 
 {% data reusables.codespaces.codespaces-monthly-billing %} For information on how organizations owners and billing managers can manage the spending limit for {% data variables.product.prodname_github_codespaces %} for an organization, see "[Managing spending limits for {% data variables.product.prodname_github_codespaces %}](/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-github-codespaces)."
 
-You can see who will pay for a codespace before you create it. For more information, see "[Creating a codespace](/codespaces/developing-in-codespaces/creating-a-codespace#creating-a-codespace)."
\ No newline at end of file
+You can see who will pay for a codespace before you create it. For more information, see "[Creating a codespace](/codespaces/developing-in-codespaces/creating-a-codespace#creating-a-codespace)."
diff --git a/translations/zh-CN/content/codespaces/prebuilding-your-codespaces/allowing-a-prebuild-to-access-other-repositories.md b/translations/zh-CN/content/codespaces/prebuilding-your-codespaces/allowing-a-prebuild-to-access-other-repositories.md
index f9f02988d3..0ef2d0b210 100644
--- a/translations/zh-CN/content/codespaces/prebuilding-your-codespaces/allowing-a-prebuild-to-access-other-repositories.md
+++ b/translations/zh-CN/content/codespaces/prebuilding-your-codespaces/allowing-a-prebuild-to-access-other-repositories.md
@@ -1,7 +1,7 @@
 ---
 title: Allowing a prebuild to access other repositories
 shortTitle: Allow external repo access
-intro: You can permit your prebuild to access other {% data variables.product.prodname_dotcom %} repositories so that it can be built successfully.
+intro: 'You can permit your prebuild to access other {% data variables.product.prodname_dotcom %} repositories so that it can be built successfully.'
 versions:
   fpt: '*'
   ghec: '*'
diff --git a/translations/zh-CN/content/codespaces/setting-up-your-project-for-codespaces/adding-a-codespaces-badge.md b/translations/zh-CN/content/codespaces/setting-up-your-project-for-codespaces/adding-a-codespaces-badge.md
new file mode 100644
index 0000000000..cb324ef21f
--- /dev/null
+++ b/translations/zh-CN/content/codespaces/setting-up-your-project-for-codespaces/adding-a-codespaces-badge.md
@@ -0,0 +1,71 @@
+---
+title: 添加“在 GitHub Codespaces 中打开”锁屏提醒
+shortTitle: Add a Codespaces badge
+intro: 可以将锁屏提醒添加到存储库中的 Markdown 文件，用户可以单击该文件来创建 codespace。
+allowTitleToDifferFromFilename: true
+versions:
+  fpt: '*'
+  ghec: '*'
+type: how_to
+topics:
+  - Codespaces
+  - Set up
+product: '{% data reusables.gated-features.codespaces %}'
+ms.openlocfilehash: d2ed02a205a4a8c3e55deb0b52fdc9ffdb855dc4
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: zh-CN
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148108071'
+---
+## 概述
+
+向 Markdown 文件添加“在 {% data variables.product.prodname_github_codespaces %} 中打开”锁屏提醒可让用户轻松地为存储库创建 codespace。
+
+![自述文件页上 Codespaces 锁屏提醒的屏幕截图](/assets/images/help/codespaces/codespaces-badge-on-readme.png)
+
+创建锁屏提醒时，可以为锁屏提醒将创建的 codespace 选择特定配置选项。
+
+当人们单击锁屏提醒时，他们会进入用于创建 codespace 的高级选项页，其中包含你预先选择的选项。 有关高级选项页的详细信息，请参阅“[创建 codespace](/codespaces/developing-in-codespaces/creating-a-codespace#creating-a-codespace)”。
+
+在高级选项页中，用户可以根据需要更改预先选择的设置，然后单击“创建 codespace”。
+
+{% note %}
+
+注意：请注意，如果尚无法访问 {% data variables.product.prodname_github_codespaces %} 的人员单击此锁屏提醒，则会看到 404 消息。
+
+{% endnote %}
+
+## 创建“在 {% data variables.product.prodname_github_codespaces %} 中打开”锁屏提醒
+
+{% data reusables.repositories.navigate-to-repo %}
+1. 在存储库名称下，使用“分支”下拉菜单选择要为其创建锁屏提醒的分支。
+
+   ![“分支”下拉菜单的屏幕截图](/assets/images/help/codespaces/branch-drop-down.png)
+
+1. 单击“{% octicon "code" aria-label="The code icon" %} 代码”按钮，然后单击“codespace”选项卡。
+
+   ![“新建 codespace”按钮的屏幕截图](/assets/images/help/codespaces/new-codespace-button.png)
+
+1. 单击“在分支上创建 codespace”按钮一侧的向下箭头，单击“配置并创建 codespace”，然后单击“配置并创建 codespace”按钮  。
+
+   ![“配置并创建 codespace”选项的屏幕截图](/assets/images/help/codespaces/configure-and-create-option.png)
+
+1. 在用于创建 codespace 的高级选项页上，选择要在每个字段中预先选择的值。
+
+   ![高级选项页的屏幕截图](/assets/images/help/codespaces/advanced-options.png)
+
+1. 复制浏览器地址栏中的 URL。
+1. 例如，将以下 Markdown 添加到存储库的 `README.md` 文件：
+
+   ```Markdown{:copy}
+   [![Open in GitHub Codespaces](https://github.com/codespaces/badge.svg)](COPIED-URL)
+   ```
+
+   例如：
+
+   ```Markdown
+   [![Open in GitHub Codespaces](https://github.com/codespaces/badge.svg)](https://github.com/codespaces/new?hide_repo_select=true&ref=main&repo=0000000&machine=premiumLinux&devcontainer_path=.devcontainer%2Fdevcontainer.json&location=WestUs2)
+   ```
+
+   在上面的示例中，`0000000` 会是存储库的引用编号。 URL 中的其他详细信息由在高级选项页上的字段中选择的值确定。
diff --git a/translations/zh-CN/content/codespaces/setting-up-your-project-for-codespaces/index.md b/translations/zh-CN/content/codespaces/setting-up-your-project-for-codespaces/index.md
index e1e3ad0cd2..6ddb3c1ba5 100644
--- a/translations/zh-CN/content/codespaces/setting-up-your-project-for-codespaces/index.md
+++ b/translations/zh-CN/content/codespaces/setting-up-your-project-for-codespaces/index.md
@@ -17,6 +17,7 @@ children:
   - /setting-up-your-java-project-for-codespaces
   - /setting-up-your-python-project-for-codespaces
   - /setting-a-minimum-specification-for-codespace-machines
+  - /automatically-opening-files-in-the-codespaces-for-a-repository
   - /adding-a-codespaces-badge
 ms.openlocfilehash: 1e172243dc351f0a173c8624b66914e1c3795495
 ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794
diff --git a/translations/zh-CN/content/codespaces/setting-up-your-project-for-codespaces/setting-a-minimum-specification-for-codespace-machines.md b/translations/zh-CN/content/codespaces/setting-up-your-project-for-codespaces/setting-a-minimum-specification-for-codespace-machines.md
index b5f3007b28..9bd36a5a2a 100644
--- a/translations/zh-CN/content/codespaces/setting-up-your-project-for-codespaces/setting-a-minimum-specification-for-codespace-machines.md
+++ b/translations/zh-CN/content/codespaces/setting-up-your-project-for-codespaces/setting-a-minimum-specification-for-codespace-machines.md
@@ -1,7 +1,7 @@
 ---
-title: 为代码空间计算机设置最低规范
+title: Setting a minimum specification for codespace machines
 shortTitle: Set a minimum machine spec
-intro: '你可以避免资源不足的计算机类型用于存储库的 {% data variables.product.prodname_github_codespaces %}。'
+intro: 'You can avoid under-resourced machine types being used for {% data variables.product.prodname_github_codespaces %} for your repository.'
 permissions: People with write permissions to a repository can create or edit the codespace configuration.
 versions:
   fpt: '*'
@@ -11,29 +11,24 @@ topics:
   - Codespaces
   - Set up
 product: '{% data reusables.gated-features.codespaces %}'
-ms.openlocfilehash: 368b7c73d13bb0624c9d838ac2d7bb18a2b050e3
-ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
-ms.translationtype: HT
-ms.contentlocale: zh-CN
-ms.lasthandoff: 09/10/2022
-ms.locfileid: '147880804'
 ---
-## 概述
 
-创建的每个代码空间都托管在单独的虚拟机上，通常可以从不同类型的虚拟机中进行选择。 每个计算机类型都有不同的资源（CPU、内存、存储），默认情况下，使用资源最少的计算机类型。 有关详细信息，请参阅“[更改 codespace 的计算机类型](/codespaces/customizing-your-codespace/changing-the-machine-type-for-your-codespace#about-machine-types)”。
+## Overview
 
-如果项目需要一定程度的计算能力，则可以配置 {% data variables.product.prodname_github_codespaces %} 以便默认情况下只能使用或由用户选择满足这些要求的计算机类型。 可以在 `devcontainer.json` 文件中进行此配置。
+Each codespace that you create is hosted on a separate virtual machine, and you can usually choose from different types of virtual machines. Each machine type has different resources (processor cores, memory, storage) and, by default, the machine type with the least resources is used. For more information, see "[Changing the machine type for your codespace](/codespaces/customizing-your-codespace/changing-the-machine-type-for-your-codespace#about-machine-types)."
+
+If your project needs a certain level of compute power, you can configure {% data variables.product.prodname_github_codespaces %} so that only machine types that meet these requirements can be used by default, or selected by users. You configure this in a `devcontainer.json` file.
 
 {% note %}
 
-重要提示：对某些计算机类型的访问可能在组织级别受到限制。 通常，这样做是为了防止人们选择以较高费率计费的资源较高的计算机。 如果您的存储库受到组织级计算机类型策略的影响，则应确保不要设置最低规范，因为该规范不会留下任何可用的计算机类型供人们选择。 有关详细信息，请参阅“[限制对计算机类型的访问](/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types)”。
+**Important:** Access to some machine types may be restricted at the organization level. Typically this is done to prevent people choosing higher resourced machines that are billed at a higher rate. If your repository is affected by an organization-level policy for machine types you should make sure you don't set a minimum specification that would leave no available machine types for people to choose. For more information, see "[Restricting access to machine types](/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types)."
 
 {% endnote %}
 
-## 设置最低计算机规范
+## Setting a minimum machine specification
 
-1. 存储库的 {% data variables.product.prodname_github_codespaces %} 在 `devcontainer.json` 文件中配置。 如果存储库尚未包含 `devcontainer.json` 文件，请立即添加一个。 请参阅“[将开发容器配置添加到存储库](/free-pro-team@latest/codespaces/setting-up-your-project-for-codespaces/setting-up-your-project-for-codespaces)”。
-1. 编辑 `devcontainer.json` 文件，添加一个 `hostRequirements` 属性，如下所示：
+{% data reusables.codespaces.edit-devcontainer-json %}
+1. Edit the `devcontainer.json` file, adding the `hostRequirements` property at the top level of the file, within the enclosing JSON object. For example:
 
    ```json{:copy}
    "hostRequirements": {
@@ -43,16 +38,16 @@ ms.locfileid: '147880804'
    }
    ```
 
-   可以指定以下任何或所有选项：`cpus`、`memory` 和 `storage`。
+   You can specify any or all of the options: `cpus`, `memory`, and `storage`.
    
-   要检查当前可用于存储库的 {% data variables.product.prodname_github_codespaces %} 计算机类型的规范，请逐步完成创建 codespace 的过程，直到看到选择的计算机类型。 有关详细信息，请参阅“[创建 codespace](/codespaces/developing-in-codespaces/creating-a-codespace#creating-a-codespace)”。
+   To check the specifications of the {% data variables.product.prodname_github_codespaces %} machine types that are currently available for your repository, step through the process of creating a codespace until you see the choice of machine types. For more information, see "[Creating a codespace](/codespaces/developing-in-codespaces/creating-a-codespace#creating-a-codespace)."
    
-1. 保存文件并将更改提交到存储库的所需分支。
+1. Save the file and commit your changes to the required branch of the repository.
 
-   现在，当你为存储库的该分支创建代码空间时，前往创建配置选项，只能选择与指定资源匹配或超过你指定的资源的计算机类型。
+   Now when you create a codespace for that branch of the repository, and you go to the creation configuration options, you will only be able to select machine types that match or exceed the resources you've specified.
 
-   ![显示有限计算机类型选择的对话框](/assets/images/help/codespaces/machine-types-limited-choice.png)
+   ![Dialog box showing a limited choice of machine types](/assets/images/help/codespaces/machine-types-limited-choice.png)
 
-## 延伸阅读
+## Further reading
 
-- “[开发容器简介](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers)”
+- "[Introduction to dev containers](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers)"
diff --git a/translations/zh-CN/content/codespaces/the-githubdev-web-based-editor.md b/translations/zh-CN/content/codespaces/the-githubdev-web-based-editor.md
index 3944c4fa55..5b85af4092 100644
--- a/translations/zh-CN/content/codespaces/the-githubdev-web-based-editor.md
+++ b/translations/zh-CN/content/codespaces/the-githubdev-web-based-editor.md
@@ -2,7 +2,7 @@
 title: The github.dev web-based editor
 intro: 'Use the github.dev {% data variables.product.prodname_serverless %} from your repository or pull request to create and commit changes.'
 versions:
-  feature: 'githubdev-editor'
+  feature: githubdev-editor
 type: how_to
 miniTocMaxHeadingLevel: 3
 topics:
diff --git a/translations/zh-CN/content/codespaces/troubleshooting/troubleshooting-dotfiles-for-codespaces.md b/translations/zh-CN/content/codespaces/troubleshooting/troubleshooting-dotfiles-for-codespaces.md
index ec51c0bd71..476e7fe0ae 100644
--- a/translations/zh-CN/content/codespaces/troubleshooting/troubleshooting-dotfiles-for-codespaces.md
+++ b/translations/zh-CN/content/codespaces/troubleshooting/troubleshooting-dotfiles-for-codespaces.md
@@ -1,5 +1,5 @@
 ---
-title: Troubleshooting dotfiles for GitHub Codespaces 
+title: Troubleshooting dotfiles for GitHub Codespaces
 allowTitleToDifferFromFilename: true
 intro: Troubleshooting steps for common dotfiles issues.
 product: '{% data reusables.gated-features.codespaces %}'
@@ -23,4 +23,4 @@ If your codespace fails to pick up configuration settings from dotfiles, you sho
    - If your dotfiles were not cloned, check `/workspaces/.codespaces/.persistedshare/EnvironmentLog.txt` to see if there was a problem cloning them.
 1. Check `/workspaces/.codespaces/.persistedshare/creation.log` for possible issues. For more information, see [Creation logs](/codespaces/troubleshooting/codespaces-logs#creation-logs).
 
-If the configuration from your dotfiles is correctly picked up, but part of the configuration is incompatible with codespaces, use the `$CODESPACES` environment variable to add conditional logic for codespace-specific configuration settings.
\ No newline at end of file
+If the configuration from your dotfiles is correctly picked up, but part of the configuration is incompatible with codespaces, use the `$CODESPACES` environment variable to add conditional logic for codespace-specific configuration settings.
diff --git a/translations/zh-CN/content/copilot/configuring-github-copilot/configuring-github-copilot-settings-on-githubcom.md b/translations/zh-CN/content/copilot/configuring-github-copilot/configuring-github-copilot-settings-on-githubcom.md
index 144d1e75f2..be71adfb7d 100644
--- a/translations/zh-CN/content/copilot/configuring-github-copilot/configuring-github-copilot-settings-on-githubcom.md
+++ b/translations/zh-CN/content/copilot/configuring-github-copilot/configuring-github-copilot-settings-on-githubcom.md
@@ -11,12 +11,12 @@ redirect_from:
   - /github/copilot/about-github-copilot-telemetry
   - /github/copilot/github-copilot-telemetry-terms
 shortTitle: GitHub.com
-ms.openlocfilehash: 139a2c93c76155eff092ca168129f8ef52ce69ae
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: cc87328504e3d9eb5e2bce83d981098b7f989ae0
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: zh-CN
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147079586'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148108034'
 ---
 ## 关于 {% data variables.product.prodname_dotcom_the_website %} 上的 {% data variables.product.prodname_copilot %} 设置
 
diff --git a/translations/zh-CN/content/developers/apps/building-oauth-apps/authorizing-oauth-apps.md b/translations/zh-CN/content/developers/apps/building-oauth-apps/authorizing-oauth-apps.md
index 9ed610b338..557287e15b 100644
--- a/translations/zh-CN/content/developers/apps/building-oauth-apps/authorizing-oauth-apps.md
+++ b/translations/zh-CN/content/developers/apps/building-oauth-apps/authorizing-oauth-apps.md
@@ -341,8 +341,8 @@ To build this link, you'll need your OAuth Apps `client_id` that you received fr
 
 * "[Troubleshooting authorization request errors](/apps/managing-oauth-apps/troubleshooting-authorization-request-errors)"
 * "[Troubleshooting OAuth App access token request errors](/apps/managing-oauth-apps/troubleshooting-oauth-app-access-token-request-errors)"
-* "[Device flow errors](#error-codes-for-the-device-flow)"{% ifversion fpt or ghae or ghes > 3.2 or ghec %}
-* "[Token expiration and revocation](/github/authenticating-to-github/keeping-your-account-and-data-secure/token-expiration-and-revocation)"{% endif %}
+* "[Device flow errors](#error-codes-for-the-device-flow)"
+* "[Token expiration and revocation](/github/authenticating-to-github/keeping-your-account-and-data-secure/token-expiration-and-revocation)"
 
 ## Further reading
 
diff --git a/translations/zh-CN/content/developers/apps/getting-started-with-apps/about-apps.md b/translations/zh-CN/content/developers/apps/getting-started-with-apps/about-apps.md
index 166ace7868..db0162551d 100644
--- a/translations/zh-CN/content/developers/apps/getting-started-with-apps/about-apps.md
+++ b/translations/zh-CN/content/developers/apps/getting-started-with-apps/about-apps.md
@@ -84,9 +84,9 @@ Keep these ideas in mind when using {% data variables.product.pat_generic %}s:
 * You can perform one-off cURL requests.
 * You can run personal scripts.
 * Don't set up a script for your whole team or company to use.
-* Don't set up a shared personal account to act as a bot user.{% ifversion fpt or ghes > 3.2 or ghae or ghec %}
+* Don't set up a shared personal account to act as a bot user.
 * Grant your token the minimal privileges it needs.
-* Set an expiration for your {% data variables.product.pat_generic %}s, to help keep your information secure.{% endif %}
+* Set an expiration for your {% data variables.product.pat_generic %}s, to help keep your information secure.
 
 ## Determining which integration to build
 
diff --git a/translations/zh-CN/content/developers/index.md b/translations/zh-CN/content/developers/index.md
index d54da3539b..fbfb082848 100644
--- a/translations/zh-CN/content/developers/index.md
+++ b/translations/zh-CN/content/developers/index.md
@@ -1,6 +1,29 @@
 ---
 title: 开发人员
-intro: '通过与我们的 API 集成，自定义您的 {% data variables.product.prodname_dotcom %} 工作流程，以及构建并与社区分享应用程序，更深入地了解 {% data variables.product.prodname_dotcom %}。'
+intro: '通过与我们的 API 和 Webhook 集成、自定义 {% data variables.product.prodname_dotcom %} 工作流程以及构建应用并与社区共享，更深入地了解 {% data variables.product.prodname_dotcom %}。'
+introLinks:
+  About apps: /developers/apps/getting-started-with-apps/about-apps
+layout: product-landing
+featuredLinks:
+  guides:
+    - /developers/apps/getting-started-with-apps/differences-between-github-apps-and-oauth-apps
+    - /developers/apps/building-github-apps/creating-a-github-app
+    - /developers/apps/building-github-apps/authenticating-with-github-apps
+    - /developers/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps
+  popular:
+    - /developers/overview/about-githubs-apis
+    - /developers/webhooks-and-events/webhooks/webhook-events-and-payloads
+    - /developers/apps/building-github-apps/creating-a-github-app
+    - /developers/apps/building-github-apps/authenticating-with-github-apps
+    - /developers/webhooks-and-events/webhooks/about-webhooks
+    - /developers/apps/building-oauth-apps/authorizing-oauth-apps
+    - /developers/github-marketplace/github-marketplace-overview/about-github-marketplace
+  guideCards:
+    - /developers/webhooks-and-events/webhooks/creating-webhooks
+    - /developers/apps/guides/using-the-github-api-in-your-app
+    - /developers/apps/guides/creating-ci-tests-with-the-checks-api
+changelog:
+  label: apps
 versions:
   fpt: '*'
   ghes: '*'
@@ -11,11 +34,11 @@ children:
   - /webhooks-and-events
   - /apps
   - /github-marketplace
-ms.openlocfilehash: 12f99e62dd1e5a4128079360b4d1721954f5e775
-ms.sourcegitcommit: 22d665055b1bee7a5df630385e734e3a149fc720
+ms.openlocfilehash: dea95cbf3a90b14441c8bd09692c27dd3798d8e5
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: zh-CN
-ms.lasthandoff: 07/13/2022
-ms.locfileid: '145098011'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148108171'
 ---
 
diff --git a/translations/zh-CN/content/developers/webhooks-and-events/webhooks/webhook-events-and-payloads.md b/translations/zh-CN/content/developers/webhooks-and-events/webhooks/webhook-events-and-payloads.md
index 0caacccdd8..7f68a7bb88 100644
--- a/translations/zh-CN/content/developers/webhooks-and-events/webhooks/webhook-events-and-payloads.md
+++ b/translations/zh-CN/content/developers/webhooks-and-events/webhooks/webhook-events-and-payloads.md
@@ -734,7 +734,6 @@ For a detailed description of this payload and the payload for each type of `act
 
 Activity related to merge groups in a merge queue. The type of activity is specified in the action property of the payload object.
 
-
 ### Availability
 
 - Repository webhooks
@@ -1621,8 +1620,6 @@ This event occurs when someone triggers a workflow run on GitHub or sends a `POS
 {{ webhookPayloadsForCurrentVersion.workflow_dispatch }}
 {% endif %}
 
-{% ifversion fpt or ghes > 3.2 or ghec or ghae %}
-
 ## workflow_job
 
 {% data reusables.webhooks.workflow_job_short_desc %}
@@ -1644,7 +1641,6 @@ This event occurs when someone triggers a workflow run on GitHub or sends a `POS
 
 {{ webhookPayloadsForCurrentVersion.workflow_job }}
 
-{% endif %}
 {% ifversion fpt or ghes or ghec %}
 ## workflow_run
 
diff --git a/translations/zh-CN/content/education/contribute-with-github-community-exchange/getting-started-with-github-community-exchange.md b/translations/zh-CN/content/education/contribute-with-github-community-exchange/getting-started-with-github-community-exchange.md
index 2efe4a89b9..3ed1c04402 100644
--- a/translations/zh-CN/content/education/contribute-with-github-community-exchange/getting-started-with-github-community-exchange.md
+++ b/translations/zh-CN/content/education/contribute-with-github-community-exchange/getting-started-with-github-community-exchange.md
@@ -4,12 +4,12 @@ shortTitle: Get started
 intro: '了解如何访问 {% data variables.product.prodname_community_exchange %} 并提交存储库。'
 versions:
   fpt: '*'
-ms.openlocfilehash: f9280e380b251c52d2b582aadb55eb319d5c342d
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: b9c866ef33c321b70b87d8bcd3682d0c02737bfe
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: zh-CN
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147574002'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148108610'
 ---
 ## 简介
 
diff --git a/translations/zh-CN/content/education/contribute-with-github-community-exchange/index.md b/translations/zh-CN/content/education/contribute-with-github-community-exchange/index.md
index ce0515e45b..ed0c5cf0d6 100644
--- a/translations/zh-CN/content/education/contribute-with-github-community-exchange/index.md
+++ b/translations/zh-CN/content/education/contribute-with-github-community-exchange/index.md
@@ -8,11 +8,11 @@ children:
   - /getting-started-with-github-community-exchange
   - /submitting-your-repository-to-github-community-exchange
   - /managing-your-submissions-to-github-community-exchange
-ms.openlocfilehash: 420db797ef8e913a597647f2a20fad8cea2c5861
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: fe002b4cff8bbecaac9ea4611ff69ab366df240f
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: zh-CN
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147409740'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148108227'
 ---
 
diff --git a/translations/zh-CN/content/education/contribute-with-github-community-exchange/managing-your-submissions-to-github-community-exchange.md b/translations/zh-CN/content/education/contribute-with-github-community-exchange/managing-your-submissions-to-github-community-exchange.md
index e31b121354..146dd34234 100644
--- a/translations/zh-CN/content/education/contribute-with-github-community-exchange/managing-your-submissions-to-github-community-exchange.md
+++ b/translations/zh-CN/content/education/contribute-with-github-community-exchange/managing-your-submissions-to-github-community-exchange.md
@@ -4,12 +4,12 @@ shortTitle: Manage your submissions
 intro: '可在 {% data variables.product.prodname_community_exchange %} 库中管理分配给每个存储库的用途、主题和产品/服务，也可删除存储库提交。'
 versions:
   fpt: '*'
-ms.openlocfilehash: 70dc65ccb387817d5b4a78c1fc27085f67dcfc6e
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: a7da6f3bede47700658fe81a1f0ec3e4e33ef316
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: zh-CN
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147409736'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148108221'
 ---
 ## 关于提交
 
diff --git a/translations/zh-CN/content/education/contribute-with-github-community-exchange/submitting-your-repository-to-github-community-exchange.md b/translations/zh-CN/content/education/contribute-with-github-community-exchange/submitting-your-repository-to-github-community-exchange.md
index dc51563c5c..3280c4d33b 100644
--- a/translations/zh-CN/content/education/contribute-with-github-community-exchange/submitting-your-repository-to-github-community-exchange.md
+++ b/translations/zh-CN/content/education/contribute-with-github-community-exchange/submitting-your-repository-to-github-community-exchange.md
@@ -4,12 +4,12 @@ shortTitle: Submit your repository
 intro: '可将存储库提交到 {% data variables.product.prodname_community_exchange %}，以供其他人查看或参与。'
 versions:
   fpt: '*'
-ms.openlocfilehash: d520f303bf368c9230f26580ba2de9bd744b21e7
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: 07198c74937470a591b30702bd027036d91d3ec7
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: zh-CN
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147409734'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148108220'
 ---
 ## 关于存储库提交
 
diff --git a/translations/zh-CN/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-students/about-github-global-campus-for-students.md b/translations/zh-CN/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-students/about-github-global-campus-for-students.md
index df79d62495..8789977ae3 100644
--- a/translations/zh-CN/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-students/about-github-global-campus-for-students.md
+++ b/translations/zh-CN/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-students/about-github-global-campus-for-students.md
@@ -10,12 +10,12 @@ redirect_from:
 versions:
   fpt: '*'
 shortTitle: For students
-ms.openlocfilehash: a34da8bd0f37646bfaad0dbff3b09c6f2df440e4
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: 9012b473399905e60b04a8876a3d4e6afd10a6ba
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: zh-CN
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147574171'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148108219'
 ---
 将 {% data variables.product.prodname_dotcom %} 用于学校项目是一种与别人协作的实用方式，可创建展示真实世界的作品集。
 
diff --git a/translations/zh-CN/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-students/apply-to-github-global-campus-as-a-student.md b/translations/zh-CN/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-students/apply-to-github-global-campus-as-a-student.md
index ecb7b10994..7b76fa9471 100644
--- a/translations/zh-CN/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-students/apply-to-github-global-campus-as-a-student.md
+++ b/translations/zh-CN/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-students/apply-to-github-global-campus-as-a-student.md
@@ -1,5 +1,5 @@
 ---
-title: 'Apply to GitHub Global Campus as a student'
+title: Apply to GitHub Global Campus as a student
 intro: 'As a student, you can apply to join {% data variables.product.prodname_global_campus %} and receive access to the student resources and benefits offered by {% data variables.product.prodname_education %}'
 redirect_from:
   - /education/teach-and-learn-with-github-education/apply-for-a-student-developer-pack
diff --git a/translations/zh-CN/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-students/index.md b/translations/zh-CN/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-students/index.md
index 9ddf11ec54..6cf996647f 100644
--- a/translations/zh-CN/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-students/index.md
+++ b/translations/zh-CN/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-students/index.md
@@ -14,11 +14,11 @@ children:
   - /why-wasnt-my-application-to-global-campus-for-students-approved
   - /about-github-community-exchange
 shortTitle: About Global Campus for students
-ms.openlocfilehash: 2ee0b90dc4cc25bbd3ac253e22c516ec3984b94a
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: 3f61867f7d7365635a8b2d3bd53a19b0180d0604
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: zh-CN
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147574206'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148108218'
 ---
 
diff --git a/translations/zh-CN/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-teachers/about-github-global-campus-for-teachers.md b/translations/zh-CN/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-teachers/about-github-global-campus-for-teachers.md
index cb3449b90c..df8cabc004 100644
--- a/translations/zh-CN/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-teachers/about-github-global-campus-for-teachers.md
+++ b/translations/zh-CN/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-teachers/about-github-global-campus-for-teachers.md
@@ -10,12 +10,12 @@ redirect_from:
 versions:
   fpt: '*'
 shortTitle: For teachers
-ms.openlocfilehash: d4e823cc97b9c75f264b856c39021e30ca0e4fed
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: 6a0e8b7ba27060b4f48438b515786256d93d6d0c
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: zh-CN
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147574167'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148108052'
 ---
 作为认证教育机构的教职员工，你可以申请 {% data variables.product.prodname_global_campus %}，其中包括 {% data variables.product.prodname_education %} 权益和资源。 有关详细信息，请参阅“[以教师身份申请加入 {% data variables.product.prodname_global_campus %}](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-teachers/apply-to-github-global-campus-as-a-teacher)”。
 
diff --git a/translations/zh-CN/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-teachers/index.md b/translations/zh-CN/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-teachers/index.md
index 40729287ee..4d6064f214 100644
--- a/translations/zh-CN/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-teachers/index.md
+++ b/translations/zh-CN/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-teachers/index.md
@@ -13,11 +13,11 @@ children:
   - /apply-to-github-global-campus-as-a-teacher
   - why-wasnt-my-application-to-global-campus-for-teachers-approved
 shortTitle: About Global Campus for teachers
-ms.openlocfilehash: f257ff9da81c99c87caf8f864e621cb7e382974d
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: b29cc4c76f0eb407dafb4080061f7f8a4c9cf62b
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: zh-CN
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147574176'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148108054'
 ---
 
diff --git a/translations/zh-CN/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-teachers/why-wasnt-my-application-to-global-campus-for-teachers-approved.md b/translations/zh-CN/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-teachers/why-wasnt-my-application-to-global-campus-for-teachers-approved.md
index acfda2ae24..a442f84c3b 100644
--- a/translations/zh-CN/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-teachers/why-wasnt-my-application-to-global-campus-for-teachers-approved.md
+++ b/translations/zh-CN/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-teachers/why-wasnt-my-application-to-global-campus-for-teachers-approved.md
@@ -12,12 +12,12 @@ redirect_from:
 versions:
   fpt: '*'
 shortTitle: Application not approved
-ms.openlocfilehash: 86d1f0c3bc1bfe451be611ce47cc3f715fd8ba92
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: 68fe0a970c94a73293505849425bc78ec78b265e
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: zh-CN
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147574175'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148108053'
 ---
 {% tip %}
 
diff --git a/translations/zh-CN/content/get-started/learning-about-github/about-github-advanced-security.md b/translations/zh-CN/content/get-started/learning-about-github/about-github-advanced-security.md
index 401194125d..7f2ad08c68 100644
--- a/translations/zh-CN/content/get-started/learning-about-github/about-github-advanced-security.md
+++ b/translations/zh-CN/content/get-started/learning-about-github/about-github-advanced-security.md
@@ -51,7 +51,7 @@ For information about {% data variables.product.prodname_advanced_security %} fe
 {% 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. {% 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 %}
 
-{% ifversion ghes > 3.1 or ghec or ghae %}
+{% ifversion ghes or ghec or ghae %}
 ## 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 and to review the rollout phases we recommended, see "[Adopting {% data variables.product.prodname_GH_advanced_security %} at scale](/code-security/adopting-github-advanced-security-at-scale)."
diff --git a/translations/zh-CN/content/get-started/quickstart/communicating-on-github.md b/translations/zh-CN/content/get-started/quickstart/communicating-on-github.md
index 746d67c59d..4681320f39 100644
--- a/translations/zh-CN/content/get-started/quickstart/communicating-on-github.md
+++ b/translations/zh-CN/content/get-started/quickstart/communicating-on-github.md
@@ -151,4 +151,4 @@ For {% data variables.product.prodname_discussions %}, you can{% ifversion fpt o
 
 For team discussions, you can edit or delete discussions on a team's page, and you can configure notifications for team discussions. For more information, see "[About team discussions](/organizations/collaborating-with-your-team/about-team-discussions)."
 
-To learn some advanced formatting features that will help you communicate, see "[Quickstart for writing on {% data variables.product.prodname_dotcom %}](/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/quickstart-for-writing-on-github)."
\ No newline at end of file
+To learn some advanced formatting features that will help you communicate, see "[Quickstart for writing on {% data variables.product.prodname_dotcom %}](/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/quickstart-for-writing-on-github)."
diff --git a/translations/zh-CN/content/get-started/quickstart/contributing-to-projects.md b/translations/zh-CN/content/get-started/quickstart/contributing-to-projects.md
index b90de8630e..4bd5001966 100644
--- a/translations/zh-CN/content/get-started/quickstart/contributing-to-projects.md
+++ b/translations/zh-CN/content/get-started/quickstart/contributing-to-projects.md
@@ -26,7 +26,7 @@ This tutorial uses [the Spoon-Knife project](https://github.com/octocat/Spoon-Kn
 
 1. Navigate to the `Spoon-Knife` project at https://github.com/octocat/Spoon-Knife.
 2. Click **Fork**.
-   ![Fork button](/assets/images/help/repository/fork_button.png)
+   ![Fork button](/assets/images/help/repository/fork_button.png){% ifversion fpt or ghec or ghes > 3.5 or ghae > 3.5 %}
 3. Select an owner for the forked repository.
    ![Create a new fork page with owner dropdown emphasized](/assets/images/help/repository/fork-choose-owner.png)
 4. By default, forks are named the same as their parent repositories. You can change the name of the fork to distinguish it further. 
@@ -43,6 +43,7 @@ This tutorial uses [the Spoon-Knife project](https://github.com/octocat/Spoon-Kn
 **Note:** If you want to copy additional branches from the parent repository, you can do so from the **Branches** page. For more information, see "[Creating and deleting branches within your repository](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository)."
 
 {% endnote %}
+{% endif %}
 
 ## Cloning a fork
 
diff --git a/translations/zh-CN/content/get-started/quickstart/fork-a-repo.md b/translations/zh-CN/content/get-started/quickstart/fork-a-repo.md
index ad5ed4621b..a8107f1dd2 100644
--- a/translations/zh-CN/content/get-started/quickstart/fork-a-repo.md
+++ b/translations/zh-CN/content/get-started/quickstart/fork-a-repo.md
@@ -57,7 +57,7 @@ You might fork a project to propose changes to the upstream, or original, reposi
 
 1. On {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom_the_website %}{% else %}{% data variables.location.product_location %}{% endif %}, navigate to the [octocat/Spoon-Knife](https://github.com/octocat/Spoon-Knife) repository.
 2. In the top-right corner of the page, click **Fork**.
-   ![Fork button](/assets/images/help/repository/fork_button.png)
+   ![Fork button](/assets/images/help/repository/fork_button.png){% ifversion fpt or ghec or ghes > 3.5 or ghae > 3.5 %}
 3. Select an owner for the forked repository.
    ![Create a new fork page with owner dropdown emphasized](/assets/images/help/repository/fork-choose-owner.png)
 4. By default, forks are named the same as their parent repositories. You can change the name of the fork to distinguish it further. 
@@ -72,7 +72,7 @@ You might fork a project to propose changes to the upstream, or original, reposi
 
 {% note %}
 
-**Note:** If you want to copy additional branches from the parent repository, you can do so from the **Branches** page. For more information, see "[Creating and deleting branches within your repository](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository)."{% endnote %}
+**Note:** If you want to copy additional branches from the parent repository, you can do so from the **Branches** page. For more information, see "[Creating and deleting branches within your repository](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository)."{% endnote %}{% endif %}
 
 {% endwebui %}
 
diff --git a/translations/zh-CN/content/get-started/using-github/keyboard-shortcuts.md b/translations/zh-CN/content/get-started/using-github/keyboard-shortcuts.md
index 63db7352b5..416cf4f6d1 100644
--- a/translations/zh-CN/content/get-started/using-github/keyboard-shortcuts.md
+++ b/translations/zh-CN/content/get-started/using-github/keyboard-shortcuts.md
@@ -94,13 +94,13 @@ For more keyboard shortcuts, see the [CodeMirror documentation](https://codemirr
 |<kbd>Command</kbd>+<kbd>K</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>K</kbd> (Windows/Linux) | Inserts Markdown formatting for creating a link{% endif %}{% ifversion fpt or ghae > 3.5 or ghes > 3.5 or ghec %}
 |<kbd>Command</kbd>+<kbd>V</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>V</kbd> (Windows/Linux) | Creates a Markdown link when applied over highlighted text{% endif %}
 |<kbd>Command</kbd>+<kbd>Shift</kbd>+<kbd>P</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>P</kbd> (Windows/Linux) | Toggles between the **Write** and **Preview** comment tabs{% ifversion fpt or ghae or ghes > 3.4 or ghec %}
-|<kbd>Command</kbd>+<kbd>Shift</kbd>+<kbd>V</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>V</kbd> (Windows/Linux) | Pastes HTML link as plain text{% endif %}{% ifversion fpt or ghae or ghes > 3.2 or ghec %}
-|<kbd>Command</kbd>+<kbd>Shift</kbd>+<kbd>Option</kbd>+<kbd>V</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>Alt</kbd>+<kbd>V</kbd> (Windows/Linux) | Pastes HTML link as plain text{% endif %}{% ifversion fpt or ghae or ghes > 3.2 or ghec %}
+|<kbd>Command</kbd>+<kbd>Shift</kbd>+<kbd>V</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>V</kbd> (Windows/Linux) | Pastes HTML link as plain text{% endif %}
+|<kbd>Command</kbd>+<kbd>Shift</kbd>+<kbd>Option</kbd>+<kbd>V</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>Alt</kbd>+<kbd>V</kbd> (Windows/Linux) | Pastes HTML link as plain text
 |<kbd>Command</kbd>+<kbd>Shift</kbd>+<kbd>7</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>7</kbd> (Windows/Linux) | Inserts Markdown formatting for an ordered list
-|<kbd>Command</kbd>+<kbd>Shift</kbd>+<kbd>8</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>8</kbd> (Windows/Linux) | Inserts Markdown formatting for an unordered list{% endif %}
+|<kbd>Command</kbd>+<kbd>Shift</kbd>+<kbd>8</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>8</kbd> (Windows/Linux) | Inserts Markdown formatting for an unordered list
 |<kbd>Command</kbd>+<kbd>Enter</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>Enter</kbd> (Windows/Linux) | Submits a comment
-|<kbd>Ctrl</kbd>+<kbd>.</kbd> and then <kbd>Ctrl</kbd>+<kbd>[saved reply number]</kbd> | Opens saved replies menu and then autofills comment field with a saved reply. For more information, see "[About saved replies](/articles/about-saved-replies)."{% ifversion fpt or ghae or ghes > 3.2 or ghec %}
-|<kbd>Command</kbd>+<kbd>Shift</kbd>+<kbd>.</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>.</kbd> (Windows/Linux) | Inserts Markdown formatting for a quote{% endif %}{% ifversion fpt or ghec %}
+|<kbd>Ctrl</kbd>+<kbd>.</kbd> and then <kbd>Ctrl</kbd>+<kbd>[saved reply number]</kbd> | Opens saved replies menu and then autofills comment field with a saved reply. For more information, see "[About saved replies](/articles/about-saved-replies)."
+|<kbd>Command</kbd>+<kbd>Shift</kbd>+<kbd>.</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>.</kbd> (Windows/Linux) | Inserts Markdown formatting for a quote{% ifversion fpt or ghec %}
 |<kbd>Command</kbd>+<kbd>G</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>G</kbd> (Windows/Linux) | Insert a suggestion. For more information, see "[Reviewing proposed changes in a pull request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request)." |{% endif %}
 |<kbd>R</kbd> | Quote the selected text in your reply. For more information, see "[Basic writing and formatting syntax](/articles/basic-writing-and-formatting-syntax#quoting-text)." |
 
diff --git a/translations/zh-CN/content/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax.md b/translations/zh-CN/content/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax.md
index b229b71ca3..5047a0f091 100644
--- a/translations/zh-CN/content/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax.md
+++ b/translations/zh-CN/content/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax.md
@@ -324,7 +324,6 @@ For a full list of available emoji and codes, check out [the Emoji-Cheat-Sheet](
 
 You can create a new paragraph by leaving a blank line between lines of text.
 
-{% ifversion fpt or ghae or ghes > 3.2 or ghec %}
 ## Footnotes
 
 You can add footnotes to your content by using this bracket syntax:
@@ -355,7 +354,6 @@ The footnote will render like this:
 Footnotes are not supported in wikis.
 
 {% endtip %}
-{% endif %}
 
 ## Hiding content with comments
 
@@ -375,14 +373,10 @@ You can tell {% data variables.product.product_name %} to ignore (or escape) Mar
 
 For more information, see Daring Fireball's "[Markdown Syntax](https://daringfireball.net/projects/markdown/syntax#backslash)."
 
-{% ifversion fpt or ghes > 3.2 or ghae or ghec %}
-
 ## Disabling Markdown rendering
 
 {% data reusables.repositories.disabling-markdown-rendering %}
 
-{% endif %}
-
 ## Further reading
 
 - [{% data variables.product.prodname_dotcom %} Flavored Markdown Spec](https://github.github.com/gfm/)
diff --git a/translations/zh-CN/content/graphql/guides/managing-enterprise-accounts.md b/translations/zh-CN/content/graphql/guides/managing-enterprise-accounts.md
index 6c5a8fa020..354bd50661 100644
--- a/translations/zh-CN/content/graphql/guides/managing-enterprise-accounts.md
+++ b/translations/zh-CN/content/graphql/guides/managing-enterprise-accounts.md
@@ -60,8 +60,8 @@ For some example queries, see "[An example query using the Enterprise Accounts A
     - `admin:enterprise`
 
   The enterprise account specific scopes are:
-    - `admin:enterprise`: Gives full control of enterprises (includes {% ifversion ghes > 3.2 or ghae or ghec %}`manage_runners:enterprise`, {% endif %}`manage_billing:enterprise` and `read:enterprise`)
-    - `manage_billing:enterprise`: Read and write enterprise billing data.{% ifversion ghes > 3.2 or ghae  %}
+    - `admin:enterprise`: Gives full control of enterprises (includes `manage_runners:enterprise`, `manage_billing:enterprise` and `read:enterprise`)
+    - `manage_billing:enterprise`: Read and write enterprise billing data.{% ifversion ghes or ghae %}
     - `manage_runners:enterprise`: Access to manage GitHub Actions enterprise runners and runner-groups.{% endif %}
     - `read:enterprise`: Read enterprise profile data.
 
diff --git a/translations/zh-CN/content/graphql/overview/breaking-changes.md b/translations/zh-CN/content/graphql/overview/breaking-changes.md
index cc778301d3..2e5ab1c88d 100644
--- a/translations/zh-CN/content/graphql/overview/breaking-changes.md
+++ b/translations/zh-CN/content/graphql/overview/breaking-changes.md
@@ -10,12 +10,12 @@ versions:
   ghae: '*'
 topics:
   - API
-ms.openlocfilehash: ee38f60dfd12d00688e46c739fc41f328203daf5
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: c76520b1f9dc806659373771b42501e072319937
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: zh-CN
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147496650'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148108226'
 ---
 ## 关于重大变更
 
diff --git a/translations/zh-CN/content/graphql/overview/changelog.md b/translations/zh-CN/content/graphql/overview/changelog.md
index 59182e7931..a1aecff045 100644
--- a/translations/zh-CN/content/graphql/overview/changelog.md
+++ b/translations/zh-CN/content/graphql/overview/changelog.md
@@ -10,11 +10,11 @@ versions:
   ghae: '*'
 topics:
   - API
-ms.openlocfilehash: e5e1fc0708f46759837f29f0eadcaf8abce15220
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: 34f0baed8b75614c939281ed6a2393d7c809c82f
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: zh-CN
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147496546'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148108107'
 ---
 重大变更包括会改变现有查询或可能影响客户端运行时行为的变更。 有关中断性变更列表及其发生时间，请参阅我们的[中断性变更日志](/graphql/overview/breaking-changes)。
diff --git a/translations/zh-CN/content/graphql/overview/schema-previews.md b/translations/zh-CN/content/graphql/overview/schema-previews.md
index 5ac9dbaf96..281375dda4 100644
--- a/translations/zh-CN/content/graphql/overview/schema-previews.md
+++ b/translations/zh-CN/content/graphql/overview/schema-previews.md
@@ -10,12 +10,12 @@ versions:
   ghae: '*'
 topics:
   - API
-ms.openlocfilehash: a4097cd792931fe33363229b24f0043b9b99a1cd
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: 038afd8cbdd60863213eae385ec9a26f707f62d8
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: zh-CN
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147496594'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148108106'
 ---
 ## 关于架构预览
 
diff --git a/translations/zh-CN/content/graphql/reference/enums.md b/translations/zh-CN/content/graphql/reference/enums.md
index ad20e7b08e..5c5a96f34d 100644
--- a/translations/zh-CN/content/graphql/reference/enums.md
+++ b/translations/zh-CN/content/graphql/reference/enums.md
@@ -4,10 +4,10 @@ redirect_from:
   - /v4/enum
   - /v4/reference/enum
 versions:
-  fpt: "*"
-  ghec: "*"
-  ghes: "*"
-  ghae: "*"
+  fpt: '*'
+  ghec: '*'
+  ghes: '*'
+  ghae: '*'
 topics:
   - API
 ---
diff --git a/translations/zh-CN/content/graphql/reference/input-objects.md b/translations/zh-CN/content/graphql/reference/input-objects.md
index 2e2b6f22a9..c2fac85996 100644
--- a/translations/zh-CN/content/graphql/reference/input-objects.md
+++ b/translations/zh-CN/content/graphql/reference/input-objects.md
@@ -4,10 +4,10 @@ redirect_from:
   - /v4/input_object
   - /v4/reference/input_object
 versions:
-  fpt: "*"
-  ghec: "*"
-  ghes: "*"
-  ghae: "*"
+  fpt: '*'
+  ghec: '*'
+  ghes: '*'
+  ghae: '*'
 topics:
   - API
 ---
diff --git a/translations/zh-CN/content/graphql/reference/interfaces.md b/translations/zh-CN/content/graphql/reference/interfaces.md
index 6575e382f5..7834a90307 100644
--- a/translations/zh-CN/content/graphql/reference/interfaces.md
+++ b/translations/zh-CN/content/graphql/reference/interfaces.md
@@ -4,10 +4,10 @@ redirect_from:
   - /v4/interface
   - /v4/reference/interface
 versions:
-  fpt: "*"
-  ghec: "*"
-  ghes: "*"
-  ghae: "*"
+  fpt: '*'
+  ghec: '*'
+  ghes: '*'
+  ghae: '*'
 topics:
   - API
 ---
diff --git a/translations/zh-CN/content/graphql/reference/mutations.md b/translations/zh-CN/content/graphql/reference/mutations.md
index 4fdac19d7f..d92aac569f 100644
--- a/translations/zh-CN/content/graphql/reference/mutations.md
+++ b/translations/zh-CN/content/graphql/reference/mutations.md
@@ -4,10 +4,10 @@ redirect_from:
   - /v4/mutation
   - /v4/reference/mutation
 versions:
-  fpt: "*"
-  ghec: "*"
-  ghes: "*"
-  ghae: "*"
+  fpt: '*'
+  ghec: '*'
+  ghes: '*'
+  ghae: '*'
 topics:
   - API
 ---
diff --git a/translations/zh-CN/content/graphql/reference/objects.md b/translations/zh-CN/content/graphql/reference/objects.md
index 0fd065294c..a843b57912 100644
--- a/translations/zh-CN/content/graphql/reference/objects.md
+++ b/translations/zh-CN/content/graphql/reference/objects.md
@@ -4,10 +4,10 @@ redirect_from:
   - /v4/object
   - /v4/reference/object
 versions:
-  fpt: "*"
-  ghec: "*"
-  ghes: "*"
-  ghae: "*"
+  fpt: '*'
+  ghec: '*'
+  ghes: '*'
+  ghae: '*'
 topics:
   - API
 ---
diff --git a/translations/zh-CN/content/graphql/reference/queries.md b/translations/zh-CN/content/graphql/reference/queries.md
index 6150e75f2e..061fb0324f 100644
--- a/translations/zh-CN/content/graphql/reference/queries.md
+++ b/translations/zh-CN/content/graphql/reference/queries.md
@@ -11,12 +11,12 @@ versions:
   ghae: '*'
 topics:
   - API
-ms.openlocfilehash: 2e4f855c4140193b2d814b937341665e13a535de
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: d5c31e8e00788d2e75f27b0bb161249f01fcfb1d
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: zh-CN
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147496522'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148108103'
 ---
 ## 关于查询
 
diff --git a/translations/zh-CN/content/graphql/reference/scalars.md b/translations/zh-CN/content/graphql/reference/scalars.md
index ca78d28f3d..07e2e2ec2f 100644
--- a/translations/zh-CN/content/graphql/reference/scalars.md
+++ b/translations/zh-CN/content/graphql/reference/scalars.md
@@ -10,12 +10,12 @@ versions:
   ghae: '*'
 topics:
   - API
-ms.openlocfilehash: f52c697c5b9659ff387102756e34cd9a332e882c
-ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.openlocfilehash: 731b2085e9b207298b39b99b4b37907c517b5814
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: zh-CN
-ms.lasthandoff: 09/10/2022
-ms.locfileid: '147877153'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148108715'
 ---
 ## 关于标量
 
diff --git a/translations/zh-CN/content/graphql/reference/unions.md b/translations/zh-CN/content/graphql/reference/unions.md
index 08cac387e2..f0e4e92119 100644
--- a/translations/zh-CN/content/graphql/reference/unions.md
+++ b/translations/zh-CN/content/graphql/reference/unions.md
@@ -4,10 +4,10 @@ redirect_from:
   - /v4/union
   - /v4/reference/union
 versions:
-  fpt: "*"
-  ghec: "*"
-  ghes: "*"
-  ghae: "*"
+  fpt: '*'
+  ghec: '*'
+  ghes: '*'
+  ghae: '*'
 topics:
   - API
 ---
diff --git a/translations/zh-CN/content/index.md b/translations/zh-CN/content/index.md
index edff84a4ad..993dddbd61 100644
--- a/translations/zh-CN/content/index.md
+++ b/translations/zh-CN/content/index.md
@@ -128,11 +128,11 @@ externalProducts:
     name: npm
     href: 'https://docs.npmjs.com/'
     external: true
-ms.openlocfilehash: dfd88a0c13da67bf929a5f5334e73319c04ad394
-ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794
+ms.openlocfilehash: 09ad193360503125adce9c659a465cfae32dd54e
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: zh-CN
-ms.lasthandoff: 09/09/2022
-ms.locfileid: '147643843'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148107627'
 ---
 
diff --git a/translations/zh-CN/content/issues/organizing-your-work-with-project-boards/index.md b/translations/zh-CN/content/issues/organizing-your-work-with-project-boards/index.md
index 97975117d9..f025c2e632 100644
--- a/translations/zh-CN/content/issues/organizing-your-work-with-project-boards/index.md
+++ b/translations/zh-CN/content/issues/organizing-your-work-with-project-boards/index.md
@@ -17,11 +17,11 @@ redirect_from:
   - /tracking-progress-on-your-project-board
   - /filtering-cards-on-a-project-board
   - /archiving-cards-on-a-project-board
-ms.openlocfilehash: c498a1e93008276aebe022dcc53a66086b86def7
-ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d
+ms.openlocfilehash: 5827065f7fe316f4ec8ea41b56be61b1e01943dd
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: zh-CN
-ms.lasthandoff: 09/11/2022
-ms.locfileid: '147422986'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148108102'
 ---
 {% data reusables.projects.project_boards_old %}
diff --git a/translations/zh-CN/content/issues/organizing-your-work-with-project-boards/managing-project-boards/about-automation-for-project-boards.md b/translations/zh-CN/content/issues/organizing-your-work-with-project-boards/managing-project-boards/about-automation-for-project-boards.md
index 5319204d8e..bf89a96f7e 100644
--- a/translations/zh-CN/content/issues/organizing-your-work-with-project-boards/managing-project-boards/about-automation-for-project-boards.md
+++ b/translations/zh-CN/content/issues/organizing-your-work-with-project-boards/managing-project-boards/about-automation-for-project-boards.md
@@ -11,12 +11,12 @@ topics:
   - Pull requests
 shortTitle: 'Automation for {% data variables.product.prodname_projects_v1 %}'
 allowTitleToDifferFromFilename: true
-ms.openlocfilehash: 76cea8f38d7470bd7b6212ae1f93601b5e8c923b
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: 28c4719cca14dff54d971b9a081837c172f4da76
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: zh-CN
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147423338'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148108082'
 ---
 {% data reusables.projects.project_boards_old %}
 
diff --git a/translations/zh-CN/content/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards.md b/translations/zh-CN/content/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards.md
index aa83f058df..1ef5d0831c 100644
--- a/translations/zh-CN/content/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards.md
+++ b/translations/zh-CN/content/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards.md
@@ -1,5 +1,5 @@
 ---
-title: About {% data variables.product.prodname_projects_v1 %}
+title: 'About {% data variables.product.prodname_projects_v1 %}'
 intro: '{% data variables.product.prodname_projects_v1_caps %} on {% data variables.product.product_name %} help you organize and prioritize your work. You can create {% data variables.projects.projects_v1_boards %} for specific feature work, comprehensive roadmaps, or even release checklists. With {% data variables.product.prodname_projects_v1 %}, you have the flexibility to create customized workflows that suit your needs.'
 redirect_from:
   - /github/managing-your-work-on-github/managing-project-boards/about-project-boards
@@ -7,7 +7,7 @@ redirect_from:
   - /articles/about-project-boards
   - /github/managing-your-work-on-github/about-project-boards
 versions:
-  feature: "projects-v1"
+  feature: projects-v1
 topics:
   - Pull requests
 allowTitleToDifferFromFilename: true
diff --git a/translations/zh-CN/content/issues/organizing-your-work-with-project-boards/managing-project-boards/changing-project-board-visibility.md b/translations/zh-CN/content/issues/organizing-your-work-with-project-boards/managing-project-boards/changing-project-board-visibility.md
index 86edb1daf6..03e1987e4d 100644
--- a/translations/zh-CN/content/issues/organizing-your-work-with-project-boards/managing-project-boards/changing-project-board-visibility.md
+++ b/translations/zh-CN/content/issues/organizing-your-work-with-project-boards/managing-project-boards/changing-project-board-visibility.md
@@ -1,6 +1,6 @@
 ---
-title: '更改 {% data variables.product.prodname_project_v1 %} 的可见性'
-intro: '作为组织所有者或 {% data variables.projects.projects_v1_board %} 管理员，你可以将 {% data variables.projects.projects_v1_board %} 设为{% ifversion ghae %}内部{% else %}公共{% endif %}或专用。'
+title: 'Changing {% data variables.product.prodname_project_v1 %} visibility'
+intro: 'As an organization owner or {% data variables.projects.projects_v1_board %} admin, you can make a {% data variables.projects.projects_v1_board %} {% ifversion ghae %}internal{% else %}public{% endif %} or private.'
 redirect_from:
   - /github/managing-your-work-on-github/managing-project-boards/changing-project-board-visibility
   - /articles/changing-project-board-visibility
@@ -11,12 +11,6 @@ topics:
   - Pull requests
 shortTitle: Change visibility
 allowTitleToDifferFromFilename: true
-ms.openlocfilehash: c288e72dccb5c1212e6e01d24197289cc77c18ce
-ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794
-ms.translationtype: HT
-ms.contentlocale: zh-CN
-ms.lasthandoff: 09/09/2022
-ms.locfileid: '147614477'
 ---
 {% data reusables.projects.project_boards_old %}
 
@@ -27,10 +21,12 @@ ms.locfileid: '147614477'
 **{% ifversion classic-project-visibility-permissions %}Notes{% else %}Note{% endif %}:** {% ifversion classic-project-visibility-permissions %}
 
 * {% data reusables.projects.owners-can-limit-visibility-permissions %}
-* {% endif %}将 {% data variables.projects.projects_v1_board %} 设为{% ifversion ghae %}内部{% else %}公共{% endif %}时，组织成员默认获得读取权限。 你可以授予特定组织成员写入或管理员权限，方法是为他们所在的团队授予访问权限或将他们作为协作者添加到 {% data variables.projects.projects_v1_board %}。 有关详细信息，请参阅“[组织的 {% data variables.product.prodname_project_v1_caps %} 权限](/articles/project-board-permissions-for-an-organization)”。
+* {% endif %}When you make your {% data variables.projects.projects_v1_board %} {% ifversion ghae %}internal{% else %}public{% endif %}, organization members are given read access by default. You can give specific organization members write or admin permissions by giving access to teams they're on or by adding them to the {% data variables.projects.projects_v1_board %} as a collaborator. For more information, see "[{% data variables.product.prodname_project_v1_caps %} permissions for an organization](/articles/project-board-permissions-for-an-organization)."
 
 {% endnote %}
 
-1. 导航到要设为{% ifversion ghae %}内部{% else %}公共{% endif %}或专用的项目板。
-{% data reusables.project-management.click-menu %} {% data reusables.project-management.access-collaboration-settings %} {% data reusables.project-management.choose-visibility %}
-1. 单击“保存” 。
+1. Navigate to the project board you want to make {% ifversion ghae %}internal{% else %}public{% endif %} or private.
+{% data reusables.project-management.click-menu %}
+{% data reusables.project-management.access-collaboration-settings %}
+{% data reusables.project-management.choose-visibility %}
+1. Click **Save**.
diff --git a/translations/zh-CN/content/issues/organizing-your-work-with-project-boards/managing-project-boards/closing-a-project-board.md b/translations/zh-CN/content/issues/organizing-your-work-with-project-boards/managing-project-boards/closing-a-project-board.md
index c83df6d077..c6801c44a9 100644
--- a/translations/zh-CN/content/issues/organizing-your-work-with-project-boards/managing-project-boards/closing-a-project-board.md
+++ b/translations/zh-CN/content/issues/organizing-your-work-with-project-boards/managing-project-boards/closing-a-project-board.md
@@ -11,12 +11,12 @@ versions:
 topics:
   - Pull requests
 allowTitleToDifferFromFilename: true
-ms.openlocfilehash: fb62345b404e94ddd5a6a22995b9481c9855914d
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: 21dfb0c6837f97d567f19168cd7f343aac06a4c0
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: zh-CN
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147422706'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148108714'
 ---
 {% data reusables.projects.project_boards_old %}
 
diff --git a/translations/zh-CN/content/issues/organizing-your-work-with-project-boards/managing-project-boards/configuring-automation-for-project-boards.md b/translations/zh-CN/content/issues/organizing-your-work-with-project-boards/managing-project-boards/configuring-automation-for-project-boards.md
index b74779a586..26756e8007 100644
--- a/translations/zh-CN/content/issues/organizing-your-work-with-project-boards/managing-project-boards/configuring-automation-for-project-boards.md
+++ b/translations/zh-CN/content/issues/organizing-your-work-with-project-boards/managing-project-boards/configuring-automation-for-project-boards.md
@@ -15,12 +15,12 @@ topics:
 shortTitle: Configure automation
 type: how_to
 allowTitleToDifferFromFilename: true
-ms.openlocfilehash: 67294015021ef97a8210bff8bbe6c95e352dc26e
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: faf559c3423178b43f3b524bbf3cdc41acd18a92
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: zh-CN
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147422682'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148108711'
 ---
 {% data reusables.projects.project_boards_old %}
 
diff --git a/translations/zh-CN/content/issues/organizing-your-work-with-project-boards/managing-project-boards/copying-a-project-board.md b/translations/zh-CN/content/issues/organizing-your-work-with-project-boards/managing-project-boards/copying-a-project-board.md
index adfdcd2512..2e1aef5aab 100644
--- a/translations/zh-CN/content/issues/organizing-your-work-with-project-boards/managing-project-boards/copying-a-project-board.md
+++ b/translations/zh-CN/content/issues/organizing-your-work-with-project-boards/managing-project-boards/copying-a-project-board.md
@@ -1,6 +1,6 @@
 ---
-title: '复制 {% data variables.product.prodname_project_v1 %}'
-intro: '可以通过复制 {% data variables.projects.projects_v1_board %} 来快速创建新项目。 复制常用或高度自定义的 {% data variables.projects.projects_v1_boards %} 有助于标准化工作流。'
+title: 'Copying a {% data variables.product.prodname_project_v1 %}'
+intro: 'You can copy a {% data variables.projects.projects_v1_board %} to quickly create a new project. Copying frequently used or highly customized {% data variables.projects.projects_v1_boards %} helps standardize your workflow.'
 redirect_from:
   - /github/managing-your-work-on-github/managing-project-boards/copying-a-project-board
   - /articles/copying-a-project-board
@@ -11,34 +11,29 @@ versions:
 topics:
   - Pull requests
 allowTitleToDifferFromFilename: true
-ms.openlocfilehash: 055e697d2bb5c7aa1ad4667d24bbe919ede87a99
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
-ms.translationtype: HT
-ms.contentlocale: zh-CN
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147423602'
 ---
 {% data reusables.projects.project_boards_old %}
 
-通过复制 {% data variables.projects.projects_v1_board %}，可以重复使用 {% data variables.projects.projects_v1_board %} 的标题、说明和自动化配置。 复制 {% data variables.projects.projects_v1_boards %} 可以避免为类似工作流创建新 {% data variables.projects.projects_v1_boards %} 的手动过程。
+Copying a {% data variables.projects.projects_v1_board %} allows you to reuse a {% data variables.projects.projects_v1_board %}'s title, description, and automation configuration. You can copy {% data variables.projects.projects_v1_boards %} to eliminate the manual process of creating new {% data variables.projects.projects_v1_boards %} for similar workflows.
 
-必须对 {% data variables.projects.projects_v1_board %} 具有读取权限才能将其复制到你有写入权限的存储库或组织。
+You must have read access to a {% data variables.projects.projects_v1_board %} to copy it to a repository or organization where you have write access.
 
-将 {% data variables.projects.projects_v1_board %} 复制到组织时，{% data variables.projects.projects_v1_board %} 的可见性将默认为专用，并且可以选择更改可见性。 有关详细信息，请参阅“[更改 {% data variables.product.prodname_project_v1 %} 的可见性](/articles/changing-project-board-visibility/)”。
+When you copy a {% data variables.projects.projects_v1_board %} to an organization, the {% data variables.projects.projects_v1_board %}'s visibility will default to private, with an option to change the visibility. For more information, see "[Changing {% data variables.product.prodname_project_v1 %} visibility](/articles/changing-project-board-visibility/)."
 
-默认情况下也会启用 {% data variables.projects.projects_v1_board %} 的自动化。 有关详细信息，请参阅“[关于 {% data variables.product.prodname_projects_v1 %} 的自动化](/articles/about-automation-for-project-boards/)”。
+A {% data variables.projects.projects_v1_board %}'s automation is also enabled by default. For more information, see "[About automation for {% data variables.product.prodname_projects_v1 %}](/articles/about-automation-for-project-boards/)."
 
-1. 导航到要复制的 {% data variables.projects.projects_v1_board %}。
+1. Navigate to the {% data variables.projects.projects_v1_board %} you want to copy.
 {% data reusables.project-management.click-menu %}
-3. 单击“{% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}”，然后单击“复制”。
-![项目板侧边栏的下拉菜单中的复制选项](/assets/images/help/projects/project-board-copy-setting.png)
-4. 在“Owner（所有者）”下，使用下拉菜单并单击要复制项目板的仓库或组织。
-![从下拉菜单中选择所复制项目板的所有者](/assets/images/help/projects/copied-project-board-owner.png)
-5. （可选）在“项目板名称”下，键入所复制 {% data variables.projects.projects_v1_board %} 的名称。
-![用于键入所复制项目板名称的字段](/assets/images/help/projects/copied-project-board-name.png)
-6. （可选）在“Description（说明）”下，键入其他人将看到的有关所复制项目板的说明。
-![用于键入所复制项目板说明的字段](/assets/images/help/projects/copied-project-board-description.png)
-7. （可选）在“Automation settings（自动化设置）”下，选择是否要复制已配置的自动工作流程。 默认情况下该选项处于启用状态。 有关详细信息，请参阅“[关于项目板的自动化](/articles/about-automation-for-project-boards/)”。
-![为复制的项目板选择自动化设置](/assets/images/help/projects/copied-project-board-automation-settings.png) {% data reusables.project-management.choose-visibility %}
-9. 单击“复制项目”。
-![“确认复制”按钮](/assets/images/help/projects/confirm-copy-project-board.png)
+3. Click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, then click **Copy**.
+![Copy option in drop-down menu from project board sidebar](/assets/images/help/projects/project-board-copy-setting.png)
+4. Under "Owner", use the drop-down menu and click the repository or organization where you want to copy the project board.
+![Select owner of copied project board from drop-down menu](/assets/images/help/projects/copied-project-board-owner.png)
+5. Optionally, under "Project board name", type the name of the copied {% data variables.projects.projects_v1_board %}.
+![Field to type a name for the copied project board](/assets/images/help/projects/copied-project-board-name.png)
+6. Optionally, under "Description", type a description of the copied project board that other people will see.
+![Field to type a description for the copied project board](/assets/images/help/projects/copied-project-board-description.png)
+7. Optionally, under "Automation settings", select whether you want to copy the configured automatic workflows. This option is enabled by default. For more information, see "[About automation for project boards](/articles/about-automation-for-project-boards/)."
+![Select automation settings for copied project board](/assets/images/help/projects/copied-project-board-automation-settings.png)
+{% data reusables.project-management.choose-visibility %}
+9. Click **Copy project**.
+![Confirm Copy button](/assets/images/help/projects/confirm-copy-project-board.png)
diff --git a/translations/zh-CN/content/issues/organizing-your-work-with-project-boards/managing-project-boards/creating-a-project-board.md b/translations/zh-CN/content/issues/organizing-your-work-with-project-boards/managing-project-boards/creating-a-project-board.md
index 1cb5e11790..8c2e267000 100644
--- a/translations/zh-CN/content/issues/organizing-your-work-with-project-boards/managing-project-boards/creating-a-project-board.md
+++ b/translations/zh-CN/content/issues/organizing-your-work-with-project-boards/managing-project-boards/creating-a-project-board.md
@@ -1,6 +1,6 @@
 ---
-title: '创建 {% data variables.product.prodname_project_v1 %}'
-intro: '{% data variables.projects.projects_v1_boards_caps %} 可用于创建自定义工作流以满足你的需求，如对特定的功能工作、全面线路图甚至是发布检查清单进行跟踪和排列优先级。'
+title: 'Creating a {% data variables.product.prodname_project_v1 %}'
+intro: '{% data variables.projects.projects_v1_boards_caps %} can be used to create customized workflows to suit your needs, like tracking and prioritizing specific feature work, comprehensive roadmaps, or even release checklists.'
 redirect_from:
   - /github/managing-your-work-on-github/managing-project-boards/creating-a-project-board
   - /articles/creating-a-project
@@ -15,12 +15,6 @@ topics:
   - Project management
 type: how_to
 allowTitleToDifferFromFilename: true
-ms.openlocfilehash: 9c55be9ea212cf9a09147267fc62da8f6f89fbbc
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
-ms.translationtype: HT
-ms.contentlocale: zh-CN
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147614253'
 ---
 {% data reusables.projects.project_boards_old %}
 
@@ -28,55 +22,94 @@ ms.locfileid: '147614253'
 
 {% data reusables.project-management.copy-project-boards %}
 
-{% data reusables.project-management.link-repos-to-project-board %} 有关详细信息，请参阅“[将存储库链接到 {% data variables.product.prodname_project_v1 %}](/articles/linking-a-repository-to-a-project-board)”。
+{% data reusables.project-management.link-repos-to-project-board %} For more information, see "[Linking a repository to a {% data variables.product.prodname_project_v1 %}
+](/articles/linking-a-repository-to-a-project-board)."
 
-创建 {% data variables.projects.projects_v1_board %} 后，可以向其添加问题、拉取请求和备注。 有关详细信息，请参阅“[将问题和拉取请求添加到 {% data variables.product.prodname_project_v1 %}](/articles/adding-issues-and-pull-requests-to-a-project-board)”和“[将备注添加到 {% data variables.product.prodname_project_v1 %}](/articles/adding-notes-to-a-project-board)”。
+Once you've created your {% data variables.projects.projects_v1_board %}, you can add issues, pull requests, and notes to it. For more information, see "[Adding issues and pull requests to a {% data variables.product.prodname_project_v1 %}](/articles/adding-issues-and-pull-requests-to-a-project-board)" and "[Adding notes to a {% data variables.product.prodname_project_v1 %}](/articles/adding-notes-to-a-project-board)."
 
-还可以配置工作流自动化，使 {% data variables.projects.projects_v1_board %} 与问题和拉取请求的状态保持同步。 有关详细信息，请参阅“[有关 {% data variables.product.prodname_projects_v1 %} 的自动化](/articles/about-automation-for-project-boards)”。
+You can also configure workflow automations to keep your {% data variables.projects.projects_v1_board %} in sync with the status of issues and pull requests. For more information, see "[About automation for {% data variables.product.prodname_projects_v1 %}](/articles/about-automation-for-project-boards)."
 
 {% data reusables.project-management.project-board-import-with-api %}
 
-## 创建用户拥有的 {% data variables.projects.projects_v1_board %}
+## Creating a user-owned {% data variables.projects.projects_v1_board %}
 
 {% data reusables.projects.classic-project-creation %}
 
 {% data reusables.profile.access_profile %}
-2. 在个人资料页面顶部的主导航栏中，单击 {% octicon "project" aria-label="The project board icon" %}“项目”。
-![项目选项卡](/assets/images/help/projects/user-projects-tab.png) {% ifversion projects-v2 %}
-1. 单击“项目(经典)”{% endif %} {% data reusables.project-management.click-new-project %} {% data reusables.project-management.create-project-name-description %} {% data reusables.project-management.choose-template %} {% data reusables.project-management.choose-visibility %} {% data reusables.project-management.linked-repositories %} {% data reusables.project-management.create-project-button %} {% data reusables.project-management.add-column-new-project %} {% data reusables.project-management.name-project-board-column %} {% data reusables.project-management.select-column-preset %} {% data reusables.project-management.select-automation-options-new-column %} {% data reusables.project-management.click-create-column %} {% data reusables.project-management.add-more-columns %}
+2. On the top of your profile page, in the main navigation, click {% octicon "project" aria-label="The project board icon" %} **Projects**.
+![Project tab](/assets/images/help/projects/user-projects-tab.png){% ifversion projects-v2 %}
+1. Click **Projects (classic)**{% endif %}
+{% data reusables.project-management.click-new-project %}
+{% data reusables.project-management.create-project-name-description %}
+{% data reusables.project-management.choose-template %}
+{% data reusables.project-management.choose-visibility %}
+{% data reusables.project-management.linked-repositories %}
+{% data reusables.project-management.create-project-button %}
+{% data reusables.project-management.add-column-new-project %}
+{% data reusables.project-management.name-project-board-column %}
+{% data reusables.project-management.select-column-preset %}
+{% data reusables.project-management.select-automation-options-new-column %}
+{% data reusables.project-management.click-create-column %}
+{% data reusables.project-management.add-more-columns %}
 
 {% data reusables.project-management.edit-project-columns %}
 
-## 创建组织范围内的 {% data variables.projects.projects_v1_board %}
+## Creating an organization-wide {% data variables.projects.projects_v1_board %}
 
 {% data reusables.projects.classic-project-creation %}
 
-{% ifversion classic-project-visibility-permissions %} {% note %}
+{% ifversion classic-project-visibility-permissions %}
+{% note %}
 
-注意：{% data reusables.projects.owners-can-limit-visibility-permissions %}
+**Note:** {% data reusables.projects.owners-can-limit-visibility-permissions %}
 
-{% endnote %} {% endif %}
+{% endnote %}
+{% endif %}
 
-{% data reusables.profile.access_org %} {% data reusables.user-settings.access_org %} {% data reusables.organizations.organization-wide-project %}{% ifversion projects-v2 %}
-1. 单击“项目(经典)”{% endif %} {% data reusables.project-management.click-new-project %} {% data reusables.project-management.create-project-name-description %} {% data reusables.project-management.choose-template %} {% data reusables.project-management.choose-visibility %} {% data reusables.project-management.linked-repositories %} {% data reusables.project-management.create-project-button %} {% data reusables.project-management.add-column-new-project %} {% data reusables.project-management.name-project-board-column %} {% data reusables.project-management.select-column-preset %} {% data reusables.project-management.select-automation-options-new-column %} {% data reusables.project-management.click-create-column %} {% data reusables.project-management.add-more-columns %}
+{% data reusables.profile.access_org %}
+{% data reusables.user-settings.access_org %}
+{% data reusables.organizations.organization-wide-project %}{% ifversion projects-v2 %}
+1. Click **Projects (classic)**{% endif %}
+{% data reusables.project-management.click-new-project %}
+{% data reusables.project-management.create-project-name-description %}
+{% data reusables.project-management.choose-template %}
+{% data reusables.project-management.choose-visibility %}
+{% data reusables.project-management.linked-repositories %}
+{% data reusables.project-management.create-project-button %}
+{% data reusables.project-management.add-column-new-project %}
+{% data reusables.project-management.name-project-board-column %}
+{% data reusables.project-management.select-column-preset %}
+{% data reusables.project-management.select-automation-options-new-column %}
+{% data reusables.project-management.click-create-column %}
+{% data reusables.project-management.add-more-columns %}
 
 {% data reusables.project-management.edit-project-columns %}
 
-## 创建存储库 {% data variables.projects.projects_v1_board %}
+## Creating a repository {% data variables.projects.projects_v1_board %}
 
 {% data reusables.projects.classic-project-creation %}
 
 {% data reusables.repositories.navigate-to-repo %}
-2. 在存储库名称下，单击 {% octicon "project" aria-label="The project board icon" %}“项目”。
-![项目选项卡](/assets/images/help/projects/repo-tabs-projects.png) {% ifversion projects-v2 %}
-1. 单击“项目(经典)”{% endif %} {% data reusables.project-management.click-new-project %} {% data reusables.project-management.create-project-name-description %} {% data reusables.project-management.choose-template %} {% data reusables.project-management.create-project-button %} {% data reusables.project-management.add-column-new-project %} {% data reusables.project-management.name-project-board-column %} {% data reusables.project-management.select-column-preset %} {% data reusables.project-management.select-automation-options-new-column %} {% data reusables.project-management.click-create-column %} {% data reusables.project-management.add-more-columns %}
+2. Under your repository name, click {% octicon "project" aria-label="The project board icon" %} **Projects**.
+![Project tab](/assets/images/help/projects/repo-tabs-projects.png){% ifversion projects-v2 %}
+1. Click **Projects (classic)**{% endif %}
+{% data reusables.project-management.click-new-project %}
+{% data reusables.project-management.create-project-name-description %}
+{% data reusables.project-management.choose-template %}
+{% data reusables.project-management.create-project-button %}
+{% data reusables.project-management.add-column-new-project %}
+{% data reusables.project-management.name-project-board-column %}
+{% data reusables.project-management.select-column-preset %}
+{% data reusables.project-management.select-automation-options-new-column %}
+{% data reusables.project-management.click-create-column %}
+{% data reusables.project-management.add-more-columns %}
 
 {% data reusables.project-management.edit-project-columns %}
 
-## 延伸阅读
+## Further reading
 
-- [关于项目板](/articles/about-project-boards)
-- [编辑项目板](/articles/editing-a-project-board){% ifversion fpt or ghec %}
-- [复制项目板](/articles/copying-a-project-board){% endif %}
-- [关闭项目板](/articles/closing-a-project-board)
-- [关于项目板的自动化](/articles/about-automation-for-project-boards)
+- "[About projects boards](/articles/about-project-boards)"
+- "[Editing a project board](/articles/editing-a-project-board)"{% ifversion fpt or ghec %}
+- "[Copying a project board](/articles/copying-a-project-board)"{% endif %}
+- "[Closing a project board](/articles/closing-a-project-board)"
+- "[About automation for project boards](/articles/about-automation-for-project-boards)"
diff --git a/translations/zh-CN/content/issues/organizing-your-work-with-project-boards/managing-project-boards/deleting-a-project-board.md b/translations/zh-CN/content/issues/organizing-your-work-with-project-boards/managing-project-boards/deleting-a-project-board.md
index dd28952bfe..da94da6f55 100644
--- a/translations/zh-CN/content/issues/organizing-your-work-with-project-boards/managing-project-boards/deleting-a-project-board.md
+++ b/translations/zh-CN/content/issues/organizing-your-work-with-project-boards/managing-project-boards/deleting-a-project-board.md
@@ -11,12 +11,12 @@ versions:
 topics:
   - Pull requests
 allowTitleToDifferFromFilename: true
-ms.openlocfilehash: 13de993715fa8e16f8cbce4555214e7940fb4917
-ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d
+ms.openlocfilehash: fb68b796fa41a565ab2e196f878c17c94ec44a06
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: zh-CN
-ms.lasthandoff: 09/11/2022
-ms.locfileid: '147422970'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148108068'
 ---
 {% data reusables.projects.project_boards_old %}
 
diff --git a/translations/zh-CN/content/issues/organizing-your-work-with-project-boards/managing-project-boards/editing-a-project-board.md b/translations/zh-CN/content/issues/organizing-your-work-with-project-boards/managing-project-boards/editing-a-project-board.md
index 7939c7fcab..1e72b47c19 100644
--- a/translations/zh-CN/content/issues/organizing-your-work-with-project-boards/managing-project-boards/editing-a-project-board.md
+++ b/translations/zh-CN/content/issues/organizing-your-work-with-project-boards/managing-project-boards/editing-a-project-board.md
@@ -12,12 +12,12 @@ versions:
 topics:
   - Pull requests
 allowTitleToDifferFromFilename: true
-ms.openlocfilehash: 23e4958654bd58de323e401ab4b47d1205aaa4ce
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: 9b3811bcd472d44be809681064476e7e4f5bef08
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: zh-CN
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147422954'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148108639'
 ---
 {% data reusables.projects.project_boards_old %}
 
diff --git a/translations/zh-CN/content/issues/organizing-your-work-with-project-boards/managing-project-boards/index.md b/translations/zh-CN/content/issues/organizing-your-work-with-project-boards/managing-project-boards/index.md
index a4f071ebb2..8e007308ff 100644
--- a/translations/zh-CN/content/issues/organizing-your-work-with-project-boards/managing-project-boards/index.md
+++ b/translations/zh-CN/content/issues/organizing-your-work-with-project-boards/managing-project-boards/index.md
@@ -22,11 +22,11 @@ children:
 redirect_from:
   - /github/managing-your-work-on-github/managing-project-boards
 allowTitleToDifferFromFilename: true
-ms.openlocfilehash: a480750b4c44c7934efa6a0a554c1cf7040629de
-ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d
+ms.openlocfilehash: b4034bc9c9ffd29709ac491c6729787c958dd50b
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: zh-CN
-ms.lasthandoff: 09/11/2022
-ms.locfileid: '147422938'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148108642'
 ---
 {% data reusables.projects.project_boards_old %}
diff --git a/translations/zh-CN/content/issues/organizing-your-work-with-project-boards/managing-project-boards/linking-a-repository-to-a-project-board.md b/translations/zh-CN/content/issues/organizing-your-work-with-project-boards/managing-project-boards/linking-a-repository-to-a-project-board.md
index 73a7ba4bc9..aba13ac318 100644
--- a/translations/zh-CN/content/issues/organizing-your-work-with-project-boards/managing-project-boards/linking-a-repository-to-a-project-board.md
+++ b/translations/zh-CN/content/issues/organizing-your-work-with-project-boards/managing-project-boards/linking-a-repository-to-a-project-board.md
@@ -11,12 +11,12 @@ topics:
   - Pull requests
 shortTitle: Link repository to board
 allowTitleToDifferFromFilename: true
-ms.openlocfilehash: 939266bff35928f5b0ae33fe1cce1b380698ee85
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: d0893b64551be80577547b9791e7a7ed6a432de0
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: zh-CN
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147423258'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148108710'
 ---
 {% data reusables.projects.project_boards_old %}
 
diff --git a/translations/zh-CN/content/issues/organizing-your-work-with-project-boards/managing-project-boards/reopening-a-closed-project-board.md b/translations/zh-CN/content/issues/organizing-your-work-with-project-boards/managing-project-boards/reopening-a-closed-project-board.md
index eedb4b5928..b408364190 100644
--- a/translations/zh-CN/content/issues/organizing-your-work-with-project-boards/managing-project-boards/reopening-a-closed-project-board.md
+++ b/translations/zh-CN/content/issues/organizing-your-work-with-project-boards/managing-project-boards/reopening-a-closed-project-board.md
@@ -11,12 +11,12 @@ topics:
   - Pull requests
 shortTitle: 'Reopen {% data variables.product.prodname_project_v1 %}'
 allowTitleToDifferFromFilename: true
-ms.openlocfilehash: d865d4b61000857c943276c45a9ec02163e9f59b
-ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.openlocfilehash: e0101378c0b7049f7cba5e04dd28231a1237d0c5
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: zh-CN
-ms.lasthandoff: 09/11/2022
-ms.locfileid: '147882197'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148108643'
 ---
 {% data reusables.projects.project_boards_old %}
 
diff --git a/translations/zh-CN/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/adding-issues-and-pull-requests-to-a-project-board.md b/translations/zh-CN/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/adding-issues-and-pull-requests-to-a-project-board.md
index 2ab125cd34..416ab22dfa 100644
--- a/translations/zh-CN/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/adding-issues-and-pull-requests-to-a-project-board.md
+++ b/translations/zh-CN/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/adding-issues-and-pull-requests-to-a-project-board.md
@@ -12,12 +12,12 @@ topics:
   - Pull requests
 shortTitle: 'Add issues & PRs to {% data variables.product.prodname_project_v1 %}'
 allowTitleToDifferFromFilename: true
-ms.openlocfilehash: 36897518283fa085c37363157fb44cbd8e1a75c6
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: 3adfb2c337a417b8e4f932ab9ae9860939217c6c
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: zh-CN
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147422770'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148108707'
 ---
 {% data reusables.projects.project_boards_old %}
 
diff --git a/translations/zh-CN/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/adding-notes-to-a-project-board.md b/translations/zh-CN/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/adding-notes-to-a-project-board.md
index e246da0b2b..2dc2b55832 100644
--- a/translations/zh-CN/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/adding-notes-to-a-project-board.md
+++ b/translations/zh-CN/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/adding-notes-to-a-project-board.md
@@ -12,12 +12,12 @@ topics:
   - Pull requests
 shortTitle: 'Add notes to {% data variables.product.prodname_project_v1 %}'
 allowTitleToDifferFromFilename: true
-ms.openlocfilehash: 46068bb6de081043b05c78e731a09e7dbaa47c78
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: fc9df02b211056a08ed608a6c98b9d2f0b78c5b7
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: zh-CN
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147422746'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148108771'
 ---
 {% data reusables.projects.project_boards_old %}
 
diff --git a/translations/zh-CN/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/archiving-cards-on-a-project-board.md b/translations/zh-CN/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/archiving-cards-on-a-project-board.md
index 58813c1998..fd4a1ec02c 100644
--- a/translations/zh-CN/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/archiving-cards-on-a-project-board.md
+++ b/translations/zh-CN/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/archiving-cards-on-a-project-board.md
@@ -11,12 +11,12 @@ topics:
   - Pull requests
 shortTitle: 'Archive cards on {% data variables.product.prodname_project_v1 %}'
 allowTitleToDifferFromFilename: true
-ms.openlocfilehash: de1d0a4981a46c4ceddd73b5d1f49b74f111601f
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: bef90f56a55d6d087c21603586def91ec2f1c9ed
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: zh-CN
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147423586'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148108706'
 ---
 {% data reusables.projects.project_boards_old %}
 
diff --git a/translations/zh-CN/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/filtering-cards-on-a-project-board.md b/translations/zh-CN/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/filtering-cards-on-a-project-board.md
index 6a83d5e507..01bbd2516c 100644
--- a/translations/zh-CN/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/filtering-cards-on-a-project-board.md
+++ b/translations/zh-CN/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/filtering-cards-on-a-project-board.md
@@ -11,12 +11,12 @@ topics:
   - Pull requests
 shortTitle: 'Filter cards on {% data variables.product.prodname_project_v1 %}'
 allowTitleToDifferFromFilename: true
-ms.openlocfilehash: 337c84415fefad0c542c6b46706de716e71c29b9
-ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d
+ms.openlocfilehash: f203785a6fc18dc5f67b2ae62934aa10c2f6e8b8
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: zh-CN
-ms.lasthandoff: 09/11/2022
-ms.locfileid: '147882309'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148108635'
 ---
 {% data reusables.projects.project_boards_old %}
 
diff --git a/translations/zh-CN/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/index.md b/translations/zh-CN/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/index.md
index 81bd7ddff3..279c1d5ce6 100644
--- a/translations/zh-CN/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/index.md
+++ b/translations/zh-CN/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/index.md
@@ -16,11 +16,11 @@ children:
 redirect_from:
   - /github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-project-boards
 allowTitleToDifferFromFilename: true
-ms.openlocfilehash: ba1428a6423198d972abfb6671165b43c4988f94
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: 75699a8c8daa2729de4aaa7389b7e9a0448f09fa
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: zh-CN
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147423618'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148108101'
 ---
 {% data reusables.projects.project_boards_old %}
diff --git a/translations/zh-CN/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/tracking-progress-on-your-project-board.md b/translations/zh-CN/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/tracking-progress-on-your-project-board.md
index 02f8819504..a9a998c509 100644
--- a/translations/zh-CN/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/tracking-progress-on-your-project-board.md
+++ b/translations/zh-CN/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/tracking-progress-on-your-project-board.md
@@ -11,12 +11,12 @@ topics:
   - Pull requests
 shortTitle: 'Track progress on {% data variables.product.prodname_project_v1 %}'
 allowTitleToDifferFromFilename: true
-ms.openlocfilehash: 8dae880cb0ef0fbd0a136e16029688c4aaef08ac
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: 5104029ad5225c217697ea89a4bca8ff2d3fa4b5
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: zh-CN
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147422666'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148108100'
 ---
 {% data reusables.projects.project_boards_old %}
 
diff --git a/translations/zh-CN/content/issues/planning-and-tracking-with-projects/automating-your-project/automating-projects-using-actions.md b/translations/zh-CN/content/issues/planning-and-tracking-with-projects/automating-your-project/automating-projects-using-actions.md
index 3b0e137b23..87e7359893 100644
--- a/translations/zh-CN/content/issues/planning-and-tracking-with-projects/automating-your-project/automating-projects-using-actions.md
+++ b/translations/zh-CN/content/issues/planning-and-tracking-with-projects/automating-your-project/automating-projects-using-actions.md
@@ -1,10 +1,10 @@
 ---
 title: 'Automating {% data variables.product.prodname_projects_v2 %} using Actions'
-shortTitle: 'Automating with Actions'
+shortTitle: Automating with Actions
 intro: 'You can use {% data variables.product.prodname_actions %} to automate your projects.'
 miniTocMaxHeadingLevel: 3
 versions:
-  feature: "projects-v2"
+  feature: projects-v2
 redirect_from:
   - /issues/trying-out-the-new-projects-experience/automating-projects
 type: tutorial
diff --git a/translations/zh-CN/content/issues/planning-and-tracking-with-projects/automating-your-project/index.md b/translations/zh-CN/content/issues/planning-and-tracking-with-projects/automating-your-project/index.md
index 875febbdd6..c730bf385c 100644
--- a/translations/zh-CN/content/issues/planning-and-tracking-with-projects/automating-your-project/index.md
+++ b/translations/zh-CN/content/issues/planning-and-tracking-with-projects/automating-your-project/index.md
@@ -13,11 +13,11 @@ children:
   - /automating-projects-using-actions
   - /archiving-items-automatically
 allowTitleToDifferFromFilename: true
-ms.openlocfilehash: 6c9777a65125f574e4a2cd05a7177448606f8348
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: 9187012a572af445192343af1b1ba121ae442087
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: zh-CN
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147423799'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148107227'
 ---
 
diff --git a/translations/zh-CN/content/issues/planning-and-tracking-with-projects/automating-your-project/using-the-api-to-manage-projects.md b/translations/zh-CN/content/issues/planning-and-tracking-with-projects/automating-your-project/using-the-api-to-manage-projects.md
index afb973e02b..e2b1241fa3 100644
--- a/translations/zh-CN/content/issues/planning-and-tracking-with-projects/automating-your-project/using-the-api-to-manage-projects.md
+++ b/translations/zh-CN/content/issues/planning-and-tracking-with-projects/automating-your-project/using-the-api-to-manage-projects.md
@@ -1,10 +1,10 @@
 ---
 title: 'Using the API to manage {% data variables.product.prodname_projects_v2 %}'
-shortTitle: 'Automating with the API'
-intro: 'You can use the GraphQL API to automate your projects.'
+shortTitle: Automating with the API
+intro: You can use the GraphQL API to automate your projects.
 miniTocMaxHeadingLevel: 3
 versions:
-  feature: "projects-v2"
+  feature: projects-v2
 redirect_from:
   - /issues/trying-out-the-new-projects-experience/using-the-api-to-manage-projects
 type: tutorial
@@ -511,7 +511,7 @@ The response will contain the node ID of the newly created draft issue.
 ```json
 {
   "data": {
-    "addProjectV2ItemById": {
+    "addProjectV2DraftIssue": {
       "projectItem": {
         "id": "PVTI_lADOANN5s84ACbL0zgBbxFc"
       }
diff --git a/translations/zh-CN/content/issues/planning-and-tracking-with-projects/automating-your-project/using-the-built-in-automations.md b/translations/zh-CN/content/issues/planning-and-tracking-with-projects/automating-your-project/using-the-built-in-automations.md
index 406865d04b..95e91a53ea 100644
--- a/translations/zh-CN/content/issues/planning-and-tracking-with-projects/automating-your-project/using-the-built-in-automations.md
+++ b/translations/zh-CN/content/issues/planning-and-tracking-with-projects/automating-your-project/using-the-built-in-automations.md
@@ -8,12 +8,12 @@ versions:
 type: tutorial
 topics:
   - Projects
-ms.openlocfilehash: 950ad805eaf73361c2c790d9e30c2e1708a871d8
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: 40f82bbe99ff036a70007f38534d401a972516f7
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: zh-CN
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147424858'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148108225'
 ---
 {% note %}
 
diff --git a/translations/zh-CN/content/issues/planning-and-tracking-with-projects/creating-projects/creating-a-project.md b/translations/zh-CN/content/issues/planning-and-tracking-with-projects/creating-projects/creating-a-project.md
index a1a4574e4f..020b9b9a4d 100644
--- a/translations/zh-CN/content/issues/planning-and-tracking-with-projects/creating-projects/creating-a-project.md
+++ b/translations/zh-CN/content/issues/planning-and-tracking-with-projects/creating-projects/creating-a-project.md
@@ -10,12 +10,12 @@ type: tutorial
 topics:
   - Projects
 allowTitleToDifferFromFilename: true
-ms.openlocfilehash: 0827845ea3dff3a641d99bbac20b8febdfaca885
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: 6cbe9313866c19e8325bdd34e90c6a39863de515
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: zh-CN
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147423920'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148108223'
 ---
 {% data variables.product.prodname_projects_v2 %} 是与 {% data variables.product.company_short %} 数据保持同步的自适应项集合。 你的项目可以跟踪问题、拉取请求以及你记下的想法。 您可以添加自定义字段并为特定目的创建视图。
 
diff --git a/translations/zh-CN/content/issues/planning-and-tracking-with-projects/creating-projects/index.md b/translations/zh-CN/content/issues/planning-and-tracking-with-projects/creating-projects/index.md
index 9f910cd35b..00888ea916 100644
--- a/translations/zh-CN/content/issues/planning-and-tracking-with-projects/creating-projects/index.md
+++ b/translations/zh-CN/content/issues/planning-and-tracking-with-projects/creating-projects/index.md
@@ -11,11 +11,11 @@ children:
   - /creating-a-project
   - /migrating-from-projects-classic
 allowTitleToDifferFromFilename: true
-ms.openlocfilehash: 3ad98749a0f404446cab9942b8e10883a31bf3ab
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: 4d982f7f1f5fa66f372bcca74cea084cb2497d9c
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: zh-CN
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147423917'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148108224'
 ---
 
diff --git a/translations/zh-CN/content/issues/planning-and-tracking-with-projects/creating-projects/migrating-from-projects-classic.md b/translations/zh-CN/content/issues/planning-and-tracking-with-projects/creating-projects/migrating-from-projects-classic.md
index 7545b1c4c7..3c10aabb59 100644
--- a/translations/zh-CN/content/issues/planning-and-tracking-with-projects/creating-projects/migrating-from-projects-classic.md
+++ b/translations/zh-CN/content/issues/planning-and-tracking-with-projects/creating-projects/migrating-from-projects-classic.md
@@ -1,6 +1,6 @@
 ---
-title: '从 {% data variables.product.prodname_projects_v1 %} 中迁移'
-intro: '可以将 {% data variables.projects.projects_v1_board %} 迁移到新的 {% data variables.product.prodname_projects_v2 %} 体验。'
+title: 'Migrating from {% data variables.product.prodname_projects_v1 %}'
+intro: 'You can migrate your {% data variables.projects.projects_v1_board %} to the new {% data variables.product.prodname_projects_v2 %} experience.'
 miniTocMaxHeadingLevel: 3
 versions:
   feature: projects-v2
@@ -10,53 +10,57 @@ type: tutorial
 topics:
   - Projects
 allowTitleToDifferFromFilename: true
-ms.openlocfilehash: b16235e98306e19a8f08dfc04913c6935772b5cc
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
-ms.translationtype: HT
-ms.contentlocale: zh-CN
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147423916'
 ---
-{% note %}
 
-**注意：**
-
-- 如果你要迁移的项目包含超过 1200 个项，则未结的问题将优先，接着是未解决的拉取请求，然后是注释。 剩余的空间将用于已解决的问题、已合并的请求拉取和已解决的拉取请求。 由于此限制而无法迁移的项将被移动到存档。 如果达到 10,000 个项的存档限制，则不会迁移其他项。
-- 注释卡被转换为草稿问题，内容被保存到草稿问题的正文中。 如果信息出现缺失，请使任何隐藏的字段可见。 有关详细信息，请参阅“[显示和隐藏字段](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/customizing-a-view#showing-and-hiding-fields)”。
-- 不会迁移自动化。
-- 不会迁移会审、存档和活动。
-- 迁移后，新迁移的项目和旧项目不会保持同步。
-
-{% endnote %}
-
-## 关于项目迁移
-
-可以将项目板迁移到新的 {% data variables.product.prodname_projects_v2 %} 体验，并试用表格、多个视图、新的自动化选项和强大的字段类型。 有关详细信息，请参阅“[关于项目](/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)”。
-
-## 迁移组织项目板
-
-{% data reusables.projects.enable-migration %} {% data reusables.profile.access_org %} {% data reusables.user-settings.access_org %} {% data reusables.organizations.organization-wide-project %}
-1. 在左侧，单击“Projects (经典)”。
-  ![显示“Projects (经典)”菜单选项的屏幕截图}](/assets/images/help/issues/projects-classic-org.png) {% data reusables.projects.migrate-project-steps %}
-
-## 迁移用户项目板
-
-{% data reusables.projects.enable-migration %} {% data reusables.profile.access_profile %}
-1. 在个人资料页面顶部的主导航栏中，单击 {% octicon "project" aria-label="The project board icon" %}“项目”。
-![“项目”选项卡](/assets/images/help/projects/user-projects-tab.png)
-1. 在项目列表上方，单击“Projects (经典)”。
-  ![显示“Projects (经典)”菜单选项的屏幕截图}](/assets/images/help/issues/projects-classic-user.png) {% data reusables.projects.migrate-project-steps %}
-
-## 迁移存储库项目板
 
 {% note %}
 
-注意：{% data variables.projects.projects_v2_caps %} 不支持存储库级别的项目。 当你迁移存储库项目板时，它将迁移到拥有存储库项目的组织或个人帐户，并且迁移的项目将被固定到原始存储库。
+**Notes:**
+
+- If the project you are migrating contains more than 1200 items, open issues will be prioritized followed by open pull requests and then notes. Remaining space will be used for closed issues, merged pull requested, and closed pull requests. Items that cannot be migrated due to this limit will be moved to the archive. If the archive limit of 10,000 items is reached, additional items will not be migrated.
+- Note cards are converted to draft issues, and the contents are saved to the body of the draft issue. If information appears to be missing, make any hidden fields visible. For more information, see "[Showing and hiding fields](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/customizing-a-view#showing-and-hiding-fields)."
+- Automation will not be migrated.
+- Triage, archive, and activity will not be migrated.
+- After migration, the new migrated project and old project will not be kept in sync.
 
 {% endnote %}
 
-{% data reusables.projects.enable-migration %} {% data reusables.repositories.navigate-to-repo %}
-1. 在存储库名称下，单击 {% octicon "project" aria-label="The project board icon" %}“项目”。
-![“项目”选项卡](/assets/images/help/projects/repo-tabs-projects.png)
-1. 单击“Projects (经典)”。
-  ![显示“Projects (经典)”菜单选项的屏幕截图}](/assets/images/help/issues/projects-classic-org.png) {% data reusables.projects.migrate-project-steps %}
+## About project migration
+
+You can migrate your project boards to the new {% data variables.product.prodname_projects_v2 %} experience and try out tables, multiple views, new automation options, and powerful field types. For more information, see "[About projects](/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)."
+
+## Migrating an organization project board
+
+{% data reusables.projects.enable-migration %}
+{% data reusables.profile.access_org %}
+{% data reusables.user-settings.access_org %}
+{% data reusables.organizations.organization-wide-project %}
+1. On the left, click **Projects (classic)**.
+  ![Screenshot showing Projects (classic) menu option}](/assets/images/help/issues/projects-classic-org.png)
+{% data reusables.projects.migrate-project-steps %}
+
+## Migrating a user project board
+
+{% data reusables.projects.enable-migration %}
+{% data reusables.profile.access_profile %}
+1. On the top of your profile page, in the main navigation, click {% octicon "project" aria-label="The project board icon" %} **Projects**.
+![Project tab](/assets/images/help/projects/user-projects-tab.png)
+1. Above the list of projects, click **Projects (classic)**.
+  ![Screenshot showing Projects (classic) menu option}](/assets/images/help/issues/projects-classic-user.png)
+{% data reusables.projects.migrate-project-steps %}
+
+## Migrating a repository project board
+
+{% note %}
+
+**Note:** {% data variables.projects.projects_v2_caps %} does not support repository level projects. When you migrate a repository project board, it will migrate to either the organization or personal account that owns the repository project, and the migrated project will be pinned to the original repository.
+
+{% endnote %}
+
+{% data reusables.projects.enable-migration %}
+{% data reusables.repositories.navigate-to-repo %}
+1. Under your repository name, click {% octicon "project" aria-label="The project board icon" %} **Projects**.
+![Project tab](/assets/images/help/projects/repo-tabs-projects.png)
+1. Click **Projects (classic)**.
+  ![Screenshot showing Projects (classic) menu option}](/assets/images/help/issues/projects-classic-org.png)
+{% data reusables.projects.migrate-project-steps %}
diff --git a/translations/zh-CN/content/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/customizing-a-view.md b/translations/zh-CN/content/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/customizing-a-view.md
index 1929b511b2..960ace9738 100644
--- a/translations/zh-CN/content/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/customizing-a-view.md
+++ b/translations/zh-CN/content/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/customizing-a-view.md
@@ -1,9 +1,9 @@
 ---
-title: 'Customizing a view'
+title: Customizing a view
 intro: 'Display the information you need by changing the layout, grouping, sorting in your project.'
 miniTocMaxHeadingLevel: 3
 versions:
-  feature: "projects-v2"
+  feature: projects-v2
 redirect_from:
   - /issues/trying-out-the-new-projects-experience/customizing-your-project-views
 type: tutorial
@@ -147,4 +147,4 @@ In the board layout, you can can choose which columns to display. The available
    
    ![Screenshot showing the list of columns](/assets/images/help/projects-v2/board-select-columns.png)
    
-{% endif %}
\ No newline at end of file
+{% endif %}
diff --git a/translations/zh-CN/content/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/filtering-projects.md b/translations/zh-CN/content/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/filtering-projects.md
index df4dccca83..d28319b816 100644
--- a/translations/zh-CN/content/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/filtering-projects.md
+++ b/translations/zh-CN/content/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/filtering-projects.md
@@ -10,12 +10,12 @@ type: tutorial
 topics:
   - Projects
 allowTitleToDifferFromFilename: true
-ms.openlocfilehash: 820a9b22deab6ecaf7fa06129e2205267b22812c
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: b1c04738a3c03d892b360c3b23def694d202ee0c
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: zh-CN
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147423964'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148108097'
 ---
 可使用筛选器和按项目中的字段来自定义项目元数据的视图，例如代理人和应用于问题的标签。 可以合并筛选并将其保存为视图。 有关详细信息，请参阅“[自定义项目视图](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/customizing-a-view)”。
 
diff --git a/translations/zh-CN/content/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/index.md b/translations/zh-CN/content/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/index.md
index 52dde05cb4..d2bda6de76 100644
--- a/translations/zh-CN/content/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/index.md
+++ b/translations/zh-CN/content/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/index.md
@@ -12,11 +12,11 @@ children:
   - /filtering-projects
   - /managing-your-views
 allowTitleToDifferFromFilename: true
-ms.openlocfilehash: c5a7f7f8aff5ab61a4711f6fbb30f64cf9fea002
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: 10c4aaf54f90773acb1d7a9ed2a8dc186278010e
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: zh-CN
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147423962'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148108098'
 ---
 
diff --git a/translations/zh-CN/content/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/managing-your-views.md b/translations/zh-CN/content/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/managing-your-views.md
index 1c5f086acf..3dd50885ea 100644
--- a/translations/zh-CN/content/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/managing-your-views.md
+++ b/translations/zh-CN/content/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/managing-your-views.md
@@ -7,12 +7,12 @@ versions:
 type: tutorial
 topics:
   - Projects
-ms.openlocfilehash: d434b4b086c1ec8526c3214161ac00d58dced4fd
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: 9b3d7f4b12210841a0c55f3b0b7356da9b225416
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: zh-CN
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147423957'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148108638'
 ---
 ## 创建项目视图
 
diff --git a/translations/zh-CN/content/issues/planning-and-tracking-with-projects/index.md b/translations/zh-CN/content/issues/planning-and-tracking-with-projects/index.md
index a1479fa53a..5f60e750b2 100644
--- a/translations/zh-CN/content/issues/planning-and-tracking-with-projects/index.md
+++ b/translations/zh-CN/content/issues/planning-and-tracking-with-projects/index.md
@@ -19,11 +19,11 @@ children:
 allowTitleToDifferFromFilename: true
 redirect_from:
   - /issues/trying-out-the-new-projects-experience
-ms.openlocfilehash: de9bdc87563e88ac945783bc8e98fd520dfb36ef
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: 80a894cdca5dda3afff3476a8209cb54589c89b5
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: zh-CN
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147425246'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148108634'
 ---
 
diff --git a/translations/zh-CN/content/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects.md b/translations/zh-CN/content/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects.md
index 80dc5f21a4..766afeb063 100644
--- a/translations/zh-CN/content/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects.md
+++ b/translations/zh-CN/content/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects.md
@@ -10,12 +10,12 @@ redirect_from:
 type: overview
 topics:
   - Projects
-ms.openlocfilehash: f50d54b95862102eafe97dcf1dfcec4daa1d7995
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: 4de4e96b6e445a29377c63188f6529c5b2023a5e
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: zh-CN
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147423955'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148108099'
 ---
 ## 关于 {% data variables.product.prodname_projects_v2 %}
 
diff --git a/translations/zh-CN/content/issues/planning-and-tracking-with-projects/learning-about-projects/best-practices-for-projects.md b/translations/zh-CN/content/issues/planning-and-tracking-with-projects/learning-about-projects/best-practices-for-projects.md
index d427bed2f3..bc5b255031 100644
--- a/translations/zh-CN/content/issues/planning-and-tracking-with-projects/learning-about-projects/best-practices-for-projects.md
+++ b/translations/zh-CN/content/issues/planning-and-tracking-with-projects/learning-about-projects/best-practices-for-projects.md
@@ -1,10 +1,10 @@
 ---
 title: 'Best practices for {% data variables.product.prodname_projects_v2 %}'
-intro: 'Learn tips for managing your projects.'
+intro: Learn tips for managing your projects.
 allowTitleToDifferFromFilename: true
 miniTocMaxHeadingLevel: 3
 versions:
-  feature: "projects-v2"
+  feature: projects-v2
 redirect_from:
   - /issues/trying-out-the-new-projects-experience/best-practices-for-managing-projects
 type: overview
diff --git a/translations/zh-CN/content/issues/planning-and-tracking-with-projects/learning-about-projects/index.md b/translations/zh-CN/content/issues/planning-and-tracking-with-projects/learning-about-projects/index.md
index 7cc7dbf2da..b8fac088ec 100644
--- a/translations/zh-CN/content/issues/planning-and-tracking-with-projects/learning-about-projects/index.md
+++ b/translations/zh-CN/content/issues/planning-and-tracking-with-projects/learning-about-projects/index.md
@@ -11,11 +11,11 @@ children:
   - /quickstart-for-projects
   - /best-practices-for-projects
 allowTitleToDifferFromFilename: true
-ms.openlocfilehash: 3bd91ba9dda01dd1dc567cde62336a86b3968260
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: 3629a25866eb08c704ee857ef78140e356202337
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: zh-CN
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147423953'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148108096'
 ---
 
diff --git a/translations/zh-CN/content/issues/planning-and-tracking-with-projects/learning-about-projects/quickstart-for-projects.md b/translations/zh-CN/content/issues/planning-and-tracking-with-projects/learning-about-projects/quickstart-for-projects.md
index fa3f779d43..72335355c0 100644
--- a/translations/zh-CN/content/issues/planning-and-tracking-with-projects/learning-about-projects/quickstart-for-projects.md
+++ b/translations/zh-CN/content/issues/planning-and-tracking-with-projects/learning-about-projects/quickstart-for-projects.md
@@ -10,12 +10,12 @@ redirect_from:
 type: quick_start
 topics:
   - Projects
-ms.openlocfilehash: 165f12f1f76bcc571a7f7c47c33106bad2d6ff42
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: 39798565419acaa831a996a0c86cc62f367f4bb7
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: zh-CN
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147423814'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148108702'
 ---
 ## 简介
 
diff --git a/translations/zh-CN/content/issues/planning-and-tracking-with-projects/managing-items-in-your-project/adding-items-to-your-project.md b/translations/zh-CN/content/issues/planning-and-tracking-with-projects/managing-items-in-your-project/adding-items-to-your-project.md
index 7fc55bb88e..25daa92188 100644
--- a/translations/zh-CN/content/issues/planning-and-tracking-with-projects/managing-items-in-your-project/adding-items-to-your-project.md
+++ b/translations/zh-CN/content/issues/planning-and-tracking-with-projects/managing-items-in-your-project/adding-items-to-your-project.md
@@ -1,10 +1,10 @@
 ---
 title: 'Adding items to your {% data variables.projects.project_v2 %}'
-shortTitle: 'Adding items'
+shortTitle: Adding items
 intro: 'Learn how to add pull requests, issues, and draft issues to your projects individually or in bulk.'
 miniTocMaxHeadingLevel: 4
 versions:
-  feature: "projects-v2"
+  feature: projects-v2
 type: tutorial
 topics:
   - Projects
@@ -83,4 +83,4 @@ Draft issues can have a title, text body, assignees, and any custom fields from
 
 **Note**: Users will not receive notifications when they are assigned to or mentioned in a draft issue unless the draft issue is converted to an issue.
 
-{% endnote %}
\ No newline at end of file
+{% endnote %}
diff --git a/translations/zh-CN/content/issues/planning-and-tracking-with-projects/managing-items-in-your-project/archiving-items-from-your-project.md b/translations/zh-CN/content/issues/planning-and-tracking-with-projects/managing-items-in-your-project/archiving-items-from-your-project.md
index d49c64ef7c..05edecb409 100644
--- a/translations/zh-CN/content/issues/planning-and-tracking-with-projects/managing-items-in-your-project/archiving-items-from-your-project.md
+++ b/translations/zh-CN/content/issues/planning-and-tracking-with-projects/managing-items-in-your-project/archiving-items-from-your-project.md
@@ -1,10 +1,10 @@
 ---
 title: 'Archiving items from your {% data variables.projects.project_v2 %}'
-shortTitle: 'Archiving items'
+shortTitle: Archiving items
 intro: 'You can archive items, keeping them available to restore, or permanently delete them.'
 miniTocMaxHeadingLevel: 2
 versions:
-  feature: "projects-v2"
+  feature: projects-v2
 type: tutorial
 topics:
   - Projects
@@ -45,4 +45,4 @@ You can delete an item to remove it from the project entirely.
 1. Click **Delete from project**.
    ![Screenshot showing delete option](/assets/images/help/projects-v2/delete-menu-item.png)
 1. When prompted, confirm your choice by clicking **Delete**.
-   ![Screenshot showing delete prompt](/assets/images/help/projects-v2/delete-item-prompt.png)
\ No newline at end of file
+   ![Screenshot showing delete prompt](/assets/images/help/projects-v2/delete-item-prompt.png)
diff --git a/translations/zh-CN/content/issues/planning-and-tracking-with-projects/managing-items-in-your-project/converting-draft-issues-to-issues.md b/translations/zh-CN/content/issues/planning-and-tracking-with-projects/managing-items-in-your-project/converting-draft-issues-to-issues.md
index 2e1e594a8b..77210b6a34 100644
--- a/translations/zh-CN/content/issues/planning-and-tracking-with-projects/managing-items-in-your-project/converting-draft-issues-to-issues.md
+++ b/translations/zh-CN/content/issues/planning-and-tracking-with-projects/managing-items-in-your-project/converting-draft-issues-to-issues.md
@@ -8,12 +8,12 @@ versions:
 type: tutorial
 topics:
   - Projects
-ms.openlocfilehash: 22d80acf06957a3ab617e51d0051c75cf42db988
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: 6c956f5453941bdd6b9fbe89191737b1b7f59cec
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: zh-CN
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147423806'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148108095'
 ---
 ## 在表格布局中转换草稿问题
 
diff --git a/translations/zh-CN/content/issues/planning-and-tracking-with-projects/managing-items-in-your-project/index.md b/translations/zh-CN/content/issues/planning-and-tracking-with-projects/managing-items-in-your-project/index.md
index 260c05774d..61dc924cb0 100644
--- a/translations/zh-CN/content/issues/planning-and-tracking-with-projects/managing-items-in-your-project/index.md
+++ b/translations/zh-CN/content/issues/planning-and-tracking-with-projects/managing-items-in-your-project/index.md
@@ -12,11 +12,11 @@ children:
   - /converting-draft-issues-to-issues
   - /archiving-items-from-your-project
 allowTitleToDifferFromFilename: true
-ms.openlocfilehash: 76a77b3ba3cf61b37aaf2b23ae1117951d5b3105
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: 99f64d6e5f4d9cb39771f1ef9f0fae42c36a8cb7
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: zh-CN
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147423803'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148108699'
 ---
 
diff --git a/translations/zh-CN/content/issues/planning-and-tracking-with-projects/managing-your-project/adding-your-project-to-a-repository.md b/translations/zh-CN/content/issues/planning-and-tracking-with-projects/managing-your-project/adding-your-project-to-a-repository.md
index 05c7a550bc..4a25eb1b62 100644
--- a/translations/zh-CN/content/issues/planning-and-tracking-with-projects/managing-your-project/adding-your-project-to-a-repository.md
+++ b/translations/zh-CN/content/issues/planning-and-tracking-with-projects/managing-your-project/adding-your-project-to-a-repository.md
@@ -9,12 +9,12 @@ type: tutorial
 topics:
   - Projects
 allowTitleToDifferFromFilename: true
-ms.openlocfilehash: 58739f4e548985729d01a962e67a12ea0c0b38e9
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: 30486f727a04ccea3b5bfd374a4da3c6367d1cb6
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: zh-CN
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147423952'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148108698'
 ---
 您可以在存储库中列出相关项目。 您只能列出由拥有存储库的同一用户或组织拥有的项目。
 
diff --git a/translations/zh-CN/content/issues/planning-and-tracking-with-projects/managing-your-project/closing-and-deleting-your-projects.md b/translations/zh-CN/content/issues/planning-and-tracking-with-projects/managing-your-project/closing-and-deleting-your-projects.md
index 92a9c177a8..c4a7ebdb4a 100644
--- a/translations/zh-CN/content/issues/planning-and-tracking-with-projects/managing-your-project/closing-and-deleting-your-projects.md
+++ b/translations/zh-CN/content/issues/planning-and-tracking-with-projects/managing-your-project/closing-and-deleting-your-projects.md
@@ -11,12 +11,12 @@ type: tutorial
 topics:
   - Projects
 allowTitleToDifferFromFilename: true
-ms.openlocfilehash: a37980d4d19ca0392fab51dc7e99987e469d2c9a
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: cfd4db85e8bd046e667b108c5c8d8c23102e0d29
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: zh-CN
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147423820'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148108695'
 ---
 ## 删除项目
 
diff --git a/translations/zh-CN/content/issues/planning-and-tracking-with-projects/managing-your-project/index.md b/translations/zh-CN/content/issues/planning-and-tracking-with-projects/managing-your-project/index.md
index fcb8ff6439..774b1e7f14 100644
--- a/translations/zh-CN/content/issues/planning-and-tracking-with-projects/managing-your-project/index.md
+++ b/translations/zh-CN/content/issues/planning-and-tracking-with-projects/managing-your-project/index.md
@@ -13,11 +13,11 @@ children:
   - /adding-your-project-to-a-repository
   - /adding-your-project-to-a-team
 allowTitleToDifferFromFilename: true
-ms.openlocfilehash: ca7c42e8dcb3daf477c70248eb79d12ca9670052
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: c7dd1657bae11e0f43895e946b5e20a209666363
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: zh-CN
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147423812'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148108094'
 ---
 
diff --git a/translations/zh-CN/content/issues/planning-and-tracking-with-projects/managing-your-project/managing-access-to-your-projects.md b/translations/zh-CN/content/issues/planning-and-tracking-with-projects/managing-your-project/managing-access-to-your-projects.md
index e5f823f24e..bda406771e 100644
--- a/translations/zh-CN/content/issues/planning-and-tracking-with-projects/managing-your-project/managing-access-to-your-projects.md
+++ b/translations/zh-CN/content/issues/planning-and-tracking-with-projects/managing-your-project/managing-access-to-your-projects.md
@@ -4,7 +4,7 @@ shortTitle: 'Managing {% data variables.projects.project_v2 %} access'
 intro: 'Learn how to manage team and individual access to your {% data variables.projects.project_v2 %}.'
 miniTocMaxHeadingLevel: 3
 versions:
-  feature: "projects-v2"
+  feature: projects-v2
 redirect_from:
   - /issues/trying-out-the-new-projects-experience/managing-access-to-projects
 type: tutorial
diff --git a/translations/zh-CN/content/issues/planning-and-tracking-with-projects/managing-your-project/managing-visibility-of-your-projects.md b/translations/zh-CN/content/issues/planning-and-tracking-with-projects/managing-your-project/managing-visibility-of-your-projects.md
index d08df1f06c..cccd2301a4 100644
--- a/translations/zh-CN/content/issues/planning-and-tracking-with-projects/managing-your-project/managing-visibility-of-your-projects.md
+++ b/translations/zh-CN/content/issues/planning-and-tracking-with-projects/managing-your-project/managing-visibility-of-your-projects.md
@@ -1,41 +1,46 @@
 ---
-title: 'Managing visibility of your {% data variables.projects.projects_v2 %}'
+title: '管理 {% data variables.projects.projects_v2 %} 的可见性'
 shortTitle: 'Managing {% data variables.projects.project_v2 %} visibility'
-intro: 'Learn about setting your {% data variables.projects.project_v2 %} to private or public visibility.'
+intro: '了解如何将 {% data variables.projects.project_v2 %} 设置为专用或公共可见性。'
 miniTocMaxHeadingLevel: 3
 versions:
-  feature: "projects-v2"
+  feature: projects-v2
 redirect_from:
   - /issues/trying-out-the-new-projects-experience/managing-the-visibility-of-your-projects
 type: tutorial
 topics:
   - Projects
 allowTitleToDifferFromFilename: true
-permissions: 'Organization owners can manage the visibility of project boards in their organization. Organization owners can also allow collaborators with admin permissions to manage project visibility. Visibility of user projects can be managed by the owner of the project and collaborators with admin permissions.'
+permissions: Organization owners can manage the visibility of project boards in their organization. Organization owners can also allow collaborators with admin permissions to manage project visibility. Visibility of user projects can be managed by the owner of the project and collaborators with admin permissions.
+ms.openlocfilehash: fbe4f0943010129b14ace21f6071b99e1160053b
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: zh-CN
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148108770'
 ---
+## 关于项目可见性
 
-## About project visibility
+项目可以是公共的，也可以是专用的。 对于公共项目，互联网上的每个人都可以查看。 对于私有项目，只有被授予至少读取访问权限的用户才能查看。
 
-Projects can be public or private. For public projects, everyone on the internet can view the project. For private projects, only users granted at least read access can see the project.
+只有项目可见性会受影响；要查看项目上的项，必须有人具有该项所属存储库所需的权限。 如果项目包含私有存储库中的项目，则不是存储库协作者的用户将无法查看该存储库中的项。
 
-Only the project visibility is affected; to view an item on the project, someone must have the required permissions for the repository that the item belongs to. If your project includes items from a private repository, people who are not collaborators in the repository will not be able to view items from that repository.
+![包含隐藏项的项目](/assets/images/help/projects/hidden-items.png)
 
-![Project with hidden item](/assets/images/help/projects/hidden-items.png)
+项目管理员和组织所有者可以控制项目可见性。 组织所有者{% ifversion project-visibility-policy %}和企业所有者{% endif %}可以将更改项目可见性的能力仅限于组织所有者。
 
-Project admins and organization owners can control project visibility. Organization owners{% ifversion project-visibility-policy %} and enterprise owners{% endif %} can restrict the ability to change project visibility to just organization owners.
+在公共和专用项目中，见解仅对具有项目写入权限的用户可见。
 
-In public and private projects, insights are only visible to users with write permissions for the project.
+在组织拥有的私有项目中，当前对项目进行更新的用户的头像将显示在项目 UI 中。
 
-In private, organization-owned projects, the avatars of users who are current making updates to the project are displayed in the project UI.
+项目管理员还可以管理对其项目的写入和管理员访问权限，并控制单个用户的读取访问权限。 有关详细信息，请参阅“[管理对项目的访问](/issues/planning-and-tracking-with-projects/managing-your-project/managing-access-to-your-projects)”。
 
-Project admins can also manage write and admin access to their project and control read access for individual users. For more information, see "[Managing access to your projects](/issues/planning-and-tracking-with-projects/managing-your-project/managing-access-to-your-projects)."
-
-## Changing project visibility
+## 更改项目可见性
 
 {% data reusables.projects.project-settings %}
-1. Next to **Visibility** in the "Danger zone", select **Private** or **Public**.
-   ![Screenshot showing the visibility controls](/assets/images/help/projects-v2/visibility.png)
+1. 在“危险区域”的“可见性”旁边，选择“专用”或“公共”  。
+   ![显示可见性控件的屏幕截图](/assets/images/help/projects-v2/visibility.png)
 
-## Further reading
+## 延伸阅读
 
-- [Allowing project visibility changes in your organization](/organizations/managing-organization-settings/allowing-project-visibility-changes-in-your-organization)
\ No newline at end of file
+- [允许在组织中更改项目可见性](/organizations/managing-organization-settings/allowing-project-visibility-changes-in-your-organization)
diff --git a/translations/zh-CN/content/issues/planning-and-tracking-with-projects/understanding-field-types/about-date-fields.md b/translations/zh-CN/content/issues/planning-and-tracking-with-projects/understanding-field-types/about-date-fields.md
index 05e8701a67..163ccc903b 100644
--- a/translations/zh-CN/content/issues/planning-and-tracking-with-projects/understanding-field-types/about-date-fields.md
+++ b/translations/zh-CN/content/issues/planning-and-tracking-with-projects/understanding-field-types/about-date-fields.md
@@ -8,12 +8,12 @@ versions:
 type: tutorial
 topics:
   - Projects
-ms.openlocfilehash: e5cdcbdfbc2e51949c22c27fb1071b6e931ee59a
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: 7c3bc45c036e209e0be682c3b13b9dafcba17885
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: zh-CN
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147423901'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148108691'
 ---
 可以使用 `YYYY-MM-DD` 格式筛选日期值，例如：`date:2022-07-01`。 还可以使用运算符，例如 `>`、`>=`、`<`、`<=` 和 `..`。 例如，`date:>2022-07-01` 和 `date:2022-07-01..2022-07-31`。 还可以提供 `@today` 来表示筛选器中的当前日期。 有关详细信息，请参阅“[筛选项目](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/filtering-projects)”。
 
diff --git a/translations/zh-CN/content/issues/planning-and-tracking-with-projects/understanding-field-types/about-iteration-fields.md b/translations/zh-CN/content/issues/planning-and-tracking-with-projects/understanding-field-types/about-iteration-fields.md
index aa74ed346c..d84ce1ec55 100644
--- a/translations/zh-CN/content/issues/planning-and-tracking-with-projects/understanding-field-types/about-iteration-fields.md
+++ b/translations/zh-CN/content/issues/planning-and-tracking-with-projects/understanding-field-types/about-iteration-fields.md
@@ -10,12 +10,12 @@ redirect_from:
 type: tutorial
 topics:
   - Projects
-ms.openlocfilehash: fe0b02e356023880b03302de93a44273efd135a5
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: 93039327ab7075e0f79c9d5ae5d6652aa635a500
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: zh-CN
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147423802'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148108766'
 ---
 可以创建一个迭代字段，将项与特定的重复时间块相关联。 迭代可以设置为任何时间长度，可以包括中断，并且可以进行单独编辑以修改名称和日期范围。 对于项目，可以按迭代分组，以可视化即将开始的工作的平衡度，使用筛选器专注于单个迭代，并按迭代进行排序。
 
diff --git a/translations/zh-CN/content/issues/planning-and-tracking-with-projects/understanding-field-types/about-single-select-fields.md b/translations/zh-CN/content/issues/planning-and-tracking-with-projects/understanding-field-types/about-single-select-fields.md
index e7bc797893..3062738bce 100644
--- a/translations/zh-CN/content/issues/planning-and-tracking-with-projects/understanding-field-types/about-single-select-fields.md
+++ b/translations/zh-CN/content/issues/planning-and-tracking-with-projects/understanding-field-types/about-single-select-fields.md
@@ -8,12 +8,12 @@ versions:
 type: tutorial
 topics:
   - Projects
-ms.openlocfilehash: 50251608201f6a5e199c235cb0c715449bc99882
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: 1dfb11e43de04bd55f544a9fb97a0a9346a22d96
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: zh-CN
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147423913'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148108165'
 ---
 可以通过指定选项按单选字段进行筛选，例如：`fieldname:option`。 可以通过提供以逗号分隔的选项列表来筛选多个值，例如：`fieldname:option,option`。 有关详细信息，请参阅“[筛选项目](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/filtering-projects)”。
 
diff --git a/translations/zh-CN/content/issues/planning-and-tracking-with-projects/understanding-field-types/about-text-and-number-fields.md b/translations/zh-CN/content/issues/planning-and-tracking-with-projects/understanding-field-types/about-text-and-number-fields.md
index f60315124f..c72139c8e3 100644
--- a/translations/zh-CN/content/issues/planning-and-tracking-with-projects/understanding-field-types/about-text-and-number-fields.md
+++ b/translations/zh-CN/content/issues/planning-and-tracking-with-projects/understanding-field-types/about-text-and-number-fields.md
@@ -8,12 +8,12 @@ versions:
 type: tutorial
 topics:
   - Projects
-ms.openlocfilehash: d6ab274812f4f35ff4f6afa9e1e2139abf86dd54
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: 2ef01bbd4ec13e37fdcd95e2a536e73c6da2304d
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: zh-CN
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147423945'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148108168'
 ---
 可以使用文本字段在项目中包含备注或任何其他自由格式的文本。
 
diff --git a/translations/zh-CN/content/issues/planning-and-tracking-with-projects/understanding-field-types/deleting-fields.md b/translations/zh-CN/content/issues/planning-and-tracking-with-projects/understanding-field-types/deleting-fields.md
index 783aaeec42..2946a60aa0 100644
--- a/translations/zh-CN/content/issues/planning-and-tracking-with-projects/understanding-field-types/deleting-fields.md
+++ b/translations/zh-CN/content/issues/planning-and-tracking-with-projects/understanding-field-types/deleting-fields.md
@@ -7,12 +7,12 @@ versions:
 type: tutorial
 topics:
   - Projects
-ms.openlocfilehash: c0e250a584d596377c5efaa15d06dacf943827a7
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: 2998d4d39a3ec5f59a649fe62fd15c974e1e7ff7
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: zh-CN
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147423932'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148108166'
 ---
 {% data reusables.projects.project-settings %}
 1. 单击希望删除的字段名称。
diff --git a/translations/zh-CN/content/issues/planning-and-tracking-with-projects/understanding-field-types/index.md b/translations/zh-CN/content/issues/planning-and-tracking-with-projects/understanding-field-types/index.md
index f7b86ff905..b1c48d4f98 100644
--- a/translations/zh-CN/content/issues/planning-and-tracking-with-projects/understanding-field-types/index.md
+++ b/translations/zh-CN/content/issues/planning-and-tracking-with-projects/understanding-field-types/index.md
@@ -15,11 +15,11 @@ children:
   - /renaming-fields
   - /deleting-fields
 allowTitleToDifferFromFilename: true
-ms.openlocfilehash: 8b4f48ba1d55d81c571256f48334c54ce3a7e71d
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: eaa9fe7d4dbd6b2c43d0ab2ad12faf173d6f571a
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: zh-CN
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147423796'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148108093'
 ---
 
diff --git a/translations/zh-CN/content/issues/planning-and-tracking-with-projects/understanding-field-types/renaming-fields.md b/translations/zh-CN/content/issues/planning-and-tracking-with-projects/understanding-field-types/renaming-fields.md
index 3e0994dbd7..62d2733b38 100644
--- a/translations/zh-CN/content/issues/planning-and-tracking-with-projects/understanding-field-types/renaming-fields.md
+++ b/translations/zh-CN/content/issues/planning-and-tracking-with-projects/understanding-field-types/renaming-fields.md
@@ -7,12 +7,12 @@ versions:
 type: tutorial
 topics:
   - Projects
-ms.openlocfilehash: ab1373e5bea18c01ba97f37a7e77441d0bb70422
-ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794
+ms.openlocfilehash: a8e43cc14edf9dd0c6838d8f75839a2c0624a7a5
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: zh-CN
-ms.lasthandoff: 09/09/2022
-ms.locfileid: '147717547'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148108121'
 ---
 {% data reusables.projects.project-settings %}
 1. 单击要重命名的字段的名称。
diff --git a/translations/zh-CN/content/issues/planning-and-tracking-with-projects/viewing-insights-from-your-project/about-insights-for-projects.md b/translations/zh-CN/content/issues/planning-and-tracking-with-projects/viewing-insights-from-your-project/about-insights-for-projects.md
index 39278927f1..7d92b09750 100644
--- a/translations/zh-CN/content/issues/planning-and-tracking-with-projects/viewing-insights-from-your-project/about-insights-for-projects.md
+++ b/translations/zh-CN/content/issues/planning-and-tracking-with-projects/viewing-insights-from-your-project/about-insights-for-projects.md
@@ -11,12 +11,12 @@ product: '{% data reusables.gated-features.historical-insights-for-projects %}'
 topics:
   - Projects
 allowTitleToDifferFromFilename: true
-ms.openlocfilehash: a90ec5dfb6aa983b8ffe26c84c4ec6ad01b0471d
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: 89f93ace53547fccd69ffb7e6d7b666a6cb48991
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: zh-CN
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147423801'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148108120'
 ---
 {% ifversion fpt %}
 
diff --git a/translations/zh-CN/content/issues/planning-and-tracking-with-projects/viewing-insights-from-your-project/configuring-charts.md b/translations/zh-CN/content/issues/planning-and-tracking-with-projects/viewing-insights-from-your-project/configuring-charts.md
index 01c6cd4cc1..967c9e88b2 100644
--- a/translations/zh-CN/content/issues/planning-and-tracking-with-projects/viewing-insights-from-your-project/configuring-charts.md
+++ b/translations/zh-CN/content/issues/planning-and-tracking-with-projects/viewing-insights-from-your-project/configuring-charts.md
@@ -8,12 +8,12 @@ type: tutorial
 product: '{% data reusables.gated-features.historical-insights-for-projects %}'
 topics:
   - Projects
-ms.openlocfilehash: 4fffa6ebd196419dc08de7abaf5d85349bd38737
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: dd8f97ac69beb90a511c36ddd0a51f0e16b2d4b3
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: zh-CN
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147423944'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148108119'
 ---
 {% ifversion fpt %}
 
diff --git a/translations/zh-CN/content/issues/planning-and-tracking-with-projects/viewing-insights-from-your-project/creating-charts.md b/translations/zh-CN/content/issues/planning-and-tracking-with-projects/viewing-insights-from-your-project/creating-charts.md
index 6b97f24a67..cde7d9faa4 100644
--- a/translations/zh-CN/content/issues/planning-and-tracking-with-projects/viewing-insights-from-your-project/creating-charts.md
+++ b/translations/zh-CN/content/issues/planning-and-tracking-with-projects/viewing-insights-from-your-project/creating-charts.md
@@ -8,12 +8,12 @@ type: tutorial
 product: '{% data reusables.gated-features.historical-insights-for-projects %}'
 topics:
   - Projects
-ms.openlocfilehash: 1f6a072676480b02bcfbd589f5d4e9011e8e8052
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: c708476decfb76086f32d96d8fc1e085030ae37e
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: zh-CN
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147423795'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148108081'
 ---
 {% data reusables.projects.access-insights %}
 3. 在左侧菜单中，单击“新建图表”。
diff --git a/translations/zh-CN/content/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests.md b/translations/zh-CN/content/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests.md
index adbebde7ee..93e9451968 100644
--- a/translations/zh-CN/content/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests.md
+++ b/translations/zh-CN/content/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests.md
@@ -107,8 +107,8 @@ You can filter a repository's list of pull requests to find:
 - Pull requests that [require a review](/github/administering-a-repository/about-protected-branches#require-pull-request-reviews-before-merging) before they can be merged
 - Pull requests that a reviewer has approved
 - Pull requests in which a reviewer has asked for changes
-- Pull requests that you have reviewed{% ifversion fpt or ghae or ghes > 3.2 or ghec %}
-- Pull requests that someone has asked you directly to review{% endif %}
+- Pull requests that you have reviewed
+- Pull requests that someone has asked you directly to review
 - Pull requests that [someone has asked you, or a team you're a member of, to review](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/requesting-a-pull-request-review)
 
 {% data reusables.repositories.navigate-to-repo %}
@@ -168,7 +168,6 @@ With issue and pull request search terms, you can:
 - Filter issues and pull requests by label: `state:open type:issue label:"bug"`
 - Filter out search terms by using `-` before the term: `state:open type:issue -author:octocat`
 
-{% ifversion fpt or ghes > 3.2 or ghae or ghec %}
 {% tip %}
 
 **Tip:** You can filter issues and pull requests by label using logical OR or using logical AND.
@@ -176,7 +175,6 @@ With issue and pull request search terms, you can:
 - To filter issues using logical AND, use separate label filters: `label:"bug" label:"wip"`.
 
 {% endtip %}
-{% endif %}
 
 For issues, you can also use search to:
 
@@ -190,8 +188,8 @@ For pull requests, you can also use search to:
 - Filter pull requests that a reviewer has approved: `state:open type:pr review:approved`
 - Filter pull requests in which a reviewer has asked for changes: `state:open type:pr review:changes_requested`
 - Filter pull requests by [reviewer](/articles/about-pull-request-reviews/): `state:open type:pr reviewed-by:octocat`
-- Filter pull requests by the specific user [requested for review](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/requesting-a-pull-request-review): `state:open type:pr review-requested:octocat`{% ifversion fpt or ghae or ghes > 3.2 or ghec %}
-- Filter pull requests that someone has asked you directly to review: `state:open type:pr user-review-requested:@me`{% endif %}
+- Filter pull requests by the specific user [requested for review](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/requesting-a-pull-request-review): `state:open type:pr review-requested:octocat`
+- Filter pull requests that someone has asked you directly to review: `state:open type:pr user-review-requested:@me`
 - Filter pull requests by the team requested for review: `state:open type:pr team-review-requested:github/docs`
 - Filter for pull requests that are linked to an issue that the pull request may close: `linked:issue`
 
diff --git a/translations/zh-CN/content/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue.md b/translations/zh-CN/content/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue.md
index 5802070b3c..10b193cadf 100644
--- a/translations/zh-CN/content/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue.md
+++ b/translations/zh-CN/content/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue.md
@@ -1,6 +1,6 @@
 ---
 title: Linking a pull request to an issue
-intro: You can link a pull request {% ifversion link-existing-branches-to-issue %}or branch {% endif %}to an issue to show that a fix is in progress and to automatically close the issue when the pull request {% ifversion link-existing-branches-to-issue %}or branch {% endif %} is merged.
+intro: 'You can link a pull request {% ifversion link-existing-branches-to-issue %}or branch {% endif %}to an issue to show that a fix is in progress and to automatically close the issue when the pull request {% ifversion link-existing-branches-to-issue %}or branch {% endif %} is merged.'
 redirect_from:
   - /github/managing-your-work-on-github/managing-your-work-with-issues-and-pull-requests/linking-a-pull-request-to-an-issue
   - /articles/closing-issues-via-commit-message
diff --git a/translations/zh-CN/content/organizations/collaborating-with-groups-in-organizations/about-organizations.md b/translations/zh-CN/content/organizations/collaborating-with-groups-in-organizations/about-organizations.md
index 0f60e87f35..d107e497eb 100644
--- a/translations/zh-CN/content/organizations/collaborating-with-groups-in-organizations/about-organizations.md
+++ b/translations/zh-CN/content/organizations/collaborating-with-groups-in-organizations/about-organizations.md
@@ -12,12 +12,12 @@ versions:
 topics:
   - Organizations
   - Teams
-ms.openlocfilehash: 3780e309aa149de90a6871fbe236aac752c67d0b
-ms.sourcegitcommit: 5b1461b419dbef60ae9dbdf8e905a4df30fc91b7
+ms.openlocfilehash: 7412c38e647ddec33543bd04d38d813bf6a93c88
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: zh-CN
-ms.lasthandoff: 09/10/2022
-ms.locfileid: '147876103'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148108080'
 ---
 ## 关于组织
 
diff --git a/translations/zh-CN/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-security-and-analysis-settings-for-your-organization.md b/translations/zh-CN/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-security-and-analysis-settings-for-your-organization.md
index 58f47d8e9d..bb75ec8494 100644
--- a/translations/zh-CN/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-security-and-analysis-settings-for-your-organization.md
+++ b/translations/zh-CN/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-security-and-analysis-settings-for-your-organization.md
@@ -70,12 +70,10 @@ You can enable or disable features for all repositories.
    {% 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 %}
+   {% ifversion ghes %}
    !["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.2 %}
-   !["Enable all" or "Disable all" button for "Configure security and analysis" features](/assets/images/enterprise/3.1/help/organizations/security-and-analysis-disable-or-enable-all-ghas.png)
-   {% endif %}
+   
    
    {% ifversion ghae %}
    !["Enable all" or "Disable all" button for "Configure security and analysis" features](/assets/images/enterprise/github-ae/organizations/security-and-analysis-disable-or-enable-all-ghae.png)
@@ -108,17 +106,15 @@ You can enable or disable features for all repositories.
    {% ifversion fpt or ghec %}
    ![Screenshot of a checkbox for enabling a feature for new repositories](/assets/images/help/organizations/security-and-analysis-enable-or-disable-feature-checkbox.png)
    {% endif %}
-  {% ifversion ghes > 3.2 %}
+  {% ifversion ghes %}
    ![Screenshot of a checkbox for enabling a feature for new repositories](/assets/images/enterprise/3.3/organizations/security-and-analysis-enable-or-disable-feature-checkbox.png)
    {% endif %}
-   {% ifversion ghes = 3.2 %}
-   ![Screenshot of a checkbox for enabling a feature for new repositories](/assets/images/enterprise/3.1/help/organizations/security-and-analysis-enable-or-disable-feature-checkbox.png)
-   {% endif %}
+   
    {% ifversion ghae %}
    ![Screenshot of a checkbox for enabling 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 fpt or ghec or ghes %}
 
 ## Allowing {% data variables.product.prodname_dependabot %} to access private dependencies
 
diff --git a/translations/zh-CN/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization.md b/translations/zh-CN/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization.md
index 8ab11cb17b..704456d6fe 100644
--- a/translations/zh-CN/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization.md
+++ b/translations/zh-CN/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization.md
@@ -42,16 +42,16 @@ To search for specific events, use the `action` qualifier in your query. Actions
 | [`auto_approve_personal_access_token_requests`](#auto_approve_personal_access_token_requests-category-actions) | Contains activities related to your organization's approval policy for {% data variables.product.pat_v2 %}s. For more information, see "[Setting a {% data variables.product.pat_generic %} policy for your organization](/organizations/managing-programmatic-access-to-your-organization/setting-a-personal-access-token-policy-for-your-organization)."{% endif %}{% ifversion fpt or ghec %}
 | [`billing`](#billing-category-actions) | Contains all activities related to your organization's billing.{% endif %}{% ifversion fpt or ghec %}
 | [`business`](#business-category-actions) | Contains activities related to business settings for an enterprise. |{% endif %}{% ifversion fpt or ghec %}
-| [`codespaces`](#codespaces-category-actions) | Contains all activities related to your organization's codespaces. |{% endif %}{% ifversion fpt or ghec or ghes > 3.2 or ghae %}
+| [`codespaces`](#codespaces-category-actions) | Contains all activities related to your organization's codespaces. |{% endif %}
 | [`dependabot_alerts`](#dependabot_alerts-category-actions) | Contains organization-level configuration activities for {% data variables.product.prodname_dependabot_alerts %} in existing repositories. For more information, see "[About {% data variables.product.prodname_dependabot_alerts %}](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)."
-| [`dependabot_alerts_new_repos`](#dependabot_alerts_new_repos-category-actions) | Contains organization-level configuration activities for {% data variables.product.prodname_dependabot_alerts %} in new repositories created in the organization.{% endif %}{% ifversion fpt or ghec or ghes > 3.2 %}
+| [`dependabot_alerts_new_repos`](#dependabot_alerts_new_repos-category-actions) | Contains organization-level configuration activities for {% data variables.product.prodname_dependabot_alerts %} in new repositories created in the organization.{% ifversion fpt or ghec or ghes %}
 | [`dependabot_security_updates`](#dependabot_security_updates-category-actions) | Contains organization-level configuration activities for {% data variables.product.prodname_dependabot_security_updates %} in existing repositories. For more information, see "[Configuring {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/configuring-dependabot-security-updates)."
 | [`dependabot_security_updates_new_repos`](#dependabot_security_updates_new_repos-category-actions) | Contains organization-level configuration activities for {% data variables.product.prodname_dependabot_security_updates %} for new repositories created in the organization.{% endif %}{% ifversion fpt or ghec %}
 | [`dependency_graph`](#dependency_graph-category-actions) | Contains organization-level configuration activities for dependency graphs for repositories. For more information, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)."
 | [`dependency_graph_new_repos`](#dependency_graph_new_repos-category-actions) | Contains organization-level configuration activities for new repositories created in the organization.{% endif %}
 | [`discussion_post`](#discussion_post-category-actions) | Contains all activities related to discussions posted to a team page.
 | [`discussion_post_reply`](#discussion_post_reply-category-actions) | Contains all activities related to replies to discussions posted to a team page.{% ifversion fpt or ghes or ghec %}
-| [`enterprise`](#enterprise-category-actions) | Contains activities related to enterprise settings. | {% endif %}
+| [`enterprise`](#enterprise-category-actions) | Contains activities related to enterprise settings. |{% endif %}
 | [`hook`](#hook-category-actions) | Contains all activities related to webhooks.
 | [`integration_installation`](#integration_installation-category-actions)  | Contains activities related to integrations installed in an account. |
 | [`integration_installation_request`](#integration_installation_request-category-actions) | Contains all activities related to organization member requests for owners to approve integrations for use in the organization. |{% ifversion ghec or ghae %}
@@ -77,8 +77,8 @@ To search for specific events, use the `action` qualifier in your query. Actions
 | [`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 %}{% 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 secret-scanning-audit-log-custom-patterns %}
-| [`repository_secret_scanning_custom_pattern`](#respository_secret_scanning_custom_pattern-category-actions) | Contains repository-level activities related to secret scanning custom patterns. For more information, see "[Defining custom patterns for secret scanning](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning)." {% endif %}{% ifversion secret-scanning-audit-log-custom-patterns %}
-| [`repository_secret_scanning_push_protection`](#respository_secret_scanning_push_protection) | Contains repository-level activities related to secret scanning custom patterns. For more information, see "[Protecting pushes with secert scanning](/code-security/secret-scanning/protecting-pushes-with-secret-scanning)." {% endif %}
+| [`repository_secret_scanning_custom_pattern`](#repository_secret_scanning_custom_pattern-category-actions) | Contains repository-level activities related to secret scanning custom patterns. For more information, see "[Defining custom patterns for secret scanning](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning)." {% endif %}{% ifversion secret-scanning-audit-log-custom-patterns %}
+| [`repository_secret_scanning_push_protection`](#repository_secret_scanning_push_protection-category-actions) | Contains repository-level activities related to secret scanning custom patterns. For more information, see "[Protecting pushes with secret scanning](/code-security/secret-scanning/protecting-pushes-with-secret-scanning)." {% endif %}
 | [`repository_vulnerability_alert`](#repository_vulnerability_alert-category-actions) | Contains all activities related to [{% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/about-dependabot-alerts).{% 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 custom-repository-roles %}
 | [`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 %}
@@ -253,7 +253,6 @@ An overview of some of the most common actions that are recorded as events in th
 | `manage_access_and_security` | Triggered when a user updates [which repositories a codespace can access](/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces).
 {% endif %}
 
-{% ifversion fpt or ghec or ghes > 3.2 or ghae %}
 ### `dependabot_alerts` category actions
 
 | Action | Description
@@ -267,9 +266,8 @@ An overview of some of the most common actions that are recorded as events in th
 |------------------|-------------------
 | `disable` | Triggered when an organization owner disables {% data variables.product.prodname_dependabot_alerts %} for all new {% ifversion fpt or ghec %}private {% endif %}repositories. For more information, see "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)."
 | `enable` | Triggered when an organization owner enables {% data variables.product.prodname_dependabot_alerts %} for all new {% ifversion fpt or ghec %}private {% endif %}repositories.
-{% endif %}
 
-{% ifversion fpt or ghec or ghes > 3.2 %}
+{% ifversion fpt or ghec or ghes %}
 ### `dependabot_security_updates` category actions
 
 | Action | Description
@@ -867,4 +865,4 @@ For more information, see "[Managing the publication of {% data variables.produc
 - "[Keeping your organization secure](/articles/keeping-your-organization-secure)"{% ifversion fpt or ghec or ghes > 3.3 or ghae > 3.3 %}
 {%- ifversion fpt or ghec %}
 - "[Exporting member information for your organization](/organizations/managing-membership-in-your-organization/exporting-member-information-for-your-organization)"{% endif %}
-{%- endif %}
\ No newline at end of file
+{%- endif %}
diff --git a/translations/zh-CN/content/organizations/managing-access-to-your-organizations-project-boards/adding-an-outside-collaborator-to-a-project-board-in-your-organization.md b/translations/zh-CN/content/organizations/managing-access-to-your-organizations-project-boards/adding-an-outside-collaborator-to-a-project-board-in-your-organization.md
index a4d2031bd0..228294ab4c 100644
--- a/translations/zh-CN/content/organizations/managing-access-to-your-organizations-project-boards/adding-an-outside-collaborator-to-a-project-board-in-your-organization.md
+++ b/translations/zh-CN/content/organizations/managing-access-to-your-organizations-project-boards/adding-an-outside-collaborator-to-a-project-board-in-your-organization.md
@@ -1,6 +1,6 @@
 ---
-title: '将外部协作者添加到组织中的 {% data variables.product.prodname_project_v1 %}'
-intro: '作为组织所有者或 {% data variables.projects.projects_v1_board %} 管理员，你可以添加外部协作者并自定义他们对 {% data variables.projects.projects_v1_board %} 的访问权限。'
+title: 'Adding an outside collaborator to a {% data variables.product.prodname_project_v1 %} in your organization'
+intro: 'As an organization owner or {% data variables.projects.projects_v1_board %} admin, you can add an outside collaborator and customize their permissions to a {% data variables.projects.projects_v1_board %}.'
 redirect_from:
   - /articles/adding-an-outside-collaborator-to-a-project-board-in-your-organization
   - /github/setting-up-and-managing-organizations-and-teams/adding-an-outside-collaborator-to-a-project-board-in-your-organization
@@ -14,18 +14,21 @@ topics:
   - Teams
 shortTitle: Add a collaborator
 allowTitleToDifferFromFilename: true
-ms.openlocfilehash: 04a8728c1dc38937a00277316e162ead9acb0fef
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
-ms.translationtype: HT
-ms.contentlocale: zh-CN
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147422946'
 ---
+
 {% data reusables.projects.project_boards_old %}
 
-外部协作者并未明确是组织的成员，但对组织的 {% data variables.projects.projects_v1_board %} 具有访问权限。
+An outside collaborator is a person who isn't explicitly a member of your organization, but who has permissions to a {% data variables.projects.projects_v1_board %} in your organization.
 
-{% data reusables.profile.access_org %} {% data reusables.user-settings.access_org %} {% data reusables.organizations.organization-wide-project %}{% ifversion projects-v2 %}
-1. 单击“项目(经典)”{% endif %} {% data reusables.project-management.select-project %} {% data reusables.project-management.click-menu %} {% data reusables.project-management.access-collaboration-settings %} {% data reusables.project-management.collaborator-option %}
-9. 在 "Search by username, full name or email address"（按用户名、全名或电子邮件地址搜索）下，输入外部协作者的姓名、用户名或 {% data variables.product.prodname_dotcom %} 电子邮件地址。
-   ![在“搜索”字段中输入了 Octocat 用户名的“协作者”部分](/assets/images/help/projects/org-project-collaborators-find-name.png) {% data reusables.project-management.add-collaborator %} {% data reusables.project-management.collaborator-permissions %}
+{% data reusables.profile.access_org %}
+{% data reusables.user-settings.access_org %}
+{% data reusables.organizations.organization-wide-project %}{% ifversion projects-v2 %}
+1. Click **Projects (classic)**{% endif %}
+{% data reusables.project-management.select-project %}
+{% data reusables.project-management.click-menu %}
+{% data reusables.project-management.access-collaboration-settings %}
+{% data reusables.project-management.collaborator-option %}
+9. Under "Search by username, full name or email address", type the outside collaborator's name, username, or {% data variables.product.prodname_dotcom %} email.
+   ![The Collaborators section with the Octocat's username entered in the search field](/assets/images/help/projects/org-project-collaborators-find-name.png)
+{% data reusables.project-management.add-collaborator %}
+{% data reusables.project-management.collaborator-permissions %}
diff --git a/translations/zh-CN/content/organizations/managing-access-to-your-organizations-project-boards/index.md b/translations/zh-CN/content/organizations/managing-access-to-your-organizations-project-boards/index.md
index cfe71919dc..39ce742252 100644
--- a/translations/zh-CN/content/organizations/managing-access-to-your-organizations-project-boards/index.md
+++ b/translations/zh-CN/content/organizations/managing-access-to-your-organizations-project-boards/index.md
@@ -22,11 +22,11 @@ children:
   - /removing-an-outside-collaborator-from-an-organization-project-board
 shortTitle: 'Manage {% data variables.product.prodname_project_v1 %} access'
 allowTitleToDifferFromFilename: true
-ms.openlocfilehash: bde0cbf48426b968aae6326e3db7a66fe47fda16
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: ec3c6cdaffc23dcb4df631879d17ec1ca6c1d61b
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: zh-CN
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147422930'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148108033'
 ---
 
diff --git a/translations/zh-CN/content/organizations/managing-access-to-your-organizations-project-boards/managing-access-to-a-project-board-for-organization-members.md b/translations/zh-CN/content/organizations/managing-access-to-your-organizations-project-boards/managing-access-to-a-project-board-for-organization-members.md
index cfd36ae0ca..c17aea1352 100644
--- a/translations/zh-CN/content/organizations/managing-access-to-your-organizations-project-boards/managing-access-to-a-project-board-for-organization-members.md
+++ b/translations/zh-CN/content/organizations/managing-access-to-your-organizations-project-boards/managing-access-to-a-project-board-for-organization-members.md
@@ -1,6 +1,6 @@
 ---
-title: '管理组织成员对 {% data variables.product.prodname_project_v1 %} 的访问权限'
-intro: '组织所有者或 {% data variables.projects.projects_v1_board %} 管理员可以设置所有组织成员对 {% data variables.projects.projects_v1_board %} 的默认权限级别。'
+title: 'Managing access to a {% data variables.product.prodname_project_v1 %} for organization members'
+intro: 'As an organization owner or {% data variables.projects.projects_v1_board %} admin, you can set a default permission level for a {% data variables.projects.projects_v1_board %} for all organization members.'
 redirect_from:
   - /articles/managing-access-to-a-project-board-for-organization-members
   - /github/setting-up-and-managing-organizations-and-teams/managing-access-to-a-project-board-for-organization-members
@@ -14,33 +14,33 @@ topics:
   - Teams
 shortTitle: Manage access for members
 allowTitleToDifferFromFilename: true
-ms.openlocfilehash: fe9d8ebee09d4eb6278545b5561b9691a0468bf5
-ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
-ms.translationtype: HT
-ms.contentlocale: zh-CN
-ms.lasthandoff: 09/10/2022
-ms.locfileid: '147880780'
 ---
+
 {% data reusables.projects.project_boards_old %}
 
-默认情况下，组织成员拥有对其组织的 {% data variables.projects.projects_v1_boards %} 的写权限，除非组织所有者或 {% data variables.projects.projects_v1_board %} 管理员对特定 {% data variables.projects.projects_v1_boards %} 设置不同的权限。
+By default, organization members have write access to their organization's {% data variables.projects.projects_v1_boards %} unless organization owners or {% data variables.projects.projects_v1_board %} admins set different permissions for specific {% data variables.projects.projects_v1_boards %}.
 
-## 为所有组织成员设置基线权限级别
+## Setting a baseline permission level for all organization members
 
 {% tip %}
 
-提示：可向组织成员授予更高的 {% data variables.projects.projects_v1_board %} 权限。 有关详细信息，请参阅“[组织的项目板权限](/articles/project-board-permissions-for-an-organization)”。
+**Tip:** You can give an organization member higher permissions to {% data variables.projects.projects_v1_board %}. For more information, see "[Project board permissions for an organization](/articles/project-board-permissions-for-an-organization)."
 
 {% endtip %}
 
-{% data reusables.profile.access_org %} {% data reusables.user-settings.access_org %} {% data reusables.organizations.organization-wide-project %}{% ifversion projects-v2 %}
-1. 单击“项目(经典)”{% endif %} {% data reusables.project-management.select-project %} {% data reusables.project-management.click-menu %} {% data reusables.project-management.access-collaboration-settings %}
-8. 在“组织成员权限”下，为所有组织成员选择基线权限级别：“读取”、“写入”、“管理员”或“无”   。
-![用于所有组织成员的基线项目板权限选项](/assets/images/help/projects/baseline-project-permissions-for-organization-members.png)
-9. 单击“ **保存**”。
+{% data reusables.profile.access_org %}
+{% data reusables.user-settings.access_org %}
+{% data reusables.organizations.organization-wide-project %}{% ifversion projects-v2 %}
+1. Click **Projects (classic)**{% endif %}
+{% data reusables.project-management.select-project %}
+{% data reusables.project-management.click-menu %}
+{% data reusables.project-management.access-collaboration-settings %}
+8. Under "Organization member permission", choose a baseline permission level for all organization members: **Read**, **Write**, **Admin**, or **None**.
+![Baseline project board permission options for all organization members](/assets/images/help/projects/baseline-project-permissions-for-organization-members.png)
+9. Click **Save**.
 
-## 延伸阅读
+## Further reading
 
-- [管理个人对组织 {% data variables.product.prodname_project_v1 %} 的访问权限](/articles/managing-an-individual-s-access-to-an-organization-project-board)
-- [管理团队对组织 {% data variables.product.prodname_project_v1 %} 的访问权限](/articles/managing-team-access-to-an-organization-project-board)
-- [组织的 {% data variables.product.prodname_project_v1_caps %} 权限](/articles/project-board-permissions-for-an-organization)
+- "[Managing an individual’s access to an organization {% data variables.product.prodname_project_v1 %}](/articles/managing-an-individual-s-access-to-an-organization-project-board)"
+- "[Managing team access to an organization {% data variables.product.prodname_project_v1 %}](/articles/managing-team-access-to-an-organization-project-board)"
+- "[{% data variables.product.prodname_project_v1_caps %} permissions for an organization](/articles/project-board-permissions-for-an-organization)"
diff --git a/translations/zh-CN/content/organizations/managing-access-to-your-organizations-project-boards/managing-an-individuals-access-to-an-organization-project-board.md b/translations/zh-CN/content/organizations/managing-access-to-your-organizations-project-boards/managing-an-individuals-access-to-an-organization-project-board.md
index e8d522b035..adaec974e3 100644
--- a/translations/zh-CN/content/organizations/managing-access-to-your-organizations-project-boards/managing-an-individuals-access-to-an-organization-project-board.md
+++ b/translations/zh-CN/content/organizations/managing-access-to-your-organizations-project-boards/managing-an-individuals-access-to-an-organization-project-board.md
@@ -1,6 +1,6 @@
 ---
-title: '管理个人对组织 {% data variables.product.prodname_project_v1 %} 的访问权限'
-intro: '作为组织所有者或 {% data variables.projects.projects_v1_board %} 管理员，你可以管理单个成员对组织拥有的 {% data variables.projects.projects_v1_board %} 的访问权限。'
+title: 'Managing an individual’s access to an organization {% data variables.product.prodname_project_v1 %}'
+intro: 'As an organization owner or {% data variables.projects.projects_v1_board %} admin, you can manage an individual member''s access to a {% data variables.projects.projects_v1_board %} owned by your organization.'
 redirect_from:
   - /articles/managing-an-individual-s-access-to-an-organization-project-board
   - /articles/managing-an-individuals-access-to-an-organization-project-board
@@ -15,40 +15,57 @@ topics:
   - Teams
 shortTitle: Manage individual access
 allowTitleToDifferFromFilename: true
-ms.openlocfilehash: 3fd77225e83df2124e8e026453b539f6961ff473
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
-ms.translationtype: HT
-ms.contentlocale: zh-CN
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147422890'
 ---
+
 {% data reusables.projects.project_boards_old %}
 
 {% note %}
 
-注意：{% data reusables.project-management.cascading-permissions %} 有关详细信息，请参阅[组织的 {% data variables.product.prodname_project_v1_caps %} 权限](/articles/project-board-permissions-for-an-organization)。 
+**Note:** {% data reusables.project-management.cascading-permissions %} For more information, see "[{% data variables.product.prodname_project_v1_caps %} permissions for an organization](/articles/project-board-permissions-for-an-organization)." 
 
 {% endnote %}
 
-## 授予组织成员访问 {% data variables.projects.projects_v1_board %} 的权限
+## Giving an organization member access to a {% data variables.projects.projects_v1_board %}
 
-{% data reusables.profile.access_org %} {% data reusables.user-settings.access_org %} {% data reusables.organizations.organization-wide-project %}{% ifversion projects-v2 %}
-1. 单击“项目(经典)”{% endif %} {% data reusables.project-management.select-project %} {% data reusables.project-management.click-menu %} {% data reusables.project-management.access-collaboration-settings %} {% data reusables.project-management.collaborator-option %}
-9. 在 "Search by username, full name or email address"（按用户名、全名或电子邮件地址搜索）下，输入协作者的姓名、用户名或 {% data variables.product.prodname_dotcom %} 电子邮件地址。
-   ![在“搜索”字段中输入了 Octocat 用户名的“协作者”部分](/assets/images/help/projects/org-project-collaborators-find-name.png) {% data reusables.project-management.add-collaborator %} {% data reusables.project-management.collaborator-permissions %}
+{% data reusables.profile.access_org %}
+{% data reusables.user-settings.access_org %}
+{% data reusables.organizations.organization-wide-project %}{% ifversion projects-v2 %}
+1. Click **Projects (classic)**{% endif %}
+{% data reusables.project-management.select-project %}
+{% data reusables.project-management.click-menu %}
+{% data reusables.project-management.access-collaboration-settings %}
+{% data reusables.project-management.collaborator-option %}
+9. Under "Search by username, full name or email address", type the collaborator's name, username, or {% data variables.product.prodname_dotcom %} email.
+   ![The Collaborators section with the Octocat's username entered in the search field](/assets/images/help/projects/org-project-collaborators-find-name.png)
+{% data reusables.project-management.add-collaborator %}
+{% data reusables.project-management.collaborator-permissions %}
 
-## 更改组织成员对 {% data variables.projects.projects_v1_board %} 的访问权限
+## Changing an organization member's access to a {% data variables.projects.projects_v1_board %}
 
-{% data reusables.profile.access_org %} {% data reusables.user-settings.access_org %} {% data reusables.organizations.organization-wide-project %}{% ifversion projects-v2 %}
-1. 单击“项目(经典)”{% endif %} {% data reusables.project-management.select-project %} {% data reusables.project-management.click-menu %} {% data reusables.project-management.access-collaboration-settings %} {% data reusables.project-management.collaborator-option %} {% data reusables.project-management.collaborator-permissions %}
+{% data reusables.profile.access_org %}
+{% data reusables.user-settings.access_org %}
+{% data reusables.organizations.organization-wide-project %}{% ifversion projects-v2 %}
+1. Click **Projects (classic)**{% endif %}
+{% data reusables.project-management.select-project %}
+{% data reusables.project-management.click-menu %}
+{% data reusables.project-management.access-collaboration-settings %}
+{% data reusables.project-management.collaborator-option %}
+{% data reusables.project-management.collaborator-permissions %}
 
-## 移除组织成员对 {% data variables.projects.projects_v1_board %} 的访问权限
+## Removing an organization member's access to a {% data variables.projects.projects_v1_board %}
 
-从 {% data variables.projects.projects_v1_board %} 移除协作者时，根据他们其他角色的权限，他们可能仍然保有对板的访问权限。 若要完全移除对 {% data variables.projects.projects_v1_board %} 的访问权限，必须移除其拥有的每个角色的访问权限。 例如，某人可以作为组织成员或团队成员具有 {% data variables.projects.projects_v1_board %} 的访问权限。 有关详细信息，请参阅[组织的 {% data variables.product.prodname_project_v1_caps %} 权限](/articles/project-board-permissions-for-an-organization)。
+When you remove a collaborator from a {% data variables.projects.projects_v1_board %}, they may still retain access to the board based on the permissions they have for other roles. To completely remove access to a {% data variables.projects.projects_v1_board %}, you must remove access for each role the person has. For instance, a person may have access to the {% data variables.projects.projects_v1_board %} as an organization member or team member. For more information, see "[{% data variables.product.prodname_project_v1_caps %} permissions for an organization](/articles/project-board-permissions-for-an-organization)."
 
-{% data reusables.profile.access_org %} {% data reusables.user-settings.access_org %} {% data reusables.organizations.organization-wide-project %}{% ifversion projects-v2 %}
-1. 单击“项目(经典)”{% endif %} {% data reusables.project-management.select-project %} {% data reusables.project-management.click-menu %} {% data reusables.project-management.access-collaboration-settings %} {% data reusables.project-management.collaborator-option %} {% data reusables.project-management.remove-collaborator %}
+{% data reusables.profile.access_org %}
+{% data reusables.user-settings.access_org %}
+{% data reusables.organizations.organization-wide-project %}{% ifversion projects-v2 %}
+1. Click **Projects (classic)**{% endif %}
+{% data reusables.project-management.select-project %}
+{% data reusables.project-management.click-menu %}
+{% data reusables.project-management.access-collaboration-settings %}
+{% data reusables.project-management.collaborator-option %}
+{% data reusables.project-management.remove-collaborator %}
 
-## 延伸阅读
+## Further reading
 
-- [组织的 {% data variables.product.prodname_project_v1_caps %} 权限](/articles/project-board-permissions-for-an-organization)
+- "[{% data variables.product.prodname_project_v1_caps %} permissions for an organization](/articles/project-board-permissions-for-an-organization)"
diff --git a/translations/zh-CN/content/organizations/managing-access-to-your-organizations-project-boards/managing-team-access-to-an-organization-project-board.md b/translations/zh-CN/content/organizations/managing-access-to-your-organizations-project-boards/managing-team-access-to-an-organization-project-board.md
index 522bc91b7a..30b1dbf759 100644
--- a/translations/zh-CN/content/organizations/managing-access-to-your-organizations-project-boards/managing-team-access-to-an-organization-project-board.md
+++ b/translations/zh-CN/content/organizations/managing-access-to-your-organizations-project-boards/managing-team-access-to-an-organization-project-board.md
@@ -1,5 +1,5 @@
 ---
-title: Managing team access to an organization {% data variables.product.prodname_project_v1 %}
+title: 'Managing team access to an organization {% data variables.product.prodname_project_v1 %}'
 intro: 'As an organization owner or {% data variables.projects.projects_v1_board %} admin, you can give a team access to a {% data variables.projects.projects_v1_board %} owned by your organization.'
 redirect_from:
   - /articles/managing-team-access-to-an-organization-project-board
@@ -68,4 +68,4 @@ If a team's access to a {% data variables.projects.projects_v1_board %} is inher
 - [Adding your project to a team](/issues/planning-and-tracking-with-projects/managing-your-project/adding-your-project-to-a-team)
 
 
-{% endif %}
\ No newline at end of file
+{% endif %}
diff --git a/translations/zh-CN/content/organizations/managing-access-to-your-organizations-project-boards/removing-an-outside-collaborator-from-an-organization-project-board.md b/translations/zh-CN/content/organizations/managing-access-to-your-organizations-project-boards/removing-an-outside-collaborator-from-an-organization-project-board.md
index 403407a7e7..fb33b5a98b 100644
--- a/translations/zh-CN/content/organizations/managing-access-to-your-organizations-project-boards/removing-an-outside-collaborator-from-an-organization-project-board.md
+++ b/translations/zh-CN/content/organizations/managing-access-to-your-organizations-project-boards/removing-an-outside-collaborator-from-an-organization-project-board.md
@@ -1,6 +1,6 @@
 ---
-title: '从组织 {% data variables.product.prodname_project_v1 %} 中删除外部协作者'
-intro: '组织所有者或 {% data variables.projects.projects_v1_board %} 管理员可以删除外部协作者对 {% data variables.projects.projects_v1_board %} 的访问权限。'
+title: 'Removing an outside collaborator from an organization {% data variables.product.prodname_project_v1 %}'
+intro: 'As an organization owner or {% data variables.projects.projects_v1_board %} admin, you can remove an outside collaborator''s access to a {% data variables.projects.projects_v1_board %}.'
 redirect_from:
   - /articles/removing-an-outside-collaborator-from-an-organization-project-board
   - /github/setting-up-and-managing-organizations-and-teams/removing-an-outside-collaborator-from-an-organization-project-board
@@ -14,14 +14,16 @@ topics:
   - Teams
 shortTitle: Remove outside collaborator
 allowTitleToDifferFromFilename: true
-ms.openlocfilehash: 2dfcc372565366328820e968d6c6384f97b0e2c1
-ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
-ms.translationtype: HT
-ms.contentlocale: zh-CN
-ms.lasthandoff: 09/11/2022
-ms.locfileid: '147884195'
 ---
+
 {% data reusables.projects.project_boards_old %}
 
-{% data reusables.profile.access_org %} {% data reusables.user-settings.access_org %} {% data reusables.organizations.organization-wide-project %}{% ifversion projects-v2 %}
-1. 单击“项目(经典)”{% endif %} {% data reusables.project-management.select-project %} {% data reusables.project-management.click-menu %} {% data reusables.project-management.access-collaboration-settings %} {% data reusables.project-management.collaborator-option %} {% data reusables.project-management.remove-collaborator %}
+{% data reusables.profile.access_org %}
+{% data reusables.user-settings.access_org %}
+{% data reusables.organizations.organization-wide-project %}{% ifversion projects-v2 %}
+1. Click **Projects (classic)**{% endif %}
+{% data reusables.project-management.select-project %}
+{% data reusables.project-management.click-menu %}
+{% data reusables.project-management.access-collaboration-settings %}
+{% data reusables.project-management.collaborator-option %}
+{% data reusables.project-management.remove-collaborator %}
diff --git a/translations/zh-CN/content/organizations/managing-organization-settings/allowing-project-visibility-changes-in-your-organization.md b/translations/zh-CN/content/organizations/managing-organization-settings/allowing-project-visibility-changes-in-your-organization.md
index 3224a89600..d8de0348ca 100644
--- a/translations/zh-CN/content/organizations/managing-organization-settings/allowing-project-visibility-changes-in-your-organization.md
+++ b/translations/zh-CN/content/organizations/managing-organization-settings/allowing-project-visibility-changes-in-your-organization.md
@@ -1,39 +1,40 @@
 ---
-title: 'Allowing project visibility changes in your organization'
-intro: 'Organization owners can allow members with admin permissions to adjust the visibility of {% data variables.projects.projects_v2_and_v1 %} in their organization.'
+title: 允许在组织中更改项目可见性
+intro: '组织所有者可以允许具有管理员权限的成员调整其组织中 {% data variables.projects.projects_v2_and_v1 %} 的可见性。'
 versions:
-  feature: "classic-project-visibility-permissions-or-projects-v2"
+  feature: classic-project-visibility-permissions-or-projects-v2
 topics:
   - Organizations
   - Projects
-shortTitle: 'Project visibility permissions'
+shortTitle: Project visibility permissions
 allowTitleToDifferFromFilename: true
-permissions: Organization owners can allow {% data variables.projects.project_v2_and_v1 %} visibility changes for an organization.
+permissions: 'Organization owners can allow {% data variables.projects.project_v2_and_v1 %} visibility changes for an organization.'
+ms.openlocfilehash: 5f8963e8c03e2c0a62586964b6331ec7b3d945b5
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: zh-CN
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148108626'
 ---
+## 关于项目的可见性更改
 
-## About visibility changes for projects
+可以限制谁能够更改组织中 {% data variables.projects.projects_v2_and_v1 %} 的可见性，例如限制成员将 {% data variables.projects.projects_v2_and_v1 %} 从专用更改为公共。 
 
-You can restrict who has the ability to change the visibility of {% data variables.projects.projects_v2_and_v1 %} in your organization, such as restricting members from changing {% data variables.projects.projects_v2_and_v1 %} from private to public. 
+可以将更改 {% data variables.projects.project_v2_and_v1 %} 可见性的权限限制为仅限组织所有者，或者可以允许获得管理员权限的任何人来更改可见性。
 
-You can limit the ability to change {% data variables.projects.project_v2_and_v1 %} visibility to just organization owners, or you can allow anyone granted admin permissions to change the visibility.
-
-{% ifversion project-visibility-policy %}
-This option may not be available to you if an enterprise owner restricts visibility changes for {% data variables.projects.projects_v2_and_v1 %} at the enterprise level. For more information, see "[Enforcing policies for projects in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-projects-in-your-enterprise)."
+{% ifversion project-visibility-policy %}如果企业所有者在企业级别限制 {% data variables.projects.projects_v2_and_v1 %} 的可见性更改，则此选项可能不可用。 有关详细信息，请参阅“[在企业中为项目实施策略](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-projects-in-your-enterprise)”。
 {% endif %}
 
-## Allowing members to change project visibilities
+## 允许成员更改项目可见性
 
-{% data reusables.profile.access_org %}
-{% data reusables.profile.org_settings %}
-1. In the "Code, planning, and automation" section of the sidebar, click **{% octicon "table" aria-label="The table icon" %} Projects**.
-1. To allow members to adjust project visibility, select **Allow members to change project visibilities for this organization**.
-  ![Screenshot showing checkbox to set visibility changes](/assets/images/help/projects-v2/visibility-change-checkbox.png)
-1. Click **Save**.
+{% data reusables.profile.access_org %} {% data reusables.profile.org_settings %}
+1. 在侧边栏的“代码、计划和自动化”部分，单击 {% octicon "table" aria-label="The table icon" %}“项目”。
+1. 若要允许成员调整项目可见性，请选择“允许成员更改此组织的项目可见性”。
+  ![显示用于设置可见性更改的复选框的屏幕截图](/assets/images/help/projects-v2/visibility-change-checkbox.png)
+1. 单击“ **保存**”。
 
-## Further reading
+## 延伸阅读
 
 {% ifversion projects-v2 %}
-- "[Managing visibility of your {% data variables.projects.projects_v2 %}](/issues/planning-and-tracking-with-projects/managing-your-project/managing-visibility-of-your-projects)"
-{%- endif %}{%- ifversion projects-v1 %}
-- "[Changing {% data variables.product.prodname_project_v1 %} visibility](/issues/organizing-your-work-with-project-boards/managing-project-boards/changing-project-board-visibility)"
-{% endif %}
\ No newline at end of file
+- "[管理 {% data variables.projects.projects_v2 %} 的可见性](/issues/planning-and-tracking-with-projects/managing-your-project/managing-visibility-of-your-projects)" {%- endif %}{%- ifversion projects-v1 %}
+- "[更改 {% data variables.product.prodname_project_v1 %} 的可见性](/issues/organizing-your-work-with-project-boards/managing-project-boards/changing-project-board-visibility)" {% endif %}
diff --git a/translations/zh-CN/content/organizations/managing-organization-settings/disabling-insights-for-projects-in-your-organization.md b/translations/zh-CN/content/organizations/managing-organization-settings/disabling-insights-for-projects-in-your-organization.md
index e2b436bf2e..c4917b2df2 100644
--- a/translations/zh-CN/content/organizations/managing-organization-settings/disabling-insights-for-projects-in-your-organization.md
+++ b/translations/zh-CN/content/organizations/managing-organization-settings/disabling-insights-for-projects-in-your-organization.md
@@ -8,12 +8,12 @@ topics:
   - Projects
 shortTitle: 'Disable {% data variables.product.prodname_projects_v2 %} insights'
 allowTitleToDifferFromFilename: true
-ms.openlocfilehash: 06ab0f550603e3810bf860f01efe9113766c0fb3
-ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.openlocfilehash: 80a35ea28d90b89c39fb7f9207b2ea950a98a8b6
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: zh-CN
-ms.lasthandoff: 09/11/2022
-ms.locfileid: '147423889'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148108032'
 ---
 为组织中的项目禁用见解后，将无法访问组织拥有的任何项目的见解。
 
diff --git a/translations/zh-CN/content/organizations/managing-organization-settings/index.md b/translations/zh-CN/content/organizations/managing-organization-settings/index.md
index eec29da364..bbdec22fba 100644
--- a/translations/zh-CN/content/organizations/managing-organization-settings/index.md
+++ b/translations/zh-CN/content/organizations/managing-organization-settings/index.md
@@ -45,11 +45,11 @@ children:
   - /disabling-insights-for-projects-in-your-organization
   - /allowing-project-visibility-changes-in-your-organization
 shortTitle: Manage organization settings
-ms.openlocfilehash: 5e89284314ef4f1125ff4ca0843031326e378b0b
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: d19c515ac3d908df15afd8c5741553f7526a6f99
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: zh-CN
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147424742'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148007900'
 ---
 {% ifversion fpt or ghec %} {% endif %}
diff --git a/translations/zh-CN/content/organizations/managing-organization-settings/managing-the-commit-signoff-policy-for-your-organization.md b/translations/zh-CN/content/organizations/managing-organization-settings/managing-the-commit-signoff-policy-for-your-organization.md
index ef4862b062..25ed41ec30 100644
--- a/translations/zh-CN/content/organizations/managing-organization-settings/managing-the-commit-signoff-policy-for-your-organization.md
+++ b/translations/zh-CN/content/organizations/managing-organization-settings/managing-the-commit-signoff-policy-for-your-organization.md
@@ -1,29 +1,26 @@
 ---
-title: 管理组织的提交签核策略
-intro: '你可以要求用户自动签核他们在 {% data variables.product.product_name %} 的 Web 界面中对组织拥有的存储库所做的所有提交。'
+title: Managing the commit signoff policy for your organization
+intro: 'You can require users to automatically sign off all commits they make in {% data variables.product.product_name %}''s web interface to repositories owned by your organization.'
 versions:
   feature: commit-signoffs
 permissions: Organization owners can require all commits to repositories owned by the organization be signed off by the commit author.
 topics:
   - Organizations
 shortTitle: Manage the commit signoff policy
-ms.openlocfilehash: 0d4f2a0fae7db59a7a1f5d8646263e965e9be9ef
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
-ms.translationtype: HT
-ms.contentlocale: zh-CN
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147409771'
 ---
-## 关于提交签核
 
-为了确认提交符合管理存储库的规则和许可，许多组织要求开发人员在每次提交时进行签核。 如果组织需要提交签核，你可以通过为经由 {% data variables.product.product_name %} 的 Web 界面提交的用户启用强制提交签核来使签核成为提交过程中无缝的一部分。 为组织启用强制提交签核后，通过 {% data variables.product.product_name %} 的 Web 界面对该组织中的存储库进行的每个提交都将由提交作者自动签核。
+## About commit signoffs
 
-对存储库具有管理员访问权限的人员还可以在存储库级别启用强制提交签核。 有关详细信息，请参阅“[管理存储库的提交签核策略](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-the-commit-signoff-policy-for-your-repository)”。
+To affirm that a commit complies with the rules and licensing governing a repository, many organizations require developers to sign off on every commit. If your organization requires commit signoffs, you can make signing off a seamless part of the commit process by enabling compulsory commit signoffs for users committing through {% data variables.product.product_name %}'s web interface. After you enable compulsory commit signoffs for an organization, every commit made to repositories in that organization through {% data variables.product.product_name %}'s web interface will automatically be signed off on by the commit author.
+
+People with admin access to a repository can also enable compulsory commit signoffs at the repository level. For more information, see "[Managing the commit signoff policy for your repository](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-the-commit-signoff-policy-for-your-repository)."
 
 {% data reusables.repositories.commit-signoffs %}
 
-## 管理组织的强制提交签核
+## Managing compulsory commit signoffs for your organization
 
-{% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} {% data reusables.organizations.repository-defaults %}
-1. 选择或取消选择“要求参与者签核基于 Web 的提交”。
-  ![“要求参与者签核基于 Web 的提交”的屏幕截图](/assets/images/help/organizations/require-signoffs.png)
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.repository-defaults %}
+1. Select or deselect **Require contributors to sign off on web-based commits**.
+  ![Screenshot of Require contributors to sign off on web-based commits](/assets/images/help/organizations/require-signoffs.png)
diff --git a/translations/zh-CN/content/organizations/managing-organization-settings/setting-permissions-for-adding-outside-collaborators.md b/translations/zh-CN/content/organizations/managing-organization-settings/setting-permissions-for-adding-outside-collaborators.md
index f7efe070e5..43c2116721 100644
--- a/translations/zh-CN/content/organizations/managing-organization-settings/setting-permissions-for-adding-outside-collaborators.md
+++ b/translations/zh-CN/content/organizations/managing-organization-settings/setting-permissions-for-adding-outside-collaborators.md
@@ -1,6 +1,6 @@
 ---
-title: 设置添加外部协作者的权限
-intro: 为了保护组织的数据和组织中使用的付费许可证数，你可以配置可向组织存储库添加外部协作者的人员。
+title: Setting permissions for adding outside collaborators
+intro: 'To protect your organization''s data and the number of paid licenses used in your organization, you can configure who can add outside collaborators to organization repositories.'
 redirect_from:
   - /articles/restricting-the-ability-to-add-outside-collaborators-to-organization-repositories
   - /articles/setting-permissions-for-adding-outside-collaborators
@@ -13,28 +13,25 @@ topics:
   - Organizations
   - Teams
 shortTitle: Set collaborator policy
-ms.openlocfilehash: eadf4f805775a99f763ec4df211fe6ea9735dabc
-ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
-ms.translationtype: HT
-ms.contentlocale: zh-CN
-ms.lasthandoff: 09/10/2022
-ms.locfileid: '145099703'
 ---
-默认情况下，对存储库具有管理员访问权限的任何人都可以邀请外部协作者处理存储库。 你可以选择将添加外部协作者的能力限制为仅添加组织所有者。
 
-{% ifversion ghec %} {% note %}
+By default, anyone with admin access to a repository can invite outside collaborators to work on the repository. You can choose to restrict the ability to add outside collaborators to organization owners only.
 
-**注意：** 只有使用 {% data variables.product.prodname_ghe_cloud %} 的组织才能限制向组织所有者邀请外部协作者的能力。 {% data reusables.enterprise.link-to-ghec-trial %}
+{% ifversion ghec %}
+{% note %}
 
-{% endnote %} {% endif %}
+**Note:** Only organizations that use {% data variables.product.prodname_ghe_cloud %} can restrict the ability to invite outside collaborators to organization owners. {% data reusables.enterprise.link-to-ghec-trial %}
 
-{% ifversion ghec %}如果贵组织属于企业帐户，在企业所有者设置了企业级策略的情况下，{% else %}你{% endif %}可能无法为组织配置此设置。 有关详细信息，请参阅“[在企业中强制实施存储库管理策略]{% ifversion ghec %}(/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-for-inviting-collaborators-to-repositories)"{% else %}(/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-for-inviting-outside-collaborators-to-repositories){% endif %}。”
+{% endnote %}
+{% endif %}
+
+{% ifversion ghec %}If your organization is owned by an enterprise account, you{% else %}You{% endif %} may not be able to configure this setting for your organization, if an enterprise owner has set a policy at the enterprise level. For more information, see "[Enforcing repository management policies in your enterprise]{% ifversion ghec %}(/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-for-inviting-collaborators-to-repositories)"{% else %}(/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-for-inviting-outside-collaborators-to-repositories){% endif %}."
 
 {% data reusables.organizations.outside-collaborators-use-seats %}
 
-{% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} {% data reusables.organizations.member-privileges %}{% ifversion ghes < 3.3 %}
-5. 在“存储库邀请”下，选择“允许成员邀请外部协作者加入组织存储库”。
-   ![“允许成员邀请外部协作者加入组织存储库”复选框](/assets/images/help/organizations/repo-invitations-checkbox-old.png){% else %}
-5. 在“存储库外部协作者”下，取消选择“允许存储库管理员邀请外部协作者加入该组织的存储库”。
-  ![“允许存储库管理员邀请外部协作者加入组织存储库”复选框](/assets/images/help/organizations/repo-invitations-checkbox-updated.png){% endif %}
-6. 单击“保存” 。
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.member-privileges %}
+5. Under "Repository outside collaborators", deselect **Allow repository administrators to invite outside collaborators to repositories for this organization**.
+  ![Checkbox to allow repository administrators to invite outside collaborators to organization repositories](/assets/images/help/organizations/repo-invitations-checkbox-updated.png)
+6. Click **Save**.
diff --git a/translations/zh-CN/content/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization.md b/translations/zh-CN/content/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization.md
index 1ea492e3f2..6c34866ebd 100644
--- a/translations/zh-CN/content/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization.md
+++ b/translations/zh-CN/content/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization.md
@@ -15,12 +15,12 @@ topics:
   - Organizations
   - Teams
 shortTitle: Roles in an organization
-ms.openlocfilehash: d8d07ff40026de0d12fce2e11479c424b781680a
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: 960f6f701ad524220e9e79ada04fa9e4d30b8e9f
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: zh-CN
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147061736'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148108023'
 ---
 ## 关于角色
 {% data reusables.organizations.about-roles %}
@@ -142,7 +142,7 @@ ms.locfileid: '147061736'
 | 启用团队同步（请参阅“[管理组织的团队同步](/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization)”） | **X** |  |  |  |  |{% endif %}
 | 管理组织中的拉取请求审查（请参阅“[管理组织中的拉取请求审查](/organizations/managing-organization-settings/managing-pull-request-reviews-in-your-organization)”） | **X** |  |  |  |  |
 
-{% elsif ghes > 3.2 or ghae %}
+{% elsif ghes or ghae %}
 <!-- GHES 3.3+ and eventual GHAE release don't have the extra columns for Moderators and Billing managers. -->
 
 | 组织操作 | 所有者 | 成员 | 安全管理员 |
@@ -167,7 +167,7 @@ ms.locfileid: '147061736'
 | 可设为团队维护员 | **X** | **X** | **X**  |
 | 转让仓库 | **X** | |  |
 | 管理安全和分析设置（请参阅“[管理组织的安全和分析设置](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)”） | **X** | | **X** |{% ifversion ghes %}
-| 查看组织的安全概述（请参阅“[关于安全概述](/code-security/security-overview/about-the-security-overview)”） | **X** | | **X** |{% endif %}{% ifversion ghes > 3.2 %}
+| 查看组织的安全概述（请参阅“[关于安全概述](/code-security/security-overview/about-the-security-overview)”） | **X** | | **X** |{% endif %}{% ifversion ghes %}
 | 管理 {% data variables.product.prodname_dependabot_security_updates %}（请参阅“[关于 {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)”） | **X** | | **X** |{% endif %}
 | 管理组织的 SSH 证书颁发机构（请参阅“[管理组织的 SSH 证书颁发机构](/articles/managing-your-organizations-ssh-certificate-authorities)”） | **X** |  |  |
 | 创建项目板（请参阅“[组织的项目板权限](/articles/project-board-permissions-for-an-organization)”） | **X** | **X** | **X** |
diff --git a/translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on.md b/translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on.md
index a6056acced..b0a8576c06 100644
--- a/translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on.md
+++ b/translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on.md
@@ -20,10 +20,12 @@ shortTitle: IAM with SAML SSO
 
 {% data reusables.saml.saml-accounts %}
 
-Organization owners can enforce SAML SSO for an individual organization, or enterprise owners can enforce SAML SSO for all organizations in an enterprise account. For more information, see "[Configuring SAML single sign-on for your enterprise](/enterprise-cloud@latest/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise)."
+{% data reusables.saml.resources-without-sso %}
 
 {% data reusables.saml.outside-collaborators-exemption %}
 
+Organization owners can enforce SAML SSO for an individual organization, or enterprise owners can enforce SAML SSO for all organizations in an enterprise account. For more information, see "[Configuring SAML single sign-on for your enterprise](/enterprise-cloud@latest/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise)."
+
 Before enabling SAML SSO for your organization, you'll need to connect your IdP to your organization. For more information, see "[Connecting your identity provider to your organization](/organizations/managing-saml-single-sign-on-for-your-organization/connecting-your-identity-provider-to-your-organization)."
 
 For an organization, SAML SSO can be disabled, enabled but not enforced, or enabled and enforced. After you enable SAML SSO for your organization and your organization's members successfully authenticate with your IdP, you can enforce the SAML SSO configuration. For more information about enforcing SAML SSO for your {% data variables.product.prodname_dotcom %} organization, see "[Enforcing SAML single sign-on for your organization](/articles/enforcing-saml-single-sign-on-for-your-organization)."
diff --git a/translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/troubleshooting-identity-and-access-management-for-your-organization.md b/translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/troubleshooting-identity-and-access-management-for-your-organization.md
index a9b4d1b04b..5588d727ce 100644
--- a/translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/troubleshooting-identity-and-access-management-for-your-organization.md
+++ b/translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/troubleshooting-identity-and-access-management-for-your-organization.md
@@ -9,12 +9,12 @@ topics:
 shortTitle: Troubleshooting access
 redirect_from:
   - /organizations/managing-saml-single-sign-on-for-your-organization/troubleshooting-identity-and-access-management
-ms.openlocfilehash: 41a629c9cff075e06e31d186a4a4edf7eebd96d2
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: d3110d61fb511f55aa840d0911c036dd342fa833
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: zh-CN
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147093165'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148106971'
 ---
 {% data reusables.saml.current-time-earlier-than-notbefore-condition %}
 
@@ -84,7 +84,7 @@ SCIM REST API 仅返回在其外部标识下填充了 SCIM 元数据的用户的
 ```
 
 ```shell
-curl -X POST -H "Authorization: Bearer <personal access token>" -H "Content-Type: application/json" -d '{ "query": "{ organization(login: \"ORG\") { samlIdentityProvider { externalIdentities(first: 100) { pageInfo { endCursor startCursor hasNextPage } edges { cursor node { samlIdentity { nameId } scimIdentity {username}  user { login } } } } } } }" }'  https://api.github.com/graphql
+curl -X POST -H "Authorization: Bearer YOUR_TOKEN" -H "Content-Type: application/json" -d '{ "query": "{ organization(login: \"ORG\") { samlIdentityProvider { externalIdentities(first: 100) { pageInfo { endCursor startCursor hasNextPage } edges { cursor node { samlIdentity { nameId } scimIdentity {username}  user { login } } } } } } }" }'  https://api.github.com/graphql
 ```
 
 有关使用 GraphQL API 的更多信息，请参阅： 
diff --git a/translations/zh-CN/content/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team.md b/translations/zh-CN/content/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team.md
index afbb13b86e..a577717cf0 100644
--- a/translations/zh-CN/content/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team.md
+++ b/translations/zh-CN/content/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team.md
@@ -86,7 +86,7 @@ Any team members that have set their status to "Busy" will not be selected for r
 {% ifversion ghes < 3.4 %}
 1. Optionally, to only notify the team members chosen by code review assignment for each pull review request, under "Notifications" select **If assigning team members, don't notify the entire team.**
 {%- endif %}
-{% ifversion fpt or ghec or ghae > 3.3 or ghes > 3.2 %}
+{% ifversion fpt or ghec or ghes or ghae > 3.3 %}
 1. Optionally, to include members of child teams as potential reviewers when assigning requests, select **Child team members**.
 1. Optionally, to count any members whose review has already been requested against the total number of members to assign, select **Count existing requests**.
 1. Optionally, to remove the review request from the team when assigning team members, select **Team review request**.
diff --git a/translations/zh-CN/content/packages/working-with-a-github-packages-registry/migrating-to-the-container-registry-from-the-docker-registry.md b/translations/zh-CN/content/packages/working-with-a-github-packages-registry/migrating-to-the-container-registry-from-the-docker-registry.md
index 400f954e6d..0fe78be916 100644
--- a/translations/zh-CN/content/packages/working-with-a-github-packages-registry/migrating-to-the-container-registry-from-the-docker-registry.md
+++ b/translations/zh-CN/content/packages/working-with-a-github-packages-registry/migrating-to-the-container-registry-from-the-docker-registry.md
@@ -9,7 +9,7 @@ redirect_from:
 versions:
   fpt: '*'
   ghec: '*'
-  feature: 'docker-ghcr-enterprise-migration'
+  feature: docker-ghcr-enterprise-migration
 shortTitle: Migration to Container registry
 topics:
   - Containers
diff --git a/translations/zh-CN/content/packages/working-with-a-github-packages-registry/working-with-the-npm-registry.md b/translations/zh-CN/content/packages/working-with-a-github-packages-registry/working-with-the-npm-registry.md
index f17d1a1b94..e687fd7b2b 100644
--- a/translations/zh-CN/content/packages/working-with-a-github-packages-registry/working-with-the-npm-registry.md
+++ b/translations/zh-CN/content/packages/working-with-a-github-packages-registry/working-with-the-npm-registry.md
@@ -142,14 +142,14 @@ You can use `publishConfig` element in the *package.json* file to specify the re
   {% endif %}
   ```shell
   "publishConfig": {
-    "registry":"https://{% ifversion fpt or ghec %}npm.pkg.github.com{% else %}npm.HOSTNAME/{% endif %}"
+    "registry": "https://{% ifversion fpt or ghec %}npm.pkg.github.com{% else %}npm.HOSTNAME/{% endif %}"
   },
   ```
   {% ifversion ghes %}
   If your instance has subdomain isolation disabled:
    ```shell
    "publishConfig": {
-     "registry":"https://HOSTNAME/_registry/npm/"
+     "registry": "https://HOSTNAME/_registry/npm/"
    },
   ```
   {% endif %}
diff --git a/translations/zh-CN/content/pages/getting-started-with-github-pages/index.md b/translations/zh-CN/content/pages/getting-started-with-github-pages/index.md
index 243b4bb4db..138e01ce3a 100644
--- a/translations/zh-CN/content/pages/getting-started-with-github-pages/index.md
+++ b/translations/zh-CN/content/pages/getting-started-with-github-pages/index.md
@@ -24,11 +24,11 @@ children:
   - /using-submodules-with-github-pages
   - /unpublishing-a-github-pages-site
 shortTitle: Get started
-ms.openlocfilehash: 7e9d3b9bb171a596b84b814eac52d4c5d22134de
-ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794
+ms.openlocfilehash: 4945585f635543fefe2f60de2f82b49bf4d10e84
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: zh-CN
-ms.lasthandoff: 09/09/2022
-ms.locfileid: '147643875'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148108169'
 ---
 
diff --git a/translations/zh-CN/content/pages/getting-started-with-github-pages/unpublishing-a-github-pages-site.md b/translations/zh-CN/content/pages/getting-started-with-github-pages/unpublishing-a-github-pages-site.md
index 34301031d0..bdaf20e577 100644
--- a/translations/zh-CN/content/pages/getting-started-with-github-pages/unpublishing-a-github-pages-site.md
+++ b/translations/zh-CN/content/pages/getting-started-with-github-pages/unpublishing-a-github-pages-site.md
@@ -1,6 +1,6 @@
 ---
-title: 取消发布 GitHub Pages 站点
-intro: '您可以取消发布 {% data variables.product.prodname_pages %} 站点，使该站点不再可用。'
+title: Unpublishing a GitHub Pages site
+intro: 'You can unpublish your {% data variables.product.prodname_pages %} site so that the site is no longer available.'
 redirect_from:
   - /articles/how-do-i-unpublish-a-project-page
   - /articles/unpublishing-a-project-page
@@ -18,38 +18,35 @@ versions:
 topics:
   - Pages
 shortTitle: Unpublish Pages site
-ms.openlocfilehash: fbfec49ec44c250e5f6cb2da85fda59261c1d0d9
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
-ms.translationtype: HT
-ms.contentlocale: zh-CN
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147428346'
 ---
+
 {% ifversion pages-custom-workflow %}
 
-取消发布站点时，该站点将不再可用。 所有现有存储库设置或内容都不受影响。
+When you unpublish your site, the site will no longer be available. Any existing repository settings or content will not be affected.
 
 {% data reusables.repositories.navigate-to-repo %}
-1. 在 {% data variables.product.prodname_pages %} 下的“站点所在位置”消息旁，单击 {% octicon "kebab-horizontal" aria-label="the horizontal kebab icon" %} 。
-1. 在显示的菜单中，选择“取消发布站点”。
+1. Under **{% data variables.product.prodname_pages %}**, next to the **Your site is live at** message, click {% octicon "kebab-horizontal" aria-label="the horizontal kebab icon" %}.
+1. In the menu that appears, select **Unpublish site**.
 
-   ![用于取消发布站点的下拉菜单](/assets/images/help/pages/unpublish-site.png)
+   ![Drop down menu to unpublish site](/assets/images/help/pages/unpublish-site.png)
 
 {% else %}
 
-## 取消发布项目站点
+## Unpublishing a project site
 
 {% data reusables.repositories.navigate-to-repo %}
-2. 如果存储库中存在 `gh-pages` 分支，请删除 `gh-pages` 分支。 有关详细信息，请参阅“[创建和删除存储库中的分支](/articles/creating-and-deleting-branches-within-your-repository#deleting-a-branch)”。
-3. 如果 `gh-pages` 分支是发布源，{% ifversion fpt or ghec %}请跳到步骤 6{% else %}你的网站现在已取消发布，你可以跳过其余步骤{% endif %}。
-{% data reusables.repositories.sidebar-settings %} {% data reusables.pages.sidebar-pages %}
-5. 在“{% data variables.product.prodname_pages %}”下，使用“源”下拉菜单，然后选择“无”。
-  ![用于选择发布源的下拉菜单](/assets/images/help/pages/publishing-source-drop-down.png) {% data reusables.pages.update_your_dns_settings %} 
+2. If a `gh-pages` branch exists in the repository, delete the `gh-pages` branch. For more information, see "[Creating and deleting branches within your repository](/articles/creating-and-deleting-branches-within-your-repository#deleting-a-branch)."
+3. If the `gh-pages` branch was your publishing source, {% ifversion fpt or ghec %}skip to step 6{% else %}your site is now unpublished and you can skip the remaining steps{% endif %}.
+{% data reusables.repositories.sidebar-settings %}
+{% data reusables.pages.sidebar-pages %}
+5. Under "{% data variables.product.prodname_pages %}", use the **Source** drop-down menu and select **None.**
+  ![Drop down menu to select a publishing source](/assets/images/help/pages/publishing-source-drop-down.png)
+{% data reusables.pages.update_your_dns_settings %}
 
-## 取消发布用户或组织站点
+## Unpublishing a user or organization site
 
 {% data reusables.repositories.navigate-to-repo %}
-2. 删除用作发布源的分支，或删除整个仓库。 有关详细信息，请参阅“[创建和删除存储库中的分支](/articles/creating-and-deleting-branches-within-your-repository#deleting-a-branch)”和“[删除存储库](/articles/deleting-a-repository)”。
+2. Delete the branch that you're using as a publishing source, or delete the entire repository. For more information, see "[Creating and deleting branches within your repository](/articles/creating-and-deleting-branches-within-your-repository#deleting-a-branch)" and "[Deleting a repository](/articles/deleting-a-repository)."
 {% data reusables.pages.update_your_dns_settings %}
 
 {% endif %}
diff --git a/translations/zh-CN/content/pages/index.md b/translations/zh-CN/content/pages/index.md
index 5c8d0c692f..19adbee123 100644
--- a/translations/zh-CN/content/pages/index.md
+++ b/translations/zh-CN/content/pages/index.md
@@ -50,3 +50,4 @@ children:
   - /setting-up-a-github-pages-site-with-jekyll
   - /configuring-a-custom-domain-for-your-github-pages-site
 ---
+
diff --git a/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request.md b/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request.md
index 5ecd5f08d3..141f27d805 100644
--- a/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request.md
+++ b/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request.md
@@ -22,8 +22,6 @@ 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 %}
diff --git a/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request.md b/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request.md
index 922f9dbb84..32a3feaa26 100644
--- a/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request.md
+++ b/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request.md
@@ -65,8 +65,6 @@ For more information on reviewing pull requests in {% data variables.product.pro
 {% ifversion fpt or ghes or ghec %}
 ## Reviewing dependency changes
 
-{% data reusables.dependency-review.beta %}
-
 If the pull request contains changes to dependencies you can use the dependency review for a manifest or lock file to see what has changed and check whether the changes introduce security vulnerabilities. For more information, see "[Reviewing dependency changes in a pull request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request)."
 
 {% data reusables.repositories.changed-files %}
diff --git a/translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches.md b/translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches.md
index ae7c873c86..a2808b957d 100644
--- a/translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches.md
+++ b/translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches.md
@@ -95,7 +95,7 @@ Optionally, you can require approvals from someone other than the last person to
 
 Required status checks ensure that all required CI tests are passing before collaborators can make changes to a protected branch. Required status checks can be checks or statuses. For more information, see "[About status checks](/github/collaborating-with-issues-and-pull-requests/about-status-checks)."
 
-Before you can enable required status checks, you must configure the repository to use the status API. For more information, see "[Repositories](/rest/reference/commits#commit-statuses)" in the REST documentation.
+Before you can enable required status checks, you must configure the repository to use the commit status API. For more information, see "[Commit statuses](/rest/commits/statuses)" in the REST API documentation.
 
 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.
 
@@ -187,7 +187,7 @@ When you enable branch restrictions, only users, teams, or apps that have been g
 Optionally, you can apply the same restrictions to the creation of branches that match the rule. For example, if you create a rule that only allows a certain team to push to any branches that contain the word `release`, only members of that team would be able to create a new branch that contains the word `release`.
 {% endif %}
 
-You can only give push access to a protected branch, or give permission to create a matching 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 or create a matching branch.
+You can only give push access to a protected branch, or give permission to create a matching 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{% ifversion restrict-pushes-create-branch %} or create a matching branch{% endif %}.
 
 ### Allow force pushes
 
diff --git a/translations/zh-CN/content/repositories/creating-and-managing-repositories/about-repositories.md b/translations/zh-CN/content/repositories/creating-and-managing-repositories/about-repositories.md
index 014c709c08..04007167b4 100644
--- a/translations/zh-CN/content/repositories/creating-and-managing-repositories/about-repositories.md
+++ b/translations/zh-CN/content/repositories/creating-and-managing-repositories/about-repositories.md
@@ -78,6 +78,14 @@ People with admin permissions for a repository can change an existing repository
 
 {% data reusables.repositories.about-internal-repos %} For more information on innersource, see {% data variables.product.prodname_dotcom %}'s whitepaper "[An introduction to innersource](https://resources.github.com/whitepapers/introduction-to-innersource/)."
 
+{% ifversion ghec %}
+{% note %}
+
+**Note:** You can only create internal repositories if you use {% data variables.product.prodname_ghe_cloud %} with an enterprise account. An enterprise account is a separate type of account that allows a central point of management for multiple organizations. For more information, see "[Types of {% data variables.product.prodname_dotcom %} account](/get-started/learning-about-github/types-of-github-accounts)."
+
+{% endnote %}
+{% endif %}
+
 All enterprise members have read permissions to the internal repository, but internal repositories are not visible to people {% ifversion fpt or ghec %}outside of the enterprise{% else %}who are not members of any organization{% endif %}, including outside collaborators on organization repositories. For more information, see "[Roles in an enterprise](/github/setting-up-and-managing-your-enterprise/roles-in-an-enterprise#enterprise-members)" and "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)."
 
 {% ifversion ghes %}
diff --git a/translations/zh-CN/content/repositories/creating-and-managing-repositories/transferring-a-repository.md b/translations/zh-CN/content/repositories/creating-and-managing-repositories/transferring-a-repository.md
index dff4c98d4d..ca7dd28f84 100644
--- a/translations/zh-CN/content/repositories/creating-and-managing-repositories/transferring-a-repository.md
+++ b/translations/zh-CN/content/repositories/creating-and-managing-repositories/transferring-a-repository.md
@@ -51,6 +51,12 @@ When you transfer a repository, its issues, pull requests, wiki, stars, and watc
   $ git remote set-url origin NEW_URL
   ```
 
+  {% warning %}
+
+  **Warning**: If you create a new repository under your account in the future, do not reuse the original name of the transferred repository. If you do, redirects to the transferred repository will no longer work.
+
+  {% endwarning %}
+
 - When you transfer a repository from an organization to a personal account, the repository's read-only collaborators will not be transferred. This is because collaborators can't have read-only access to repositories owned by a personal account. For more information about repository permission levels, see "[Permission levels for a personal account repository](/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository)" and "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)."{% ifversion fpt or ghec %}
 - Sponsors who have access to the repository through a sponsorship tier may be affected. For more information, see "[Adding a repository to a sponsorship tier](/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers#adding-a-repository-to-a-sponsorship-tier)".{% endif %}
 
diff --git a/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-citation-files.md b/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-citation-files.md
index 3292c1ee79..e059ce5619 100644
--- a/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-citation-files.md
+++ b/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-citation-files.md
@@ -5,17 +5,17 @@ redirect_from:
   - /github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github/about-citation-files
 versions:
   fpt: '*'
-  ghes: '>=3.3'
+  ghes: '*'
   ghae: '*'
   ghec: '*'
 topics:
   - Repositories
-ms.openlocfilehash: 2f7869e9218679c3c18c3182b15835bcd24e134d
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: 96e5e7308ba5d1877f231dcb454d7b797a63f221
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: zh-CN
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '145193800'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148108079'
 ---
 ## 关于 CITION 文件
 
diff --git a/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners.md b/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners.md
index 343a994c1e..d3212418a8 100644
--- a/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners.md
+++ b/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners.md
@@ -37,13 +37,11 @@ Each CODEOWNERS file assigns the code owners for a single branch in the reposito
 
 For code owners to receive review requests, the CODEOWNERS file must be on the base branch of the pull request. For example, if you assign `@octocat` as the code owner for *.js* files on the `gh-pages` branch of your repository, `@octocat` will receive review requests when a pull request with changes to *.js* files is opened between the head branch and `gh-pages`.
 
-{% ifversion fpt or ghec or ghes > 3.2 or ghae %}
 ## CODEOWNERS file size
 
 CODEOWNERS files must be under 3 MB in size. A CODEOWNERS file over this limit will not be loaded, which means that code owner information is not shown and the appropriate code owners will not be requested to review changes in a pull request.
 
 To reduce the size of your CODEOWNERS file, consider using wildcard patterns to consolidate multiple entries into a single entry.
-{% endif %}
 
 ## CODEOWNERS syntax
 
@@ -129,7 +127,6 @@ apps/ @octocat
 ## CODEOWNERS and branch protection
 Repository owners can add branch protection rules to ensure that changed code is reviewed by the owners of the changed files. For more information, see "[About protected branches](/github/administering-a-repository/defining-the-mergeability-of-pull-requests/about-protected-branches)."
 
-
 ## Further reading
 
 - "[Creating new files](/articles/creating-new-files)"
diff --git a/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-readmes.md b/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-readmes.md
index 03bfb1040b..7de402dfc0 100644
--- a/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-readmes.md
+++ b/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-readmes.md
@@ -17,7 +17,7 @@ topics:
 ---
 ## About READMEs
 
-You can add a README file to a repository to communicate important information about your project. A README, along with a repository license{% ifversion fpt or ghes > 3.2 or ghae or ghec %}, citation file{% endif %}{% ifversion fpt or ghec %}, contribution guidelines, and a code of conduct{% elsif ghes %} and contribution guidelines{% endif %}, communicates expectations for your project and helps you manage contributions.
+You can add a README file to a repository to communicate important information about your project. A README, along with a repository license, citation file{% ifversion fpt or ghec %}, contribution guidelines, and a code of conduct{% elsif ghes %} and contribution guidelines{% endif %}, communicates expectations for your project and helps you manage contributions.
 
 For more information about providing guidelines for your project, see {% ifversion fpt or ghec %}"[Adding a code of conduct to your project](/communities/setting-up-your-project-for-healthy-contributions/adding-a-code-of-conduct-to-your-project)" and {% endif %}"[Setting up your project for healthy contributions](/communities/setting-up-your-project-for-healthy-contributions)."
 
@@ -66,4 +66,4 @@ A README should contain only the necessary information for developers to get sta
 - 18F's "[Making READMEs readable](https://github.com/18F/open-source-guide/blob/18f-pages/pages/making-readmes-readable.md)"
 {%- ifversion fpt or ghec %} 
 - "[Adding an 'Open in GitHub Codespaces' badge](/codespaces/setting-up-your-project-for-codespaces/adding-a-codespaces-badge)"
-{%- endif %}   
\ No newline at end of file
+{%- endif %}   
diff --git a/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/classifying-your-repository-with-topics.md b/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/classifying-your-repository-with-topics.md
index 1878e0a5e8..0227ac595d 100644
--- a/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/classifying-your-repository-with-topics.md
+++ b/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/classifying-your-repository-with-topics.md
@@ -1,6 +1,6 @@
 ---
-title: 使用主题对仓库分类
-intro: 为帮助其他人找到并参与您的项目，可以为仓库添加主题，这些主题可以与项目的预期目的、学科领域、关联团队或其他重要特点相关。
+title: Classifying your repository with topics
+intro: 'To help other people find and contribute to your project, you can add topics to your repository related to your project''s intended purpose, subject area, affinity groups, or other important qualities.'
 redirect_from:
   - /articles/about-topics
   - /articles/classifying-your-repository-with-topics
@@ -14,35 +14,36 @@ versions:
 topics:
   - Repositories
 shortTitle: Classify with topics
-ms.openlocfilehash: 68bd754ac6c50968961c61e533cb6b9de26e4cc4
-ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
-ms.translationtype: HT
-ms.contentlocale: zh-CN
-ms.lasthandoff: 09/10/2022
-ms.locfileid: '145129349'
 ---
-## 关于主题
 
-使用主题可以探索特定主题领域的仓库，查找要参与的项目，以及发现特定问题的新解决方案。 主题显示在仓库的主页面上。 可以单击主题名称以{% ifversion fpt or ghec %}查看相关主题和按该主题分类的其他存储库列表{% else %}搜索具有该主题的其他存储库{% endif %}。
+## About topics
 
-![显示主题的测试仓库主页面](/assets/images/help/repository/os-repo-with-topics.png)
+With topics, you can explore repositories in a particular subject area, find projects to contribute to, and discover new solutions to a specific problem. Topics appear on the main page of a repository. You can click a topic name to {% ifversion fpt or ghec %}see related topics and a list of other repositories classified with that topic{% else %}search for other repositories with that topic{% endif %}.
 
-若要浏览最常用的主题，请转到 https://github.com/topics/ 。
+![Main page of the test repository showing topics](/assets/images/help/repository/os-repo-with-topics.png)
 
-{% ifversion fpt or ghec %}可以在 [github/explore](https://github.com/github/explore) 存储库中参与 {% data variables.product.product_name %} 的一组精选主题。 {% endif %}
+To browse the most used topics, go to https://github.com/topics/.
 
-仓库管理员可以添加他们喜欢的任何主题到仓库。 用于对存储库进行分类的有用主题包括存储库的预期用途、主题领域、社区或语言。{% ifversion fpt or ghec %}此外，{% data variables.product.product_name %} 分析公共存储库内容，并生成存储库管理员可接受或拒绝的建议主题。 私有仓库内容不可分析，也不会收到主题建议。{% endif %}
+{% ifversion fpt or ghec %}You can contribute to {% data variables.product.product_name %}'s set of featured topics in the [github/explore](https://github.com/github/explore) repository. {% endif %}
 
-{% ifversion fpt %}公共和私有{% elsif ghec or ghes %}公共、私有和内部{% elsif ghae %}私有和内部{% endif %} 存储库可以包含主题，但您只会在主题搜索结果中看到您有权访问的私有存储库。
+Repository admins can add any topics they'd like to a repository. Helpful topics to classify a repository include the repository's intended purpose, subject area, community, or language.{% ifversion fpt or ghec %} Additionally, {% data variables.product.product_name %} analyzes public repository content and generates suggested topics that repository admins can accept or reject. Private repository content is not analyzed and does not receive topic suggestions.{% endif %}
 
-您可以搜索与公共仓库关联的仓库。 有关详细信息，请参阅“[搜索存储库](/search-github/searching-on-github/searching-for-repositories#search-by-topic)”。 您也可以搜索 {% data variables.product.product_name %} 中的主题列表。 有关详细信息，请参阅“[搜索主题](/search-github/searching-on-github/searching-topics)”。
+{% ifversion fpt %}Public and private{% elsif ghec or ghes %}Public, private, and internal{% elsif ghae %}Private and internal{% endif %} repositories can have topics, although you will only see private repositories that you have access to in topic search results.
 
-## 添加主题到仓库
+You can search for repositories that are associated with a particular topic. For more information, see "[Searching for repositories](/search-github/searching-on-github/searching-for-repositories#search-by-topic)." You can also search for a list of topics on {% data variables.product.product_name %}. For more information, see "[Searching topics](/search-github/searching-on-github/searching-topics)."
+
+## Adding topics to your repository
+
+{% note %}
+
+**Note:** Topic names are always public, even if you create the topic from within a private repository.
+
+{% endnote %}
 
 {% data reusables.repositories.navigate-to-repo %}
-2. 在“关于”右侧，单击 {% octicon "gear" aria-label="The Gear icon" %}。
-  ![存储库主页上的齿轮图标](/assets/images/help/repository/edit-repository-details-gear.png)
-3. 在“"Topics（主题）”下，键入要添加到仓库的主题，然后键入空格。
-  ![用于输入主题的表单](/assets/images/help/repository/add-topic-form.png)
-4. 完成添加主题后，单击“保存更改”。
-  ![“编辑存储库详细信息”中的“保存更改”按钮](/assets/images/help/repository/edit-repository-details-save-changes-button.png)
+2. To the right of "About", click {% octicon "gear" aria-label="The Gear icon" %}.
+  ![Gear icon on main page of a repository](/assets/images/help/repository/edit-repository-details-gear.png)
+3. Under "Topics", type the topic you want to add to your repository, then type a space.
+  ![Form to enter topics](/assets/images/help/repository/add-topic-form.png)
+4. After you've finished adding topics, click **Save changes**.
+  !["Save changes" button in "Edit repository details"](/assets/images/help/repository/edit-repository-details-save-changes-button.png)
diff --git a/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/disabling-project-boards-in-a-repository.md b/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/disabling-project-boards-in-a-repository.md
index 157c1380a4..873374d90c 100644
--- a/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/disabling-project-boards-in-a-repository.md
+++ b/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/disabling-project-boards-in-a-repository.md
@@ -15,12 +15,12 @@ topics:
   - Pull requests
 shortTitle: 'Disable {% data variables.projects.projects_v1_boards %}'
 allowTitleToDifferFromFilename: true
-ms.openlocfilehash: 0407d6df39ae664474aa3fb5c99dc7998df1b951
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: 8c550cd9ebc767327298e39dc0b3a6a11368dc3f
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: zh-CN
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147422658'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148108619'
 ---
 禁用 {% data variables.projects.projects_v1_boards %} 时，时间线或[审核日志](/articles/reviewing-your-security-log/)中将不再显示 {% data variables.projects.projects_v1_board %} 信息。
 
diff --git a/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-security-and-analysis-settings-for-your-repository.md b/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-security-and-analysis-settings-for-your-repository.md
index 3bc55f4486..1cbb6dffab 100644
--- a/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-security-and-analysis-settings-for-your-repository.md
+++ b/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-security-and-analysis-settings-for-your-repository.md
@@ -50,8 +50,7 @@ You can manage the security and analysis features for your {% ifversion fpt or g
 {% ifversion fpt or ghes or ghec %}
 4. Under "Code security and analysis", 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 %}
   ![Screenshot of "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 %}
-  ![Screenshot of "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.6 or ghae > 3.6 %}<!--Insert screenshot for GHES 3.7 when available-->{% elsif ghes = 3.2 %}
-  ![Screenshot of "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){% else %}
+  ![Screenshot of "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.6 or ghae > 3.6 %}<!--Insert screenshot for GHES 3.7 when available-->
   ![Screenshot of "Enable" or "Disable" button for "Configure security and analysis" features](/assets/images/enterprise/3.3/repository/security-and-analysis-disable-or-enable-ghes.png){% endif %}
   
   {% ifversion not fpt %}
@@ -81,23 +80,19 @@ Organization owners and repository administrators can only grant access to view
 {% data reusables.repositories.sidebar-settings %}
 {% data reusables.repositories.navigate-to-code-security-and-analysis %}
 4. Under "Access to alerts", in the search field, start typing the name of the person or team you'd like to find, then click a name in the list of matches.
-   {% ifversion fpt or ghec or ghes > 3.2 %}
+   {% ifversion fpt or ghec or ghes %}
    ![Search field for granting people or teams access to security alerts](/assets/images/help/repository/security-and-analysis-security-alerts-person-or-team-search.png)
    {% endif %}
-   {% ifversion ghes < 3.3 %}
-   ![Search field for granting people or teams access to security alerts](/assets/images/enterprise/3.2/repository/security-and-analysis-security-alerts-person-or-team-search.png)
-   {% endif %}
+   
    {% ifversion ghae %}
    ![Search field for granting people or teams access to security alerts](/assets/images/enterprise/github-ae/repository/security-and-analysis-security-alerts-person-or-team-search-ghae.png)
    {% endif %}
    
 5. Click **Save changes**.
-   {% ifversion fpt or ghes > 3.2 or ghec %}
+   {% ifversion fpt or ghes or ghec %}
    !["Save changes" button for changes to security alert settings](/assets/images/help/repository/security-and-analysis-security-alerts-save-changes.png)
    {% endif %}
-   {% ifversion ghes < 3.3 %}
-   !["Save changes" button for changes to security alert settings](/assets/images/enterprise/3.2/repository/security-and-analysis-security-alerts-save-changes.png)
-   {% endif %}
+   
    {% ifversion ghae %}
    !["Save changes" button for changes to security alert settings](/assets/images/enterprise/github-ae/repository/security-and-analysis-security-alerts-save-changes-ghae.png)
    {% endif %}
@@ -108,12 +103,10 @@ Organization owners and repository administrators can only grant access to view
 {% data reusables.repositories.sidebar-settings %}
 {% data reusables.repositories.navigate-to-code-security-and-analysis %}
 4. Under "Access to alerts", to the right of the person or team whose access you'd like to remove, click {% octicon "x" aria-label="X symbol" %}.
-   {% ifversion fpt or ghec or ghes > 3.2 %}  
+   {% ifversion fpt or ghec or ghes %}  
    !["x" button to remove someone's access to security alerts for your repository](/assets/images/help/repository/security-and-analysis-security-alerts-username-x.png)
    {% endif %}
-   {% ifversion ghes < 3.3 %}
-   !["x" button to remove someone's access to security alerts for your repository](/assets/images/enterprise/3.2/repository/security-and-analysis-security-alerts-username-x.png)
-   {% endif %}
+   
    {% ifversion ghae %}
    !["x" button to remove someone's access to security alerts for your repository](/assets/images/enterprise/github-ae/repository/security-and-analysis-security-alerts-username-x-ghae.png)
    {% endif %}
diff --git a/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-the-commit-signoff-policy-for-your-repository.md b/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-the-commit-signoff-policy-for-your-repository.md
index 188b4b10dc..941d10d1b0 100644
--- a/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-the-commit-signoff-policy-for-your-repository.md
+++ b/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-the-commit-signoff-policy-for-your-repository.md
@@ -1,6 +1,6 @@
 ---
 title: Managing the commit signoff policy for your repository
-intro: You can require users to automatically sign off on the commits they make to your repository using {% data variables.product.product_name %}'s web interface.
+intro: 'You can require users to automatically sign off on the commits they make to your repository using {% data variables.product.product_name %}''s web interface.'
 versions:
   feature: commit-signoffs
 permissions: Organization owners and repository administrators can require all commits to a repository to be signed off by the commit author.
@@ -22,4 +22,4 @@ Organization owners can also enable compulsory commit signoffs at the organizati
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
 1. Select **Require contributors to sign off on web-based commits**.
-  ![Screenshot of Require contributors to sign off on web-based commits](/assets/images/help/repository/require-signoffs.png)
\ No newline at end of file
+  ![Screenshot of Require contributors to sign off on web-based commits](/assets/images/help/repository/require-signoffs.png)
diff --git a/translations/zh-CN/content/repositories/releasing-projects-on-github/managing-releases-in-a-repository.md b/translations/zh-CN/content/repositories/releasing-projects-on-github/managing-releases-in-a-repository.md
index d01f6e8e7a..832a7ae04f 100644
--- a/translations/zh-CN/content/repositories/releasing-projects-on-github/managing-releases-in-a-repository.md
+++ b/translations/zh-CN/content/repositories/releasing-projects-on-github/managing-releases-in-a-repository.md
@@ -39,22 +39,19 @@ You can choose whether {% data variables.large_files.product_name_long %} ({% da
 1. Click **Draft a new release**.
 
    {% ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4 %}![Releases draft button](/assets/images/help/releases/draft-release-button-with-search.png){% else %}![Releases draft button](/assets/images/help/releases/draft_release_button.png){% endif %}
-1. {% ifversion fpt or ghec or ghes > 3.2 or ghae %}Click **Choose a tag**, type{% else %}Type{% endif %} a version number for your release{% ifversion fpt or ghec or ghes > 3.2 or ghae %}, and press **Enter**{% endif %}. Alternatively, select an existing tag.
+1. Click **Choose a tag**, type a version number for your release, and press **Enter**. Alternatively, select an existing tag.
 
-   {% ifversion fpt or ghec or ghes > 3.2 or ghae %}![Enter a tag](/assets/images/help/releases/releases-tag-create.png)
+   ![Enter a tag](/assets/images/help/releases/releases-tag-create.png)
 1. If you are creating a new tag, click **Create new tag**.
 
    ![Screenshot of confirming you want to create a new tag](/assets/images/help/releases/releases-tag-create-confirm.png)
-   {% else %}
-   ![Screenshot of the Releases tagged version](/assets/images/enterprise/releases/releases-tag-version.png)
-{% endif %}
+   
 1. If you have created a new tag, use the drop-down menu to select the branch that contains the project you want to release.
 
-   {% ifversion fpt or ghec or ghes > 3.2 or ghae %}
+   
    ![Screenshot of dropdown to choose a branch](/assets/images/help/releases/releases-choose-branch.png)
 
-   {% else %}
-   ![Screenshot of the Releases tagged branch](/assets/images/enterprise/releases/releases-tag-branch.png){% endif %}
+   
 
 {%- data reusables.releases.previous-release-tag %}
 1. Type a title and description for your release.
@@ -90,7 +87,7 @@ You can choose whether {% data variables.large_files.product_name_long %} ({% da
 1. If you're ready to publicize your release, click **Publish release**. To work on the release later, click **Save draft**.
    ![Publish release and Draft release buttons](/assets/images/help/releases/release_buttons.png)
 
-   {%- ifversion fpt or ghec or ghes > 3.2 or ghae > 3.3 %}
+   {%- ifversion fpt or ghec or ghae > 3.3 %}
    You can then view your published or draft releases in the releases feed for your repository. For more information, see "[Screenshot of your repository's releases and tags](/github/administering-a-repository/releasing-projects-on-github/viewing-your-repositorys-releases-and-tags)."
 
    {% ifversion fpt or ghec or ghes > 3.4 or ghae > 3.3 %}
diff --git a/translations/zh-CN/content/repositories/releasing-projects-on-github/searching-a-repositorys-releases.md b/translations/zh-CN/content/repositories/releasing-projects-on-github/searching-a-repositorys-releases.md
index 8c3af76159..fe8bba4455 100644
--- a/translations/zh-CN/content/repositories/releasing-projects-on-github/searching-a-repositorys-releases.md
+++ b/translations/zh-CN/content/repositories/releasing-projects-on-github/searching-a-repositorys-releases.md
@@ -6,16 +6,16 @@ shortTitle: Searching releases
 versions:
   fpt: '*'
   ghec: '*'
-  ghes: '>3.2'
+  ghes: '*'
   ghae: '>= 3.4'
 topics:
   - Repositories
-ms.openlocfilehash: 193363cc5762db6cb030906a64dacb7bab6f5b7a
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: a61e49521452befdcddf2724cad837062c7d54a1
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: zh-CN
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147066184'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148108683'
 ---
 ## 在存储库中搜索版本
 
diff --git a/translations/zh-CN/content/repositories/working-with-files/using-files/working-with-non-code-files.md b/translations/zh-CN/content/repositories/working-with-files/using-files/working-with-non-code-files.md
index 5dd1df54fe..d8ad87c848 100644
--- a/translations/zh-CN/content/repositories/working-with-files/using-files/working-with-non-code-files.md
+++ b/translations/zh-CN/content/repositories/working-with-files/using-files/working-with-non-code-files.md
@@ -199,14 +199,10 @@ You can click {% octicon "file" aria-label="The paper icon" %} to see the change
 
 ![Rendered Prose changes](/assets/images/help/repository/rendered_prose_changes.png)
 
-{% ifversion fpt or ghes > 3.2 or ghae or ghec %}
-
 ### Disabling Markdown rendering
 
 {% data reusables.repositories.disabling-markdown-rendering %}
 
-{% endif %}
-
 ### Visualizing attribute changes
 
 We provide a tooltip
diff --git a/translations/zh-CN/content/rest/deployments/branch-policies.md b/translations/zh-CN/content/rest/deployments/branch-policies.md
index 9f0ed245ac..c08791db6b 100644
--- a/translations/zh-CN/content/rest/deployments/branch-policies.md
+++ b/translations/zh-CN/content/rest/deployments/branch-policies.md
@@ -11,12 +11,12 @@ versions:
 topics:
   - API
 miniTocMaxHeadingLevel: 3
-ms.openlocfilehash: 70f5d05f0a28e9fa21bf7bc99abbac6bd4a6509a
-ms.sourcegitcommit: 76b840f45ba85fb79a7f0c1eb43bc663b3eadf2b
+ms.openlocfilehash: 109bf81019d62e4c654ba6da4fa71f8fd359ceb4
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: zh-CN
-ms.lasthandoff: 09/12/2022
-ms.locfileid: '147549109'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148108654'
 ---
 ## 关于部署分支策略 API
 
diff --git a/translations/zh-CN/content/rest/enterprise-admin/audit-log.md b/translations/zh-CN/content/rest/enterprise-admin/audit-log.md
index 33ca7acbfc..f5f5ec12fb 100644
--- a/translations/zh-CN/content/rest/enterprise-admin/audit-log.md
+++ b/translations/zh-CN/content/rest/enterprise-admin/audit-log.md
@@ -2,7 +2,7 @@
 title: Audit log
 intro: ''
 versions:
-  ghes: '>=3.3'
+  ghes: '*'
   ghec: '*'
   ghae: '*'
 topics:
diff --git a/translations/zh-CN/content/rest/enterprise-admin/scim.md b/translations/zh-CN/content/rest/enterprise-admin/scim.md
index 05b64bf796..5f0be8c0ba 100644
--- a/translations/zh-CN/content/rest/enterprise-admin/scim.md
+++ b/translations/zh-CN/content/rest/enterprise-admin/scim.md
@@ -1,6 +1,6 @@
 ---
 title: SCIM
-intro: 'You can automate user creation and team memberships using the SCIM API.'
+intro: You can automate user creation and team memberships using the SCIM API.
 versions:
   ghes: '>=3.6'
 topics:
diff --git a/translations/zh-CN/content/rest/overview/api-previews.md b/translations/zh-CN/content/rest/overview/api-previews.md
index 4f8ac73172..9ec7f2ffc9 100644
--- a/translations/zh-CN/content/rest/overview/api-previews.md
+++ b/translations/zh-CN/content/rest/overview/api-previews.md
@@ -1,203 +1,29 @@
 ---
-title: API 预览
-intro: 您可以使用 API 预览来试用新功能并在这些功能正式发布之前提供反馈。
+title: API previews
+intro: You can use API previews to try out new features and provide feedback before these features become official.
 redirect_from:
   - /v3/previews
 versions:
   ghes: <3.4
 topics:
   - API
-ms.openlocfilehash: fe00e2ab78881edab8d0f7704f80f2f20163fdeb
-ms.sourcegitcommit: ac00e2afa6160341c5b258d73539869720b395a4
-ms.translationtype: HT
-ms.contentlocale: zh-CN
-ms.lasthandoff: 09/09/2022
-ms.locfileid: '147876003'
 ---
-API 预览允许您试用新的 API 以及对现有 API 方法的更改（在它们被纳入正式的 GitHub API 之前）。
 
-在预览期间，我们可以根据开发者的反馈更改某些功能。 如果我们确实进行了更改，我们将在[开发者博客](https://developer.github.com/changes/)上公布这些更改，而不会事先通知。
 
-要访问 API 预览，需要在请求的 `Accept` 标头中提供自定义[媒体类型](/rest/overview/media-types)。 每个预览的功能文档可指定要提供的自定义媒体类型。
+API previews let you try out new APIs and changes to existing API methods before they become part of the official GitHub API.
 
-{% ifversion ghes < 3.3 %}
+During the preview period, we may change some features based on developer feedback. If we do make changes, we'll announce them on the [developer blog](https://developer.github.com/changes/) without advance notice.
 
-## 增强型部署
-
-使用更详细和更精细的方式更好地控制[部署](/rest/reference/repos#deployments)。
-
-自定义媒体类型：`ant-man-preview`
-公布日期：[2016-04-06](https://developer.github.com/changes/2016-04-06-deployment-and-deployment-status-enhancements/)
-
-{% endif %}
-
-{% ifversion ghes < 3.3 %}
-
-## 反应
-
-管理对提交、问题和注释的[反应](/rest/reference/reactions)。
-
-自定义媒体类型：`squirrel-girl-preview`
-公布日期：[2016-05-12](https://developer.github.com/changes/2016-05-12-reactions-api-preview/)
-更新日期：[2016-06-07](https://developer.github.com/changes/2016-06-07-reactions-api-update/)
-
-{% endif %}
-
-{% ifversion ghes < 3.3 %}
-
-## 时间线
-
-获取问题或拉取请求的[事件列表](/rest/reference/issues#timeline)。
-
-自定义媒体类型：`mockingbird-preview`
-公布日期：[2016-05-23](https://developer.github.com/changes/2016-05-23-timeline-preview-api/)
-
-{% endif %}
-
-{% ifversion ghes < 3.3 %}
-## 项目
-
-管理[项目](/rest/reference/projects)。
-
-自定义媒体类型：`inertia-preview`
-公布日期：[2016-09-14](https://developer.github.com/changes/2016-09-14-projects-api/)
-更新日期：[2016-10-27](https://developer.github.com/changes/2016-10-27-changes-to-projects-api/) {% endif %} {% ifversion ghes < 3.3 %}
-
-## 提交搜索
-
-[搜索提交](/rest/reference/search)。
-
-自定义媒体类型：`cloak-preview`
-公布日期：[2017-01-05](https://developer.github.com/changes/2017-01-05-commit-search-api/) {% endif %} {% ifversion ghes < 3.3 %}
-
-## 仓库主题
-
-在返回存储库结果的[调用](/rest/reference/repos)中查看[存储库主题](/articles/about-topics/)列表。
-
-自定义媒体类型：`mercy-preview`
-公布日期：[2017-01-31](https://github.com/blog/2309-introducing-topics) {% endif %} {% ifversion ghes < 3.3 %}
-
-## 行为准则
-
-查看所有[行为准则](/rest/reference/codes-of-conduct)或获取存储库的当前行为准则。
-
-自定义媒体类型：`scarlet-witch-preview`
-
-{% endif %}
-
-{% ifversion ghes < 3.3 %}
-
-## 全局 web 挂钩
-
-为[组织](/webhooks/event-payloads/#organization)和[用户](/webhooks/event-payloads/#user)事件类型启用[全局 Webhook](/rest/reference/enterprise-admin#global-webhooks/)。 此 API 预览仅适用于 {% data variables.product.prodname_ghe_server %}。
-
-自定义媒体类型：`superpro-preview`
-公布日期：[2017-12-12](/rest/reference/enterprise-admin#global-webhooks)
-
-{% endif %}
-
-{% ifversion ghes < 3.3 %}
-
-## 要求签名提交
-
-现在，可以使用 API 来管理[要求在受保护的分支上进行签名提交](/rest/reference/repos#branches)的设置。
-
-自定义媒体类型：`zzzax-preview`
-公布日期：[2018-02-22](https://developer.github.com/changes/2018-02-22-protected-branches-required-signatures) {% endif %} {% ifversion ghes < 3.3 %}
-
-## 要求多次审批
-
-现在，可以使用 API [要求多次审批](/rest/reference/repos#branches)拉取请求。
-
-自定义媒体类型：`luke-cage-preview`
-公布日期：[2018-03-16](https://developer.github.com/changes/2018-03-16-protected-branches-required-approving-reviews)
-
-{% endif %}
-
-{% ifversion ghes < 3.3 %}
-
-## 项目卡详细信息
-
-REST API 对[问题事件](/rest/reference/issues#events)和[问题时间表事件](/rest/reference/issues#timeline)的响应现在可返回项目相关事件的 `project_card` 字段。
-
-自定义媒体类型：`starfox-preview`
-公布日期：[2018-09-05](https://developer.github.com/changes/2018-09-05-project-card-events)
-
-{% endif %}
-
-{% ifversion ghes < 3.3 %}
-
-## 部署状态
-
-现在可以更新[部署状态](/rest/reference/deployments#create-a-deployment-status)的 `environment` 并使用 `in_progress` 和 `queued` 状态。 创建部署状态时，现在可以使用 `auto_inactive` 参数将旧的 `production` 部署标记为 `inactive`。
-
-自定义媒体类型：`flash-preview`
-公布日期：[2018-10-16](https://developer.github.com/changes/2018-10-16-deployments-environments-states-and-auto-inactive-updates/)
-
-{% endif %}
-
-{% ifversion ghes < 3.3 %}
-
-## 仓库创建权限
-
-现在，您可以配置组织成员是否可以创建仓库以及他们可以创建哪些类型的仓库。 有关详细信息，请参阅“[更新组织](/rest/reference/orgs#update-an-organization)”。
-
-自定义媒体类型：`surtur-preview`
-公布日期：[2019-12-03](https://developer.github.com/changes/2019-12-03-internal-visibility-changes/)
-
-{% endif %}
+To access an API preview, you'll need to provide a custom [media type](/rest/overview/media-types) in the `Accept` header for your requests. Feature documentation for each preview specifies which custom media type to provide.
 
 {% ifversion ghes < 3.4 %}
-## 内容附件
+## Content attachments
 
-现在，您可以在 GitHub 中使用 {% data variables.product.prodname_unfurls %} API 提供有关链接到注册域的 URL 的更多信息。 有关详细信息，请参阅“[使用内容附件](/apps/using-content-attachments/)”。
+You can now provide more information in GitHub for URLs that link to registered domains by using the {% data variables.product.prodname_unfurls %} API. See "[Using content attachments](/apps/using-content-attachments/)" for more details.
 
-自定义媒体类型：`corsair-preview`
-公布日期：[2018-12-10](https://developer.github.com/changes/2018-12-10-content-attachments-api/)
-
-{% endif %} {% ifversion ghes < 3.3 %}
-
-## 启用和禁用页面
-
-可以使用[页面 API](/rest/reference/repos#pages) 中的新终结点来启用或禁用页面。 若要了解有关页面的详细信息，请参阅“[GitHub 页面基础知识](/categories/github-pages-basics)”。
-
-自定义媒体类型：`switcheroo-preview`
-公布日期：[2019-03-14](https://developer.github.com/changes/2019-03-14-enabling-disabling-pages/)
+**Custom media types:** `corsair-preview`
+**Announced:** [2018-12-10](https://developer.github.com/changes/2018-12-10-content-attachments-api/)
 
 {% endif %}
 
-{% ifversion ghes < 3.3 %}
 
-## 列出提交的分支或拉取请求
-
-可以使用[提交 API](/rest/reference/repos#commits) 中的两个新终结点来列出提交的分支或拉取请求。
-
-自定义媒体类型：`groot-preview`
-公布日期：[2019-04-11](https://developer.github.com/changes/2019-04-11-pulls-branches-for-commit/)
-
-{% endif %}
-
-{% ifversion ghes < 3.3 %}
-
-## 更新拉取请求分支
-
-可以使用新的终结点根据上游分支的 HEAD 更改来[更新拉取请求分支](/rest/reference/pulls#update-a-pull-request-branch)。
-
-自定义媒体类型：`lydian-preview`
-公布日期：[2019-05-29](https://developer.github.com/changes/2019-05-29-update-branch-api/)
-
-{% endif %} {% ifversion ghes < 3.3 %}
-
-## 创建和使用仓库模板
-
-可以使用新的终结点来[使用模板创建存储库](/rest/reference/repos#create-a-repository-using-a-template)，并通过将 `is_template` 参数设置为 `true`，[为经过身份验证的用户创建存储库](/rest/reference/repos#create-a-repository-for-the-authenticated-user)。 [获取存储库](/rest/reference/repos#get-a-repository)以检查是否使用 `is_template` 键将其设置为模板存储库。
-
-自定义媒体类型：`baptiste-preview`
-公布日期：[2019-07-05](https://developer.github.com/changes/2019-07-16-repository-templates-api/) {% endif %} {% ifversion ghes < 3.3 %}
-
-## 仓库 API 的新可见性参数
-
-可以在[存储库 API](/rest/reference/repos) 中设置和检索存储库可见性。
-
-自定义媒体类型：`nebula-preview`
-公布日期：[2019-11-25](https://developer.github.com/changes/2019-12-03-internal-visibility-changes/) {% endif %}
diff --git a/translations/zh-CN/content/rest/overview/endpoints-available-for-github-apps.md b/translations/zh-CN/content/rest/overview/endpoints-available-for-github-apps.md
index 79f190daec..19f1ec484a 100644
--- a/translations/zh-CN/content/rest/overview/endpoints-available-for-github-apps.md
+++ b/translations/zh-CN/content/rest/overview/endpoints-available-for-github-apps.md
@@ -13,11 +13,11 @@ versions:
 topics:
   - API
 shortTitle: GitHub App-enabled endpoints
-ms.openlocfilehash: ab79abe1df9a14f7fdcc73f863e7bce5aa4abd4c
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: d8bb53e1844b8171a1ce742fc38e4c4bb29013e7
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: zh-CN
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147410361'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148108618'
 ---
 <!-- The content of this page is rendered as a NextJS page component. -->
diff --git a/translations/zh-CN/content/rest/overview/permissions-required-for-github-apps.md b/translations/zh-CN/content/rest/overview/permissions-required-for-github-apps.md
index 67ed185aab..3d7ecba758 100644
--- a/translations/zh-CN/content/rest/overview/permissions-required-for-github-apps.md
+++ b/translations/zh-CN/content/rest/overview/permissions-required-for-github-apps.md
@@ -140,6 +140,7 @@ If you set the metadata permission to **No access** and select a permission that
 - [`GET /repos/:owner/:repo/actions/workflows`](/rest/reference/actions#list-repository-workflows) (read)
 - [`GET /repos/:owner/:repo/actions/workflows/:workflow_id`](/rest/reference/actions#get-a-workflow) (read)
 - [`GET /repos/:owner/:repo/actions/workflows/:workflow_id/runs`](/rest/reference/actions#list-workflow-runs) (read)
+- [`POST /repos/:owner/:repo/actions/workflows/:workflow_id/dispatches`](/rest/reference/actions#create-a-workflow-dispatch-event) (write)
 {% endif %}
 
 ## Administration
@@ -284,20 +285,14 @@ If you set the metadata permission to **No access** and select a permission that
 - [`GET /repos/:owner/:repo/code-scanning/alerts`](/rest/reference/code-scanning#list-code-scanning-alerts-for-a-repository) (read)
 - [`GET /repos/:owner/:repo/code-scanning/alerts/:alert_number`](/rest/reference/code-scanning#get-a-code-scanning-alert) (read)
 - [`PATCH /repos/:owner/:repo/code-scanning/alerts/:alert_number`](/rest/reference/code-scanning#update-a-code-scanning-alert) (write)
-{% ifversion fpt or ghec or ghes or ghae -%}
 - [`GET /repos/:owner/:repo/code-scanning/alerts/:alert_number/instances`](/rest/reference/code-scanning#list-instances-of-a-code-scanning-alert) (read)
-{% endif -%}
 - [`GET /repos/:owner/:repo/code-scanning/analyses`](/rest/reference/code-scanning#list-code-scanning-analyses-for-a-repository) (read)
-{% ifversion fpt or ghec or ghes or ghae -%}
 - [`GET /repos/:owner/:repo/code-scanning/analyses/:analysis_id`](/rest/reference/code-scanning#get-a-code-scanning-analysis-for-a-repository) (read)
-{% endif -%}
 {% ifversion fpt or ghec or ghes -%}
 - [`DELETE /repos/:owner/:repo/code-scanning/analyses/:analysis_id`](/rest/reference/code-scanning#delete-a-code-scanning-analysis-from-a-repository) (write)
 {% endif -%}
 - [`POST /repos/:owner/:repo/code-scanning/sarifs`](/rest/reference/code-scanning#upload-an-analysis-as-sarif-data) (write)
-{% ifversion fpt or ghec or ghes or ghae -%}
 - [`GET /repos/:owner/:repo/code-scanning/sarifs/:sarif_id`](/rest/reference/code-scanning#get-information-about-a-sarif-upload) (read)
-{% endif -%}
 {% ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4 -%}
 - [`GET /orgs/:org/code-scanning/alerts`](/rest/reference/code-scanning#list-code-scanning-alerts-by-organization) (read)
 {% endif -%}
diff --git a/translations/zh-CN/content/rest/repos/autolinks.md b/translations/zh-CN/content/rest/repos/autolinks.md
index cc6910adac..852de8e2c3 100644
--- a/translations/zh-CN/content/rest/repos/autolinks.md
+++ b/translations/zh-CN/content/rest/repos/autolinks.md
@@ -5,18 +5,18 @@ shortTitle: Autolinks
 intro: 为了帮助简化您的工作流程，您可以使用 API 向外部资源（如 JIRA 问题和 Zendesk 事件单）添加自动链接。
 versions:
   fpt: '*'
-  ghes: '>=3.3'
+  ghes: '*'
   ghae: '*'
   ghec: '*'
 topics:
   - API
 miniTocMaxHeadingLevel: 3
-ms.openlocfilehash: 1a0900a0665675526381987836631c7ff3496a81
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: c35d9232ec43cf9dc19c9559de0e8411fa85e242
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: zh-CN
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147066552'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148108091'
 ---
 ## 关于存储库自动链接 API
 
diff --git a/translations/zh-CN/content/rest/repos/lfs.md b/translations/zh-CN/content/rest/repos/lfs.md
index a258ba1f75..a402c744c9 100644
--- a/translations/zh-CN/content/rest/repos/lfs.md
+++ b/translations/zh-CN/content/rest/repos/lfs.md
@@ -3,7 +3,7 @@ title: Git LFS
 intro: 'You can enable or disable {% data variables.large_files.product_name_long %} (LFS) for a repository.'
 versions:
   fpt: '*'
-  ghes: '>=3.3'
+  ghes: '*'
   ghae: '*'
   ghec: '*'
 topics:
diff --git a/translations/zh-CN/content/rest/users/ssh-signing-keys.md b/translations/zh-CN/content/rest/users/ssh-signing-keys.md
new file mode 100644
index 0000000000..d9757685eb
--- /dev/null
+++ b/translations/zh-CN/content/rest/users/ssh-signing-keys.md
@@ -0,0 +1,21 @@
+---
+title: SSH 签名密钥
+intro: ''
+versions:
+  fpt: '*'
+  ghes: '>=3.7'
+  ghec: '*'
+topics:
+  - API
+miniTocMaxHeadingLevel: 3
+allowTitleToDifferFromFilename: true
+ms.openlocfilehash: c8b9b71cf14efdd119f759fa36f5baae8e7a9301
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: zh-CN
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148108067'
+---
+## 关于用户 SSH 签名密钥 API
+
+{% data reusables.user-settings.user-api %}
diff --git a/translations/zh-CN/content/search-github/searching-on-github/searching-issues-and-pull-requests.md b/translations/zh-CN/content/search-github/searching-on-github/searching-issues-and-pull-requests.md
index 0054f0a88c..71105cabcd 100644
--- a/translations/zh-CN/content/search-github/searching-on-github/searching-issues-and-pull-requests.md
+++ b/translations/zh-CN/content/search-github/searching-on-github/searching-issues-and-pull-requests.md
@@ -163,8 +163,8 @@ You can narrow your results by labels, using the `label` qualifier. Since issues
 | ------------- | -------------
 | <code>label:<em>LABEL</em></code> | [**label:"help wanted" language:ruby**](https://github.com/search?utf8=%E2%9C%93&q=label%3A%22help+wanted%22+language%3Aruby&type=Issues) matches issues with the label "help wanted" that are in Ruby repositories.
 |  | [**broken in:body -label:bug label:priority**](https://github.com/search?q=broken+in%3Abody+-label%3Abug+label%3Apriority&type=Issues) matches issues with the word "broken" in the body, that lack the label "bug", but *do* have the label "priority."
-| | [**label:bug label:resolved**](https://github.com/search?l=&q=label%3Abug+label%3Aresolved&type=Issues) matches issues with the labels "bug" and "resolved."{% ifversion fpt or ghes > 3.2 or ghae or ghec %}
-| | [**label:bug,resolved**](https://github.com/search?q=label%3Abug%2Cresolved&type=Issues) matches issues with the label "bug" or the label "resolved."{% endif %}
+| | [**label:bug label:resolved**](https://github.com/search?l=&q=label%3Abug+label%3Aresolved&type=Issues) matches issues with the labels "bug" and "resolved."
+| | [**label:bug,resolved**](https://github.com/search?q=label%3Abug%2Cresolved&type=Issues) matches issues with the label "bug" or the label "resolved."
 
 ## Search by milestone
 
@@ -266,8 +266,8 @@ You can filter pull requests based on their [review status](/pull-requests/colla
 | `review:approved` | [**type:pr review:approved**](https://github.com/search?utf8=%E2%9C%93&q=type%3Apr+review%3Aapproved&type=Issues) matches pull requests that a reviewer has approved.
 | `review:changes_requested` | [**type:pr review:changes_requested**](https://github.com/search?utf8=%E2%9C%93&q=type%3Apr+review%3Achanges_requested&type=Issues) matches pull requests in which a reviewer has asked for changes.
 | <code>reviewed-by:<em>USERNAME</em></code> | [**type:pr reviewed-by:gjtorikian**](https://github.com/search?utf8=%E2%9C%93&q=type%3Apr+reviewed-by%3Agjtorikian&type=Issues) matches pull requests reviewed by a particular person.
-| <code>review-requested:<em>USERNAME</em></code> | [**type:pr review-requested:benbalter**](https://github.com/search?utf8=%E2%9C%93&q=type%3Apr+review-requested%3Abenbalter&type=Issues) matches pull requests where a specific person is requested for review. Requested reviewers are no longer listed in the search results after they review a pull request. If the requested person is on a team that is requested for review, then review requests for that team will also appear in the search results.{% ifversion fpt or ghae or ghes > 3.2 or ghec %}
-| <code>user-review-requested:@me</code> | [**type:pr user-review-requested:@me**](https://github.com/search?q=is%3Apr+user-review-requested%3A%40me+) matches pull requests that you have directly been asked to review.{% endif %}
+| <code>review-requested:<em>USERNAME</em></code> | [**type:pr review-requested:benbalter**](https://github.com/search?utf8=%E2%9C%93&q=type%3Apr+review-requested%3Abenbalter&type=Issues) matches pull requests where a specific person is requested for review. Requested reviewers are no longer listed in the search results after they review a pull request. If the requested person is on a team that is requested for review, then review requests for that team will also appear in the search results.
+| <code>user-review-requested:@me</code> | [**type:pr user-review-requested:@me**](https://github.com/search?q=is%3Apr+user-review-requested%3A%40me+) matches pull requests that you have directly been asked to review.
 | <code>team-review-requested:<em>TEAMNAME</em></code> | [**type:pr team-review-requested:github/docs**](https://github.com/search?q=type%3Apr+team-review-requested%3Agithub%2Fdocs&type=pullrequests) matches pull requests that have review requests from the team `github/docs`. Requested reviewers are no longer listed in the search results after they review a pull request.
 
 ## Search by when an issue or pull request was created or last updated
diff --git a/translations/zh-CN/content/search/index.md b/translations/zh-CN/content/search/index.md
index fa0337ecc7..35190ef81c 100644
--- a/translations/zh-CN/content/search/index.md
+++ b/translations/zh-CN/content/search/index.md
@@ -6,11 +6,11 @@ versions:
   ghec: '*'
   ghes: '*'
   ghae: '*'
-ms.openlocfilehash: d7e276ed5305ffc8fd9732f6895fdf3b7461fb4c
-ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794
+ms.openlocfilehash: 1a780ae1a9481af58598ac2a37eec1553b08f627
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: zh-CN
-ms.lasthandoff: 09/09/2022
-ms.locfileid: '147648278'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148108030'
 ---
 
diff --git a/translations/zh-CN/content/sponsors/receiving-sponsorships-through-github-sponsors/index.md b/translations/zh-CN/content/sponsors/receiving-sponsorships-through-github-sponsors/index.md
index 2789f89036..fb3e5e2360 100644
--- a/translations/zh-CN/content/sponsors/receiving-sponsorships-through-github-sponsors/index.md
+++ b/translations/zh-CN/content/sponsors/receiving-sponsorships-through-github-sponsors/index.md
@@ -23,11 +23,11 @@ children:
   - /tax-information-for-github-sponsors
   - /disabling-your-github-sponsors-account
   - /unpublishing-your-github-sponsors-profile
-ms.openlocfilehash: 7f7a6e7a1f46dadaac3cf75b8387bf18dd22e0d0
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: d7d3b8f98e7acf74ee24e7cf705f0ddb3c5d4b26
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: zh-CN
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '145149674'
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148108029'
 ---
 
diff --git a/translations/zh-CN/data/glossaries/external.yml b/translations/zh-CN/data/glossaries/external.yml
index ab2e874d2f..2fd18cd191 100644
--- a/translations/zh-CN/data/glossaries/external.yml
+++ b/translations/zh-CN/data/glossaries/external.yml
@@ -1,564 +1,788 @@
-- term: '@提及'
+- term: '@mention'
   description:
-    用于通过在用户名前使用 `@` 来通知 GitHub 上的个人。GitHub 上组织中的用户也可以是可以被提及的团队中的一员。
-- term: 访问令牌
+    To notify a person on GitHub by using `@` before their username. Users in an organization on GitHub can also be a part of a team that can be
+    mentioned.
+- term: access token
   description: >-
-    在命令行或 API 上使用 Git 通过 HTTPS 执行 Git 操作时，用来代替密码的令牌。也称为个人访问令牌。
-- term: API 预览
+    A token that is used in place of a password when performing Git operations
+    over HTTPS with Git on the command line or the API. Also called a personal
+    access token.
+- term: API preview
   description: >-
-    一种尝试新 API 以及在现有 API 方法成为正式 GitHub API 之前对其进行更改的方式。
-- term: 工具
+    A way to try out new APIs and changes to existing API methods before they
+    become part of the official GitHub API.
+- term: appliance
   description: >-
-    一种结合恰当操作系统 (JeOS) 在行业标准硬件（通常是服务器）上或虚拟机中最佳运行的软件应用程序。
+    A software application combined with just enough operating system (JeOS) to
+    run optimally on industry-standard hardware (typically a server) or in a
+    virtual machine.
 - term: assignee
-  description: 分配到某个问题的用户。
-- term: 验证码
+  description: The user that is assigned to an issue.
+- term: authentication code
   description: >-
-    通过浏览器使用 2FA 登录时，除了 GitHub 密码外，还需要提供代码。此代码由应用程序生成或通过短信发送到你的手机。也称为“2FA 验证码”。
-- term: 基础分支
+    A code you'll supply, in addition to your GitHub password, when signing in
+    with 2FA via the browser. This code is either generated by an application or delivered to
+    your phone via text message. Also called a "2FA authentication code."
+- term: base branch
   description:
-    合并拉取请求时，将更改合并到其中的分支。创建拉取请求时，如果需要，可以将基础分支从存储库的默认分支更改为另一个分支。
-- term: 基本身份验证
+    The branch into which changes are combined when you merge a pull request.
+    When you create a pull request, you can change the base branch from the repository's default branch to another branch if required.
+- term: basic authentication
   description: >-
-    凭据以未加密文本形式发送的身份验证方法。
-- term: 个人简历
+    A method of authentication where the credentials are sent as
+    unencrypted text.
+- term: bio
   description: >-
-    个人资料中用户生成的描述：[为个人资料添加简介](/articles/adding-a-bio-to-your-profile)
-- term: 计费周期
-  description: 特定计费计划的时间间隔。
-- term: 计费邮箱
+    The user-generated description found on a profile:
+    [Adding a bio to your profile](/articles/adding-a-bio-to-your-profile)
+- term: billing cycle
+  description: The interval of time for your specific billing plan.
+- term: billing email
   description: >-
-    GitHub 用于发送收据、信用卡或 PayPal 费用及其他计费相关信息的组织电子邮件地址。
-- term: 计费管理员
-  description: 负责管理组织计费设置的组织成员。
-- term: 收费计划
+    The organization email address where GitHub sends receipts, credit card or
+    PayPal charges, and other billing-related communication.
+- term: billing manager
+  description: The organization member that manages billing settings for an organization.
+- term: billing plan
   description: >-
-    用户和组织的付款计划，包括每种计划的设置功能。
-- term: 追溯
+    Payment plans for users and organizations that include set features for each
+    type of plan.
+- term: blame
   description: >-
-    Git 中的“追溯”功能描述文件中每一行的最后修改，通常显示修订、作者和时间信息。例如，在跟踪添加某项功能的时间或导致特定 bug 的提交时，此功能非常有用。
+    The "blame" feature in Git describes the last modification to each line of a
+    file, which generally displays the revision, author and time. This is
+    helpful, for example, in tracking down when a feature was added, or which
+    commit led to a particular bug.
 - term: block
   description: >-
-    用于删除用户协作处理组织存储库的能力。
+    To remove a user's ability to collaborate on an organization's repositories.
 - term: branch
   description: >-
-    分支是存储库的并行版本。它包含在存储库中，但不会影响主分支，从而允许在不影响“在线”版本的情况下自由工作。完成所需更改后，可以将分支合并回主分支以发布你的更改。
-- term: 分支限制
+    A branch is a parallel version of a repository. It is contained within the
+    repository, but does not affect the primary or main branch allowing you to
+    work freely without disrupting the "live" version. When you've made the
+    changes you want to make, you can merge your branch back into the main
+    branch to publish your changes.
+- term: branch restriction
   description: >-
-    存储库管理员可以启用的一种限制，只允许特定用户或团队推送到分支或做出特定的更改。
-- term: 业务计划
+    A restriction that repository admins can enable so that only certain users
+    or teams can push or make certain changes to the branch.
+- term: Business plan
   description: >-
-    一种组织计费计划，可以在其中协作处理无限的公共和专用存储库，允许或要求组织成员使用 SAML SSO 对 GitHub 进行身份验证，以及使用 SAML 或 SCIM 预配和取消预配访问权限。
-- term: CA 证书
+    An organization billing plan where you can collaborate on unlimited public
+    and private repositories, allow or require organization members to
+    authenticate to GitHub using SAML SSO, and provision and deprovision access
+    with SAML or SCIM.
+- term: CA certificate
   description: >-
-    由证书机构 (CA) 颁发的数字证书，用于确保有效连接两台计算机，例如用户的计算机和 GitHub.com，以及验证站点的所有权。
-- term: 卡
-  description: 项目板中与某个问题或拉取请求关联的可移动方框。
-- term: 检查
+    A digital certificate issued by Certificate Authority (CA) that ensures there are valid connections between two machines, such as a user's computer and GitHub.com and verifies the ownership of a site.
+- term: card
+  description: A movable square within a project board associated with an issue or pull request.
+- term: check
   description: >-
-    检查是 {% data variables.product.product_name %} 上的一种状态检查类型。请参阅“[状态检查](#status-checks)”。
-- term: 签出
+    A check is a type of status check on {% data variables.product.product_name %}. See "[Status checks](#status-checks)."
+- term: checkout
   description: >-
-    可在命令行上使用 `git checkout` 创建新分支，将当前工作分支更改为其他分支，也可使用 `git checkout [分支名称] [文件路径]` 从不同的分支切换到不同版本的文件。“签出”操作使用对象数据库中的树对象或 Blob 更新全部或部分工作树，如果整个工作树指向新分支，则更新索引和 HEAD。
-- term: 挑拣
+    You can use `git checkout` on the command line to create a new branch, change your current working branch to a different branch, or even to switch to a different version of a file from a different branch with `git checkout [branchname] [path to file]`. The "checkout" action updates all or part of the working tree with a tree object or
+    blob from the object database, and updates the index and HEAD if the whole
+    working tree is pointing to a new branch.
+- term: cherry-picking
   description: >-
-    用于从一系列更改（通常是提交）中选择更改的子集，并将它们记录为位于不同代码库之上的一系列新更改。在 Git 中，此操作是由 `git cherry-pick` 命令执行的，用于提取另一个分支上现有提交引入的更改，并根据当前分支的提示将其记录为新提交。有关详细信息，请参阅 Git 文档中的 [git-cherry-pick](https://git-scm.com/docs/git-cherry-pick)。
-- term: 子团队
+    To choose a subset of changes from a series of changes (typically commits) and record them as a new series of changes on top of a different codebase. In Git, this is performed by the `git cherry-pick` command to extract the change introduced by an existing commit on another branch and to record it based on the tip of the current branch as a new commit. For more information, see [git-cherry-pick](https://git-scm.com/docs/git-cherry-pick) in the Git documentation.
+- term: child team
   description: >-
-    在嵌套团队内，继承父团队访问权限和 @提及的子团队。
-- term: 清洁
+    Within nested teams, the subteam that inherits the parent team's access
+    permissions and @mentions.
+- term: clean
   description: >-
-    如果工作树与当前 HEAD 引用的版本对应，则工作树是清洁的。另请参阅“脏”。
-- term: 克隆
+    A working tree is clean if it corresponds to the revision referenced by the
+    current HEAD. Also see "dirty".
+- term: clone
   description: >-
-    克隆是存在于计算机上（而不是网站的服务器上）的存储库副本，或者表示创建该副本的行为。进行克隆时，可以在无需联机的情况下，在首选编辑器中编辑文件并使用 Git 跟踪你的更改。克隆的存储库仍将连接到远程版本，这样你就可以将本地更改推送到远程，以便在联机时使其保持同步。
-- term: 聚类分析
+    A clone is a copy of a repository that lives on your computer instead of on
+    a website's server somewhere, or the act of making that copy. When you make a
+    clone, you can edit the files in your preferred editor and use Git to keep
+    track of your changes without having to be online. The repository you cloned
+    is still connected to the remote version so that you can push your local
+    changes to the remote to keep them synced when you're online.
+- term: clustering
   description: >-
-    跨多个节点运行 GitHub Enterprise 服务并在它们之间实现请求的负载平衡的功能。
-- term: 代码频率图
+    The ability to run GitHub Enterprise services across multiple nodes and load
+    balance requests between them.
+- term: code frequency graph
   description: >-
-    一种显示存储库历史记录中每周的内容添加和删除的存储库图。
-- term: 行为准则
-  description: 定义关于如何参与社区的标准的文档。
-- term: 代码所有者
+    A repository graph that shows the content additions and deletions for each
+    week in a repository's history.
+- term: code of conduct
+  description: A document that defines standards for how to engage in a community.
+- term: code owner
   description: >-
-    被指定为部分存储库代码所有者的个人。当有人打开对代码所有者拥有的代码进行更改的拉取请求（非草稿模式）时，会自动请求代码所有者进行审查。
-- term: 协作者
+    A person who is designated as an owner of a portion of a repository's code. The code owner is automatically requested for review when someone opens a pull request (not in draft mode) that makes changes to code the code owner owns.
+- term: collaborator
   description: >-
-    协作者是受存储库所有者邀请参与，对存储库拥有读取和写入权限的人。
-- term: 提交 (commit)
+    A collaborator is a person with read and write access to a repository who
+    has been invited to contribute by the repository owner.
+- term: commit
   description: >-
-    提交或“修订”是对文件（或文件集）的单独更改。当提交以保存工作时，Git 将创建一个唯一的 ID（也称为“SHA”或“哈希”），它允许记录提交的特定更改以及提交者和提交时间。提交通常包含提交消息，该消息简要说明所做的更改。
-- term: 提交作者
-  description: 进行提交的用户。
-- term: 提交图
+    A commit, or "revision", is an individual change to a file (or set of
+    files). When you make a commit to save your work, Git creates a unique ID (a.k.a. the "SHA" or "hash") that allows you to keep record of the specific changes committed along with who made them and when. Commits usually contain a
+    commit message which is a brief description of what changes were made.
+- term: commit author
+  description: The user who makes the commit.
+- term: Commit graph
   description: >-
-    显示过去一年对存储库的所有提交的存储库图。
-- term: 提交 ID
-  description: 也称为 SHA。用于识别提交的 40 个字符的校验和哈希。
-- term: 提交消息
+    A repository graph that shows all the commits made to a repository in the
+    past year.
+- term: commit ID
+  description: Also known as SHA. A 40-character checksum hash that identifies the commit.
+- term: commit message
   description: >-
-    随附于提交的简短描述性文字，用于沟通提交引入的更改。
-- term: 比较分支
+    Short, descriptive text that accompanies a commit and communicates the change
+    the commit is introducing.
+- term: compare branch
   description: >-
-    用于创建拉取请求的分支。将此分支与为拉取请求选择的基础分支进行比较，并识别更改。合并拉取请求时，基础分支将使用比较分支中的更改进行更新。也称为拉取请求的“头部分支”。
-- term: 持续集成
+    The branch you use to create a pull request.
+    This branch is compared to the base branch you choose for the pull request, and the changes are identified.
+    When the pull request is merged, the base branch is updated with the changes from the compare branch.
+    Also known as the "head branch" of the pull request.
+- term: continuous integration
   description: >-
-    也称为 CI。有人将更改提交到 GitHub 上配置的存储库后，就会运行自动生成和测试的过程。CI 是软件开发中常见的最佳做法，有助于检测错误。
-- term: 参与图
+    Also known as CI. A process that runs automated builds and tests once a person commits a change to a configured repository on GitHub. CI is a common best practice in software development that helps detect errors.
+- term: contribution graph
   description: >-
-    用户个人资料中显示其参与记录（最长一年，按天显示）的部分。
-- term: 参与指南
-  description: 说明人们应如何参与项目的文档。
-- term: 参与
+    The part of a user's profile that shows their contributions over a period of
+    up to one year, day by day.
+- term: contribution guidelines
+  description: A document explaining how people should contribute to your project.
+- term: contributions
   description: >-
-    GitHub 上的特定活动，将会：- 添加方块到用户的参与图：“[什么算作参与](/articles/viewing-contributions-on-your-profile/#what-counts-as-a-contribution)”- 添加活动到用户个人资料上的时间线：“[参与活动](/articles/viewing-contributions-on-your-profile/#contribution-activity)”
-- term: 参与者
+    Specific activities on GitHub that will:
+    - Add a square to a user's contribution graph: "[What counts as a contribution](/articles/viewing-contributions-on-your-profile/#what-counts-as-a-contribution)"
+    - Add activities to a user's timeline on their profile: "[Contribution activity](/articles/viewing-contributions-on-your-profile/#contribution-activity)"
+- term: contributor
   description: >-
-    参与者是指对存储库没有协作者权限但参与过项目，并且他们打开的拉取请求已合并到存储库的人员。
-- term: 参与者图
-  description: 显示存储库前 100 个参与者的存储库图。
-- term: 优惠券
+    A contributor is someone who does not have collaborator access to a repository but has contributed to a project and had a pull request they opened merged into the repository.
+- term: contributors graph
+  description: A repository graph that displays the top 100 contributors to a repository.
+- term: coupon
   description: >-
-    一种由 GitHub 提供的代码，用户或组织可使用它支付其所有或部分订阅费用。
+    A GitHub-provided code that users or organizations can use to pay for all or
+    part of their subscription.
 - term: cron
-  description: 类似于 Unix 的计算机操作系统中的一个基于时间的作业计划程序。
+  description: A time-based job scheduler in Unix-like computer operating systems.
 - term: cURL
-  description: 在命令行或脚本中用于传输数据。
-- term: 仪表板
+  description: Used in command lines or scripts to transfer data.
+- term: dashboard
   description: >-
-    个人仪表板是 GitHub 上的活动的主要中心。通过个人仪表板，可跟踪正在关注或处理的问题和拉取请求、导航到顶层存储库和团队页面，以及了解正在关注或参与的存储库中的最近活动。还可以发现新的存储库，这些存储库是根据正在关注的用户和已加星标的存储库而推荐的。要仅查看特定组织的活动，请访问该组织的仪表板。有关详细信息，请参阅“[关于个人仪表板](/articles/about-your-personal-dashboard)”或“[关于组织仪表板](/articles/about-your-organization-dashboard)”。
-- term: 默认分支
+    Your personal dashboard is the main hub of your activity on GitHub. From your personal dashboard, you can keep track of issues and pull requests you're following or working on, navigate to your top repositories and team pages, and learn about recent activity in repositories you're watching or participating in. You can also discover new repositories, which are recommended based on users you're following and repositories you have starred. To only view activity for a specific organization, visit your organization's dashboard. For more information, see "[About your personal dashboard](/articles/about-your-personal-dashboard)" or "[About your organization dashboard](/articles/about-your-organization-dashboard)."
+- term: default branch
   description: >-
-    存储库中新拉取请求和代码提交的基础分支。每个存储库至少具有一个分支，Git 在初始化存储库时将会创建该分支。第一个分支通常被称为 {% ifversion ghes < 3.2 %}`master`{% else %}`main`{% endif %}，通常是默认分支。
-- term: 依赖项图
+    The base branch for new pull requests and code commits in a repository. Each repository has at least one branch, which Git creates when you initialize the repository. The first branch is usually called {% ifversion ghes < 3.2 %}`master`{% else %}`main`{% endif %}, and is often the default branch.
+- term: dependents graph
   description: >-
-    一种显示依赖于公共存储库的包、项目和存储库的存储库图。
-- term: 依赖项关系图
+    A repository graph that shows the packages, projects, and repositories that depend on a
+    public repository.
+- term: dependency graph
   description: >-
-    一种显示存储库所依赖的包和项目的存储库图。
-- term: 部署密钥
+    A repository graph that shows the packages and projects that the repository depends on.
+- term: deploy key
   description: >-
-    部署密钥是存储在服务器上并授予对单个 GitHub 存储库的访问权限的 SSH 密钥。此密钥直接附加到存储库，而不是附加到个人用户帐户。
-- term: 拆离的 HEAD
+    A deploy key is an SSH key that is stored on your server and grants access
+    to a single GitHub repository. This key is attached directly to the
+    repository instead of to a personal user account.
+- term: detached HEAD
   description: >-
-    如果正在处理拆离的 HEAD，Git 将发出警告，这意味着 Git 没有指向某个分支，并且所做的任何提交都不会出现在提交历史记录中。 例如，当签出不属于任何特定分支的最新提交的任意提交时，表示你正在处理“拆离的 HEAD”。
-- term: 诊断
-  description: GitHub Enterprise 实例设置和环境的概述。
+    Git will warn you if you're working on a detached HEAD, which means that Git
+    is not pointing to a branch and that any commits you make will not appear in
+    commit history.  For example, when you check out an arbitrary commit that
+    is not the latest commit of any particular branch, you're working on a
+    "detached HEAD."
+- term: diagnostics
+  description: An overview of a GitHub Enterprise instance's settings and environment.
 - term: diff
   description: >-
-    差异是两次提交或保存的更改之间的更改差异。差异将直观地描述自上次提交以来文件中添加的或删除的内容。
+    A diff is the difference in changes between two commits, or saved changes.
+    The diff will visually describe what was added or removed from a file since
+    its last commit.
 - term: directory
   description: >-
-    包含一个或多个文件/文件夹的文件夹。可以创建目录来组织存储库的内容。
-- term: 脏
+    A folder containing one or more files or folders. You can create directories to organize the contents of a repository.
+- term: dirty
   description: >-
-    工作树如果包含尚未提交到当前分支的更改，将被视为“脏”。
-- term: 电子邮件通知
-  description: 已发送到用户的电子邮件地址的通知。
-- term: 企业帐户
-  description: "企业帐户允许集中管理多个组织的策略和计费。{% data reusables.gated-features.enterprise-accounts %}"
-- term: 资源管理器
+    A working tree is considered "dirty" if it contains modifications that have
+    not been committed to the current branch.
+- term: email notifications
+  description: Notifications sent to a user's email address.
+- term: enterprise account
+  description: Enterprise accounts allow you to centrally manage policy and billing for multiple organizations. {% data reusables.gated-features.enterprise-accounts %}
+- term: Explorer
   description: >-
-    GraphiQL 的实例，它是“图形交互式浏览器内 GraphQL IDE”。
-- term: 转发
+    An instance of GraphiQL, which is a "graphical interactive in-browser GraphQL
+    IDE."
+- term: fast-forward
   description: >-
-    转发是一种特殊类型的合并，其中有一个修订，并且你将“合并”另一个分支的更改，这些更改恰好是你所拥有的内容的后代。在这种情况下，不会进行新的合并提交，而只是更新到此修订。这将在远程存储库的远程跟踪分支上经常发生。
-- term: 功能分支
+    A fast-forward is a special type of merge where you have a revision and you
+    are "merging" another branch's changes that happen to be a descendant of
+    what you have. In such a case, you do not make a new merge commit but
+    instead just update to this revision. This will happen frequently on a
+    remote-tracking branch of a remote repository.
+- term: feature branch
   description: >-
-    用于试验新功能或修复非生产环境中的问题的分支。也称为主题分支。
-- term: 围栏代码块
-  description: "可以在代码块前后使用三个反引号 \\`\\`\\` 通过 GitHub 风格的 Markdown 创建的缩进代码块。请参阅此 [示例](/articles/creating-and-highlighting-code-blocks#fenced-code-blocks)。"
-- term: “etch
+    A branch used to experiment with a new feature or fix an issue that is not in production. Also called a topic branch.
+- term: fenced code block
+  description: An indented block of code you can create with GitHub Flavored Markdown using triple backticks \`\`\` before and after the code block. See this [example](/articles/creating-and-highlighting-code-blocks#fenced-code-blocks).
+- term: fetch
   description: >-
-    当使用 `git fetch` 时，将更改从远程存储库添加到本地工作分支，而无需提交它们。与 `git pull` 不同，提取允许在将更改提交到本地分支之前查看该更改。
-- term: 跟进（用户）
-  description: 用于获取关于另一个用户的贡献和活动的通知。
-- term: 强制推送
+    When you use `git fetch`, you're adding changes from the remote repository to
+    your local working branch without committing them. Unlike `git pull`, fetching
+    allows you to review changes before committing them to your local branch.
+- term: following (users)
+  description: To get notifications about another user's contributions and activity.
+- term: force push
   description: >-
-    使用本地更改覆盖远程存储库而不考虑冲突的 Git 推送。
-- term: 分支
+    A Git push that overwrites the remote repository with local changes without
+    regard for conflicts.
+- term: fork
   description: >-
-    分支是位于帐户中的其他用户存储库的个人副本。通过分支，可随意更改项目，而不会影响原始上游存储库。还可以在上游存储库中打开拉取请求，并使分支与最新更改保持同步，因为这两个存储库仍处于连接状态。
-- term: 免费计划
+    A fork is a personal copy of another user's repository that lives on your
+    account. Forks allow you to freely make changes to a project without
+    affecting the original upstream repository. You can also open a pull request in
+    the upstream repository and keep your fork synced with the latest changes since
+    both repositories are still connected.
+- term: Free plan
   description: >-
-    免费的用户帐户计费计划。用户可以与无限的协作者协作处理无限的公共存储库。
+    A user account billing plan that is free. Users can collaborate on unlimited
+    public repositories with unlimited collaborators.
 - term: gist
   description: >-
-    gist 是一个可共享的文件，可在 GitHub 上对其进行编辑、克隆和创建分支。可以将 gist 设为{% ifversion ghae %}internal{% else %}公开{% endif %}或机密，但任何{% ifversion ghae %}any enterprise member{% else %}拥有该 URL 的人{% endif %}都可以使用机密。
+    A gist is a shareable file that you can edit, clone, and fork on GitHub.
+    You can make a gist {% ifversion ghae %}internal{% else %}public{% endif %} or secret, although secret gists will be
+    available to {% ifversion ghae %}any enterprise member{% else %}anyone{% endif %} with the URL.
 - term: Git
   description: >-
-    Git 是一个开源程序，用于跟踪文本文件中的更改。它由 Linux 操作系统的作者编写，是 GitHub、社交和用户界面赖以构建的核心技术。
-- term: GitHub Apps
+    Git is an open source program for tracking changes in text files. It was
+    written by the author of the Linux operating system, and is the core
+    technology that GitHub, the social and user interface, is built on top of.
+- term: GitHub App
   description: >-
-    GitHub Apps 为整个组织提供服务，并在执行其功能时使用自己的标识。它们可以直接安装在组织和用户帐户上，并获得对特定存储库的访问权限。它们随附精细的权限和内置的 Webhook。
-- term: GitHub 风格的 Markdown
-  description: "GitHub 特定的 Markdown，用于在 GitHub 上格式化 prose 和代码。请参阅 [GitHub 风格的 Markdown 规范](https://github.github.com/gfm/) 或 [在 GitHub 上编写和设置格式入门](/articles/getting-started-with-writing-and-formatting-on-github)。"
-- term: GitHub 导入工具
+    GitHub Apps provide a service to an entire organization and use their own
+    identity when performing their function. They can be installed directly on
+    organizations and user accounts and granted access to specific repositories.
+    They come with granular permissions and built-in webhooks.
+- term: GitHub Flavored Markdown
+  description: GitHub-specific Markdown used to format prose and code across GitHub. See [GitHub Flavored Markdown Spec](https://github.github.com/gfm/) or [Getting started with writing and formatting on GitHub](/articles/getting-started-with-writing-and-formatting-on-github).
+- term: GitHub Importer
   description: >-
-    一种可让用户快速将源代码存储库（包括提交和修订历史记录）导入 GitHub 的工具。
+    A tool that quickly imports source code repositories, including commits and
+    revision history, to GitHub for users.
 - term: GitHub Jobs
   description: >-
-    一个 GitHub 网站，雇主可在其中发布 GitHub 用户可能感兴趣的职位。
+    A GitHub site where employers can post jobs that GitHub users may be
+    interested in.
 - term: GitHub Marketplace
   description: >-
-    GitHub 用户和组织用于购买和安装可扩展及补充其工作流的应用程序的子站点。
+    A subsite for GitHub users and organizations to purchase and install
+    applications that extend and complement their workflow.
 - term: GitHub Pages
   description: >-
-    也称为 Pages。设计为直接托管 GitHub 存储库中的个人、组织或项目页面的静态站点托管服务。
+    Also referred to as Pages. A static site hosting service designed to host
+    your personal, organization, or project pages directly from a GitHub
+    repository.
 - term: GitHub Wiki
-  description: 用于在 GitHub 存储库上托管 Wiki 样式文档的部分。
+  description: A section for hosting wiki style documentation on a GitHub repository.
 - term: gitfile
   description: >-
-    一个纯文本 `.git` 文件，它始终位于工作树的根目录中，并指向包含整个 Git 存储库及其元数据的 Git 目录。可在命令行上使用作为真正存储库的 `git rev-parse --git-dir` 查看存储库的此文件。
+    A plain `.git` file, which is always at the root of a working tree and points to the Git directory, which has the entire Git repository and its meta data. You can view this file for your repository on the command line with `git rev-parse --git-dir`.
+    that is the real repository.
 - term: GraphQL
   description: >-
-    一种针对 API 的查询语言，以及用于使用现有数据完成这些查询的运行时。
+    A query language for APIs and a runtime for fulfilling those queries with
+    your existing data.
 - term: HEAD
-  description: 定义的分支提交，通常是分支顶端的最新提交。
-- term: 头部分支
-  description: 合并拉取请求时，将其更改合并到基础分支中的分支。也称为“比较分支”。
+  description: A defined commit of a branch, usually the most recent commit at the tip of the branch.
+- term: head branch
+  description: The branch whose changes are combined into the base branch
+    when you merge a pull request.
+    Also known as the "compare branch."
 - term: 'Hello, World'
   description: >-
-    “Hello, World”程序是向用户输出或显示“Hello, World!”的计算机程序。由于此程序通常非常简单，因此常被用作编程语言的基本语法的示例，并作为学习新编程语言的第一个常见练习。
-- term: 高可用性
+    A "Hello, World!" program is a computer program that outputs or displays
+    "Hello, World!" to a user. Since this program is usually very simple, it is
+    often used as an example of a programming language's basic syntax and
+    serves as a common first exercise for learning a new programming language.
+- term: high-availability
   description: >-
-    可持续运行较长时间的系统或组件。
-- term: 挂钩
+    A system or component that is continuously operational for a desirably long
+    length of time.
+- term: hook
   description: >-
-    在几个 Git 命令的正常执行过程中，将调用允许开发人员添加功能或进行检查的可选脚本。通常，挂钩允许预先验证且可能中止的命令，并允许在操作完成后发布后通知。
+    During the normal execution of several Git commands, call-outs are made to
+    optional scripts that allow a developer to add functionality or checking.
+    Typically, the hooks allow for a command to be pre-verified and potentially
+    aborted, and allow for a post-notification after the operation is done.
 - term: hostname
   description: >-
-    人类可读的昵称，与连接到网络的设备地址对应。
-- term: 默认肖像
+    Human-readable nicknames that correspond to the address of a device
+    connected to a network.
+- term: identicon
   description: >-
-    当用户注册 GitHub 时，用作默认个人资料照片的自动生成图像。用户可以用自己的个人资料照片替换其标识图标。
-- term: 标识提供者
+    An auto-generated image used as a default profile photo when users sign up for
+    GitHub. Users can replace their identicon with their own profile photo.
+- term: identity provider
   description: >-
-    也称为 IdP。受信任的提供者，可让你使用 SAML 单一登录 (SSO) 访问其他网站。
+    Also known as an IdP. A trusted provider that lets you use SAML single
+    sign-on (SSO) to access other websites.
 - term: instance
   description: >-
-    包含在组织配置和控制的虚拟机中的组织 GitHub 私人副本。
-- term: 集成
+    An organization's private copy of GitHub contained within a virtual machine
+    that they configure and control.
+- term: integration
   description: >-
-    与 GitHub 集成的第三方应用程序。这些应用程序可以是 GitHub Apps、OAuth Apps 或 Webhook。
-- term: 问题
+    A third-party application that integrates with GitHub. These can be GitHub
+    Apps, OAuth Apps, or webhooks.
+- term: issue
   description: >-
-    问题是与存储库相关的建议改进、任务或问题。问题可由任何人创建（对于公共存储库），并由存储库协作者进行管理。每个问题都包含自己的讨论线程。还可以使用标签对问题进行分类，并将其分配给某人。
+    Issues are suggested improvements, tasks or questions related to the
+    repository. Issues can be created by anyone (for public repositories), and
+    are moderated by repository collaborators. Each issue contains its own discussion thread. You can also categorize an issue with labels and assign it to someone.
 - term: Jekyll
-  description: 针对个人、项目或组织站点的静态站点生成器。
-- term: Jekyll 主题选择器
+  description: A static site generator for personal, project, or organization sites.
+- term: Jekyll Theme Chooser
   description: >-
-    一种无需编辑或复制 CSS 文件即可为 Jekyll 站点选择视觉对象主题的自动化方式。
-- term: 密钥指纹
-  description: 用于标识较长公钥的短字节序列。
-- term: 密钥链
-  description: macOS 中的密码管理系统。
-- term: 关键字 (keyword)
-  description: 用在拉取请求中时可关闭问题的特定词。
+    An automated way to select a visual theme for your Jekyll site without editing or
+    copying CSS files.
+- term: key fingerprint
+  description: A short sequence of bytes used to identify a longer public key.
+- term: keychain
+  description: A password management system in macOS.
+- term: keyword
+  description: A specific word that closes an issue when used within a pull request.
 - term: label
   description: >-
-    问题或拉取请求上的标记。存储库随附一系列默认标签，但用户也可创建自定义标签。
+    A tag on an issue or pull request. Repositories come with a handful of
+    default labels, but users can create custom labels.
 - term: LFS
   description: >-
-    Git Large File Storage。一种开源 Git 扩展，用于对大文件进行版本控制。
+    Git Large File Storage. An open source Git extension for versioning large
+    files.
 - term: license
   description: >-
-    一种可随附于项目的文档，告知人们能够对源代码执行哪些操作，不能执行哪些操作。
+    A document that you can include with your project to let people know what
+    they can and can't do with your source code.
 - term: Linguist
   description: >-
-    GitHub 上使用的一个库，用于检测 Blob l语言，忽略二进制或 vendor 文件，抑制差异中生成的文件，以及生成语言细分图。
-- term: 行注释
-  description: 拉取请求内特定代码行上的评论。
-- term: 行结束符
+    A library used on GitHub to detect blob languages, ignore binary or vendored
+    files, suppress generated files in diffs, and generate language breakdown
+    graphs.
+- term: line comment
+  description: A comment within a pull request on a specific line of code.
+- term: line ending
   description: >-
-    用符号表示文本文件中一行结束的不可见字符。
-- term: 已锁定个人帐户
+    An invisible character or characters that symbolize the end of a line in a
+    text file.
+- term: locked personal account
   description: >-
-    用户无法访问的个人帐户。当用户将其付费帐户降级到免费帐户或者其付费计划过期时，帐户将被锁定。
-- term: 管理控制台
+    A personal account that cannot be accessed by the user. Accounts are locked
+    when users downgrade their paid account to a free one, or if their paid plan
+    is past due.
+- term: management console
   description: >-
-    GitHub Enterprise 界面中包含管理功能的部分。
+    A section within the GitHub Enterprise interface that contains
+    administrative features.
 - term: Markdown
   description: >-
-    Markdown 是一种非常简单的语义文件格式，与 .doc、.rtf 及 .txt 区别不大。Markdown 可帮助没有网络发布功底的人编写 prose（包括链接、列表、项目符号等）并将其显示为网站。GitHub 支持 Markdown 并使用一种特殊形式的 Markdown，称为 GitHub 风格的 Markdown。请参阅 [GitHub 风格的 Markdown 规范](https://github.github.com/gfm/) 或 [在 GitHub 上编写和设置格式入门](/articles/getting-started-with-writing-and-formatting-on-github)。
-- term: 标记
-  description: 一种用于注释和格式化文档的系统。
+    Markdown is an incredibly simple semantic file format, not too dissimilar
+    from .doc, .rtf and .txt. Markdown makes it easy for even those without a
+    web-publishing background to write prose (including with links, lists,
+    bullets, etc.) and have it displayed like a website. GitHub supports
+    Markdown and uses a particular form of Markdown called GitHub Flavored Markdown. See [GitHub Flavored Markdown Spec](https://github.github.com/gfm/) or [Getting started with writing and formatting on GitHub](/articles/getting-started-with-writing-and-formatting-on-github).
+- term: markup
+  description: A system for annotating and formatting a document.
 - term: main
   description: >-
-    {% ifversion fpt or ghes > 3.1 or ghae %}默认开发分支。每当创建 Git 存储库时，都会创建一个名为 `main` 的分支，并使其成为活动分支。在大多数情况下，这包含本地开发，不过这纯粹是按照惯例的，也不是必需的。{% else %}通常选择名称作为存储库默认分支的 `master` 的替代品。{% endif %}
-- term: 主
+    The default development branch. Whenever you create a Git repository,
+    a branch named `main` is created, and becomes the active branch.
+    In most cases, this contains the local development, though that is purely by
+    convention and is not required.
+- term: master
   description: >-
-    许多 Git 存储库中的默认分支。默认情况下，每当在命令行上创建新的 Git 存储库时，都会创建一个名为 `master` 的分支。许多工具现在为默认分支使用替代名称。{% ifversion fpt or ghes > 3.1 or ghae %}例如，当在 GitHub 上创建新存储库时，默认分支称为 `main`。{% endif %}
-- term: 成员图
-  description: 显示存储库所有分支的存储库图。
-- term: 提及
+    The default branch in many Git repositories. By default, when you create
+    a new Git repository on the command line, a branch called `master` is created.
+    Many tools now use an alternative name for the default branch. For example,
+    when you create a new repository on GitHub, the default branch is called `main`.
+- term: members graph
+  description: A repository graph that shows all the forks of a repository.
+- term: mention
   description: >-
-    通过在用户名前加上 @ 符号发送给用户的通知。GitHub 上组织中的用户也可以是可以被提及的团队中的一员。
+    A notification sent to a user by prefacing their username with the @ symbol.
+    Users in an organization on GitHub can also be a part of a team that can be
+    mentioned.
 - term: merge
   description: >-
-    合并从一个分支（在同一个存储库中或来自分支）中获取更改并将其应用到另一个分支。这通常作为“拉取请求”（可被视为合并请求）或通过命令行发生。如果没有冲突的更改，可以通过 GitHub.com Web 界面的拉取请求完成合并，也可以始终通过命令行完成合并。
-- term: 合并冲突
+    Merging takes the changes from one branch (in the same repository or from a
+    fork), and applies them into another. This often happens as a "pull request"
+    (which can be thought of as a request to merge), or via the command line. A
+    merge can be done through a pull request via the GitHub.com web
+    interface if there are no conflicting changes, or can always be done via the
+    command line.
+- term: merge conflict
   description: >-
-    合并分支之间发生的差异。当人们对相同文件的相同行进行不同的更改时，或者一个人编辑文件而另一个人删除同一文件时，就会发生合并冲突。必须先解决合并冲突，然后才能合并分支。
-- term: 里程碑
+    A difference that occurs between merged branches. Merge conflicts happen
+    when people make different changes to the same line of the same file, or
+    when one person edits a file and another person deletes the same file. The
+    merge conflict must be resolved before you can merge the branches.
+- term: milestone
   description: >-
-    一种跟踪存储库中问题或拉取请求组进度的方式。
-- term: 镜像
-  description: 存储库的新副本。
-- term: 嵌套团队
+    A way to track the progress on groups of issues or pull requests in a
+    repository.
+- term: mirror
+  description: A new copy of a repository.
+- term: nested team
   description: >-
-    父团队的子团队。可以拥有多个子（或嵌套）团队。
-- term: 网络图
+    A child team of a parent team. You can have multiple children (or nested)
+    teams.
+- term: network graph
   description: >-
-    显示整个存储库网络的分支历史记录的存储库图，其中包括根存储库的分支以及包含网络独有提交的分叉的分支。
-- term: 消息馈送
+    A repository graph that shows the branch history of the entire repository
+    network, including branches of the root repository and branches of forks
+    that contain commits unique to the network.
+- term: news feed
   description: >-
-    监视的存储库或人员的活动视图。组织的消息馈送显示该组织拥有的存储库上的活动。
-- term: 非快进
+    An activity view of repositories or people you watch. An organization's News
+    Feed shows activity on repositories owned by the organization.
+- term: non-fast-forward
   description: >-
-    当存储库的本地副本未与上游存储库同步时，需要在推送本地更改之前获取上游更改。
-- term: 通知
+    When your local copy of a repository is out-of-sync with the upstream
+    repository and you need to fetch the upstream changes before you push your
+    local changes.
+- term: notification
   description: >-
-    通过 Web 或电子邮件（具体取决于你的设置）提供的更新，它提供有关你感兴趣的活动的信息。
+    Updates, delivered by either the web or email depending on your settings,
+    that give you information about the activities you're interested in.
 - term: OAuth App
   description: >-
-    使用访问令牌而非密码来访问用户信息的第三方应用程序。
-- term: OAuth 令牌
-  description: OAuth Apps 中用于访问用户信息的访问令牌。
-- term: 外部协作者
+    A third-party application that uses access tokens rather than passwords to
+    access information for users.
+- term: OAuth token
+  description: The access token used in OAuth Apps to access information for users.
+- term: outside collaborator
   description: >-
-    已被授予对组织的一个或多个存储库的访问权限，但对该组织没有其他访问权限且不属于组织成员的用户。
-- term: 开源
+    A user who has been given access to one or more of an organization’s
+    repositories, but has no other access to the organization and is not a
+    member of the organization.
+- term: open source
   description: >-
-    开源软件是任何人都可以自由使用、修改和共享（以修改和未修改的形式）的软件。今天，“开源”的概念往往超越了软件，它代表一种协作理念：任何人都可以在线获取工作材料，然后创建分支、修改和讨论它们并为项目做出贡献。
+    Open source software is software that can be freely used, modified, and
+    shared (in both modified and unmodified form) by anyone. Today the concept
+    of "open source" is often extended beyond software, to represent a
+    philosophy of collaboration in which working materials are made available
+    online for anyone to fork, modify, discuss, and contribute to.
 - term: organization
   description: >-
-    组织是由两个或多个用户组成的组，它们通常反映了真实世界的组织。它们由用户管理，可以同时包含存储库和团队。
-- term: 组织所有者
-  description: 对自己拥有的组织具有完全管理访问权限的用户。
+    Organizations are a group of two or more users that typically mirror
+    real-world organizations. They are administered by users and can contain
+    both repositories and teams.
+- term: organization owner
+  description: Users who have full administrative access to the organization they own.
 - term: origin
   description: >-
-    默认上游存储库。大多数项目至少有一个他们跟踪的上游项目。默认情况下，原点用于此目的。
+    The default upstream repository. Most projects have at least one upstream
+    project that they track. By default, origin is used for that purpose.
 - term: owner
   description: >-
-    对组织具有完全管理权限的组织成员。
-- term: 父团队
+    Organization members that have complete administrative access to the
+    organization.
+- term: parent team
   description: >-
-    在嵌套团队内，子团队继承访问权限和 @提及的主要团队。
-- term: 参与通知
+    Within nested teams, the main team from which child teams inherit access
+    permissions and @mentions.
+- term: participating notifications
   description: >-
-    关于用户名或团队被提及或之前在评论中回复的问题或拉取请求中对话更新的通知。
-- term: 永久链接
-  description: 指向特定网页的永久静态超链接。
-- term: 个人帐户
+    A notification about an update in a conversation in an issue or pull request
+    where your username or team was mentioned or where you have previously replied
+    in a comment.
+- term: permalink
+  description: A permanent static hyperlink to a particular web page.
+- term: personal account
   description: >-
-    属于个别用户的 GitHub 帐户。
-- term: 主电子邮件地址
+    A GitHub account that belongs to an individual user.
+- term: primary email address
   description: >-
-    GitHub 用于发送收据、信用卡或 PayPal 费用及其他计费相关信息的主要电子邮件地址。
-- term: 固定存储库
+    The main email address where GitHub sends receipts, credit card or PayPal
+    charges, and other billing-related communication.
+- term: pinned repository
   description: >-
-    用户已决定在其个人资料中突出显示的存储库。
-- term: 预接收挂钩
+    A repository that a user has decided to display prominently on their
+    profile.
+- term: pre-receive hooks
   description: >-
-    在可用于实现质量检查的 GitHub Enterprise 服务器上运行的脚本。
-- term: 专用贡献
-  description: 对专用（与公共相对）存储库的贡献。
-- term: 专用存储库
+    Scripts that run on the GitHub Enterprise server that you can use to
+    implement quality checks.
+- term: private contributions
+  description: Contributions made to a private (vs. public) repository.
+- term: private repository
   description: >-
-    专用存储库仅对存储库所有者和所有者指定的协作者可见。
-- term: 生产分支
+    Private repositories are only visible to the repository owner and
+    collaborators that the owner specified.
+- term: production branch
   description: >-
-    包含可使用或部署到应用程序或站点的最终更改的分支。
-- term: 个人资料
-  description: 显示 GitHub 上用户活动相关信息的页面。
-- term: 个人资料照片
+    A branch with final changes that are ready to be used or deployed to an application or site.
+- term: profile
+  description: The page that shows information about a user's activity on GitHub.
+- term: profile photo
   description: >-
-    用户上传到 GitHub 的自定义图像，用于标识其活动，通常与其用户名结合使用。这也称为“应用”。
-- term: 项目板
+    A custom image users upload to GitHub to identify their activity, usually
+    along with their username. This is also referred to as an avatar.
+- term: project board
   description: >-
-    GitHub 内由问题、拉取请求和注释组成的板，按列分类为卡。
-- term: 受保护分支
+    Boards within GitHub that are made up of issues, pull requests, and notes
+    that are categorized as cards in columns.
+- term: protected branch
   description: >-
-    受保护分支在存储库管理员选择保护的分支上阻止 Git 的多个功能。不能在没有通过所需检查或批准所需审查的情况下强制推送、删除、合并更改这些分支，也不能将文件从 GitHub Web 界面上传到它。受保护分支通常为默认分支。
-- term: 公共贡献
-  description: 对公共（与专用相对）存储库的贡献。
-- term: 公共存储库
+    Protected branches block several features of Git on a branch that a
+    repository administrator chooses to protect. They can't be force pushed,
+    deleted, have changes merged without required checks passing or required
+    reviews approved, or have files uploaded to it from the GitHub web
+    interface. A protected branch is usually the default branch.
+- term: public contributions
+  description: Contributions made to a public (vs. private) repository.
+- term: public repository
   description: >-
-    公共存储库可供任何人查看，包括不是 GitHub 用户的人员。
+    A public repository can be viewed by anyone, including people who aren't
+    GitHub users.
 - term: pull
   description: >-
-    拉取指的是提取更改并合并这些更改的行为。例如，如果有人编辑了你们正在合作处理的远程文件，则需要将这些更改拉取到本地副本，以使其保持最新状态。另请参阅“提取”。
-- term: 拉取权限
-  description: 读取权限的同义词。
-- term: 拉取请求
+    Pull refers to when you are fetching in changes and merging them. For
+    instance, if someone has edited the remote file you're both working on,
+    you'll want to pull in those changes to your local copy so that it's up to
+    date. See also fetch.
+- term: pull access
+  description: A synonym for read access.
+- term: pull request
   description: >-
-    拉取请求是由用户提交的对存储库的建议更改，由存储库协作者接受或拒绝。与问题一样，每个拉取请求都有自己的讨论论坛。
-- term: 拉取请求审查
+    Pull requests are proposed changes to a repository submitted by a user and
+    accepted or rejected by a repository's collaborators. Like issues, pull
+    requests each have their own discussion forum.
+- term: pull request review
   description: >-
-    拉取请求中协作者批准更改或在拉取请求合并之前申请进一步更改的评论。
-- term: 脉冲图
-  description: 提供存储库活动概述的存储库图。
-- term: 打卡图
+    Comments from collaborators on a pull request that approve the changes or
+    request further changes before the pull request is merged.
+- term: pulse graph
+  description: A repository graph that gives you an overview of a repository's activity.
+- term: punch graph
   description: >-
-    根据周日期和时间显示存储库更新频率的存储库图
+    A repository graph that shows the frequency of updates to a repository based
+    on the day of week and time of day
 - term: push
   description: >-
-    推送意味着将提交的更改发送到 GitHub.com 上的远程存储库。例如，如果在本地更改了某些内容，则可以推送这些更改，以便其他人可以访问它们。
-- term: 推送分支
+    To push means to send your committed changes to a remote repository on
+    GitHub.com. For instance, if you change something locally, you can push those changes so that others may access them.
+- term: push a branch
   description: >-
-    如果成功将分支推送到远程存储库，则可以使用本地分支中的更改更新远程分支。当“推送分支”时，Git 将在远程存储库中搜索分支的 HEAD 引用，并验证它是否是该分支的本地 HEAD 引用的直接上级。验证后，Git 将所有对象（可从本地 HEAD 引用访问，但在远程存储库中丢失）拉取到远程对象数据库，然后更新远程 HEAD 引用。如果远程 HEAD 不是本地 HEAD 的上级，则推送将失败。
-- term: 推送访问权限
-  description: 写入访问权限的同义词。
-- term: 读取访问权限
+    When you successfully push a branch to a remote repository, you update the remote branch with changes from your local branch. When you "push a branch", Git will search for the branch's HEAD ref in the remote repository and verify that it is a direct ancestor to the branch's local HEAD ref. Once verified, Git pulls all objects (reachable from the local HEAD ref and missing from the remote repository) into the remote object database and then updates the remote HEAD ref. If the remote HEAD is not an ancestor to the local HEAD, the push fails.
+- term: push access
+  description: A synonym for write access.
+- term: read access
   description: >-
-    存储库上的权限级别，可让用户从存储库中拉取或读取信息。所有公共存储库都为所有 GitHub 用户提供读取访问权限。拉取访问权限的同义词。
-- term: 自述文件
-  description: 一个包含有关存储库中文件的信息的文本文件，该文件通常是存储库访问者将看到的第一个文件。自述文件以及存储库许可证、参与指南和行为准则可帮助你共享期望并管理对项目的贡献。
-- term: 变基
+    A permission level on a repository that allows the user to pull, or read,
+    information from the repository. All public repositories give read access to
+    all GitHub users. A synonym for pull access.
+- term: README
+  description: A text file containing information about the files in a repository that is typically the first file a visitor to your repository will see. A README file, along with a repository license, contribution guidelines, and a code of conduct, helps you share expectations and manage contributions to your project.
+- term: rebase
   description: >-
-    要将一系列变更从一个分支重新应用到不同的基础分支，并将该分支的 HEAD 重置为结果。
-- term: 恢复代码
-  description: 帮助你重新获取对 GitHub 帐户的访问权限的代码。
-- term: 发布
-  description: GitHub 封装软件并向用户提供软件的方式。
+    To reapply a series of changes from a branch to a different base, and reset
+    the HEAD of that branch to the result.
+- term: recovery code
+  description: A code that helps you regain access to your GitHub account.
+- term: release
+  description: GitHub's way of packaging and providing software to your users.
 - term: remote
   description: >-
-    这是托管在服务器上的存储库或分支的版本，很可能是 GitHub.com。远程版本可以连接到本地克隆，以便可以同步更改。
-- term: 远程存储库
+    This is the version of a repository or branch that is hosted on a server, most likely
+    GitHub.com. Remote versions can be connected to local clones so that changes can be
+    synced.
+- term: remote repository
   description: >-
-    用于跟踪同一个项目但储存在其他位置的存储库。
-- term: 远程 URL
+    A repository that is used to track the same project but resides somewhere
+    else.
+- term: remote URL
   description: >-
-    存储代码的位置：GitHub、其他用户分支甚至不同服务器上的存储库。
-- term: 副本 (replica)
+    The place where your code is stored: a repository on GitHub, another user's
+    fork, or even a different server.
+- term: replica
   description: >-
-    为主要 GitHub Enterprise 实例提供冗余的 GitHub Enterprise 实例。
+    A GitHub Enterprise instance that provides redundancy for the primary GitHub
+    Enterprise instance.
 - term: repository
   description: >-
-    存储库是 GitHub 最基本的元素。它们很容易被想象为项目的文件夹。存储库包含所有项目文件（包括文档），并存储每个文件的修订历史记录。存储库可以有多个协作者，并且可以是公共的，也可以是专用的。
-- term: 存储库缓存
+    A repository is the most basic element of GitHub. They're easiest to imagine
+    as a project's folder. A repository contains all of the project files
+    (including documentation), and stores each file's revision history.
+    Repositories can have multiple collaborators and can be either public or
+    private.
+- term: repository cache
   description: >-
-    GitHub Enterprise 服务器实例的存储库的只读镜像，位于分布式团队和 CI 客户端附近。
-- term: 存储库图
-  description: 存储库数据的视觉对象表现形式。
-- term: 存储库维护者
+    A read-only mirror of repositories for your GitHub Enterprise server instance, located near
+    distributed teams and CI clients.
+- term: repository graph
+  description: A visual representation of your repository's data.
+- term: repository maintainer
   description: >-
-    管理存储库的人。此人可以帮助分类问题，并使用标签和其他功能来管理存储库的工作。此人还可能负责更新自述文件和参与文件。
-- term: 必需拉取请求审查
+    Someone who manages a repository. This person may help triage issues and use labels and other features to manage the work of the repository. This person may also be responsible for keeping the README and contributing files updated.
+- term: required pull request review
   description: >-
-    必需审查确保拉取请求至少获得一次审批审查之后，协作者才可更改受保护分支。
-- term: 必需状态检查
+    Required reviews ensure that pull requests have at least one approved review
+    before collaborators can make changes to a protected branch.
+- term: required status check
   description: >-
-    拉取请求检查，确保在协作者可以对受保护分支进行更改前，所有必需的 CI 测试都已通过。
+    Checks on pull requests that ensure all required CI tests are passing before
+    collaborators can make changes to a protected branch.
 - term: resolve
-  description: 手动修复自动合并失败的操作。
-- term: 还原
+  description: The action of fixing up manually what a failed automatic merge left behind.
+- term: revert
   description: >-
-    当在 GitHub 上还原拉取请求时，会自动打开一个新的拉取请求，其中包含一个从原始合并拉取请求还原合并提交的提交。在 Git 中，可以使用 `git revert` 还原提交。
-- term: 审查
+    When you revert a pull request on GitHub, a new pull request is automatically opened, which has one commit that reverts the merge commit
+    from the original merged pull request. In Git, you can revert commits with `git revert`.
+- term: review
   description: >-
-    审查允许对存储库具有访问权限的其他人评论拉取请求中建议的更改、批准更改或在合并拉取请求之前请求进一步更改。
-- term: 根目录
-  description: 层次结构中的第一个目录。
-- term: 根文件系统
-  description: 基本操作系统和 GitHub Enterprise 应用程序环境。
-- term: 已保存回复
+    Reviews allow others with access to your repository to comment on the changes proposed in pull
+    requests, approve the changes, or request further changes before the pull
+    request is merged.
+- term: root directory
+  description: The first directory in a hierarchy.
+- term: root filesystem
+  description: The base operating system and the GitHub Enterprise application environment.
+- term: saved reply
   description: >-
-    可保存并添加到 GitHub 用户帐户的评论，这样你就可以在 GitHub 中的问题和拉取请求中使用它。
+    A comment you can save and add to your GitHub user account so that you can
+    use it across GitHub in issues and pull requests.
 - term: scope
   description: >-
-    OAuth App 可以请求访问公共和非公共数据的命名权限组。
-- term: 席位
+    Named groups of permissions that an OAuth App can request to access both
+    public and non-public data.
+- term: seat
   description: >-
-    GitHub Enterprise 组织内的用户。这可以被称为“席位数”。
-- term: 机密团队
+    A user within a GitHub Enterprise organization. This may be referred to as
+    "seat count."
+- term: secret team
   description: >-
-    只有团队其他人以及具有所有者权限的人员可见的团队。
-- term: 安全日志
+    A team that is only visible to the other people on the team and people with owner
+    permissions.
+- term: security log
   description: >-
-    列出最近 50 次操作或过去 90 天内执行的操作的日志。
-- term: 服务器到服务器请求
+    A log that lists the last 50 actions or those performed within the last 90
+    days.
+- term: server-to-server request
   description: >-
-    由充当机器人的应用程序使用的 API 请求，独立于任何特定用户。例如，按计划运行并关闭长时间没有活动的问题的应用程序。使用此类身份验证的应用程序不使用许可的 GitHub 帐户，因此，在具有允许使用一定数量许可证的计费计划的企业中，服务器到服务器机器人不会使用其中一个 GitHub 许可证。服务器到服务器请求中使用的令牌是通过 [GitHub API](/rest/reference/apps#create-an-installation-access-token-for-an-app) 以编程方式获取的。另请参阅“[用户到服务器请求](#user-to-server-request)”。
-- term: 服务挂钩
+    An API request used by an application that acts as a bot, independently of any particular user. For example, an application that runs on a scheduled basis and closes issues where there has been no activity for a long time. Applications that use this type of authentication don't use a licensed GitHub account so, in an enterprise with a billing plan that allows a certain number of licenses to be used, a server-to-server bot is not consuming one of your GitHub licenses. The token used in a server-to-server request is acquired programmatically, via [the GitHub API](/rest/reference/apps#create-an-installation-access-token-for-an-app). See also, "[user-to-server request](#user-to-server-request)."
+- term: service hook
   description: >-
-    也称为“Webhook”。 Webhook 是一种通知方式，只要存储库或组织上发生特定操作，就会发送通知到外部 Web 服务器。
-- term: 单一登录
+    Also called "webhook." Webhooks provide a way for notifications to be
+    delivered to an external web server whenever certain actions occur on a
+    repository or organization.
+- term: single sign-on
   description: >-
-    也称为 SSO。允许用户登录到一个位置，然后标识提供者 (IdP) 授予用户对其他服务提供程序的访问权限。
-- term: 快照
-  description: 虚拟机在某一时间点的检查点。
-- term: 压缩
-  description: 用于将多个提交合并为一个提交。也称为 Git 命令。
-- term: SSH 密钥
+    Also called SSO. Allows users to sign in to a single location - an identity
+    provider (IdP) - that then gives the user access to other service providers.
+- term: snapshot
+  description: A checkpoint of a virtual machine at a point in time.
+- term: squash
+  description: To combine multiple commits into a single commit. Also a Git command.
+- term: SSH key
   description: >-
-    SSH 密钥是一种使用加密消息向在线服务器标识自己的方法。就好像计算机对其他服务具有自己的唯一密码一样。{% data variables.product.product_name %}使用 SSH 密钥将信息安全地传输到计算机。
-- term: 暂存实例
+    SSH keys are a way to identify yourself to an online server, using an encrypted message. It's as if your computer has its own unique password to another service. {% data variables.product.product_name %} uses SSH keys to securely transfer information to your computer.
+- term: staging instance
   description: >-
-    在将修改应用到实际 GitHub Enterprise 实例之前测试修改的一种方法。
+    A way to test modifications before they are applied to your actual GitHub
+    Enterprise instance.
 - term: status
   description: >-
-    拉取请求中的视觉对象表现形式，表示提交符合为参与的存储库设置的条件。
-- term: 状态检查
+    A visual representation within a pull request that your commits meet the
+    conditions set for the repository you're contributing to.
+- term: status checks
   description: >-
-    状态检查是为在存储库中进行的每个提交而运行的外部进程，例如持续集成生成。有关详细信息，请参阅“[关于状态检查](/articles/about-status-checks)”。
-- term: 星级
+    Status checks are external processes, such as continuous integration builds, which run for each commit you make in a repository. For more information, see "[About status checks](/articles/about-status-checks)."
+- term: star
   description: >-
-    对存储库的书签或表示赞赏。星级是一种手动对项目的受欢迎程度进行排名的方法。
-- term: 订阅
-  description: 用户或组织的 GitHub 计划。
-- term: 团队
+    A bookmark or display of appreciation for a repository. Stars are a manual
+    way to rank the popularity of projects.
+- term: subscription
+  description: A user or organization's GitHub plan.
+- term: team
   description: >-
-    通过级联访问权限和提及来反映公司或组结构的组织成员组。
-- term: 团队维护者
+    A group of organization members that reflect your company or group's
+    structure with cascading access permissions and mentions.
+- term: team maintainer
   description: >-
-    具有组织所有者一部分团队管理权限的组织成员。
-- term: 团队计划
+    Organization members that have a subset of permissions available to
+    organization owners to manage teams.
+- term: Team plan
   description: >-
-    提供无限公共和专用存储库的组织计费计划。
-- term: 时间线
-  description: 拉取请求或用户个人资料中的一系列事件。
-- term: 主题分支
+    An organization billing plan that gives you unlimited public and private
+    repositories.
+- term: timeline
+  description: A series of events in a pull request or on a user profile.
+- term: topic branch
   description: >-
-    一个常规的 Git 分支，开发人员使用它来识别开发的概念线。由于分支非常简单且成本低廉，因此通常希望有几个小分支，每个分支都包含定义非常明确的概念或小的增量但相关的更改。也可以称为特征分支。
+    A regular Git branch that is used by a developer to identify a conceptual
+    line of development. Since branches are very easy and inexpensive, it is
+    often desirable to have several small branches that each contain very well
+    defined concepts or small incremental yet related changes. Can also be called a feature branch.
 - term: topics
   description: >-
-    一种方法，用于探索特定主题领域中的存储库，查找要参与的项目，以及在 GitHub 上发现特定问题的新解决方案。
-- term: 流量图
+    A way to explore repositories in a particular subject area, find projects to
+    contribute to, and discover new solutions to a specific problem on GitHub.
+- term: traffic graph
   description: >-
-    显示存储库流量的存储库图，包括完整克隆（非提取）、过去 14 天的访问者、推荐站点及热门内容。
-- term: 传输
+    A repository graph that shows a repository's traffic, including full clones
+    (not fetches), visitors from the past 14 days, referring sites, and popular
+    content.
+- term: transfer
   description: >-
-    转让存储库是指更改存储库的所有者。新所有者能够立即管理存储库的内容、问题、拉取请求、发行版和设置。
-- term: 上游
+    To transfer a repository means to change the owner of a repository. The new owner will be able to
+    immediately administer the repository's contents, issues, pull requests,
+    releases, and settings.
+- term: upstream
   description: >-
-    在谈论分支或分叉时，原始存储库上的主分支通常被称为“上游”，因为它是获取其他更改的主要位置。正在处理的分支/分叉则被称为“下游”。也称为原点。
-- term: 上游分支
+    When talking about a branch or a fork, the primary branch on the original
+    repository is often referred to as the "upstream", since that is the main
+    place that other changes will come in from. The branch/fork you are working
+    on is then called the "downstream". Also called origin.
+- term: upstream branch
   description: >-
-    合并到相关分支（或相关分支重新基于的分支）中的默认分支。它是通过 `branch.<name>.remote` 和 `branch.<name>.merge` 配置的。如果 A 的上游分支是原点/B，有时表示为“A 是跟踪原点/B”。
+    The default branch that is merged into the branch in question (or the branch
+    in question is rebased onto). It is configured via `branch.<name>.remote` and
+    `branch.<name>.merge`. If the upstream branch of A is origin/B sometimes we
+    say "A is tracking origin/B".
 - term: user
   description: >-
-    用户是拥有个人 GitHub 帐户的人员。每个用户都有自己的个人资料，并且可以拥有多个公共或专用存储库。他们可以创建或受邀加入组织，也可以在其他用户的存储库上进行协作。
+    Users are people with personal GitHub accounts. Each user has a personal profile, and
+    can own multiple repositories, public or private. They can create or be
+    invited to join organizations or collaborate on another user's repository.
 - term: username
-  description: GitHub 上的用户句柄。
-- term: 用户到服务器请求
+  description: A user's handle on GitHub.
+- term: user-to-server request
   description: >-
-    由代表特定用户执行任务的应用程序所使用的 API 请求。如果使用用户到服务器身份验证执行任务，则在 GitHub 上显示为由用户通过应用程序完成的任务。例如，可以选择在第三方应用程序中创建问题，该应用程序将代表用户在 GitHub 上执行此操作。应用程序可使用用户到服务器请求执行的任务范围受到应用和用户的权限和访问权限的限制。用户到服务器请求中所使用的令牌是通过 OAuth 获取的。有关详细信息，请参阅“[识别和授权 GitHub Apps 的用户](/developers/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps)”。 另请参阅“[服务器到服务器请求](#server-to-server-request)”。
-- term: 可见团队
-  description: 可被每个组织成员查看和 @提及的团队。
-- term: 监视
+    An API request used by an application that performs a task on behalf of a particular user. Where a task is carried out with user-to-server authentication it's shown on GitHub as having been done by a user via an application. For example, you might choose to create an issue from within a third-party application, and the application would do this on your behalf on GitHub. The scope of tasks an application can perform using a user-to-server request is restricted by both the app's and the user's permissions and access. The token used in a user-to-server request is acquired via OAuth. For more information, see "[Identifying and authorizing users for GitHub Apps](/developers/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps)." See also, "[server-to-server request](#server-to-server-request)."
+- term: visible team
+  description: A team that can be viewed and @mentioned by every organization member.
+- term: watch
   description: >-
-    可以监视存储库或问题，以在对问题或拉取请求进行更新时接收通知。
-- term: 查看通知
-  description: 关于用户订阅的存储库中活动的通知。
-- term: Web 通知
+    You can watch a repository or issue to receive notifications when updates are made to an issue or pull request.
+- term: watching notifications
+  description: A notification about activity in a repository a user has subscribed to.
+- term: web notifications
   description: >-
-    显示在 GitHub 的 Web 界面中的通知：https://github.com/notifications
+    Notifications displayed in the web interface on GitHub:
+    https://github.com/notifications
 - term: webhooks
   description: >-
-    Webhook 允许构建或设置订阅 GitHub.com 上某些事件的 GitHub Apps。Webhook 是一种通知方式，只要存储库或组织上发生特定操作，就会发送通知到外部 Web 服务器。也被称为服务挂钩。
-- term: 写入访问权限
+    Webhooks allow you to build or set up GitHub Apps which subscribe to certain
+    events on GitHub.com. Webhooks provide a way for notifications to be
+    delivered to an external web server whenever certain actions occur on a
+    repository or organization. Also called a service hook.
+- term: write access
   description: >-
-    存储库上的权限级别，可让用户推送或写入对存储库的更改。
+    A permission level on a repository that allows the user to push, or write,
+    changes to the repository.
diff --git a/translations/zh-CN/data/graphql/ghes-3.2/graphql_previews.enterprise.yml b/translations/zh-CN/data/graphql/ghes-3.2/graphql_previews.enterprise.yml
deleted file mode 100644
index 051a7af5e2..0000000000
--- a/translations/zh-CN/data/graphql/ghes-3.2/graphql_previews.enterprise.yml
+++ /dev/null
@@ -1,117 +0,0 @@
-- title: 使用包版本删除
-  description: 此预览支持允许删除私有包版本 DeletePackageVersion 突变。
-  toggled_by: ':package-deletes-preview'
-  announcement: null
-  updates: null
-  toggled_on:
-    - Mutation.deletePackageVersion
-  owning_teams:
-    - '@github/pe-package-registry'
-- title: 部署
-  description: 此预览支持部署突变和新部署功能。
-  toggled_by: ':flash-preview'
-  announcement: null
-  updates: null
-  toggled_on:
-    - DeploymentStatus.environment
-    - Mutation.createDeploymentStatus
-    - CreateDeploymentStatusInput
-    - CreateDeploymentStatusPayload
-    - Mutation.createDeployment
-    - CreateDeploymentInput
-    - CreateDeploymentPayload
-  owning_teams:
-    - '@github/c2c-actions-service'
-- title: MergeInfoPreview - 有关拉取请求合并状态的更多详细信息。
-  description: 此预览支持访问提供有关拉取请求合并状态的更多详细信息的字段。
-  toggled_by: ':merge-info-preview'
-  announcement: null
-  updates: null
-  toggled_on:
-    - PullRequest.canBeRebased
-    - PullRequest.mergeStateStatus
-  owning_teams:
-    - '@github/pe-pull-requests'
-- title: UpdateRefsPreview - 在单个操作中更新多个 ref。
-  description: 此预览支持在单个操作中更新多个 ref。
-  toggled_by: ':update-refs-preview'
-  announcement: null
-  updates: null
-  toggled_on:
-    - Mutation.updateRefs
-    - GitRefname
-    - RefUpdate
-    - UpdateRefsInput
-    - UpdateRefsPayload
-  owning_teams:
-    - '@github/reponauts'
-- title: 项目事件详细信息
-  description: 此预览将项目、项目卡和项目列详细信息添加到与项目相关的议题事件。
-  toggled_by: ':starfox-preview'
-  announcement: null
-  updates: null
-  toggled_on:
-    - AddedToProjectEvent.project
-    - AddedToProjectEvent.projectCard
-    - AddedToProjectEvent.projectColumnName
-    - ConvertedNoteToIssueEvent.project
-    - ConvertedNoteToIssueEvent.projectCard
-    - ConvertedNoteToIssueEvent.projectColumnName
-    - MovedColumnsInProjectEvent.project
-    - MovedColumnsInProjectEvent.projectCard
-    - MovedColumnsInProjectEvent.projectColumnName
-    - MovedColumnsInProjectEvent.previousProjectColumnName
-    - RemovedFromProjectEvent.project
-    - RemovedFromProjectEvent.projectColumnName
-  owning_teams:
-    - '@github/github-projects'
-- title: 创建内容附件
-  description: 此预览支持创建内容附件。
-  toggled_by: ':corsair-preview'
-  announcement: null
-  updates: null
-  toggled_on:
-    - Mutation.createContentAttachment
-  owning_teams:
-    - '@github/feature-lifecycle'
-- title: 标签预览
-  description: 此预览支持添加、更新、创建和删除标签。
-  toggled_by: ':bane-preview'
-  announcement: null
-  updates: null
-  toggled_on:
-    - Mutation.createLabel
-    - CreateLabelPayload
-    - CreateLabelInput
-    - Mutation.deleteLabel
-    - DeleteLabelPayload
-    - DeleteLabelInput
-    - Mutation.updateLabel
-    - UpdateLabelPayload
-    - UpdateLabelInput
-  owning_teams:
-    - '@github/pe-pull-requests'
-- title: 导入项目
-  description: 此预览增加了对导入项目的支持。
-  toggled_by: ':slothette-preview'
-  announcement: null
-  updates: null
-  toggled_on:
-    - Mutation.importProject
-  owning_teams:
-    - '@github/pe-issues-projects'
-- title: 团队审查任务预览
-  description: 此预览支持更新团队审查任务的设置。
-  toggled_by: ':stone-crop-preview'
-  announcement: null
-  updates: null
-  toggled_on:
-    - Mutation.updateTeamReviewAssignment
-    - UpdateTeamReviewAssignmentInput
-    - TeamReviewAssignmentAlgorithm
-    - Team.reviewRequestDelegationEnabled
-    - Team.reviewRequestDelegationAlgorithm
-    - Team.reviewRequestDelegationMemberCount
-    - Team.reviewRequestDelegationNotifyTeam
-  owning_teams:
-    - '@github/pe-pull-requests'
\ No newline at end of file
diff --git a/translations/zh-CN/data/learning-tracks/code-security.yml b/translations/zh-CN/data/learning-tracks/code-security.yml
index 3f545dfa4c..3b35eb0a73 100644
--- a/translations/zh-CN/data/learning-tracks/code-security.yml
+++ b/translations/zh-CN/data/learning-tracks/code-security.yml
@@ -1,25 +1,29 @@
 # Feature available only on dotcom
 security_advisories:
-  title: '修复并披露安全漏洞'
-  description: '使用存储库安全建议私下修复报告的漏洞并获取 CVE。'
+  title: 'Fix and disclose a security vulnerability'
+  description: 'Using repository security advisories to privately fix a reported vulnerability and get a CVE.'
   featured_track: '{% ifversion fpt or ghec %}true{% else %}false{% endif %}'
   guides:
-    - /code-security/repository-security-advisories/about-coordinated-disclosure-of-security-vulnerabilities
-    - /code-security/repository-security-advisories/creating-a-repository-security-advisory
-    - /code-security/repository-security-advisories/adding-a-collaborator-to-a-repository-security-advisory
-    - /code-security/repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability
-    - /code-security/repository-security-advisories/publishing-a-repository-security-advisory
-    - /code-security/repository-security-advisories/editing-a-repository-security-advisory
-    - /code-security/repository-security-advisories/withdrawing-a-repository-security-advisory
-    - /code-security/repository-security-advisories/removing-a-collaborator-from-a-repository-security-advisory
+    - /code-security/security-advisories/repository-security-advisories/about-coordinated-disclosure-of-security-vulnerabilities
+    - /code-security/security-advisories/global-security-advisories/about-the-github-advisory-database
+    - /code-security/security-advisories/global-security-advisories/about-global-security-advisories
+    - /code-security/security-advisories/repository-security-advisories/about-repository-security-advisories
+    - /code-security/security-advisories/repository-security-advisories/creating-a-repository-security-advisory
+    - /code-security/security-advisories/repository-security-advisories/adding-a-collaborator-to-a-repository-security-advisory
+    - /code-security/security-advisories/repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability
+    - /code-security/security-advisories/repository-security-advisories/publishing-a-repository-security-advisory
+    - /code-security/security-advisories/repository-security-advisories/editing-a-repository-security-advisory
+    - /code-security/security-advisories/repository-security-advisories/withdrawing-a-repository-security-advisory
+    - /code-security/security-advisories/repository-security-advisories/removing-a-collaborator-from-a-repository-security-advisory
+    - /code-security/security-advisories/guidance-on-reporting-and-writing/best-practices-for-writing-repository-security-advisories
 
 # Feature available on dotcom and GHES 3.3+, so articles available on GHAE and earlier GHES hidden to hide the learning track
 dependabot_alerts:
-  title: '获取有关不安全依赖项的通知'
-  description: '设置 Dependabot 提醒你的依赖项中有新漏洞{% ifversion GH-advisory-db-supports-malware %}或恶意软件{% endif %}。'
+  title: 'Get notifications for insecure dependencies'
+  description: 'Set up Dependabot to alert you to new vulnerabilities{% ifversion GH-advisory-db-supports-malware %} or malware{% endif %} in your dependencies.'
   guides:
     - /code-security/dependabot/dependabot-alerts/about-dependabot-alerts
-    - '{% ifversion fpt or ghec or ghes > 3.2 %}/github/administering-a-repository/managing-repository-settings/managing-security-and-analysis-settings-for-your-repository{% endif %}'
+    - '{% ifversion fpt or ghec or ghes %}/github/administering-a-repository/managing-repository-settings/managing-security-and-analysis-settings-for-your-repository{% endif %}'
     - /code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts
     - /code-security/dependabot/dependabot-alerts/configuring-notifications-for-dependabot-alerts
     - /code-security/dependabot/working-with-dependabot/managing-pull-requests-for-dependency-updates
@@ -28,20 +32,20 @@ dependabot_alerts:
 
 # Feature available on dotcom and GHES 3.3+, so articles available on GHAE and earlier GHES hidden to hide the learning track
 dependabot_security_updates:
-  title: '获取拉取请求以更新你的漏洞依赖项'
-  description: '设置 Dependabot 以在报告新漏洞时创建拉取请求。'
+  title: 'Get pull requests to update your vulnerable dependencies'
+  description: 'Set up Dependabot to create pull requests when new vulnerabilities are reported.'
   guides:
     - /code-security/dependabot/dependabot-security-updates/about-dependabot-security-updates
     - /code-security/dependabot/dependabot-security-updates/configuring-dependabot-security-updates
-    - '{% ifversion fpt or ghec or ghes > 3.2 %}/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/configuring-notifications-for-vulnerable-dependencies{% endif %}'
-    - '{% ifversion fpt or ghec or ghes > 3.2 %}/github/administering-a-repository/managing-repository-settings/managing-security-and-analysis-settings-for-your-repository{% endif %}'
+    - '{% ifversion fpt or ghec or ghes %}/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/configuring-notifications-for-vulnerable-dependencies{% endif %}'
+    - '{% ifversion fpt or ghec or ghes %}/github/administering-a-repository/managing-repository-settings/managing-security-and-analysis-settings-for-your-repository{% endif %}'
     - /code-security/dependabot/working-with-dependabot/managing-pull-requests-for-dependency-updates
-    - '{% ifversion fpt or ghec or ghes > 3.2 %}/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/troubleshooting-the-detection-of-vulnerable-dependencies{% endif %}'
+    - '{% ifversion fpt or ghec or ghes %}/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/troubleshooting-the-detection-of-vulnerable-dependencies{% endif %}'
 
 # Feature available only on dotcom and GHES 3.3+
 dependency_version_updates:
-  title: '保持更新依赖项'
-  description: '使用 Dependabot 检查新版本并创建拉取请求来更新你的依赖项。'
+  title: 'Keep your dependencies up-to-date'
+  description: 'Use Dependabot to check for new releases and create pull requests to update your dependencies.'
   guides:
     - /code-security/dependabot/dependabot-version-updates/about-dependabot-version-updates
     - /code-security/dependabot/dependabot-version-updates/configuring-dependabot-version-updates
@@ -56,8 +60,8 @@ dependency_version_updates:
 
 # Feature available in GHEC, GHES 3.0 up, and GHAE. Feature limited on FPT so hidden there.
 secret_scanning:
-  title: '扫描机密'
-  description: '设置机密扫描以防意外检入令牌、密码和其他机密到你的存存储库。'
+  title: 'Scan for secrets'
+  description: 'Set up secret scanning to guard against accidental check-ins of tokens, passwords, and other secrets to your repository.'
   guides:
     - '{% ifversion not fpt %}/code-security/secret-scanning/about-secret-scanning{% endif %}'
     - '{% ifversion not fpt %}/code-security/secret-scanning/configuring-secret-scanning-for-your-repositories{% endif %}'
@@ -69,20 +73,20 @@ secret_scanning:
 
 # Security overview feature available in GHEC and GHES 3.2+, so other articles hidden to hide the learning path in other versions
 security_alerts:
-  title: '探索和管理安全警报'
-  description: '了解在哪里可以查找和解决安全警报。'
+  title: 'Explore and manage security alerts'
+  description: 'Learn where to find and resolve security alerts.'
   guides:
-    - '{% ifversion ghec or ghes > 3.1 %}/code-security/security-overview/about-the-security-overview {% endif %}'
-    - '{% ifversion ghec or ghes > 3.1 %}/code-security/security-overview/viewing-the-security-overview {% endif %}'
-    - '{% ifversion ghec or ghes > 3.1 %}/code-security/secret-scanning/managing-alerts-from-secret-scanning {% endif %}'
-    - '{% ifversion ghec or ghes > 3.1 %}/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository{% endif %}'
-    - '{% ifversion ghec or ghes > 3.1 %}/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/triaging-code-scanning-alerts-in-pull-requests{% endif %}'
-    - '{% ifversion ghec or ghes > 3.1 %}/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/viewing-and-updating-vulnerable-dependencies-in-your-repository{% endif %}'
+    - '{% ifversion ghec or ghes %}/code-security/security-overview/about-the-security-overview {% endif %}'
+    - '{% ifversion ghec or ghes %}/code-security/security-overview/viewing-the-security-overview {% endif %}'
+    - '{% ifversion ghec or ghes %}/code-security/secret-scanning/managing-alerts-from-secret-scanning {% endif %}'
+    - '{% ifversion ghec or ghes %}/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository{% endif %}'
+    - '{% ifversion ghec or ghes %}/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/triaging-code-scanning-alerts-in-pull-requests{% endif %}'
+    - '{% ifversion ghec or ghes %}/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/viewing-and-updating-vulnerable-dependencies-in-your-repository{% endif %}'
 
 # Feature available in all versions from GHES 2.22 up
 code_security_actions:
-  title: '使用 GitHub Actions 运行代码扫描'
-  description: '检查默认分支和每个拉取请求，以排除存储库中的漏洞和错误。'
+  title: 'Run code scanning with GitHub Actions'
+  description: 'Check your default branch and every pull request to keep vulnerabilities and errors out of your repository.'
   featured_track: '{% ifversion ghae or ghes %}true{% else %}false{% endif %}'
   guides:
     - /code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning
@@ -94,8 +98,8 @@ code_security_actions:
 
 # Feature available in all versions from GHES 2.22 up
 code_security_integration:
-  title: '与代码扫描集成'
-  description: '使用 SARIF 将分析结果从第三方系统上传到 GitHub。'
+  title: 'Integrate with code scanning'
+  description: 'Upload code analysis results from third-party systems to GitHub using SARIF.'
   guides:
     - /code-security/code-scanning/integrating-with-code-scanning/about-integration-with-code-scanning
     - /code-security/code-scanning/integrating-with-code-scanning/uploading-a-sarif-file-to-github
@@ -104,8 +108,8 @@ code_security_integration:
 
 # Feature available in all versions from GHES 2.22 up
 code_security_ci:
-  title: '在 CI 中运行 CodeQL 代码扫描'
-  description: '在现有的 CI 中设置 CodeQL 并将结果上传到 GitHub 代码扫描。'
+  title: 'Run CodeQL code scanning in your CI'
+  description: 'Set up CodeQL within your existing CI and upload results to GitHub code scanning.'
   guides:
     - /code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/about-codeql-code-scanning-in-your-ci-system
     - /code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/installing-codeql-cli-in-your-ci-system
@@ -115,8 +119,8 @@ code_security_ci:
 
 # Feature available in all versions
 end_to_end_supply_chain:
-  title: '端到端供应链'
-  description: '如何考虑保护用户帐户、代码和生成流程。'
+  title: 'End-to-end supply chain'
+  description: 'How to think about securing your user accounts, your code, and your build process.'
   guides:
     - /code-security/supply-chain-security/end-to-end-supply-chain/end-to-end-supply-chain-overview
     - /code-security/supply-chain-security/end-to-end-supply-chain/securing-accounts
diff --git a/translations/zh-CN/data/reusables/actions/about-runner-groups.md b/translations/zh-CN/data/reusables/actions/about-runner-groups.md
new file mode 100644
index 0000000000..6986c9d7ea
--- /dev/null
+++ b/translations/zh-CN/data/reusables/actions/about-runner-groups.md
@@ -0,0 +1,23 @@
+---
+ms.openlocfilehash: 8492ebc0962837c6f748fe30dbca08f529c353fc
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: zh-CN
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148108118"
+---
+{% ifversion fpt %} {% note %}
+
+注意：所有组织都有单个默认运行器组。 只有企业帐户和企业帐户拥有的组织才能创建和管理其他运行器组。
+
+{% endnote %}
+
+运行器组用于控制对运行器的访问。 组织管理员可以配置访问策略，用以控制组织中的哪些组织可以访问运行器组。
+
+如果使用 {% data variables.product.prodname_ghe_cloud %}，你可以创建额外的运行器组；企业管理员可以配置访问策略，控制企业中哪些组织可以访问运行器组；组织管理员可以为企业运行器组分配额外的细致存储库访问策略。 {% endif -%} {% ifversion ghec or ghes or ghae %}
+
+{% data reusables.actions.runner-group-enterprise-overview %}
+
+新运行器在创建时，将自动分配给默认组。 运行器每次只能在一个组中。 您可以将运行器从默认组移到另一组。 有关详细信息，请参阅“[将运行器移动到组](#moving-a-runner-to-a-group)”。
+
+{% endif %}
diff --git a/translations/zh-CN/data/reusables/actions/actions-audit-events-workflow.md b/translations/zh-CN/data/reusables/actions/actions-audit-events-workflow.md
index 7f82e808ab..3abb7179e7 100644
--- a/translations/zh-CN/data/reusables/actions/actions-audit-events-workflow.md
+++ b/translations/zh-CN/data/reusables/actions/actions-audit-events-workflow.md
@@ -1,12 +1,20 @@
-| Action | Description
+---
+ms.openlocfilehash: 1162ab428d4c20f7f0ca4af8c1ec743b30e42852
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: zh-CN
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148108117"
+---
+| 操作 | 说明
 |------------------|-------------------
-| `cancel_workflow_run` | Triggered when a workflow run has been cancelled. For more information, see "[Canceling a workflow](/actions/managing-workflow-runs/canceling-a-workflow)."{% ifversion fpt or ghec or ghes > 3.2 or ghae %}
-| `completed_workflow_run` | Triggered when a workflow status changes to `completed`. Can only be viewed using the REST API; not visible in the UI or the JSON/CSV export. For more information, see "[Viewing workflow run history](/actions/managing-workflow-runs/viewing-workflow-run-history)."{% endif %}{% ifversion fpt or ghec or ghes > 3.2 or ghae %}
-| `created_workflow_run` | Triggered when a workflow run is created. Can only be viewed using the REST API; not visible in the UI or the JSON/CSV export. For more information, see "[Create an example workflow](/actions/learn-github-actions/introduction-to-github-actions#create-an-example-workflow)."{% endif %}
-| `delete_workflow_run` | Triggered when a workflow run is deleted. For more information, see "[Deleting a workflow run](/actions/managing-workflow-runs/deleting-a-workflow-run)."
-| `disable_workflow` | Triggered when a workflow is disabled.
-| `enable_workflow` | Triggered when a workflow is enabled, after previously being disabled by `disable_workflow`.
-| `rerun_workflow_run` | Triggered when a workflow run is re-run. For more information, see "[Re-running a workflow](/actions/managing-workflow-runs/re-running-a-workflow)."{% ifversion fpt or ghec or ghes > 3.2 or ghae %}
-| `prepared_workflow_job` | Triggered when a workflow job is started. Includes the list of secrets that were provided to the job. Can only be viewed using the REST API. It is not visible in the the {% data variables.product.prodname_dotcom %} web interface or included in the JSON/CSV export. For more information, see "[Events that trigger workflows](/actions/reference/events-that-trigger-workflows)."{% endif %}
-| `approve_workflow_job` | Triggered when a workflow job has been approved. For more information, see "[Reviewing deployments](/actions/managing-workflow-runs/reviewing-deployments)."
-| `reject_workflow_job` | Triggered when a workflow job has been rejected. For more information, see "[Reviewing deployments](/actions/managing-workflow-runs/reviewing-deployments)."
+| `cancel_workflow_run` | 工作流程运行取消时触发。 有关详细信息，请参阅“[取消工作流](/actions/managing-workflow-runs/canceling-a-workflow)”。
+| `completed_workflow_run` | 当工作流状态更改为 `completed` 时触发。 只能使用 REST API 查看；在 UI 或 JSON/CSV 导出中不可见。 有关详细信息，请参阅“[查看工作流运行历史记录](/actions/managing-workflow-runs/viewing-workflow-run-history)”。
+| `created_workflow_run` | 工作流程运行创建时触发。 只能使用 REST API 查看；在 UI 或 JSON/CSV 导出中不可见。 有关详细信息，请参阅“[创建示例工作流](/actions/learn-github-actions/introduction-to-github-actions#create-an-example-workflow)”。
+| `delete_workflow_run` | 工作流程运行被删除时触发。 有关详细信息，请参阅“[删除工作流运行](/actions/managing-workflow-runs/deleting-a-workflow-run)”。
+| `disable_workflow` | 工作流程禁用时触发。
+| `enable_workflow` | 在此前经 `disable_workflow` 禁用后，在工作流启用时触发。
+| `rerun_workflow_run` | 工作流程运行重新运行时触发。 有关详细信息，请参阅“[重新运行工作流](/actions/managing-workflow-runs/re-running-a-workflow)”。
+| `prepared_workflow_job` | 工作流程作业启动时触发。 包括提供给作业的机密列表。 只能使用 REST API 查看。 它在 {% data variables.product.prodname_dotcom %} Web 接口中不可见，也不包含在 JSON/CSV 导出中。 有关详细信息，请参阅“[触发工作流的事件](/actions/reference/events-that-trigger-workflows)”。
+| `approve_workflow_job` | 在工作流作业被批准后触发。 有关详细信息，请参阅“[审查部署](/actions/managing-workflow-runs/reviewing-deployments)”。
+| `reject_workflow_job` | 在工作流作业被拒绝后触发。 有关详细信息，请参阅“[审查部署](/actions/managing-workflow-runs/reviewing-deployments)”。
diff --git a/translations/zh-CN/data/reusables/actions/add-hosted-runner-overview.md b/translations/zh-CN/data/reusables/actions/add-hosted-runner-overview.md
new file mode 100644
index 0000000000..030f1e8c36
--- /dev/null
+++ b/translations/zh-CN/data/reusables/actions/add-hosted-runner-overview.md
@@ -0,0 +1,11 @@
+---
+ms.openlocfilehash: 955bbcc4f03b8a3a810f282c74230f220908f6b8
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: zh-CN
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148108116"
+---
+可以从可用选项列表中选择操作系统和硬件配置。 通过自动缩放部署此运行器的新实例时，它们会使用此处定义的相同操作系统和硬件配置。
+
+还可以定义标识运行器的标签，即工作流如何能够将作业发送到运行器进行处理（使用 `runs-on`）。 新运行器会自动分配给默认组，也可以在运行器创建过程中选择运行器必须加入的组。 此外，可以在注册运行器后修改运行器组成员身份。 有关详细信息，请参阅“[控制对 {% data variables.actions.hosted_runner %} 的访问](/actions/using-github-hosted-runners/controlling-access-to-larger-runners)”。
diff --git a/translations/zh-CN/data/reusables/actions/add-hosted-runner.md b/translations/zh-CN/data/reusables/actions/add-hosted-runner.md
new file mode 100644
index 0000000000..809ed2ad54
--- /dev/null
+++ b/translations/zh-CN/data/reusables/actions/add-hosted-runner.md
@@ -0,0 +1,11 @@
+1. Click **New runner**, then click **{% octicon "mark-github" aria-label="New hosted runner" %} New {% data variables.product.prodname_dotcom %}-hosted runner**.
+1. Complete the required details to configure your new runner:
+
+    - **Name**: Enter a name for your new runner. For easier identification, this should indicate its hardware and operating configuration, such as `ubuntu-20.04-16core`.
+    - **Runner image**: Choose an operating system from the available options. Once you've selected an operating system, you will be able to choose a specific version.
+    - **Runner size**: Choose a hardware configuration from the drop-down list of available options.
+    - **Auto-scaling**: Choose the maximum number of runners that can be active at any time.
+    - **Runner group**: Choose the group that your runner will be a member of. This group will host multiple instances of your runner, as they scale up and down to suit demand.
+    - **Networking**: Only for {% data variables.product.prodname_ghe_cloud %}: Choose whether a static IP address range will be assigned to instances of the {% data variables.actions.hosted_runner %}. You can use up to 10 static IP addresses in total.
+
+1. Click **Create runner**.
diff --git a/translations/zh-CN/data/reusables/actions/automatically-adding-a-runner-to-a-group.md b/translations/zh-CN/data/reusables/actions/automatically-adding-a-runner-to-a-group.md
new file mode 100644
index 0000000000..112575c926
--- /dev/null
+++ b/translations/zh-CN/data/reusables/actions/automatically-adding-a-runner-to-a-group.md
@@ -0,0 +1,19 @@
+---
+ms.openlocfilehash: 4e8c79051e378c800568f0fcf36c783a1bdd8811
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: zh-CN
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148108114"
+---
+可以使用配置脚本自动向组添加新运行器。 例如，此命令会注册一个新运行器，并使用 `--runnergroup` 参数将其添加到名为 `rg-runnergroup` 的组。
+
+```sh
+./config.sh --url $org_or_enterprise_url --token $token --runnergroup rg-runnergroup
+```
+
+如果运行器组不存在，命令将失败：
+
+```
+Could not find any self-hosted runner group named "rg-runnergroup".
+```
diff --git a/translations/zh-CN/data/reusables/actions/enterprise-http-proxy.md b/translations/zh-CN/data/reusables/actions/enterprise-http-proxy.md
index 6b17543e34..1c7693f8ea 100644
--- a/translations/zh-CN/data/reusables/actions/enterprise-http-proxy.md
+++ b/translations/zh-CN/data/reusables/actions/enterprise-http-proxy.md
@@ -3,4 +3,4 @@ If you have an **HTTP Proxy Server** configured on {% data variables.location.pr
   - You must add `localhost` and `127.0.0.1` to the **HTTP Proxy Exclusion** list.
   - If your external storage location is not routable, then you must also add your external storage URL to the exclusion list.
 
-  For more information on changing your proxy settings, see "[Configuring an outbound web proxy server](/admin/configuration/configuring-an-outbound-web-proxy-server)."
\ No newline at end of file
+  For more information on changing your proxy settings, see "[Configuring an outbound web proxy server](/admin/configuration/configuring-an-outbound-web-proxy-server)."
diff --git a/translations/zh-CN/data/reusables/actions/github_sha_description.md b/translations/zh-CN/data/reusables/actions/github_sha_description.md
index edba0bfeea..2a359eb974 100644
--- a/translations/zh-CN/data/reusables/actions/github_sha_description.md
+++ b/translations/zh-CN/data/reusables/actions/github_sha_description.md
@@ -1,9 +1,9 @@
 ---
-ms.openlocfilehash: 6d59b7ddcb233704ff06531143d1f2d7126f874b
-ms.sourcegitcommit: 80842b4e4c500daa051eff0ccd7cde91c2d4bb36
+ms.openlocfilehash: b362ff01387cbd9a70aeeceb51bff2b48f776bb9
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: zh-CN
-ms.lasthandoff: 09/12/2022
-ms.locfileid: "147888184"
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148108754"
 ---
-触发工作流的提交 SHA。 此提交 SHA 的值取决于触发工作流程的事件。 有关详细信息，请参阅“[触发工作流的事件](/actions/using-workflows/events-that-trigger-workflows)”。 例如，`ffac537e6cbbf934b08745a378932722df287a53`。
\ No newline at end of file
+触发工作流的提交 SHA。 此提交 SHA 的值取决于触发工作流程的事件。 有关详细信息，请参阅“[触发工作流的事件](/actions/using-workflows/events-that-trigger-workflows)”。 例如，`ffac537e6cbbf934b08745a378932722df287a53`。
diff --git a/translations/zh-CN/data/reusables/actions/hosted-runner-security-admonition.md b/translations/zh-CN/data/reusables/actions/hosted-runner-security-admonition.md
new file mode 100644
index 0000000000..d0e0c5b384
--- /dev/null
+++ b/translations/zh-CN/data/reusables/actions/hosted-runner-security-admonition.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: 2ce890fe0439b1030ce00041ff72cd98aeca73db
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: zh-CN
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148108755"
+---
+{% warning %}
+
+警告：{% data reusables.actions.hosted-runner-security %}
+
+{% endwarning %}
diff --git a/translations/zh-CN/data/reusables/actions/message-parameters.md b/translations/zh-CN/data/reusables/actions/message-parameters.md
index c6ec0fc2ad..2d37cc50dd 100644
--- a/translations/zh-CN/data/reusables/actions/message-parameters.md
+++ b/translations/zh-CN/data/reusables/actions/message-parameters.md
@@ -1,9 +1,8 @@
----
-ms.openlocfilehash: bbc3a414d8a29780d8df51bd14b9f8a5843a6c4b
-ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
-ms.translationtype: HT
-ms.contentlocale: zh-CN
-ms.lasthandoff: 09/10/2022
-ms.locfileid: "145098432"
----
-| Parameter | Value | | :- | :- |{% ifversion fpt or ghes > 3.2 or ghae or ghec %} | `title` | Custom title |{% endif %} | `file` | Filename | | `col` | Column number, starting at 1 |{% ifversion fpt or ghes > 3.2 or ghae or ghec %} | `endColumn` | End column number |{% endif %} | `line` | Line number, starting at 1 |{% ifversion fpt or ghes > 3.2 or ghae or ghec %} | `endLine` | End line number |{% endif %}
+| Parameter | Value |
+| :- | :- |
+| `title` | Custom title |
+| `file` | Filename |
+| `col` | Column number, starting at 1 |
+| `endColumn` | End column number |
+| `line` | Line number, starting at 1 |
+| `endLine` | End line number |
diff --git a/translations/zh-CN/data/reusables/actions/more-resources-for-ghes.md b/translations/zh-CN/data/reusables/actions/more-resources-for-ghes.md
index 32feb04c51..f3b008579a 100644
--- a/translations/zh-CN/data/reusables/actions/more-resources-for-ghes.md
+++ b/translations/zh-CN/data/reusables/actions/more-resources-for-ghes.md
@@ -1,18 +1,5 @@
----
-ms.openlocfilehash: 0a3393009a2dcd812f5b20e3cdd1b160aee69d5e
-ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d
-ms.translationtype: HT
-ms.contentlocale: zh-CN
-ms.lasthandoff: 09/11/2022
-ms.locfileid: "147168304"
----
-如果计划为实例的用户启用 {% data variables.product.prodname_actions %}，则需要更多资源。
+If you plan to enable {% data variables.product.prodname_actions %} for the users of your instance, more resources are required.
 
-{%- ifversion ghes = 3.2 %}
-
-{% data reusables.actions.hardware-requirements-3.2 %}
-
-{%- endif %}
 
 {%- ifversion ghes = 3.3 %}
 
@@ -32,4 +19,4 @@ ms.locfileid: "147168304"
 
 {%- endif %}
 
-有关这些要求的详细信息，请参阅“[{% data variables.product.prodname_ghe_server %} 的 {% data variables.product.prodname_actions %} 使用入门](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server#review-hardware-considerations)”。
+For more information about these requirements, see "[Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_server %}](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server#review-hardware-considerations)."
diff --git a/translations/zh-CN/data/reusables/actions/removing-a-runner-group.md b/translations/zh-CN/data/reusables/actions/removing-a-runner-group.md
new file mode 100644
index 0000000000..4f17168123
--- /dev/null
+++ b/translations/zh-CN/data/reusables/actions/removing-a-runner-group.md
@@ -0,0 +1,16 @@
+---
+ms.openlocfilehash: d3eda8a12037f1da8ec915c4652fa658f34fcc6b
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: zh-CN
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148108746"
+---
+运行器在其组被移除时将自动返回到默认组。
+
+{% ifversion ghes or ghae or ghec %} {% data reusables.actions.runner-groups-navigate-to-repo-org-enterprise %}
+1. 在组列表中，在要删除的组右侧，单击 {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}。
+2. 若要删除组，请单击“删除组”。
+3. 查看确认提示，然后单击“删除此运行器组”。 此组中的任何运行器都会自动移动到默认组，在该组中它们会继承分配给该组的访问权限。
+
+{% endif %}
diff --git a/translations/zh-CN/data/reusables/actions/runner-group-enterprise-overview.md b/translations/zh-CN/data/reusables/actions/runner-group-enterprise-overview.md
new file mode 100644
index 0000000000..dc58f71fc8
--- /dev/null
+++ b/translations/zh-CN/data/reusables/actions/runner-group-enterprise-overview.md
@@ -0,0 +1,11 @@
+---
+ms.openlocfilehash: 761cee3710852bda8e1f36d47da475e2c6d6b130
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: zh-CN
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148108743"
+---
+运行器组用于控制对组织和企业级运行器的访问。 企业所有者可以配置访问策略，用于控制企业中哪些组织{% ifversion restrict-groups-to-workflows %}和工作流{% endif %}可以访问运行器组。 组织所有者可以配置访问策略，用于控制组织中哪些存储库{% ifversion restrict-groups-to-workflows %}和工作流{% endif %}可以访问运行器组。
+
+当企业所有者授予对运行器组的访问权限时，组织所有者可以看到组织的运行器设置中列出的运行器组。 然后，组织所有者可以为企业运行器组分配更精细的存储库{% ifversion restrict-groups-to-workflows %}和工作流{% endif %}访问策略。
diff --git a/translations/zh-CN/data/reusables/actions/self-hosted-runner-auto-removal.md b/translations/zh-CN/data/reusables/actions/self-hosted-runner-auto-removal.md
index 85f4863a10..f6fa64f23f 100644
--- a/translations/zh-CN/data/reusables/actions/self-hosted-runner-auto-removal.md
+++ b/translations/zh-CN/data/reusables/actions/self-hosted-runner-auto-removal.md
@@ -1,12 +1,6 @@
----
-ms.openlocfilehash: 80d40b1947f72a35fad5cf4cfb69f7ce68d28eab
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
-ms.translationtype: HT
-ms.contentlocale: zh-CN
-ms.lasthandoff: 09/05/2022
-ms.locfileid: "147558373"
----
-{%- ifversion fpt or ghec or ghes > 3.6 %} 自托管运行器与 {% data variables.product.prodname_actions %} 未连接超过 14 天，将被自动从 {% data variables.product.product_name %} 中删除。  
-临时自托管运行器与 {% data variables.product.prodname_actions %} 未连接超过 1 天，将被自动从 {% data variables.product.product_name %} 中删除。  
-{%- elsif ghae or ghes < 3.7 %} 自托管运行器与 {% data variables.product.prodname_actions %} 未连接超过 30 天，将被自动从 {% data variables.product.product_name %} 中删除。  
-{%- endif %}
\ No newline at end of file
+{%- ifversion fpt or ghec or ghes > 3.6 %}
+A self-hosted runner is automatically removed from {% data variables.product.product_name %} if it has not connected to {% data variables.product.prodname_actions %} for more than 14 days.  
+An ephemeral self-hosted runner is automatically removed from {% data variables.product.product_name %} if it has not connected to {% data variables.product.prodname_actions %} for more than 1 day.  
+{%- elsif ghae or ghes < 3.7 %}
+A self-hosted runner is automatically removed from {% data variables.product.product_name %} if it has not connected to {% data variables.product.prodname_actions %} for more than 30 days.  
+{%- endif %}
diff --git a/translations/zh-CN/data/reusables/actions/self-hosted-runner-security-admonition.md b/translations/zh-CN/data/reusables/actions/self-hosted-runner-security-admonition.md
new file mode 100644
index 0000000000..5811f7362a
--- /dev/null
+++ b/translations/zh-CN/data/reusables/actions/self-hosted-runner-security-admonition.md
@@ -0,0 +1,15 @@
+---
+ms.openlocfilehash: 8c2084dcfcee3042fd067f1e82138875724c59ac
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: zh-CN
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148108739"
+---
+{% warning %}
+
+警告：{% data reusables.actions.self-hosted-runner-security %}
+
+有关详细信息，请参阅[关于自承载运行器](/actions/hosting-your-own-runners/about-self-hosted-runners#self-hosted-runner-security-with-public-repositories)。
+
+{% endwarning %}
diff --git a/translations/zh-CN/data/reusables/actions/self-hosted-runner-security.md b/translations/zh-CN/data/reusables/actions/self-hosted-runner-security.md
index 07fc938105..f49e9afeee 100644
--- a/translations/zh-CN/data/reusables/actions/self-hosted-runner-security.md
+++ b/translations/zh-CN/data/reusables/actions/self-hosted-runner-security.md
@@ -1,9 +1,9 @@
 ---
-ms.openlocfilehash: 736651c236f667201be543ea6cb1462ed10bc9c7
-ms.sourcegitcommit: 22d665055b1bee7a5df630385e734e3a149fc720
+ms.openlocfilehash: 518c31dffd71180ff4733f98ba7df3d5fe6028d9
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: zh-CN
-ms.lasthandoff: 07/13/2022
-ms.locfileid: "145065847"
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148108738"
 ---
-建议仅将自托管运行器用于私有仓库。 这是因为，通过创建在工作流程中执行代码的拉取请求，仓库的复刻可能会在您的自托管运行器上运行危险代码。
+建议仅将自托管运行器用于私有仓库。 这是因为，通过创建在工作流中执行代码的拉取请求，公共存储库的分支可能会在自托管运行器计算机上运行危险代码。
diff --git a/translations/zh-CN/data/reusables/actions/sidebar-secret.md b/translations/zh-CN/data/reusables/actions/sidebar-secret.md
index 5fa0f6887b..91d60259f5 100644
--- a/translations/zh-CN/data/reusables/actions/sidebar-secret.md
+++ b/translations/zh-CN/data/reusables/actions/sidebar-secret.md
@@ -2,4 +2,4 @@
 1. In the "Security" section of the sidebar, select **{% octicon "key-asterisk" aria-label="The key-asterisk icon" %} Secrets**, then click **Actions**.
 {%- else %}
 1. In the left sidebar, click **Secrets**.
-{%- endif %}
\ No newline at end of file
+{%- endif %}
diff --git a/translations/zh-CN/data/reusables/actions/usage-workflow-run-time.md b/translations/zh-CN/data/reusables/actions/usage-workflow-run-time.md
index e368272fe8..9d41c4d993 100644
--- a/translations/zh-CN/data/reusables/actions/usage-workflow-run-time.md
+++ b/translations/zh-CN/data/reusables/actions/usage-workflow-run-time.md
@@ -1 +1 @@
-- **Workflow run time** - {% ifversion fpt or ghec or ghes > 3.2 or ghae %}Each workflow run is limited to 35 days. If a workflow run reaches this limit, the workflow run is cancelled. This period includes execution duration, and time spent on waiting and approval.{% else %}Each workflow run is limited to 72 hours. If a workflow run reaches this limit, the workflow run is cancelled.{% endif %}
+- **Workflow run time** - Each workflow run is limited to 35 days. If a workflow run reaches this limit, the workflow run is cancelled. This period includes execution duration, and time spent on waiting and approval.
diff --git a/translations/zh-CN/data/reusables/advanced-security/custom-link-beta.md b/translations/zh-CN/data/reusables/advanced-security/custom-link-beta.md
new file mode 100644
index 0000000000..731d4195f5
--- /dev/null
+++ b/translations/zh-CN/data/reusables/advanced-security/custom-link-beta.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: f9f5661230c99fb281c3625972b7e5d0fce98963
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: zh-CN
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148108027"
+---
+{% note %}
+
+注意：将资源链接添加到被阻止的推送消息的功能目前处于公共 beta 版，可能会发生更改。
+
+{% endnote %}
diff --git a/translations/zh-CN/data/reusables/advanced-security/secret-scanning-create-custom-pattern.md b/translations/zh-CN/data/reusables/advanced-security/secret-scanning-create-custom-pattern.md
index 8b6afe3169..f4fc70a9c2 100644
--- a/translations/zh-CN/data/reusables/advanced-security/secret-scanning-create-custom-pattern.md
+++ b/translations/zh-CN/data/reusables/advanced-security/secret-scanning-create-custom-pattern.md
@@ -1 +1 @@
-1. When you're satisfied with your new custom pattern, click {% ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4 %}**Publish pattern**{% elsif  ghes > 3.2 or ghae %}**Create pattern**{% elsif ghes = 3.2 %}**Create custom pattern**{% endif %}.
+1. When you're satisfied with your new custom pattern, click {% ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4 %}**Publish pattern**{% else %}**Create pattern**.{% endif %}
diff --git a/translations/zh-CN/data/reusables/advanced-security/secret-scanning-new-custom-pattern.md b/translations/zh-CN/data/reusables/advanced-security/secret-scanning-new-custom-pattern.md
index 021ffa2c32..0f675c8f77 100644
--- a/translations/zh-CN/data/reusables/advanced-security/secret-scanning-new-custom-pattern.md
+++ b/translations/zh-CN/data/reusables/advanced-security/secret-scanning-new-custom-pattern.md
@@ -1,9 +1 @@
----
-ms.openlocfilehash: fffcf27ed7d0b6a175d218436989af63172b5d2b
-ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
-ms.translationtype: HT
-ms.contentlocale: zh-CN
-ms.lasthandoff: 09/11/2022
-ms.locfileid: "145098390"
----
-1. 在“{% data variables.product.prodname_secret_scanning_caps %}”下，在“自定义模式”下，单击{% ifversion fpt or ghes > 3.2 or ghae or ghec %}“新建模式”{% elsif ghes = 3.2 %}“新建自定义模式”{% endif %} 。
+1. Under "{% data variables.product.prodname_secret_scanning_caps %}", under "Custom patterns", click **New pattern**.
diff --git a/translations/zh-CN/data/reusables/audit_log/audit-data-retention-tab.md b/translations/zh-CN/data/reusables/audit_log/audit-data-retention-tab.md
index 1c0a2db472..c40ec2f0dc 100644
--- a/translations/zh-CN/data/reusables/audit_log/audit-data-retention-tab.md
+++ b/translations/zh-CN/data/reusables/audit_log/audit-data-retention-tab.md
@@ -1,11 +1,11 @@
 ---
-ms.openlocfilehash: 7b51303370d46101100bc953a25193ea3d14d032
-ms.sourcegitcommit: 770ed406ec075528ec9c9695aa4bfdc8c8b25fd3
+ms.openlocfilehash: ce590bb087145ff4abfb195d7257c614464c2b19
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: zh-CN
-ms.lasthandoff: 09/11/2022
-ms.locfileid: "147884419"
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148108730"
 ---
 1. 在“审核日志”下，单击“审核数据保留期”。
 
-   ![“审核数据保留期”选项卡的屏幕截图](/assets/images/help/enterprises/audit-data-retention-tab.png)
\ No newline at end of file
+   ![“审核数据保留期”选项卡的屏幕截图](/assets/images/help/enterprises/audit-data-retention-tab.png)
diff --git a/translations/zh-CN/data/reusables/audit_log/audit-log-action-categories.md b/translations/zh-CN/data/reusables/audit_log/audit-log-action-categories.md
index a135b85355..f6f3bf77d0 100644
--- a/translations/zh-CN/data/reusables/audit_log/audit-log-action-categories.md
+++ b/translations/zh-CN/data/reusables/audit_log/audit-log-action-categories.md
@@ -33,12 +33,11 @@
 {%- ifversion ghes %}
 | `config_entry` |  Contains activities related to configuration settings. These events are only visible in the site admin audit log.
 {%- endif %}
-{%- ifversion fpt or ghec or ghes > 3.2 or ghae %} |
+|
 | `dependabot_alerts`  | Contains organization-level configuration activities for {% data variables.product.prodname_dependabot_alerts %} in existing repositories. For more information, see "[About {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)."
 | `dependabot_alerts_new_repos`   | Contains organization-level configuration activities for  {% data variables.product.prodname_dependabot_alerts %} in new repositories created in the organization.
 | `dependabot_repository_access` | Contains activities related to which private repositories in an organization {% data variables.product.prodname_dependabot %} is allowed to access.
-{%- endif %}
-{%- ifversion fpt or ghec or ghes > 3.2 %}
+{%- ifversion fpt or ghec or ghes %}
 | `dependabot_security_updates`   | Contains organization-level configuration activities for {% data variables.product.prodname_dependabot_security_updates %} in existing repositories. For more information, see "[Configuring {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/configuring-dependabot-security-updates)."
 | `dependabot_security_updates_new_repos` | Contains organization-level configuration activities for {% data variables.product.prodname_dependabot_security_updates %} for new repositories created in the organization.
 {%- endif %}
diff --git a/translations/zh-CN/data/reusables/audit_log/audit-log-events-workflows.md b/translations/zh-CN/data/reusables/audit_log/audit-log-events-workflows.md
index a41b568841..a5b8769233 100644
--- a/translations/zh-CN/data/reusables/audit_log/audit-log-events-workflows.md
+++ b/translations/zh-CN/data/reusables/audit_log/audit-log-events-workflows.md
@@ -7,8 +7,6 @@
 | `workflows.enable_workflow` | A workflow was enabled, after previously being disabled by `disable_workflow`.
 | `workflows.reject_workflow_job` | A workflow job was rejected. For more information, see "[Reviewing deployments](/actions/managing-workflow-runs/reviewing-deployments)."
 | `workflows.rerun_workflow_run` | A workflow run was re-run. For more information, see "[Re-running a workflow](/actions/managing-workflow-runs/re-running-a-workflow)."
-{%- ifversion fpt or ghec or ghes > 3.2 or ghae %}
 | `workflows.completed_workflow_run` | A workflow status changed to `completed`. Can only be viewed using the REST API; not visible in the UI or the JSON/CSV export. For more information, see "[Viewing workflow run history](/actions/managing-workflow-runs/viewing-workflow-run-history).
 | `workflows.created_workflow_run` | A workflow run was created. Can only be viewed using the REST API; not visible in the UI or the JSON/CSV export. For more information, see "[Create an example workflow](/actions/learn-github-actions/introduction-to-github-actions#create-an-example-workflow)."
 | `workflows.prepared_workflow_job` | A workflow job was started. Includes the list of secrets that were provided to the job. Can only be viewed using the REST API. It is not visible in the the {% data variables.product.prodname_dotcom %} web interface or included in the JSON/CSV export. For more information, see "[Events that trigger workflows](/actions/reference/events-that-trigger-workflows)."
-{%- endif %}
diff --git a/translations/zh-CN/data/reusables/audit_log/git-events-not-in-search-results.md b/translations/zh-CN/data/reusables/audit_log/git-events-not-in-search-results.md
index c3eb69049e..b30888cea7 100644
--- a/translations/zh-CN/data/reusables/audit_log/git-events-not-in-search-results.md
+++ b/translations/zh-CN/data/reusables/audit_log/git-events-not-in-search-results.md
@@ -1,13 +1,13 @@
 ---
-ms.openlocfilehash: a17c50cfb04b759fe451f686129f86bb4b22fcff
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: 6b7d1cd8cae2ecd6688a1a5d41d7bda03d8e8d97
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: zh-CN
-ms.lasthandoff: 09/05/2022
-ms.locfileid: "147424844"
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148108682"
 ---
 {% ifversion git-events-audit-log %} {% note %}
 
 注意：搜索结果中不包括 Git 事件。
 
-{% endnote %} {% endif %}
\ No newline at end of file
+{% endnote %} {% endif %}
diff --git a/translations/zh-CN/data/reusables/audit_log/streaming-check-s3-endpoint.md b/translations/zh-CN/data/reusables/audit_log/streaming-check-s3-endpoint.md
index 33619483d6..36a31e9790 100644
--- a/translations/zh-CN/data/reusables/audit_log/streaming-check-s3-endpoint.md
+++ b/translations/zh-CN/data/reusables/audit_log/streaming-check-s3-endpoint.md
@@ -1,11 +1,11 @@
 ---
-ms.openlocfilehash: e52e6f55f04b57e1b1f8a8d044b4651b69e2caf5
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: 6e4387a1736c320dbef802ea07c22dfc1fa091a6
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: zh-CN
-ms.lasthandoff: 09/05/2022
-ms.locfileid: "147079576"
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148108170"
 ---
 1. 若要验证 {% data variables.product.prodname_dotcom %} 是否可以连接并写入 Amazon S3 终结点，请单击“检查终结点”。
    
-   ![检查端点](/assets/images/help/enterprises/audit-stream-check.png)
\ No newline at end of file
+   ![检查端点](/assets/images/help/enterprises/audit-stream-check.png)
diff --git a/translations/zh-CN/data/reusables/audit_log/streaming-choose-s3.md b/translations/zh-CN/data/reusables/audit_log/streaming-choose-s3.md
index 0520ae9b77..ba11d62efd 100644
--- a/translations/zh-CN/data/reusables/audit_log/streaming-choose-s3.md
+++ b/translations/zh-CN/data/reusables/audit_log/streaming-choose-s3.md
@@ -1,11 +1,11 @@
 ---
-ms.openlocfilehash: 67009b930a04da090718919ea104317809515027
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: c8ea836ffb23f1d69d2a42c5204143442480eafa
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: zh-CN
-ms.lasthandoff: 09/05/2022
-ms.locfileid: "147079575"
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148108163"
 ---
 1. 选择“配置流”下拉列表，然后单击“Amazon S3”。 
    
-   ![从下拉菜单中选择 Amazon S3](/assets/images/help/enterprises/audit-stream-choice-s3.png)
\ No newline at end of file
+   ![从下拉菜单中选择 Amazon S3](/assets/images/help/enterprises/audit-stream-choice-s3.png)
diff --git a/translations/zh-CN/data/reusables/billing/billing-hosted-runners.md b/translations/zh-CN/data/reusables/billing/billing-hosted-runners.md
new file mode 100644
index 0000000000..bf6bd015ee
--- /dev/null
+++ b/translations/zh-CN/data/reusables/billing/billing-hosted-runners.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 44593ccc9877d4cb1a224122f7c1dd9695db27f6
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: zh-CN
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148108162"
+---
+|  Linux   |   4  |   $0.016   | |  Linux   |   8  |   $0.032   | |  Linux   |  16  |   $0.064   | |  Linux   |  32   |   $0.128   | |  Linux   |   64  |   $0.256   | |  Windows   |   8  |   $0.064   | |  Windows   |  16  |   $0.128   | |  Windows   |  32 |   $0.256   | |  Windows   |  64  |   $0.512   |
diff --git a/translations/zh-CN/data/reusables/code-scanning/alerts-found-in-generated-code.md b/translations/zh-CN/data/reusables/code-scanning/alerts-found-in-generated-code.md
index 7c4e861c95..7f8f459e7c 100644
--- a/translations/zh-CN/data/reusables/code-scanning/alerts-found-in-generated-code.md
+++ b/translations/zh-CN/data/reusables/code-scanning/alerts-found-in-generated-code.md
@@ -1,11 +1,3 @@
----
-ms.openlocfilehash: 599e48d3a38c855896fac842f5c8b4833488aeae
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
-ms.translationtype: HT
-ms.contentlocale: zh-CN
-ms.lasthandoff: 09/05/2022
-ms.locfileid: "147063727"
----
-对于 Java、C、C++ 和 C# 等编译语言，{% data variables.product.prodname_codeql %} 分析在工作流程运行过程中构建的所有代码。 要限制要分析的代码量，请通过在 `run` 块中指定自己的生成步骤，仅生成要分析的代码。 可以将指定自己的生成步骤与对 `pull_request` 和 `push` 事件使用 `paths` 或 `paths-ignore` 筛选器相结合，以确保工作流仅在特定代码更改时运行。 有关详细信息，请参阅 [{% data variables.product.prodname_actions %} 的工作流语法](/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestpull_request_targetpathspaths-ignore)。
+For compiled languages like Java,{% ifversion codeql-go-autobuild %} Go,{% endif %} C, C++, and C#, {% data variables.product.prodname_codeql %} analyzes all of the code which was built during the workflow run. To limit the amount of code being analyzed, build ony the code which you wish to analyze by specifying your own build steps in a `run` block. You can combine specifying your own build steps with using the `paths` or `paths-ignore` filters on the `pull_request` and `push` events to ensure that your workflow only runs when specific code is changed. For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestpull_request_targetpathspaths-ignore)."
 
-对于 Go、JavaScript、Python 和 TypeScript 等语言， {% data variables.product.prodname_codeql %} 分析而不编译源代码，您可以指定其他配置选项来限制要分析的代码量。 有关详细信息，请参阅“[指定要扫描的目录](/code-security/secure-coding/configuring-code-scanning#specifying-directories-to-scan)”。
+For languages like{% ifversion codeql-go-autobuild %}{% else %} Go,{% endif %} JavaScript, Python, and TypeScript, that {% data variables.product.prodname_codeql %} analyzes without compiling the source code, you can specify additional configuration options to limit the amount of code to analyze. For more information, see "[Specifying directories to scan](/code-security/secure-coding/configuring-code-scanning#specifying-directories-to-scan)."
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/code-scanning/analyze-go.md b/translations/zh-CN/data/reusables/code-scanning/analyze-go.md
index 432d0add0d..82b4cb08b3 100644
--- a/translations/zh-CN/data/reusables/code-scanning/analyze-go.md
+++ b/translations/zh-CN/data/reusables/code-scanning/analyze-go.md
@@ -1 +1,9 @@
-For these three languages, {% data variables.product.prodname_codeql %} analyzes the source files in your repository that are built. {% data variables.product.prodname_codeql %} also runs a build for Go projects to set up the project, but then analyzes _all_ Go files in the repository, not just the files that are built. For any of these languages, including Go, you can disable `autobuild` and instead use custom build commands in order to analyze only the files that are built by these custom commands.
\ No newline at end of file
+---
+ms.openlocfilehash: e9f2162fa5c65d4a59b2bd350aea2b131205f9a6
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: zh-CN
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145098236"
+---
+{% data variables.product.prodname_codeql %} 也运行 Go 项目的构建来设置项目。 但与其他编译的语言不同，存储库中的所有文件都将被提取，而不只是生成的文件。 可以使用自定义生成命令跳过提取生成时不会接触到的 Go 文件。
diff --git a/translations/zh-CN/data/reusables/code-scanning/autobuild-compiled-languages.md b/translations/zh-CN/data/reusables/code-scanning/autobuild-compiled-languages.md
index 320555380d..58d3db79d2 100644
--- a/translations/zh-CN/data/reusables/code-scanning/autobuild-compiled-languages.md
+++ b/translations/zh-CN/data/reusables/code-scanning/autobuild-compiled-languages.md
@@ -1,9 +1 @@
----
-ms.openlocfilehash: d772b6eae7cf42f2635bb427605b6d0626bdad05
-ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
-ms.translationtype: HT
-ms.contentlocale: zh-CN
-ms.lasthandoff: 09/11/2022
-ms.locfileid: "145098232"
----
-对于受支持的编译语言，你可使用 {% data variables.product.prodname_codeql_workflow %} 中的 `autobuild` 操作来构建代码。 这避免了为 C/C++、C# 和 Java 指定显式生成命令。
+For the supported compiled languages, you can use the `autobuild` action in the {% data variables.product.prodname_codeql_workflow %} to build your code. This avoids you having to specify explicit build commands for C/C++, C#,{% ifversion codeql-go-autobuild %} Go,{% endif %} and Java.
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/code-scanning/example-configuration-files.md b/translations/zh-CN/data/reusables/code-scanning/example-configuration-files.md
index a55b33e606..a7dd2fe282 100644
--- a/translations/zh-CN/data/reusables/code-scanning/example-configuration-files.md
+++ b/translations/zh-CN/data/reusables/code-scanning/example-configuration-files.md
@@ -1,4 +1,12 @@
-This configuration file adds the `security-and-quality` query suite to the list of queries run by {% data variables.product.prodname_codeql %} when scanning your code. For more information about the query suites available for use, see "[Running additional queries](#running-additional-queries)."
+---
+ms.openlocfilehash: 77c9b4b73d2d839bc9c0bdaa73ffc148f0eda6ca
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: zh-CN
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148108159"
+---
+当扫描代码时，此配置文件将 `security-and-quality` 查询套件添加到 {% data variables.product.prodname_codeql %} 运行的查询列表中。 有关可供使用的查询套件的详细信息，请参阅“[运行其他查询](#running-additional-queries)”。
 
 ``` yaml
 name: "My {% data variables.product.prodname_codeql %} config"
@@ -7,7 +15,7 @@ queries:
   - uses: security-and-quality
 ```
 
-The following configuration file disables the default queries and specifies a set of custom queries to run instead. It also configures {% data variables.product.prodname_codeql %} to scan files in the _src_ directory (relative to the root), except for the _src/node_modules_ directory, and except for files whose name ends in _.test.js_. Files in _src/node_modules_ and files with names ending _.test.js_ are therefore excluded from analysis.
+以下配置文件禁用默认查询，并指定一组要运行的自定义查询。 它还配置 {% data variables.product.prodname_codeql %} 以扫描 src 目录（相对于根目录）中的文件，除了 src/node_modules 目录和名称以 .test.js 结尾的文件  。 因此，src/node_modules 中的文件和名称以 .test.js 结尾的文件被排除在分析之外 。
 
 ``` yaml
 name: "My {% data variables.product.prodname_codeql %} config"
@@ -33,7 +41,7 @@ paths-ignore:
 
 {% ifversion code-scanning-exclude-queries-from-analysis %}
 
-The following configuration file only runs queries that generate alerts of severity error. The configuration first selects all the default queries, all queries in `./my-queries`, and the default suite in `codeql/java-queries`, then excludes all the queries that generate warnings or recommendations. 
+以下配置文件仅运行生成严重性错误警报的查询。 该配置首先选择所有默认查询、`./my-queries` 中的所有查询以及 `codeql/java-queries` 中的默认套件，然后排除生成警告或建议的所有查询。 
 
 ``` yaml
 queries:
@@ -48,4 +56,4 @@ query-filters:
       - recommendation
 ```
 
-{% endif %}
\ No newline at end of file
+{% endif %}
diff --git a/translations/zh-CN/data/reusables/code-scanning/non-glibc-linux-support.md b/translations/zh-CN/data/reusables/code-scanning/non-glibc-linux-support.md
new file mode 100644
index 0000000000..8f73cababd
--- /dev/null
+++ b/translations/zh-CN/data/reusables/code-scanning/non-glibc-linux-support.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 2c492c061232518888ac11c439ee5917fe032eeb
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: zh-CN
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148108158"
+---
+{% data variables.product.prodname_codeql_cli %} 当前与非 glibc Linux 发行版不兼容，例如（基于 musl 的）Alpine Linux。
diff --git a/translations/zh-CN/data/reusables/codespaces/about-changing-default-editor.md b/translations/zh-CN/data/reusables/codespaces/about-changing-default-editor.md
new file mode 100644
index 0000000000..413098ced8
--- /dev/null
+++ b/translations/zh-CN/data/reusables/codespaces/about-changing-default-editor.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: ba91a4555a2ae0e8ec359aee8c466e201525647c
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: zh-CN
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148108157"
+---
+您可以在个人设置页面中设置 {% data variables.product.prodname_codespaces %} 的默认编辑器。
diff --git a/translations/zh-CN/data/reusables/codespaces/accessing-prebuild-configuration.md b/translations/zh-CN/data/reusables/codespaces/accessing-prebuild-configuration.md
new file mode 100644
index 0000000000..dea6f221ba
--- /dev/null
+++ b/translations/zh-CN/data/reusables/codespaces/accessing-prebuild-configuration.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: e18c37f7f93e2125d7280bd5b24a6eebea77d935
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: zh-CN
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148106939"
+---
+{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %}
+1. 在边栏的“代码和自动化”部分中，单击“{% octicon "codespaces" aria-label="The Codespaces icon" %} {% data variables.product.prodname_codespaces %}”。
diff --git a/translations/zh-CN/data/reusables/codespaces/click-remote-explorer-icon-vscode.md b/translations/zh-CN/data/reusables/codespaces/click-remote-explorer-icon-vscode.md
index 0173775ec3..7908d425c0 100644
--- a/translations/zh-CN/data/reusables/codespaces/click-remote-explorer-icon-vscode.md
+++ b/translations/zh-CN/data/reusables/codespaces/click-remote-explorer-icon-vscode.md
@@ -1,13 +1,13 @@
 ---
-ms.openlocfilehash: 008615ba94fed6838f09aa137e6da23e89168573
-ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794
+ms.openlocfilehash: a0a609a6e7a1cab14059012a15b6a08be53d8cbd
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: zh-CN
-ms.lasthandoff: 09/09/2022
-ms.locfileid: "147682485"
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148108154"
 ---
 1. 在 {% data variables.product.prodname_vscode_shortname %} 中，从左侧边栏单击“远程 Explorer”图标。
 
    ![{% data variables.product.prodname_vscode %} 中的 Remote Explorer 图标](/assets/images/help/codespaces/click-remote-explorer-icon-vscode.png)
 
-{% indented_data_reference reusables.codespaces.remote-explorer spaces=3 %}
\ No newline at end of file
+{% indented_data_reference reusables.codespaces.remote-explorer spaces=3 %}
diff --git a/translations/zh-CN/data/reusables/codespaces/links-to-get-started.md b/translations/zh-CN/data/reusables/codespaces/links-to-get-started.md
index 37b7fa79a8..b27dca483d 100644
--- a/translations/zh-CN/data/reusables/codespaces/links-to-get-started.md
+++ b/translations/zh-CN/data/reusables/codespaces/links-to-get-started.md
@@ -1 +1 @@
-To get started with {% data variables.product.prodname_github_codespaces %}, see "[Quickstart for {% data variables.product.prodname_github_codespaces %}](/codespaces/getting-started/quickstart)." For more information on creating or reopening a codespace, see "[Creating a codespace](/codespaces/developing-in-codespaces/creating-a-codespace)" and "[Opening an existing codespace](/codespaces/developing-in-codespaces/opening-an-existing-codespace)." To learn more about how {% data variables.product.prodname_github_codespaces %} works, see "[Deep dive into {% data variables.product.prodname_github_codespaces %}](/codespaces/getting-started/deep-dive)."
\ No newline at end of file
+To get started with {% data variables.product.prodname_github_codespaces %}, see "[Quickstart for {% data variables.product.prodname_github_codespaces %}](/codespaces/getting-started/quickstart)." For more information on creating or reopening a codespace, see "[Creating a codespace](/codespaces/developing-in-codespaces/creating-a-codespace)" and "[Opening an existing codespace](/codespaces/developing-in-codespaces/opening-an-existing-codespace)." To learn more about how {% data variables.product.prodname_github_codespaces %} works, see "[Deep dive into {% data variables.product.prodname_github_codespaces %}](/codespaces/getting-started/deep-dive)."
diff --git a/translations/zh-CN/data/reusables/codespaces/max-number-codespaces.md b/translations/zh-CN/data/reusables/codespaces/max-number-codespaces.md
index 314d077d97..3b0bae3234 100644
--- a/translations/zh-CN/data/reusables/codespaces/max-number-codespaces.md
+++ b/translations/zh-CN/data/reusables/codespaces/max-number-codespaces.md
@@ -1,9 +1,9 @@
 ---
-ms.openlocfilehash: f2d4527cb962dc9dc65d1aa1cc150f048814a917
-ms.sourcegitcommit: 505b84dc7227e8a5d518a71eb5c7eaa65b38ce0e
+ms.openlocfilehash: 5a221eb6ab8719ebea834e50059bbc6aead1fa79
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: zh-CN
-ms.lasthandoff: 09/09/2022
-ms.locfileid: "147876055"
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148108152"
 ---
-可以创建的 codespace 数量和可以同时运行的 codespace 数量受到限制。 这些限制因多种因素而异。 如果达到最大 codespace 数并尝试创建另一个 codespace，则会显示一条消息，告知你必须删除现有 codespace，然后才能创建新的 codespace。
\ No newline at end of file
+可以创建的 codespace 数量和可以同时运行的 codespace 数量受到限制。 这些限制因多种因素而异。 如果达到最大 codespace 数并尝试创建另一个 codespace，则会显示一条消息，告知你必须删除现有 codespace，然后才能创建新的 codespace。
diff --git a/translations/zh-CN/data/reusables/codespaces/prebuilds-permission-authorization.md b/translations/zh-CN/data/reusables/codespaces/prebuilds-permission-authorization.md
index 16095fe397..ddfbefe4b1 100644
--- a/translations/zh-CN/data/reusables/codespaces/prebuilds-permission-authorization.md
+++ b/translations/zh-CN/data/reusables/codespaces/prebuilds-permission-authorization.md
@@ -1,10 +1,10 @@
 ---
-ms.openlocfilehash: 21a587f89a71ccd8e9f1a69aa5423a840f26b9a6
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: c32a9f6f6a799c3653cb17fe89721090fc01d155
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: zh-CN
-ms.lasthandoff: 09/05/2022
-ms.locfileid: "147431597"
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148108150"
 ---
    如果存储库的开发容器配置指定了访问其他存储库的权限，你将看到一个授权页面。 有关如何在 `devcontainer.json` 文件中指定此权限的详细信息，请参阅“[管理对 codespace 中其他存储库的访问](/codespaces/managing-your-codespaces/managing-repository-access-for-your-codespaces)”。   
 
@@ -18,4 +18,4 @@ ms.locfileid: "147431597"
 
    **注意**：使用此预生成创建 codespace 的用户也需要授予这些权限。
 
-   {% endnote %}
\ No newline at end of file
+   {% endnote %}
diff --git a/translations/zh-CN/data/reusables/codespaces/stopping-a-codespace.md b/translations/zh-CN/data/reusables/codespaces/stopping-a-codespace.md
new file mode 100644
index 0000000000..5afaa37962
--- /dev/null
+++ b/translations/zh-CN/data/reusables/codespaces/stopping-a-codespace.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: 5431cd0a877d3a87e4dd22fc3503bb9f67058b76
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: zh-CN
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148108149"
+---
+您可以随时停止代码空间。 停止代码空间时，将停止所有正在运行的进程并清除终端历史记录。 下次启动代码空间时，代码空间中的任何已保存更改仍将可用。 如果未明确停止代码空间，它将继续运行，直到它因非活动而超时。 有关详细信息，请参阅“[codespaces 超时](/codespaces/developing-in-codespaces/codespaces-lifecycle#codespaces-timeouts)”。
+
+只有运行的代码空间才会产生 CPU 费用；停止的代码空间仅产生存储成本。
+
+您可能希望停止并重新启动代码空间以对其应用更改。 例如，如果更改用于代码空间的计算机类型，则需要停止并重新启动它才能使更改生效。 您还可以停止代码空间，并在遇到错误或意外情况时选择重新启动或删除它。
diff --git a/translations/zh-CN/data/reusables/codespaces/using-codespaces-in-vscode.md b/translations/zh-CN/data/reusables/codespaces/using-codespaces-in-vscode.md
new file mode 100644
index 0000000000..8e70a77e37
--- /dev/null
+++ b/translations/zh-CN/data/reusables/codespaces/using-codespaces-in-vscode.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 93ed5f6170cc81999a5389dbc94453ac93023db1
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: zh-CN
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148108148"
+---
+要在 {% data variables.product.prodname_vscode_shortname %} 中使用 {% data variables.product.prodname_github_codespaces %}，你需要安装 {% data variables.product.prodname_codespaces %} 扩展。
diff --git a/translations/zh-CN/data/reusables/codespaces/your-codespaces-procedure-step.md b/translations/zh-CN/data/reusables/codespaces/your-codespaces-procedure-step.md
index 7ff974f84e..ff9f666cb8 100644
--- a/translations/zh-CN/data/reusables/codespaces/your-codespaces-procedure-step.md
+++ b/translations/zh-CN/data/reusables/codespaces/your-codespaces-procedure-step.md
@@ -1 +1 @@
-1. Navigate to the "Your codespaces" page at [github.com/codespaces](https://github.com/codespaces).
\ No newline at end of file
+1. Navigate to the "Your codespaces" page at [github.com/codespaces](https://github.com/codespaces).
diff --git a/translations/zh-CN/data/reusables/copilot/dotcom-settings.md b/translations/zh-CN/data/reusables/copilot/dotcom-settings.md
index 29edf89d54..c63d7165e6 100644
--- a/translations/zh-CN/data/reusables/copilot/dotcom-settings.md
+++ b/translations/zh-CN/data/reusables/copilot/dotcom-settings.md
@@ -1,10 +1,10 @@
 ---
-ms.openlocfilehash: e1df21c0657c55fb934b9c1d837a0ee19df7e37b
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: 224ce401421d3af0e9afa5976695c95ed219a7b5
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: zh-CN
-ms.lasthandoff: 09/05/2022
-ms.locfileid: "147419743"
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148108146"
 ---
 ## 在 {% data variables.product.prodname_dotcom_the_website %} 上配置 {% data variables.product.prodname_copilot %} 设置
 
@@ -28,4 +28,4 @@ ms.locfileid: "147419743"
 
 ## 延伸阅读
 
-- [{% data variables.product.prodname_copilot %} 常见问题解答](https://github.com/features/copilot/#faq)
\ No newline at end of file
+- [{% data variables.product.prodname_copilot %} 常见问题解答](https://github.com/features/copilot/#faq)
diff --git a/translations/zh-CN/data/reusables/dependabot/beta-security-and-version-updates-onboarding.md b/translations/zh-CN/data/reusables/dependabot/beta-security-and-version-updates-onboarding.md
deleted file mode 100644
index 81684c5267..0000000000
--- a/translations/zh-CN/data/reusables/dependabot/beta-security-and-version-updates-onboarding.md
+++ /dev/null
@@ -1,17 +0,0 @@
----
-ms.openlocfilehash: 22d4fde4f9dd7adbb4c9620e9d72e6dc52a716d4
-ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
-ms.translationtype: HT
-ms.contentlocale: zh-CN
-ms.lasthandoff: 09/11/2022
-ms.locfileid: "145129911"
----
-{% ifversion ghes > 3.2 %}
-
-{% note %}
-
-注意：Dependabot 安全更新和版本更新目前可用于 {% data variables.product.prodname_ghe_cloud %}，其测试版可用于 {% data variables.product.prodname_ghe_server %} 3.3。 有关如何启用 Dependabot 更新的说明，请[联系帐户管理团队](https://enterprise.github.com/contact)。
-
-{% endnote %}
-
-{% endif %}
diff --git a/translations/zh-CN/data/reusables/dependabot/beta-security-and-version-updates.md b/translations/zh-CN/data/reusables/dependabot/beta-security-and-version-updates.md
index d1a685249b..a6d2d6cd01 100644
--- a/translations/zh-CN/data/reusables/dependabot/beta-security-and-version-updates.md
+++ b/translations/zh-CN/data/reusables/dependabot/beta-security-and-version-updates.md
@@ -1,4 +1,4 @@
-{% ifversion ghes > 3.2 and ghes < 3.5 %}
+{% ifversion ghes < 3.5 %}
 
 {% note %}
 {% ifversion ghes = 3.4 %}
diff --git a/translations/zh-CN/data/reusables/dependabot/enterprise-enable-dependabot.md b/translations/zh-CN/data/reusables/dependabot/enterprise-enable-dependabot.md
index 844b35d9ea..86180c6b2a 100644
--- a/translations/zh-CN/data/reusables/dependabot/enterprise-enable-dependabot.md
+++ b/translations/zh-CN/data/reusables/dependabot/enterprise-enable-dependabot.md
@@ -1,4 +1,4 @@
-{% ifversion ghes > 3.2 %}
+{% ifversion ghes %}
 
 {% note %}
 
diff --git a/translations/zh-CN/data/reusables/dependency-review/action-enterprise.md b/translations/zh-CN/data/reusables/dependency-review/action-enterprise.md
index ecb1efc4b5..b0b6e52fbe 100644
--- a/translations/zh-CN/data/reusables/dependency-review/action-enterprise.md
+++ b/translations/zh-CN/data/reusables/dependency-review/action-enterprise.md
@@ -1,10 +1,10 @@
 ---
-ms.openlocfilehash: 5a31b3124d838bfaad532763c644a8b446dcd0aa
-ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.openlocfilehash: ff7a0c836b3df74110b4613fa032541e0f27d347
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: zh-CN
-ms.lasthandoff: 09/12/2022
-ms.locfileid: "147887831"
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148108142"
 ---
 {% ifversion ghes or ghae %}企业所有者和对存储库具有管理员访问权限的人员可以分别将 {% data variables.product.prodname_dependency_review_action %} 添加到其企业和存储库。
-{% endif %}
\ No newline at end of file
+{% endif %}
diff --git a/translations/zh-CN/data/reusables/dependency-review/beta.md b/translations/zh-CN/data/reusables/dependency-review/beta.md
deleted file mode 100644
index d8e659ee0f..0000000000
--- a/translations/zh-CN/data/reusables/dependency-review/beta.md
+++ /dev/null
@@ -1,15 +0,0 @@
----
-ms.openlocfilehash: b55c1d61ba8da90884c50184240d2aea8e8b0ee9
-ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
-ms.translationtype: HT
-ms.contentlocale: zh-CN
-ms.lasthandoff: 09/11/2022
-ms.locfileid: "145129866"
----
-{% ifversion ghes = 3.2 %} {% note %}
-
-注意：依赖项评审目前以 beta 版本提供，并且可能会发生更改。
-
-{% endnote %}
-
-{% endif %}
diff --git a/translations/zh-CN/data/reusables/education/about-github-community-exchange-intro.md b/translations/zh-CN/data/reusables/education/about-github-community-exchange-intro.md
index fcd0898558..a642d4ace0 100644
--- a/translations/zh-CN/data/reusables/education/about-github-community-exchange-intro.md
+++ b/translations/zh-CN/data/reusables/education/about-github-community-exchange-intro.md
@@ -1,9 +1,9 @@
 ---
-ms.openlocfilehash: 3419a29bb8fad04801ff8e2846c11da684f61910
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: 82c3a5fa91313a6f2e27e58b62c706ea5b0ef4d9
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: zh-CN
-ms.lasthandoff: 09/05/2022
-ms.locfileid: "147410735"
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148108679"
 ---
-{% data variables.product.prodname_community_exchange %} 是 {% data variables.product.prodname_global_campus %} 门户中的一个学生社区。 对于学生来说，这是一个可以公开项目的地方，还可以发现需要协作者和维护者的其他学生存储库。
\ No newline at end of file
+{% data variables.product.prodname_community_exchange %} 是 {% data variables.product.prodname_global_campus %} 门户中的一个学生社区。 对于学生来说，这是一个可以公开项目的地方，还可以发现需要协作者和维护者的其他学生存储库。
diff --git a/translations/zh-CN/data/reusables/education/submit-application.md b/translations/zh-CN/data/reusables/education/submit-application.md
index d881e524c5..5014f7638f 100644
--- a/translations/zh-CN/data/reusables/education/submit-application.md
+++ b/translations/zh-CN/data/reusables/education/submit-application.md
@@ -7,4 +7,4 @@
 
     {% endnote %}
 
- If your application is approved, you'll receive a confirmation email. Applications are usually processed within a few days, but it may take longer during peak times, such as during the start of a new semester.
\ No newline at end of file
+ If your application is approved, you'll receive a confirmation email. Applications are usually processed within a few days, but it may take longer during peak times, such as during the start of a new semester.
diff --git a/translations/zh-CN/data/reusables/enterprise-licensing/about-license-sync.md b/translations/zh-CN/data/reusables/enterprise-licensing/about-license-sync.md
index ade5050e49..805834cd9e 100644
--- a/translations/zh-CN/data/reusables/enterprise-licensing/about-license-sync.md
+++ b/translations/zh-CN/data/reusables/enterprise-licensing/about-license-sync.md
@@ -1,9 +1,9 @@
 ---
-ms.openlocfilehash: 12b28d4c3665573a1cfc0d56e2a61b616ee0a9ec
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: fbb3311774be7ef276adaba8461a100f73c1c6bb
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: zh-CN
-ms.lasthandoff: 09/05/2022
-ms.locfileid: "147572670"
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148108678"
 ---
-要让使用多个 {% data variables.product.prodname_enterprise %} 环境的用户仅使用单个许可证，你必须在环境之间同步许可证使用情况。 然后，{% data variables.product.company_short %} 将根据与用户帐户关联的电子邮件地址删除重复用户。 有关详细信息，请参阅“[排查 {% data variables.product.prodname_enterprise %} 的许可证使用情况问题](/billing/managing-your-license-for-github-enterprise/troubleshooting-license-usage-for-github-enterprise#about-the-calculation-of-consumed-licenses)”。
\ No newline at end of file
+要让使用多个 {% data variables.product.prodname_enterprise %} 环境的用户仅使用单个许可证，你必须在环境之间同步许可证使用情况。 然后，{% data variables.product.company_short %} 将根据与用户帐户关联的电子邮件地址删除重复用户。 有关详细信息，请参阅“[排查 {% data variables.product.prodname_enterprise %} 的许可证使用情况问题](/billing/managing-your-license-for-github-enterprise/troubleshooting-license-usage-for-github-enterprise#about-the-calculation-of-consumed-licenses)”。
diff --git a/translations/zh-CN/data/reusables/enterprise/about-github-for-enterprises.md b/translations/zh-CN/data/reusables/enterprise/about-github-for-enterprises.md
index 362e32698f..792b857aa9 100644
--- a/translations/zh-CN/data/reusables/enterprise/about-github-for-enterprises.md
+++ b/translations/zh-CN/data/reusables/enterprise/about-github-for-enterprises.md
@@ -1,9 +1,9 @@
 ---
-ms.openlocfilehash: de369a16e292dac48d6e6aee2907e28ae1f46af3
-ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.openlocfilehash: a708ef37153f09729c17dd9a06f258cb64579e6b
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: zh-CN
-ms.lasthandoff: 09/10/2022
-ms.locfileid: "147390422"
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148108674"
 ---
-若要详细了解企业如何使用 {% data variables.product.company_short %} 的产品来支持自身的软件开发生命周期，请参阅“[关于 {% data variables.product.prodname_dotcom %} for enterprises](/admin/overview/about-github-for-enterprises)”。
\ No newline at end of file
+若要详细了解企业如何使用 {% data variables.product.company_short %} 的产品来支持自身的软件开发生命周期，请参阅“[关于 {% data variables.product.prodname_dotcom %} for enterprises](/admin/overview/about-github-for-enterprises)”。
diff --git a/translations/zh-CN/data/reusables/enterprise/repository-caching-release-phase.md b/translations/zh-CN/data/reusables/enterprise/repository-caching-release-phase.md
index d39f09edf5..31a2b15709 100644
--- a/translations/zh-CN/data/reusables/enterprise/repository-caching-release-phase.md
+++ b/translations/zh-CN/data/reusables/enterprise/repository-caching-release-phase.md
@@ -1,13 +1,7 @@
----
-ms.openlocfilehash: 4d2db8622a5ddf12d83595e903e3b2ba1774727b
-ms.sourcegitcommit: 5b1461b419dbef60ae9dbdf8e905a4df30fc91b7
-ms.translationtype: HT
-ms.contentlocale: zh-CN
-ms.lasthandoff: 09/10/2022
-ms.locfileid: "147876151"
----
-{% ifversion ghes < 3.6 %} {% note %}
+{% ifversion ghes < 3.6 %}
+{% note %}
 
-**注意：** 存储库缓存目前为 beta 版本，可能会有变动。
+**Note:** Repository caching is currently in beta and subject to change.
 
-{% endnote %} {% endif %}
\ No newline at end of file
+{% endnote %}
+{% endif %}
diff --git a/translations/zh-CN/data/reusables/enterprise/upgrade-ghes-for-actions.md b/translations/zh-CN/data/reusables/enterprise/upgrade-ghes-for-actions.md
deleted file mode 100644
index a52d82b036..0000000000
--- a/translations/zh-CN/data/reusables/enterprise/upgrade-ghes-for-actions.md
+++ /dev/null
@@ -1,10 +0,0 @@
----
-ms.openlocfilehash: ce032c1829e6b93f7adcd62e1b731953669ffb91
-ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
-ms.translationtype: HT
-ms.contentlocale: zh-CN
-ms.lasthandoff: 09/10/2022
-ms.locfileid: "145097865"
----
-{% ifversion ghes < 3.3 %} {% data variables.product.prodname_actions %} 在 {% data variables.product.prodname_ghe_server %} 3.0 或更高版本中可用。 如果使用的是早期版本的 {% data variables.product.prodname_ghe_server %}，则必须升级才能使用 {% data variables.product.prodname_actions %}。 有关升级 {% data variables.product.prodname_ghe_server %} 实例的详细信息，请参阅“[关于升级到新版本](/admin/overview/about-upgrades-to-new-releases)”。
-{% endif %}
diff --git a/translations/zh-CN/data/reusables/enterprise_backup_utilities/enterprise-backup-utils-directory.md b/translations/zh-CN/data/reusables/enterprise_backup_utilities/enterprise-backup-utils-directory.md
index 0301f77140..6883d53248 100644
--- a/translations/zh-CN/data/reusables/enterprise_backup_utilities/enterprise-backup-utils-directory.md
+++ b/translations/zh-CN/data/reusables/enterprise_backup_utilities/enterprise-backup-utils-directory.md
@@ -1,9 +1,9 @@
 ---
-ms.openlocfilehash: 5c1cf00625a805fc4054a78bc4ac675a161a1c1b
-ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794
+ms.openlocfilehash: 5302e6f9d952c4a8881d1f28fe7ea847a70d0efe
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: zh-CN
-ms.lasthandoff: 09/09/2022
-ms.locfileid: "147861685"
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148108671"
 ---
-1. 在备份主机上，导航到 {% data variables.product.prodname_enterprise_backup_utilities %} 目录，通常为 `backup-utils`。
\ No newline at end of file
+1. 在备份主机上，导航到 {% data variables.product.prodname_enterprise_backup_utilities %} 目录，通常为 `backup-utils`。
diff --git a/translations/zh-CN/data/reusables/enterprise_backup_utilities/enterprise-backup-utils-verify-upgrade.md b/translations/zh-CN/data/reusables/enterprise_backup_utilities/enterprise-backup-utils-verify-upgrade.md
index 2df6bfe4bb..77d3b0e47b 100644
--- a/translations/zh-CN/data/reusables/enterprise_backup_utilities/enterprise-backup-utils-verify-upgrade.md
+++ b/translations/zh-CN/data/reusables/enterprise_backup_utilities/enterprise-backup-utils-verify-upgrade.md
@@ -1,10 +1,10 @@
 ---
-ms.openlocfilehash: 8289b9aadf88b85cf8d4dc71d2fc74db42c01289
-ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794
+ms.openlocfilehash: 76be6868da14b227e1b0fbc16b8c9f913b4f04e0
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: zh-CN
-ms.lasthandoff: 09/09/2022
-ms.locfileid: "147861679"
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148108670"
 ---
 1. 若要验证是否已成功升级，请运行以下命令。
   ```shell
@@ -15,4 +15,4 @@ ms.locfileid: "147861679"
   ```shell
   ./bin/ghe-host-check
   ```
-  
\ No newline at end of file
+  
diff --git a/translations/zh-CN/data/reusables/enterprise_enterprise_support/installing-releases.md b/translations/zh-CN/data/reusables/enterprise_enterprise_support/installing-releases.md
index 444818f8fe..f9044ae820 100644
--- a/translations/zh-CN/data/reusables/enterprise_enterprise_support/installing-releases.md
+++ b/translations/zh-CN/data/reusables/enterprise_enterprise_support/installing-releases.md
@@ -4,4 +4,4 @@
 
 To ensure that {% data variables.location.product_location %} is stable, you must install and implement {% data variables.product.prodname_ghe_server %} releases. Installing {% data variables.product.prodname_ghe_server %} releases ensures that you have the latest features, modifications, and enhancements as well as any updates to features, code corrections, patches or other general updates and fixes to {% data variables.product.prodname_ghe_server %}.
 
-{% endif %}
\ No newline at end of file
+{% endif %}
diff --git a/translations/zh-CN/data/reusables/enterprise_management_console/unlocking-management-console-with-shell.md b/translations/zh-CN/data/reusables/enterprise_management_console/unlocking-management-console-with-shell.md
new file mode 100644
index 0000000000..f765e86f57
--- /dev/null
+++ b/translations/zh-CN/data/reusables/enterprise_management_console/unlocking-management-console-with-shell.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 88d76852d3e379e556b364b31199800e73ecd0c7
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: zh-CN
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148108192"
+---
+要立即解锁 {% data variables.enterprise.management_console %}，请通过管理 shell 使用 `ghe-reactivate-admin-login` 命令。 有关详细信息，请参阅“[命令行实用工具](/enterprise/admin/guides/installation/command-line-utilities#ghe-reactivate-admin-login)”和“[访问管理 shell (SSH)](/enterprise/admin/guides/installation/accessing-the-administrative-shell-ssh/)”。
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/gated-features/code-scanning.md b/translations/zh-CN/data/reusables/gated-features/code-scanning.md
index 87bb7275dd..10475ce322 100644
--- a/translations/zh-CN/data/reusables/gated-features/code-scanning.md
+++ b/translations/zh-CN/data/reusables/gated-features/code-scanning.md
@@ -1,13 +1,17 @@
-{%- ifversion fpt %}
-{% data variables.product.prodname_code_scanning_capc %} is available for all public repositories on {% data variables.product.prodname_dotcom_the_website %}. {% data variables.product.prodname_code_scanning_capc %} is also available for private repositories owned by organizations that use {% data variables.product.prodname_ghe_cloud %} and have a license for {% data variables.product.prodname_GH_advanced_security %}.
+---
+ms.openlocfilehash: 0ea67362c541ed183fec256765d5bb9d1fd18e3c
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: zh-CN
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148108190"
+---
+{%- ifversion fpt %} {% data variables.product.prodname_code_scanning_capc %} 可用于 {% data variables.product.prodname_dotcom_the_website %} 上的所有公共存储库。 {% data variables.product.prodname_code_scanning_capc %} 也可用于使用 {% data variables.product.prodname_ghe_cloud %} 并拥有 {% data variables.product.prodname_GH_advanced_security %} 许可证的组织所拥有的专用存储库。
 
-{%- elsif ghec %}
-{% data variables.product.prodname_code_scanning_capc %} is available for all public repositories on {% data variables.product.prodname_dotcom_the_website %}. To use {% data variables.product.prodname_code_scanning %} in a private repository owned by an organization, you must have a license for {% data variables.product.prodname_GH_advanced_security %}.
+{%- elsif ghec %} {% data variables.product.prodname_code_scanning_capc %} 可用于 {% data variables.product.prodname_dotcom_the_website %} 上的所有公共存储库。 若要在组织拥有的专用存储库中使用 {% data variables.product.prodname_code_scanning %}，必须具有 {% data variables.product.prodname_GH_advanced_security %} 许可证。
 
-{%- elsif ghes %}
-{% data variables.product.prodname_code_scanning_capc %} is available for organization-owned repositories in {% data variables.product.product_name %}. This feature requires a license for {% data variables.product.prodname_GH_advanced_security %}.
+{%- elsif ghes %} {% data variables.product.prodname_code_scanning_capc %} 可用于 {% data variables.product.product_name %} 中的组织拥有的存储库。 此功能需要 {% data variables.product.prodname_GH_advanced_security %} 的许可证。
 
-{%- elsif ghae %}
-{% data variables.product.prodname_code_scanning_capc %} is available for organization-owned repositories in {% data variables.product.product_name %}. This is a {% data variables.product.prodname_GH_advanced_security %} feature (free during the beta release).
+{%- elsif ghae %} {% data variables.product.prodname_code_scanning_capc %} 可用于 {% data variables.product.product_name %} 中的组织拥有的存储库。 这是一项 {% data variables.product.prodname_GH_advanced_security %} 功能（在 beta 版本发行期间免费）。
 
-{%- endif %} {% data reusables.advanced-security.more-info-ghas %}
\ No newline at end of file
+{%- endif %} {% data reusables.advanced-security.more-info-ghas %}
diff --git a/translations/zh-CN/data/reusables/gated-features/historical-insights-for-projects.md b/translations/zh-CN/data/reusables/gated-features/historical-insights-for-projects.md
index 6e9663f357..24ac987865 100644
--- a/translations/zh-CN/data/reusables/gated-features/historical-insights-for-projects.md
+++ b/translations/zh-CN/data/reusables/gated-features/historical-insights-for-projects.md
@@ -1,9 +1,9 @@
 ---
-ms.openlocfilehash: fd865e1bcf0fb2af69739d4d81fa27796e2e0b33
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: f28c558acbb1dacd503964146c0522145d44948b
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: zh-CN
-ms.lasthandoff: 09/05/2022
-ms.locfileid: "147423973"
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148108188"
 ---
-历史图表可用于组织的 {% data variables.product.prodname_team %} 或 {% data variables.product.prodname_ghe_cloud %}。 可在组织的 {% data variables.product.prodname_team %} 和 {% data variables.product.prodname_ghe_cloud %} 以及用户的 {% data variables.product.prodname_pro %} 的专用项目中保存无限图表。 使用公共项目的用户和组织也可以保存无限的图表。 使用 {% data variables.product.prodname_free_team %} 或旧版计划的用户和组织可以在专用项目中保存两个图表。  {% data reusables.gated-features.more-info %}
\ No newline at end of file
+历史图表可用于组织的 {% data variables.product.prodname_team %} 或 {% data variables.product.prodname_ghe_cloud %}。 可在组织的 {% data variables.product.prodname_team %} 和 {% data variables.product.prodname_ghe_cloud %} 以及用户的 {% data variables.product.prodname_pro %} 的专用项目中保存无限图表。 使用公共项目的用户和组织也可以保存无限的图表。 使用 {% data variables.product.prodname_free_team %} 或旧版计划的用户和组织可以在专用项目中保存两个图表。  {% data reusables.gated-features.more-info %}
diff --git a/translations/zh-CN/data/reusables/gated-features/hosted-runners.md b/translations/zh-CN/data/reusables/gated-features/hosted-runners.md
new file mode 100644
index 0000000000..338a9f8744
--- /dev/null
+++ b/translations/zh-CN/data/reusables/gated-features/hosted-runners.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 54a0c4cae87acc79c4d4763521f11da1a37cd2d6
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: zh-CN
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148108187"
+---
+{% data variables.actions.hosted_runner %} 功能目前对使用 {% data variables.product.prodname_team %} 或 {% data variables.product.prodname_ghe_cloud %} 计划的组织和企业为 beta 版本，可能会更改。 若要请求访问 beta 版本，请访问[注册页](https://github.com/features/github-hosted-runners/signup)。
diff --git a/translations/zh-CN/data/reusables/getting-started/bearer-vs-token.md b/translations/zh-CN/data/reusables/getting-started/bearer-vs-token.md
index 5f2f77e810..f53bc5de8a 100644
--- a/translations/zh-CN/data/reusables/getting-started/bearer-vs-token.md
+++ b/translations/zh-CN/data/reusables/getting-started/bearer-vs-token.md
@@ -1,9 +1,9 @@
 ---
-ms.openlocfilehash: a6189685e97d4aeabb737421203acb96ccd0f61c
-ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794
+ms.openlocfilehash: 43a23bdc9abc48a087e62f93a6d01a1aaabe0eb0
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: zh-CN
-ms.lasthandoff: 09/09/2022
-ms.locfileid: "147718212"
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148108186"
 ---
-在大多数情况下，可以使用 `Authorization: Bearer` 或 `Authorization: token` 传递令牌。 但是，如果要传递 JSON Web 令牌 (JWT)，则必须使用 `Authorization: Bearer`。
\ No newline at end of file
+在大多数情况下，可以使用 `Authorization: Bearer` 或 `Authorization: token` 传递令牌。 但是，如果要传递 JSON Web 令牌 (JWT)，则必须使用 `Authorization: Bearer`。
diff --git a/translations/zh-CN/data/reusables/getting-started/math-and-diagrams.md b/translations/zh-CN/data/reusables/getting-started/math-and-diagrams.md
index 3a2bb1a64c..55bb237ae8 100644
--- a/translations/zh-CN/data/reusables/getting-started/math-and-diagrams.md
+++ b/translations/zh-CN/data/reusables/getting-started/math-and-diagrams.md
@@ -1,9 +1,9 @@
 ---
-ms.openlocfilehash: d68b3fb76a086f8ba99cd3c968b547f9d94eb8c9
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: ff4fa65700cd685f99a3e94541df48a2f5e77985
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: zh-CN
-ms.lasthandoff: 09/05/2022
-ms.locfileid: "147529758"
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148108185"
 ---
-{% ifversion mermaid %}可使用 Markdown 将呈现的数学表达式、关系图、地图和 3D 模型添加到 Wiki。 有关创建呈现的数学表达式的详细信息，请参阅“[编写数学表达式](/get-started/writing-on-github/working-with-advanced-formatting/writing-mathematical-expressions)”。 有关创建关系图、地图和 3D 模型的详细信息，请参阅“[创建关系图](/get-started/writing-on-github/working-with-advanced-formatting/creating-diagrams)”。{% endif %}
\ No newline at end of file
+{% ifversion mermaid %}可使用 Markdown 将呈现的数学表达式、关系图、地图和 3D 模型添加到 Wiki。 有关创建呈现的数学表达式的详细信息，请参阅“[编写数学表达式](/get-started/writing-on-github/working-with-advanced-formatting/writing-mathematical-expressions)”。 有关创建关系图、地图和 3D 模型的详细信息，请参阅“[创建关系图](/get-started/writing-on-github/working-with-advanced-formatting/creating-diagrams)”。{% endif %}
diff --git a/translations/zh-CN/data/reusables/git/no-credential-manager.md b/translations/zh-CN/data/reusables/git/no-credential-manager.md
new file mode 100644
index 0000000000..337fd8a44c
--- /dev/null
+++ b/translations/zh-CN/data/reusables/git/no-credential-manager.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: af8f3c7c0c5378080257097644571e8a0d04a840
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: zh-CN
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148108184"
+---
+- 如果输出不包含凭据管理器的名称，则未配置凭据管理器，可以继续执行下一步。
diff --git a/translations/zh-CN/data/reusables/github-ae/saml-idp-table.md b/translations/zh-CN/data/reusables/github-ae/saml-idp-table.md
index c2ef59482a..bf5abef584 100644
--- a/translations/zh-CN/data/reusables/github-ae/saml-idp-table.md
+++ b/translations/zh-CN/data/reusables/github-ae/saml-idp-table.md
@@ -1,8 +1,16 @@
+---
+ms.openlocfilehash: 8afd93954b55495a93b01ca1ed2c0a58946ffbd5
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: zh-CN
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148108183"
+---
 {% ifversion ghae %}
 
-IdP | SAML | User provisioning | Team mapping| 
+IdP | SAML | 用户预配 | 团队映射| 
 --- | --- | ---------------- | --------- |
 [Azure Active Directory (Azure AD)](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad) | {% octicon "check-circle-fill" aria-label="The check icon" %} | {% octicon "check-circle-fill" aria-label="The check icon" %}| {% octicon "check-circle-fill" aria-label="The check icon" %} |
-[Okta](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/configuring-authentication-and-provisioning-for-your-enterprise-using-okta) | {% octicon "check-circle-fill" aria-label="The check icon" %}[<sup>Beta</sup>](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/configuring-authentication-and-provisioning-for-your-enterprise-using-okta)| {% octicon "check-circle-fill" aria-label="The check icon" %}[<sup>Beta</sup>](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/configuring-authentication-and-provisioning-for-your-enterprise-using-okta)| {% octicon "check-circle-fill" aria-label= "The check icon" %}[<sup>Beta</sup>](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/mapping-okta-groups-to-teams) |
+[Okta](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/configuring-authentication-and-provisioning-for-your-enterprise-using-okta) | {% octicon "check-circle-fill" aria-label="The check icon" %}[<sup>试用版</sup>](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/configuring-authentication-and-provisioning-for-your-enterprise-using-okta)| {% octicon "check-circle-fill" aria-label="The check icon" %}[<sup>试用版</sup>](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/configuring-authentication-and-provisioning-for-your-enterprise-using-okta)| {% octicon "check-circle-fill" aria-label= "The check icon" %}[<sup>试用版</sup>](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/mapping-okta-groups-to-teams) |
 
 {% endif %}
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/gpg/configure-ssh-signing.md b/translations/zh-CN/data/reusables/gpg/configure-ssh-signing.md
new file mode 100644
index 0000000000..d57748c837
--- /dev/null
+++ b/translations/zh-CN/data/reusables/gpg/configure-ssh-signing.md
@@ -0,0 +1,12 @@
+---
+ms.openlocfilehash: 0a0e572422bee311ca8adb2b40c81a00907c0dfb
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: zh-CN
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148108667"
+---
+1. 配置 Git 使用 SSH 对提交和标记签名：
+  ```bash
+  $ git config --global gpg.format ssh
+  ```
diff --git a/translations/zh-CN/data/reusables/identity-and-permissions/about-adding-ip-allow-list-entries.md b/translations/zh-CN/data/reusables/identity-and-permissions/about-adding-ip-allow-list-entries.md
new file mode 100644
index 0000000000..eb228c7495
--- /dev/null
+++ b/translations/zh-CN/data/reusables/identity-and-permissions/about-adding-ip-allow-list-entries.md
@@ -0,0 +1,11 @@
+---
+ms.openlocfilehash: db4c80c49c4e3effe99073f29010147f3a1efc08
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: zh-CN
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148108066"
+---
+可以通过添加各自包含 IP 地址或地址范围的条目来创建 IP 允许列表。{% ifversion ip-allow-list-address-check %}添加条目完成后，可以检查列表中是否有任何已启用条目允许使用特定 IP 地址。{% endif %}
+
+在列表限制对{% ifversion ghae %}你的企业{% else %}企业中由组织拥有的专用资产{% endif %}的访问之前，还必须启用允许的 IP 地址。
diff --git a/translations/zh-CN/data/reusables/identity-and-permissions/about-checking-ip-address.md b/translations/zh-CN/data/reusables/identity-and-permissions/about-checking-ip-address.md
new file mode 100644
index 0000000000..8ec0d30b28
--- /dev/null
+++ b/translations/zh-CN/data/reusables/identity-and-permissions/about-checking-ip-address.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: d7e7459f3ed9898a892c8b3504a32c1106e69442
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: zh-CN
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148108065"
+---
+可以检查 IP 允许列表中是否有任何已启用条目允许使用特定 IP 地址（即使列表当前未启用）。
diff --git a/translations/zh-CN/data/reusables/identity-and-permissions/about-editing-ip-allow-list-entries.md b/translations/zh-CN/data/reusables/identity-and-permissions/about-editing-ip-allow-list-entries.md
new file mode 100644
index 0000000000..84b7a21abc
--- /dev/null
+++ b/translations/zh-CN/data/reusables/identity-and-permissions/about-editing-ip-allow-list-entries.md
@@ -0,0 +1,12 @@
+---
+ms.openlocfilehash: 8f78a77c83ea498d8d41a0deff20903062542479
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: zh-CN
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148108064"
+---
+可以在 IP 允许列表中编辑条目。 如果编辑已启用的条目，则更改会立即实施。 
+
+{% ifversion ip-allow-list-address-check %}编辑条目完成之后，可以检查列表中是否有任何已启用条目允许使用特定 IP 地址。
+{% endif %}
diff --git a/translations/zh-CN/data/reusables/identity-and-permissions/about-enabling-allowed-ip-addresses.md b/translations/zh-CN/data/reusables/identity-and-permissions/about-enabling-allowed-ip-addresses.md
new file mode 100644
index 0000000000..63f2a8d857
--- /dev/null
+++ b/translations/zh-CN/data/reusables/identity-and-permissions/about-enabling-allowed-ip-addresses.md
@@ -0,0 +1,12 @@
+---
+ms.openlocfilehash: 095556009ed66ca0b687734f62f21c70fd87699a
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: zh-CN
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148108063"
+---
+创建 IP 允许列表后，可以启用允许的 IP 地址。 启用允许的 IP 地址时，{% data variables.product.company_short %} 会立即强制实施 IP 允许列表中的任何已启用条目。
+
+{% ifversion ip-allow-list-address-check %}启用允许的 IP 地址之前，可以检查列表中是否有任何已启用条目允许使用特定 IP 地址。 有关详细信息，请参阅“[检查是否允许使用 IP 地址](#checking-if-an-ip-address-is-permitted)”。
+{% endif %}
diff --git a/translations/zh-CN/data/reusables/identity-and-permissions/check-ip-address-step.md b/translations/zh-CN/data/reusables/identity-and-permissions/check-ip-address-step.md
new file mode 100644
index 0000000000..ae02e780cd
--- /dev/null
+++ b/translations/zh-CN/data/reusables/identity-and-permissions/check-ip-address-step.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 5eaf0aa831a27f61216ae9574df61fe7445f2f94
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: zh-CN
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148108666"
+---
+1. 在“检查 IP 地址”下，输入 IP 地址。
+   ![“检查 IP 地址”文本字段的屏幕截图](/assets/images/help/security/check-ip-address.png)
diff --git a/translations/zh-CN/data/reusables/identity-and-permissions/check-ip-address.md b/translations/zh-CN/data/reusables/identity-and-permissions/check-ip-address.md
new file mode 100644
index 0000000000..3b9cc1e550
--- /dev/null
+++ b/translations/zh-CN/data/reusables/identity-and-permissions/check-ip-address.md
@@ -0,0 +1,11 @@
+---
+ms.openlocfilehash: 7b848e4c3bb4a9a4578e3f1ff92f6249dd20c699
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: zh-CN
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148108663"
+---
+{%- ifversion ip-allow-list-address-check %}
+1. （可选）检查列表中是否有任何已启用条目允许使用特定 IP 地址。 有关详细信息，请参阅“[检查是否允许使用 IP 地址](#checking-if-an-ip-address-is-permitted)”。
+{%- endif %}
diff --git a/translations/zh-CN/data/reusables/identity-and-permissions/ipv6-allow-lists.md b/translations/zh-CN/data/reusables/identity-and-permissions/ipv6-allow-lists.md
new file mode 100644
index 0000000000..a0af03f69d
--- /dev/null
+++ b/translations/zh-CN/data/reusables/identity-and-permissions/ipv6-allow-lists.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: 1df7a9480c4cfd3a5edfc1ee16cd2a3259921e6b
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: zh-CN
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148108622"
+---
+{% ifversion fpt or ghec %} {% note %}
+
+注意：{% data variables.product.company_short %} 正在逐步推出对 IPv6 的支持。 随着 {% data variables.product.prodname_dotcom %} 服务继续添加 IPv6 支持，我们将开始识别 {% data variables.product.prodname_dotcom %} 用户的 IPv6 地址。 若要防止可能的访问中断，请确保将任何所需的 IPv6 地址添加到 IP 允许列表。
+
+{% endnote %} {% endif %}
diff --git a/translations/zh-CN/data/reusables/identity-and-permissions/vigilant-mode-beta-note.md b/translations/zh-CN/data/reusables/identity-and-permissions/vigilant-mode-beta-note.md
index 1913d6e459..8c5bcb44ec 100644
--- a/translations/zh-CN/data/reusables/identity-and-permissions/vigilant-mode-beta-note.md
+++ b/translations/zh-CN/data/reusables/identity-and-permissions/vigilant-mode-beta-note.md
@@ -4,4 +4,4 @@
 **Note:** Vigilant mode is currently in beta and subject to change.
 
 {% endnote %}
-{% endif %}
\ No newline at end of file
+{% endif %}
diff --git a/translations/zh-CN/data/reusables/notifications-v2/custom-notification-types.md b/translations/zh-CN/data/reusables/notifications-v2/custom-notification-types.md
index cd318e85fc..b6445e487a 100644
--- a/translations/zh-CN/data/reusables/notifications-v2/custom-notification-types.md
+++ b/translations/zh-CN/data/reusables/notifications-v2/custom-notification-types.md
@@ -1 +1 @@
-issues, pull requests, releases, security alerts, or discussions
\ No newline at end of file
+issues, pull requests, releases, security alerts, or discussions
diff --git a/translations/zh-CN/data/reusables/organizations/about-following-organizations.md b/translations/zh-CN/data/reusables/organizations/about-following-organizations.md
new file mode 100644
index 0000000000..d46091e849
--- /dev/null
+++ b/translations/zh-CN/data/reusables/organizations/about-following-organizations.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: f9490c302fe4534be6937805e0eec85fe9c5db1a
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: zh-CN
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148108650"
+---
+当你在 {% data variables.product.product_name %} 上关注组织时，你会在个人仪表板上看到其{% ifversion fpt or ghec %}公开{% endif %}活动。 此活动包括新讨论、赞助和存储库。
diff --git a/translations/zh-CN/data/reusables/organizations/follow-organizations-beta.md b/translations/zh-CN/data/reusables/organizations/follow-organizations-beta.md
index 5e40ef5972..eb17735b3c 100644
--- a/translations/zh-CN/data/reusables/organizations/follow-organizations-beta.md
+++ b/translations/zh-CN/data/reusables/organizations/follow-organizations-beta.md
@@ -1,13 +1,13 @@
 ---
-ms.openlocfilehash: f64274ea187e812242eb07e1dd9a7204b6522e50
-ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794
+ms.openlocfilehash: 4e2e744a966a1e1b8111f6f5194542f7512670fc
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: zh-CN
-ms.lasthandoff: 09/09/2022
-ms.locfileid: "147692128"
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148108662"
 ---
 {% note %}
 
 注意：关注组织的功能目前为公共 beta 版，可能会有变动。
 
-{% endnote %}
\ No newline at end of file
+{% endnote %}
diff --git a/translations/zh-CN/data/reusables/organizations/new_team.md b/translations/zh-CN/data/reusables/organizations/new_team.md
index 58818b59d4..ad329ffe34 100644
--- a/translations/zh-CN/data/reusables/organizations/new_team.md
+++ b/translations/zh-CN/data/reusables/organizations/new_team.md
@@ -1,12 +1,8 @@
----
-ms.openlocfilehash: 383ba2a3fe279dfa18f20c931a58a5b4785e8727
-ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d
-ms.translationtype: HT
-ms.contentlocale: zh-CN
-ms.lasthandoff: 09/11/2022
-ms.locfileid: "147883754"
----
-1. 在组织名称下，单击 {% octicon "people" aria-label="The people icon" %}“团队”。
-  {% ifversion fpt or ghes > 3.2 or ghec %}![“团队”选项卡](/assets/images/help/organizations/organization-teams-tab-with-overview.png) {% else %}![“团队”选项卡](/assets/images/help/organizations/organization-teams-tab.png) {% endif %}
-1. 在“团队”选项卡的右侧，单击“新团队”。
-  ![新团队按钮](/assets/images/help/teams/new-team-button.png)
+1. Under your organization name, click {% octicon "people" aria-label="The people icon" %} **Teams**.
+  {% ifversion fpt or ghes or ghec %}
+  ![Teams tab](/assets/images/help/organizations/organization-teams-tab-with-overview.png)
+  {% else %}
+  ![Teams tab](/assets/images/help/organizations/organization-teams-tab.png)
+  {% endif %}
+1. On the right side of the Teams tab, click **New team**.
+  ![New team button](/assets/images/help/teams/new-team-button.png)
diff --git a/translations/zh-CN/data/reusables/organizations/org_settings.md b/translations/zh-CN/data/reusables/organizations/org_settings.md
index 083d4402f6..4e84c3e807 100644
--- a/translations/zh-CN/data/reusables/organizations/org_settings.md
+++ b/translations/zh-CN/data/reusables/organizations/org_settings.md
@@ -1,10 +1,6 @@
----
-ms.openlocfilehash: 86e15f92ffd6a5a5b90d7a70a666447a6a51a62a
-ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
-ms.translationtype: HT
-ms.contentlocale: zh-CN
-ms.lasthandoff: 09/10/2022
-ms.locfileid: "145100528"
----
-1. 在组织名称下，单击{% octicon "gear" aria-label="The Settings gear" %}“设置”。
-  {% ifversion fpt or ghes > 3.2 or ghec %} ![组织设置按钮](/assets/images/help/organizations/organization-settings-tab-with-overview-tab.png) {% else %} ![组织设置按钮](/assets/images/help/organizations/organization-settings-tab.png) {% endif %}
+1. Under your organization name, click {% octicon "gear" aria-label="The Settings gear" %} **Settings**.
+  {% ifversion fpt or ghes or ghec %}
+  ![Organization settings button](/assets/images/help/organizations/organization-settings-tab-with-overview-tab.png)
+  {% else %}
+  ![Organization settings button](/assets/images/help/organizations/organization-settings-tab.png)
+  {% endif %}
diff --git a/translations/zh-CN/data/reusables/organizations/organization-wide-project.md b/translations/zh-CN/data/reusables/organizations/organization-wide-project.md
index 4c054ef817..052670fdf5 100644
--- a/translations/zh-CN/data/reusables/organizations/organization-wide-project.md
+++ b/translations/zh-CN/data/reusables/organizations/organization-wide-project.md
@@ -1,10 +1,6 @@
----
-ms.openlocfilehash: cba236cbf17553914d18f006b2a17a77a4892658
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
-ms.translationtype: HT
-ms.contentlocale: zh-CN
-ms.lasthandoff: 09/05/2022
-ms.locfileid: "145100516"
----
-1. 在组织名称下，单击 {% octicon "project" aria-label="The Projects icon" %}“项目”。
-  {% ifversion fpt or ghes > 3.2 or ghec %} ![组织的“项目”选项卡](/assets/images/help/organizations/organization-projects-tab-with-overview-tab.png) {% else %} ![组织的“项目”选项卡](/assets/images/help/organizations/organization-projects-tab.png) {% endif %}
+1. Under your organization name, click {% octicon "project" aria-label="The Projects icon" %} **Projects**.
+  {% ifversion fpt or ghes or ghec %}
+  ![Projects tab for your organization](/assets/images/help/organizations/organization-projects-tab-with-overview-tab.png)
+  {% else %}
+  ![Projects tab for your organization](/assets/images/help/organizations/organization-projects-tab.png)
+  {% endif %}
diff --git a/translations/zh-CN/data/reusables/organizations/owners-team.md b/translations/zh-CN/data/reusables/organizations/owners-team.md
index a41633ced2..b66f0838ca 100644
--- a/translations/zh-CN/data/reusables/organizations/owners-team.md
+++ b/translations/zh-CN/data/reusables/organizations/owners-team.md
@@ -1,12 +1,8 @@
----
-ms.openlocfilehash: 953f11ac28cbb526cd4e93bc316cf81b12241f08
-ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
-ms.translationtype: HT
-ms.contentlocale: zh-CN
-ms.lasthandoff: 09/10/2022
-ms.locfileid: "145100509"
----
-1. 在组织名称下，单击 {% octicon "people" aria-label="The people icon" %}“团队”。
-  {% ifversion fpt or ghes > 3.2 or ghec %}![“团队”选项卡](/assets/images/help/organizations/organization-teams-tab-with-overview.png) {% else %}![“团队”选项卡](/assets/images/help/organizations/organization-teams-tab.png) {% endif %}
-1. 在“团队”选项卡上，单击“所有者”。
-  ![已选择所有者团队](/assets/images/help/teams/owners-team.png)
+1. Under your organization name, click {% octicon "people" aria-label="The people icon" %} **Teams**.
+  {% ifversion fpt or ghes or ghec %}
+  ![Teams tab](/assets/images/help/organizations/organization-teams-tab-with-overview.png)
+  {% else %}
+  ![Teams tab](/assets/images/help/organizations/organization-teams-tab.png)
+  {% endif %}
+1. On the Teams tab, click **Owners**.
+  ![Owners team selected](/assets/images/help/teams/owners-team.png)
diff --git a/translations/zh-CN/data/reusables/organizations/people.md b/translations/zh-CN/data/reusables/organizations/people.md
index ab2b114619..d69d13281b 100644
--- a/translations/zh-CN/data/reusables/organizations/people.md
+++ b/translations/zh-CN/data/reusables/organizations/people.md
@@ -1,10 +1,6 @@
----
-ms.openlocfilehash: 3a40932cc10fd659071bbc951940a79a1c0498bf
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
-ms.translationtype: HT
-ms.contentlocale: zh-CN
-ms.lasthandoff: 09/05/2022
-ms.locfileid: "145100507"
----
-1. 在你的组织名称下，单击 {% octicon "person" aria-label="The Person icon" %}“人员”。
-  {% ifversion fpt or ghes > 3.2 or ghec %} ![“人员”选项卡](/assets/images/help/organizations/organization-people-tab-with-overview-tab.png) {% else %} ![“人员”选项卡](/assets/images/help/organizations/organization-people-tab.png) {% endif %}
+1. Under your organization name, click {% octicon "person" aria-label="The Person icon" %} **People**.
+  {% ifversion fpt or ghes or ghec %}
+  ![The People tab](/assets/images/help/organizations/organization-people-tab-with-overview-tab.png)
+  {% else %}
+  ![The People tab](/assets/images/help/organizations/organization-people-tab.png)
+  {% endif %}
diff --git a/translations/zh-CN/data/reusables/organizations/specific_team.md b/translations/zh-CN/data/reusables/organizations/specific_team.md
index 5dc29a04dc..655628972a 100644
--- a/translations/zh-CN/data/reusables/organizations/specific_team.md
+++ b/translations/zh-CN/data/reusables/organizations/specific_team.md
@@ -1,12 +1,8 @@
----
-ms.openlocfilehash: e073e782e9271d660c789014a93a5b0f7d703de9
-ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
-ms.translationtype: HT
-ms.contentlocale: zh-CN
-ms.lasthandoff: 09/10/2022
-ms.locfileid: "145100464"
----
-1. 在组织名称下，单击 {% octicon "people" aria-label="The people icon" %}“团队”。
-  {% ifversion fpt or ghes > 3.2 or ghec %}![“团队”选项卡](/assets/images/help/organizations/organization-teams-tab-with-overview.png) {% else %} ![“团队”选项卡](/assets/images/help/organizations/organization-teams-tab.png) {% endif %}
-1. 在 Teams（团队）选项卡上，单击团队名称。
-  ![组织的团队列表](/assets/images/help/teams/click-team-name.png)
+1. Under your organization name, click {% octicon "people" aria-label="The people icon" %} **Teams**.
+  {% ifversion fpt or ghes or ghec %}
+  ![Teams tab](/assets/images/help/organizations/organization-teams-tab-with-overview.png)
+  {% else %}
+  ![Teams tab](/assets/images/help/organizations/organization-teams-tab.png)
+  {% endif %}
+1. On the Teams tab, click the name of the team.
+  ![List of the organization's teams](/assets/images/help/teams/click-team-name.png)
diff --git a/translations/zh-CN/data/reusables/organizations/teams.md b/translations/zh-CN/data/reusables/organizations/teams.md
index 3716f6445e..55600311cf 100644
--- a/translations/zh-CN/data/reusables/organizations/teams.md
+++ b/translations/zh-CN/data/reusables/organizations/teams.md
@@ -1,10 +1,6 @@
----
-ms.openlocfilehash: ddf350dbd9a76a2d7168e67fe690662ac2e63c35
-ms.sourcegitcommit: 5b1461b419dbef60ae9dbdf8e905a4df30fc91b7
-ms.translationtype: HT
-ms.contentlocale: zh-CN
-ms.lasthandoff: 09/10/2022
-ms.locfileid: "147876083"
----
-1. 在组织名称下，单击 {% octicon "people" aria-label="The people icon" %}“团队”。
-  {% ifversion fpt or ghes > 3.2 or ghec %} ![组织页面上的“团队”选项卡](/assets/images/help/organizations/organization-teams-tab-with-overview.png) {% else %} ![组织页面上的“团队”选项卡](/assets/images/help/organizations/organization-teams-tab.png) {% endif %}
+1. Under your organization name, click {% octicon "people" aria-label="The people icon" %} **Teams**.
+  {% ifversion fpt or ghes or ghec %}
+  ![Teams tab on the organization page](/assets/images/help/organizations/organization-teams-tab-with-overview.png)
+  {% else %}
+  ![Teams tab on the organization page](/assets/images/help/organizations/organization-teams-tab.png)
+  {% endif %}
diff --git a/translations/zh-CN/data/reusables/package_registry/container-registry-ghes-migration-availability.md b/translations/zh-CN/data/reusables/package_registry/container-registry-ghes-migration-availability.md
index 4d5b78d313..1383869f25 100644
--- a/translations/zh-CN/data/reusables/package_registry/container-registry-ghes-migration-availability.md
+++ b/translations/zh-CN/data/reusables/package_registry/container-registry-ghes-migration-availability.md
@@ -1,9 +1,9 @@
 ---
-ms.openlocfilehash: 86b8c01b5dc27c55e316ba0d81176fd693f85e45
-ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.openlocfilehash: 4a39732206e0ad91422acfb3977ba7bea7d0b283
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: zh-CN
-ms.lasthandoff: 09/10/2022
-ms.locfileid: "147410696"
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148108615"
 ---
-{% data variables.product.product_name %} 3.6 支持迁移存储在组织中的 Docker 映像。 未来的版本将支持迁移用户拥有的映像。
\ No newline at end of file
+{% data variables.product.product_name %} 3.6 支持迁移存储在组织中的 Docker 映像。 未来的版本将支持迁移用户拥有的映像。
diff --git a/translations/zh-CN/data/reusables/package_registry/no-graphql-to-delete-packages.md b/translations/zh-CN/data/reusables/package_registry/no-graphql-to-delete-packages.md
new file mode 100644
index 0000000000..5d26a70da3
--- /dev/null
+++ b/translations/zh-CN/data/reusables/package_registry/no-graphql-to-delete-packages.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 5f35d3186458109231db91e80343bcb64a2193c1
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: zh-CN
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148108061"
+---
+{% ifversion fpt or ghec %}{% data variables.product.prodname_registry %}GraphQL API 不支持使用包命名空间 `https://ghcr.io/OWNER/PACKAGE-NAME` 的容器或 Docker 映像，或是使用包命名空间 `https://npm.pkg.github.com/OWNER/PACKAGE-NAME` 的 npm 映像。{% endif %}
diff --git a/translations/zh-CN/data/reusables/package_registry/package-settings-from-org-level.md b/translations/zh-CN/data/reusables/package_registry/package-settings-from-org-level.md
index 951277bdf6..d46f87514d 100644
--- a/translations/zh-CN/data/reusables/package_registry/package-settings-from-org-level.md
+++ b/translations/zh-CN/data/reusables/package_registry/package-settings-from-org-level.md
@@ -1,11 +1,7 @@
----
-ms.openlocfilehash: f0e8ddbcd9cbfd2166663191a293876d6e2f8a2e
-ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
-ms.translationtype: HT
-ms.contentlocale: zh-CN
-ms.lasthandoff: 09/10/2022
-ms.locfileid: "145100370"
----
-1. 在 {% data variables.product.prodname_dotcom %} 上，导航到组织的主页面。
-2. 在组织名称下，单击“包”。
-  {% ifversion fpt or ghes > 3.2 or ghec %} ![组织登录页上的“包”选项卡](/assets/images/help/package-registry/org-tab-for-packages-with-overview-tab.png) {% else %} ![Packages tab on org landing page](/assets/images/help/package-registry/org-tab-for-packages.png) {% endif %}
+1. On {% data variables.product.prodname_dotcom %}, navigate to the main page of your organization.
+2. Under your organization name, click **Packages**.
+  {% ifversion fpt or ghes or ghec %}
+  ![Packages tab on org landing page](/assets/images/help/package-registry/org-tab-for-packages-with-overview-tab.png)
+  {% else %}
+  ![Packages tab on org landing page](/assets/images/help/package-registry/org-tab-for-packages.png)
+  {% endif %}
diff --git a/translations/zh-CN/data/reusables/pages/check-workflow-run.md b/translations/zh-CN/data/reusables/pages/check-workflow-run.md
index fb906643b7..3bebb178d3 100644
--- a/translations/zh-CN/data/reusables/pages/check-workflow-run.md
+++ b/translations/zh-CN/data/reusables/pages/check-workflow-run.md
@@ -1,10 +1,10 @@
 ---
-ms.openlocfilehash: d2f50ce890ed4d9a90015498ecdf9909348155fb
-ms.sourcegitcommit: 96bbb6b8f3c9172209d80cb1502017ace3019807
+ms.openlocfilehash: 258f73f928cd99de64f45fda0e6cec8e08ff335c
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: zh-CN
-ms.lasthandoff: 09/10/2022
-ms.locfileid: "147877201"
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148108062"
 ---
 {% ifversion build-pages-with-actions %}
 1. {% data variables.product.prodname_pages %} 站点是使用 {% data variables.product.prodname_actions %} 工作流生成和部署的。 有关详细信息，请参阅“[查看工作流运行历史记录](/actions/monitoring-and-troubleshooting-workflows/viewing-workflow-run-history)”。
@@ -15,4 +15,4 @@ ms.locfileid: "147877201"
 
   {% endnote %}
 
-{% endif %}
\ No newline at end of file
+{% endif %}
diff --git a/translations/zh-CN/data/reusables/pages/pages-custom-workflow-beta.md b/translations/zh-CN/data/reusables/pages/pages-custom-workflow-beta.md
index 45ad356525..c18bef19ba 100644
--- a/translations/zh-CN/data/reusables/pages/pages-custom-workflow-beta.md
+++ b/translations/zh-CN/data/reusables/pages/pages-custom-workflow-beta.md
@@ -1,10 +1,10 @@
 ---
-ms.openlocfilehash: 653ecfef09a75144cb39fc0d3bf47ba7394a1ce8
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: a231b3c0bf02051ba3593f5dd04ac7fdf5506ea7
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: zh-CN
-ms.lasthandoff: 09/05/2022
-ms.locfileid: "147428429"
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148108209"
 ---
 {% ifversion pages-custom-workflow %}
 
@@ -14,4 +14,4 @@ ms.locfileid: "147428429"
 
 {% endnote %}
 
-{% endif %}
\ No newline at end of file
+{% endif %}
diff --git a/translations/zh-CN/data/reusables/profile/navigating-to-profile.md b/translations/zh-CN/data/reusables/profile/navigating-to-profile.md
new file mode 100644
index 0000000000..8f092f2a2f
--- /dev/null
+++ b/translations/zh-CN/data/reusables/profile/navigating-to-profile.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 32a0fded4915b0b23b3db1110d556bd14e0830a8
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: zh-CN
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148106643"
+---
+1. 在任意 {% data variables.product.product_name %} 页面的右上角，单击个人资料照片，然后单击“你的个人资料”。 
diff --git a/translations/zh-CN/data/reusables/projects/access-workflows.md b/translations/zh-CN/data/reusables/projects/access-workflows.md
new file mode 100644
index 0000000000..c1012912a4
--- /dev/null
+++ b/translations/zh-CN/data/reusables/projects/access-workflows.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: 2637ffcb5913f0c84f3ae092653c410ad0a5fdad
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: zh-CN
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148106588"
+---
+1. 导航到你的项目。
+1. 在右上角，单击 {% octicon "kebab-horizontal" aria-label="The menu icon" %} 以打开菜单。
+  ![显示菜单图标的屏幕截图](/assets/images/help/projects-v2/open-menu.png)
+1. 在菜单中，单击“{% octicon "workflow" aria-label="The workflow icon" %} 工作流”。
+  ![显示“工作流”菜单项的屏幕截图](/assets/images/help/projects-v2/workflows-menu-item.png)
diff --git a/translations/zh-CN/data/reusables/projects/add-draft-issue.md b/translations/zh-CN/data/reusables/projects/add-draft-issue.md
index fd032d48a8..b7117b1eba 100644
--- a/translations/zh-CN/data/reusables/projects/add-draft-issue.md
+++ b/translations/zh-CN/data/reusables/projects/add-draft-issue.md
@@ -1,12 +1,12 @@
 ---
-ms.openlocfilehash: 8dd7d544c14de78ff9150bebb1192bbd4a6007f0
-ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.openlocfilehash: 303fc7fa60ba2ccc37689055f6056a59655a6eae
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: zh-CN
-ms.lasthandoff: 09/10/2022
-ms.locfileid: "147880202"
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148108136"
 ---
 {% data reusables.projects.add-item-bottom-row %}
 1. 键入想法，然后按 Enter 键。
   ![显示粘贴问题 URL 以将其添加到项目的屏幕截图](/assets/images/help/projects-v2/add-draft-issue.png)
-1. 要添加正文文本，请单击草稿议题的标题。 在显示的 Markdown 输入框中，输入草拟的问题正文文本，然后单击“保存”。
\ No newline at end of file
+1. 要添加正文文本，请单击草稿议题的标题。 在显示的 Markdown 输入框中，输入草拟的问题正文文本，然后单击“保存”。
diff --git a/translations/zh-CN/data/reusables/projects/add-item-bottom-row.md b/translations/zh-CN/data/reusables/projects/add-item-bottom-row.md
index 8ffbc5b328..5cdf2a1f24 100644
--- a/translations/zh-CN/data/reusables/projects/add-item-bottom-row.md
+++ b/translations/zh-CN/data/reusables/projects/add-item-bottom-row.md
@@ -1,10 +1,10 @@
 ---
-ms.openlocfilehash: 62086a2f270c2d05a7e3774431e23e6ed089e1cb
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: 8af3f341f8b2a91038d1e489a1d2ed59d8743234
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: zh-CN
-ms.lasthandoff: 09/05/2022
-ms.locfileid: "147423980"
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148108130"
 ---
 1. 将光标放在项目底部一行，{% octicon "plus" aria-label="plus icon" %} 的旁边。
-  ![显示要添加项的底行的屏幕截图](/assets/images/help/projects-v2/add-item.png)
\ No newline at end of file
+  ![显示要添加项的底行的屏幕截图](/assets/images/help/projects-v2/add-item.png)
diff --git a/translations/zh-CN/data/reusables/projects/add-item-via-paste.md b/translations/zh-CN/data/reusables/projects/add-item-via-paste.md
index 2ea4f23773..b30ad6135b 100644
--- a/translations/zh-CN/data/reusables/projects/add-item-via-paste.md
+++ b/translations/zh-CN/data/reusables/projects/add-item-via-paste.md
@@ -1,12 +1,12 @@
 ---
-ms.openlocfilehash: 0191556eb977c4b657f1fd78330f6f691f34f039
-ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.openlocfilehash: 477122edeb960deca31d1ad0b97b7ad30681f23b
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: zh-CN
-ms.lasthandoff: 09/10/2022
-ms.locfileid: "147423816"
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148108208"
 ---
 {% data reusables.projects.add-item-bottom-row %}
 1. 粘贴议题或拉取请求的 URL。
   ![显示粘贴问题 URL 以将其添加到项目的屏幕截图](/assets/images/help/projects-v2/paste-url-to-add.png)
-3. 若要添加问题或拉取请求，请按 <kbd>Return</kbd>。
\ No newline at end of file
+3. 若要添加问题或拉取请求，请按 <kbd>Return</kbd>。
diff --git a/translations/zh-CN/data/reusables/projects/bulk-add.md b/translations/zh-CN/data/reusables/projects/bulk-add.md
index 3e78737c62..08d7757223 100644
--- a/translations/zh-CN/data/reusables/projects/bulk-add.md
+++ b/translations/zh-CN/data/reusables/projects/bulk-add.md
@@ -1,14 +1,14 @@
 ---
-ms.openlocfilehash: b8288219bd82b857d0bbeeefef3b27a3c8f0d3de
-ms.sourcegitcommit: 80842b4e4c500daa051eff0ccd7cde91c2d4bb36
+ms.openlocfilehash: d0d7eb973a255091345f61ff69f8f20f6361d0d9
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: zh-CN
-ms.lasthandoff: 09/11/2022
-ms.locfileid: "147884710"
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148108140"
 ---
 1. （可选）若要更改存储库，请单击下拉列表并选择存储库。 还可以搜索特定问题和拉取请求。
   ![显示存储库下拉列表的屏幕截图](/assets/images/help/projects-v2/add-bulk-select-repo.png)
 1. 选择要添加的问题和拉取请求。
   ![显示选择要添加的问题和拉取请求的屏幕截图](/assets/images/help/projects-v2/add-bulk-select-issues.png)
 1. 单击“添加选定项”。
-  ![显示“添加选定项”按钮的屏幕截图](/assets/images/help/projects-v2/add-bulk-save.png)
\ No newline at end of file
+  ![显示“添加选定项”按钮的屏幕截图](/assets/images/help/projects-v2/add-bulk-save.png)
diff --git a/translations/zh-CN/data/reusables/projects/classic-project-creation.md b/translations/zh-CN/data/reusables/projects/classic-project-creation.md
index 2ac265f969..5594006a99 100644
--- a/translations/zh-CN/data/reusables/projects/classic-project-creation.md
+++ b/translations/zh-CN/data/reusables/projects/classic-project-creation.md
@@ -1,10 +1,10 @@
 ---
-ms.openlocfilehash: cd5e613522bc536aa433d900e193ef2276df6410
-ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d
+ms.openlocfilehash: 682ba253ea2660d8608033598343393372ae3cbf
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: zh-CN
-ms.lasthandoff: 09/11/2022
-ms.locfileid: "147375719"
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148108206"
 ---
 {% ifversion fpt or ghec %}
 
@@ -14,4 +14,4 @@ ms.locfileid: "147375719"
 
 {% endnote %}
 
-{% endif %}
\ No newline at end of file
+{% endif %}
diff --git a/translations/zh-CN/data/reusables/projects/new-field.md b/translations/zh-CN/data/reusables/projects/new-field.md
index 0fa5f8eb0f..641a7f7fe7 100644
--- a/translations/zh-CN/data/reusables/projects/new-field.md
+++ b/translations/zh-CN/data/reusables/projects/new-field.md
@@ -1,14 +1,14 @@
 ---
-ms.openlocfilehash: daf5b47c71e8cbde44c6dab38eabf7c6d922be9a
-ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.openlocfilehash: 3acee6d785e2b633f979e7edb8f80544dfa09ced
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: zh-CN
-ms.lasthandoff: 09/11/2022
-ms.locfileid: "147882873"
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148108205"
 ---
 1. 在表视图中，单击最右侧字段标题中的 {% octicon "plus" aria-label="the plus icon" %}。
    ![显示“新建字段”按钮的屏幕截图](/assets/images/help/projects-v2/new-field-button.png)
 1. 单击“新建字段”。
    ![显示“新建字段”菜单项的屏幕截图](/assets/images/help/projects-v2/new-field-menu-item.png)
 1. 键入新字段的名称。
-   ![显示字段名称的屏幕截图](/assets/images/help/projects-v2/new-field-name.png)
\ No newline at end of file
+   ![显示字段名称的屏幕截图](/assets/images/help/projects-v2/new-field-name.png)
diff --git a/translations/zh-CN/data/reusables/projects/new-view.md b/translations/zh-CN/data/reusables/projects/new-view.md
index cdd64c7bf6..1a63cac99e 100644
--- a/translations/zh-CN/data/reusables/projects/new-view.md
+++ b/translations/zh-CN/data/reusables/projects/new-view.md
@@ -1,10 +1,10 @@
 ---
-ms.openlocfilehash: 831716db8a52f44aee809924a38f8288952d23df
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: 9bac51e4098b1da121c0763f8581716a547353af
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: zh-CN
-ms.lasthandoff: 09/05/2022
-ms.locfileid: "147423936"
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148108045"
 ---
 1. 在现有视图的右侧，单击“新建视图”
-   ![显示列字段菜单的屏幕截图](/assets/images/help/projects-v2/new-view.png)
\ No newline at end of file
+   ![显示列字段菜单的屏幕截图](/assets/images/help/projects-v2/new-view.png)
diff --git a/translations/zh-CN/data/reusables/projects/open-item-menu.md b/translations/zh-CN/data/reusables/projects/open-item-menu.md
index 0d63a0472f..4d26fb9724 100644
--- a/translations/zh-CN/data/reusables/projects/open-item-menu.md
+++ b/translations/zh-CN/data/reusables/projects/open-item-menu.md
@@ -1,9 +1,9 @@
 ---
-ms.openlocfilehash: 15b1ba8ed434c9c9c6bb81c0ca0376c2e42fca48
-ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794
+ms.openlocfilehash: 10c8c2b298fd4eaec742bf9efbc686d6f2bb3c0b
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: zh-CN
-ms.lasthandoff: 09/09/2022
-ms.locfileid: "147876052"
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148108204"
 ---
-1.  选择 {% octicon "triangle-down" aria-label="the item menu" %}（在表格布局中）或 {% octicon "kebab-horizontal" aria-label="the item menu" %}（在板布局中）。
\ No newline at end of file
+1.  选择 {% octicon "triangle-down" aria-label="the item menu" %}（在表格布局中）或 {% octicon "kebab-horizontal" aria-label="the item menu" %}（在板布局中）。
diff --git a/translations/zh-CN/data/reusables/projects/open-view-menu.md b/translations/zh-CN/data/reusables/projects/open-view-menu.md
index d5b8d37e39..32bb4878a8 100644
--- a/translations/zh-CN/data/reusables/projects/open-view-menu.md
+++ b/translations/zh-CN/data/reusables/projects/open-view-menu.md
@@ -1,10 +1,10 @@
 ---
-ms.openlocfilehash: 0873b7b527997d2472413b016a12f2f413f06e86
-ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.openlocfilehash: 167d4ab0b57e2af8ee07f720db569725829adf69
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: zh-CN
-ms.lasthandoff: 09/10/2022
-ms.locfileid: "147880138"
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148108202"
 ---
 1. 单击当前打开视图名称旁边的 {% octicon "triangle-down" aria-label="the drop-down icon" %}。
-  ![显示视图菜单图标的屏幕截图](/assets/images/help/projects-v2/view-menu-icon.png)
\ No newline at end of file
+  ![显示视图菜单图标的屏幕截图](/assets/images/help/projects-v2/view-menu-icon.png)
diff --git a/translations/zh-CN/data/reusables/projects/owners-can-limit-visibility-permissions.md b/translations/zh-CN/data/reusables/projects/owners-can-limit-visibility-permissions.md
index a1fbe7cef8..ed777df368 100644
--- a/translations/zh-CN/data/reusables/projects/owners-can-limit-visibility-permissions.md
+++ b/translations/zh-CN/data/reusables/projects/owners-can-limit-visibility-permissions.md
@@ -1,9 +1,9 @@
 ---
-ms.openlocfilehash: e9790db64c727836fb25001ef5160b0030a12da4
-ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794
+ms.openlocfilehash: a811a75bedf573e347f2346a8872dd533b3a4466
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: zh-CN
-ms.lasthandoff: 09/09/2022
-ms.locfileid: "147614526"
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148108060"
 ---
-组织所有者可控制组织成员创建公共 {% data variables.projects.projects_v2_and_v1 %} 的能力，也可将现有 {% data variables.projects.projects_v2_and_v1 %} 的可见性更改为公共。 有关详细信息，请参阅“[允许在组织中更改项目可见性](/organizations/managing-organization-settings/allowing-project-visibility-changes-in-your-organization)”。
\ No newline at end of file
+组织所有者可控制组织成员创建公共 {% data variables.projects.projects_v2_and_v1 %} 的能力，也可将现有 {% data variables.projects.projects_v2_and_v1 %} 的可见性更改为公共。 有关详细信息，请参阅“[允许在组织中更改项目可见性](/organizations/managing-organization-settings/allowing-project-visibility-changes-in-your-organization)”。
diff --git a/translations/zh-CN/data/reusables/projects/save-view.md b/translations/zh-CN/data/reusables/projects/save-view.md
index fd878d1102..6d4340d39f 100644
--- a/translations/zh-CN/data/reusables/projects/save-view.md
+++ b/translations/zh-CN/data/reusables/projects/save-view.md
@@ -1,11 +1,11 @@
 ---
-ms.openlocfilehash: 9103637cf5f41c5c40b4328f050edf1c5ca8eabc
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: 2a7a472bbfeed56c58e483b61c2a140aa52e63e8
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: zh-CN
-ms.lasthandoff: 09/05/2022
-ms.locfileid: "147423977"
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148108047"
 ---
 {% data reusables.projects.open-view-menu %}
 1. 单击“保存更改”。 
-   ![显示“保存”菜单项的屏幕截图](/assets/images/help/projects-v2/save-view.png)
\ No newline at end of file
+   ![显示“保存”菜单项的屏幕截图](/assets/images/help/projects-v2/save-view.png)
diff --git a/translations/zh-CN/data/reusables/projects/select-an-item.md b/translations/zh-CN/data/reusables/projects/select-an-item.md
index 3671049a6e..2dc48e081f 100644
--- a/translations/zh-CN/data/reusables/projects/select-an-item.md
+++ b/translations/zh-CN/data/reusables/projects/select-an-item.md
@@ -1,13 +1,13 @@
 ---
-ms.openlocfilehash: a78a08bd4cdf72ca732b4c2a664164d0f69f1815
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: 8fef95ca781a57606206a89a8408bcd4774402e2
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: zh-CN
-ms.lasthandoff: 09/05/2022
-ms.locfileid: "147423976"
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148108611"
 ---
 1. 选择该项。 要选择多个项，请执行下列操作之一：
      - 按住 <kbd>Command</kbd> (Mac) 或 <kbd>Ctrl</kbd> (Windows/Linux) 并单击每个项。
      - 选择某项，然后按 <kbd>Shift</kbd>+<kbd>↑</kbd> 或 <kbd>Shift</kbd>+<kbd>↓</kbd> 以选择所选项上方或下方的其他项。
      - 选择一个项，然后按 <kbd>Shift</kbd> 并单击另一个项以选择两个项之间的所有项。
-     - 选择一行或一项后，按 <kbd>Command</kbd>+<kbd>A</kbd> (Mac) 或 <kbd>Ctrl</kbd>+<kbd>A</kbd> (Windows/Linux)，以选择板布局中某一列的所有项或表格布局中的所有项。
\ No newline at end of file
+     - 选择一行或一项后，按 <kbd>Command</kbd>+<kbd>A</kbd> (Mac) 或 <kbd>Ctrl</kbd>+<kbd>A</kbd> (Windows/Linux)，以选择板布局中某一列的所有项或表格布局中的所有项。
diff --git a/translations/zh-CN/data/reusables/pull_requests/merge-queue-beta.md b/translations/zh-CN/data/reusables/pull_requests/merge-queue-beta.md
index fe55c68405..97c035c0e5 100644
--- a/translations/zh-CN/data/reusables/pull_requests/merge-queue-beta.md
+++ b/translations/zh-CN/data/reusables/pull_requests/merge-queue-beta.md
@@ -1,7 +1,14 @@
-{% ifversion fpt or ghec %}
-{% note %}
+---
+ms.openlocfilehash: 85db1024fd3a47bebaf0a6fef56843c8be2509a9
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: zh-CN
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148007904"
+---
+{% ifversion fpt or ghec %} {% note %}
 
-**Note:** The pull request merge queue feature is currently in limited public beta and subject to change.
+注意：拉取请求合并队列功能目前处于有限公测阶段，可能会发生更改。
 
 {% endnote %}
 
diff --git a/translations/zh-CN/data/reusables/repositories/commit-signoffs.md b/translations/zh-CN/data/reusables/repositories/commit-signoffs.md
index c1eef2a52f..cf051fc92f 100644
--- a/translations/zh-CN/data/reusables/repositories/commit-signoffs.md
+++ b/translations/zh-CN/data/reusables/repositories/commit-signoffs.md
@@ -1,10 +1,10 @@
 ---
-ms.openlocfilehash: 50db50aff42d977575a89a2e22287b1672081ee4
-ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.openlocfilehash: 1b3e7f64c7507fde4a126cddaca3c4a97247d967
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: zh-CN
-ms.lasthandoff: 09/11/2022
-ms.locfileid: "147881387"
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148108222"
 ---
 强制提交签字仅适用于通过 Web 界面进行的提交。 对于通过 Git 命令行接口进行的提交，提交作者必须使用 `--signoff` 选项签字提交。 有关详细信息，请参阅 [Git 文档](https://git-scm.com/docs/git-commit)。
 
@@ -15,4 +15,4 @@ ms.locfileid: "147881387"
 
 在签字提交之前，应确保提交符合有关管理所提交的存储库的规则和许可。 存储库可使用签字协议，例如来自 Linux 基金会的开发者来源证书。 有关详细信息，请参阅[开发者来源证书](https://developercertificate.org/)。
 
-签字提交与签名提交不同。 有关签名提交的详细信息，请参阅“[关于提交签名验证](/authentication/managing-commit-signature-verification/about-commit-signature-verification)”。
\ No newline at end of file
+签字提交与签名提交不同。 有关签名提交的详细信息，请参阅“[关于提交签名验证](/authentication/managing-commit-signature-verification/about-commit-signature-verification)”。
diff --git a/translations/zh-CN/data/reusables/repositories/security-advisories-republishing.md b/translations/zh-CN/data/reusables/repositories/security-advisories-republishing.md
index 24caf9b29c..c2f7cd1471 100644
--- a/translations/zh-CN/data/reusables/repositories/security-advisories-republishing.md
+++ b/translations/zh-CN/data/reusables/repositories/security-advisories-republishing.md
@@ -1,9 +1 @@
----
-ms.openlocfilehash: 0ac903914a15eacb9f6db488c4c1cac01a6411e6
-ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
-ms.translationtype: HT
-ms.contentlocale: zh-CN
-ms.lasthandoff: 09/11/2022
-ms.locfileid: "145086751"
----
-您还可以使用 {% data variables.product.prodname_security_advisories %} 重新发布已在其他地方披露的安全漏洞详细信息，方法是将该漏洞的详细信息复制并粘贴到新的安全通告中。
+You can also use repository security advisories to republish the details of a security vulnerability that you have already disclosed elsewhere by copying and pasting the details of the vulnerability into a new security advisory.
diff --git a/translations/zh-CN/data/reusables/saml/ae-uses-saml-sso.md b/translations/zh-CN/data/reusables/saml/ae-uses-saml-sso.md
index 203d47072b..cc2d0a8444 100644
--- a/translations/zh-CN/data/reusables/saml/ae-uses-saml-sso.md
+++ b/translations/zh-CN/data/reusables/saml/ae-uses-saml-sso.md
@@ -1,9 +1,9 @@
 ---
-ms.openlocfilehash: 3657d22416c277ff6af595279480f31134d7b6d8
-ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.openlocfilehash: 8396c212c048ddf20c4b00d4891a21052555325e
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: zh-CN
-ms.lasthandoff: 09/10/2022
-ms.locfileid: "145099330"
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148108131"
 ---
-{% data variables.product.product_name %} 使用 SAML SSO 进行用户身份验证。 您可以从支持 SAML 2.0 标准的 IdP 集中管理对 {% data variables.product.prodname_ghe_managed %} 的访问。
+{% data variables.product.product_name %} 使用 SAML SSO 进行用户身份验证。 您可以从支持 SAML 2.0 标准的 IdP 集中管理对 {% data variables.product.prodname_ghe_managed %} 的访问。
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/saml/authentication-loop.md b/translations/zh-CN/data/reusables/saml/authentication-loop.md
index ee8f511b7d..d786b82e39 100644
--- a/translations/zh-CN/data/reusables/saml/authentication-loop.md
+++ b/translations/zh-CN/data/reusables/saml/authentication-loop.md
@@ -1,10 +1,10 @@
 ---
-ms.openlocfilehash: e7dd0182fdc70186e5b3d137ac99cebd2ff562ea
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: 7e0f711826a1f1ea1bee8cec18bf5b4614815174
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: zh-CN
-ms.lasthandoff: 09/05/2022
-ms.locfileid: "147093162"
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148108132"
 ---
 ## 用户反复重定向到身份验证
 
@@ -12,4 +12,4 @@ ms.locfileid: "147093162"
 
 SAML 响应中发送的 `SessionNotOnOrAfter` 值决定何时将用户重定向回 IdP 进行身份验证。 如果 SAML 会话持续时间配置为 2 小时或更短，{% data variables.product.prodname_dotcom_the_website %} 将在 SAML 会话过期前 5 分钟刷新它。 如果会话持续时间配置为 5 分钟或更短，则用户可能会卡在 SAML 身份验证循环中。 
 
-若要解决此问题，建议将 SAML 会话的最短持续时间配置为 4 小时。 有关详细信息，请参阅“[SAML 配置参考](/admin/identity-and-access-management/using-saml-for-enterprise-iam/saml-configuration-reference#session-duration-and-timeout)”。
\ No newline at end of file
+若要解决此问题，建议将 SAML 会话的最短持续时间配置为 4 小时。 有关详细信息，请参阅“[SAML 配置参考](/admin/identity-and-access-management/using-saml-for-enterprise-iam/saml-configuration-reference#session-duration-and-timeout)”。
diff --git a/translations/zh-CN/data/reusables/saml/current-time-earlier-than-notbefore-condition.md b/translations/zh-CN/data/reusables/saml/current-time-earlier-than-notbefore-condition.md
index 3863f1cdbc..f472aa8ae1 100644
--- a/translations/zh-CN/data/reusables/saml/current-time-earlier-than-notbefore-condition.md
+++ b/translations/zh-CN/data/reusables/saml/current-time-earlier-than-notbefore-condition.md
@@ -1,10 +1,10 @@
 ---
-ms.openlocfilehash: b0db396765557122de192fe6dde98aeeb0057ec2
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: a9ba68f182b48a4186a4ae63909ef4e146d7c392
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: zh-CN
-ms.lasthandoff: 09/05/2022
-ms.locfileid: "147093166"
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148108133"
 ---
 ## 错误：“当前时间早于 NotBefore 条件”
 
@@ -12,4 +12,4 @@ ms.locfileid: "147093166"
 
 {% ifversion ghes %}为防止此问题，我们建议将设备指向与 IdP 相同的网络时间协议 (NTP) 源（如果可能）。 {% endif %}如果遇到此错误，请确保 {% ifversion ghes %}设备{% else %}IdP{% endif %} 上的时间与 NTP 服务器正确同步。
 
-如果使用 ADFS 作为 IdP，则对于 {% data variables.product.prodname_dotcom %}，也将 ADFS 中的 `NotBeforeSkew` 设置为 1 分钟。 如果 `NotBeforeSkew` 设置为 0，即使非常小的时间差（包括几毫秒）也会导致身份验证问题。
\ No newline at end of file
+如果使用 ADFS 作为 IdP，则对于 {% data variables.product.prodname_dotcom %}，也将 ADFS 中的 `NotBeforeSkew` 设置为 1 分钟。 如果 `NotBeforeSkew` 设置为 0，即使非常小的时间差（包括几毫秒）也会导致身份验证问题。
diff --git a/translations/zh-CN/data/reusables/saml/okta-ae-sso-beta.md b/translations/zh-CN/data/reusables/saml/okta-ae-sso-beta.md
index 1fc5466e5c..b424e2873e 100644
--- a/translations/zh-CN/data/reusables/saml/okta-ae-sso-beta.md
+++ b/translations/zh-CN/data/reusables/saml/okta-ae-sso-beta.md
@@ -1,8 +1,16 @@
+---
+ms.openlocfilehash: eef3fbd7285fbea49bf20ed9359b2a7c6c49fff1
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: zh-CN
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148108111"
+---
 {% ifversion ghae %}
 
 {% note %}
 
-**Note:** {% data variables.product.prodname_ghe_managed %} single sign-on (SSO) support for Okta is currently in beta.
+注意：{% data variables.product.prodname_ghe_managed %} 单一登录 (SSO) 对 Okta 的支持目前处于 beta 版本。
 
 {% endnote %}
 
diff --git a/translations/zh-CN/data/reusables/saml/okta-sign-on-tab.md b/translations/zh-CN/data/reusables/saml/okta-sign-on-tab.md
index c32bf7bc83..16908b62d6 100644
--- a/translations/zh-CN/data/reusables/saml/okta-sign-on-tab.md
+++ b/translations/zh-CN/data/reusables/saml/okta-sign-on-tab.md
@@ -1,10 +1,11 @@
 ---
-ms.openlocfilehash: 0626c11052a92500820ca0a3ac24f0cad784ebd6
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: c1c07418ac678e38f387f9be4ebc00153558ae22
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: zh-CN
-ms.lasthandoff: 09/05/2022
-ms.locfileid: "145127343"
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148108179"
 ---
 1. 在应用程序名称下，单击“登录”。
-  ![Okta 应用程序的“登录”选项卡的屏幕截图](/assets/images/help/saml/okta-sign-on-tab.png)
+
+   ![“登录”选项卡](/assets/images/help/saml/okta-ae-sign-on-tab.png)
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/saml/okta-view-setup-instructions.md b/translations/zh-CN/data/reusables/saml/okta-view-setup-instructions.md
index d4abd59246..977fe45508 100644
--- a/translations/zh-CN/data/reusables/saml/okta-view-setup-instructions.md
+++ b/translations/zh-CN/data/reusables/saml/okta-view-setup-instructions.md
@@ -1,9 +1,11 @@
 ---
-ms.openlocfilehash: 0c41ccbde38c607916822e265d7fb749318db717
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: fef8d78e7518ea1b11d657f0ed82929847cd5575
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: zh-CN
-ms.lasthandoff: 09/05/2022
-ms.locfileid: "145127341"
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148108020"
 ---
 1. 在“登录方法”下，单击“查看设置说明”。
+
+   ![“登录”选项卡](/assets/images/help/saml/okta-ae-view-setup-instructions.png)
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/saml/saml-accounts.md b/translations/zh-CN/data/reusables/saml/saml-accounts.md
index edf389ca37..75a2372c3a 100644
--- a/translations/zh-CN/data/reusables/saml/saml-accounts.md
+++ b/translations/zh-CN/data/reusables/saml/saml-accounts.md
@@ -1,10 +1,10 @@
 ---
-ms.openlocfilehash: 41c1afacc9dbebc6722e5b60cbd5a52b5786df5d
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: b5ea320db35c6a770853644bcdb50117d3da578d
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: zh-CN
-ms.lasthandoff: 09/05/2022
-ms.locfileid: "147526814"
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148108018"
 ---
 如果配置了 SAML SSO，组织成员将继续在 {% data variables.product.prodname_dotcom_the_website %} 上登录到其个人帐户。 当成员访问组织内的非公共资源时，{% data variables.product.prodname_dotcom %} 会将成员重定向到你的 IdP 以进行身份验证。 身份验证成功后，IdP 将该成员重定向回 {% data variables.product.prodname_dotcom %}。 有关详细信息，请参阅“[关于通过 SAML 单一登录进行身份验证](/enterprise-cloud@latest/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on)”。
 
@@ -12,4 +12,4 @@ ms.locfileid: "147526814"
 
 **注意：** SAML SSO 不会取代 {% data variables.product.prodname_dotcom %} 的正常登录过程。 除非使用 {% data variables.product.prodname_emus %}，否则成员将继续在 {% data variables.product.prodname_dotcom_the_website %} 上登录到其个人帐户，并且每个个人帐户都将链接到 IdP 中的外部标识。
 
-{% endnote %}
\ No newline at end of file
+{% endnote %}
diff --git a/translations/zh-CN/data/reusables/secret-scanning/partner-secret-list-private-repo.md b/translations/zh-CN/data/reusables/secret-scanning/partner-secret-list-private-repo.md
index af2f8af01c..3d68fc424b 100644
--- a/translations/zh-CN/data/reusables/secret-scanning/partner-secret-list-private-repo.md
+++ b/translations/zh-CN/data/reusables/secret-scanning/partner-secret-list-private-repo.md
@@ -9,8 +9,7 @@ Alibaba Cloud | Alibaba Cloud Access Key ID with Alibaba Cloud Access Key Secret
 {%- ifversion fpt or ghec or ghes > 3.3 or ghae > 3.3 %}
 Amazon | Amazon OAuth Client ID with Amazon OAuth Client Secret | amazon_oauth_client_id </br>amazon_oauth_client_secret{% endif %}
 Amazon Web Services (AWS) | Amazon AWS Access Key ID with Amazon AWS Secret Access Key | aws_access_key_id </br>aws_secret_access_key
-{%- ifversion fpt or ghec or ghes > 3.2 or ghae %}
-Amazon Web Services (AWS) | Amazon AWS Session Token with Amazon AWS Temporary Access Key ID and Amazon AWS Secret Access Key | aws_session_token </br>aws_temporary_access_key_id </br>aws_secret_access_key{% endif %}
+Amazon Web Services (AWS) | Amazon AWS Session Token with Amazon AWS Temporary Access Key ID and Amazon AWS Secret Access Key | aws_session_token </br>aws_temporary_access_key_id </br>aws_secret_access_key
 Asana | Asana {% data variables.product.pat_generic %} | asana_personal_access_token
 Atlassian | Atlassian API Token | atlassian_api_token
 Atlassian | Atlassian JSON Web Token | atlassian_jwt
@@ -31,14 +30,12 @@ Azure | Azure Service Management Certificate | azure_management_certificate
 {%- ifversion ghes < 3.4 or ghae < 3.4 %}
 Azure | Azure SQL Connection String | azure_sql_connection_string{% endif %}
 Azure | Azure Storage Account Key | azure_storage_account_key
-{%- ifversion fpt or ghec or ghes > 3.2 or ghae %}
-Beamer | Beamer API Key | beamer_api_key{% endif %}
+Beamer | Beamer API Key | beamer_api_key
 Checkout.com | Checkout.com Production Secret Key | checkout_production_secret_key
 Checkout.com | Checkout.com Test Secret Key | checkout_test_secret_key
 Clojars | Clojars Deploy Token | clojars_deploy_token
 CloudBees CodeShip | CloudBees CodeShip Credential | codeship_credential
-{%- ifversion fpt or ghec or ghes > 3.2 or ghae %}
-Contentful | Contentful {% data variables.product.pat_generic %} | contentful_personal_access_token{% endif %}
+Contentful | Contentful {% data variables.product.pat_generic %} | contentful_personal_access_token
 Databricks | Databricks Access Token | databricks_access_token
 {%- ifversion fpt or ghec or ghes > 3.8 or ghae > 3.8 %}
 DevCycle | DevCycle Client API Key | devcycle_client_api_key
@@ -69,8 +66,7 @@ Flutterwave | Flutterwave Live API Secret Key | flutterwave_live_api_secret_key
 Flutterwave | Flutterwave Test API Secret Key | flutterwave_test_api_secret_key
 Frame.io | Frame.io JSON Web Token | frameio_jwt
 Frame.io| Frame.io Developer Token | frameio_developer_token
-{%- ifversion fpt or ghec or ghes > 3.2 or ghae %}
-FullStory | FullStory API Key | fullstory_api_key{% endif %}
+FullStory | FullStory API Key | fullstory_api_key
 GitHub | GitHub {% data variables.product.pat_generic %} | github_personal_access_token
 GitHub | GitHub OAuth Access Token | github_oauth_access_token
 GitHub | GitHub Refresh Token | github_refresh_token
@@ -80,14 +76,11 @@ GitHub | GitHub SSH Private Key | github_ssh_private_key
 GitLab | GitLab Access Token | gitlab_access_token{% endif %}
 GoCardless | GoCardless Live Access Token | gocardless_live_access_token
 GoCardless | GoCardless Sandbox Access Token | gocardless_sandbox_access_token
-{%- ifversion fpt or ghec or ghes > 3.2 or ghae %}
-Google | Firebase Cloud Messaging Server Key | firebase_cloud_messaging_server_key{% endif %}
+Google | Firebase Cloud Messaging Server Key | firebase_cloud_messaging_server_key
 Google | Google API Key | google_api_key
 Google | Google Cloud Private Key ID | 
-{%- ifversion fpt or ghec or ghes > 3.2 or ghae %}
-Google | Google Cloud Storage Service Account Access Key ID with Google Cloud Storage Access Key Secret | google_cloud_storage_service_account_access_key_id </br>google_cloud_storage_access_key_secret{% endif %}
-{%- ifversion fpt or ghec or ghes > 3.2 or ghae %}
-Google | Google Cloud Storage User Access Key ID with Google Cloud Storage Access Key Secret | google_cloud_storage_user_access_key_id </br>google_cloud_storage_access_key_secret{% endif %}
+Google | Google Cloud Storage Service Account Access Key ID with Google Cloud Storage Access Key Secret | google_cloud_storage_service_account_access_key_id </br>google_cloud_storage_access_key_secret
+Google | Google Cloud Storage User Access Key ID with Google Cloud Storage Access Key Secret | google_cloud_storage_user_access_key_id </br>google_cloud_storage_access_key_secret
 {%- ifversion fpt or ghec or ghes > 3.3 or ghae > 3.3 %}
 Google | Google OAuth Access Token | google_oauth_access_token{% endif %}
 {%- ifversion fpt or ghec or ghes > 3.3 or ghae > 3.3 %}
@@ -97,6 +90,8 @@ Google | Google OAuth Refresh Token | google_oauth_refresh_token{% endif %}
 Grafana | Grafana API Key | grafana_api_key
 HashiCorp | Terraform Cloud / Enterprise API Token | terraform_api_token
 HashiCorp | HashiCorp Vault Batch Token | hashicorp_vault_batch_token
+{%- ifversion fpt or ghec or ghes > 3.8 or ghae > 3.8 %}
+HashiCorp | HashiCorp Vault Root Service Token | hashicorp_vault_root_service_token{% endif %}
 HashiCorp | HashiCorp Vault Service Token | hashicorp_vault_service_token
 Hubspot | Hubspot API Key | hubspot_api_key
 Intercom | Intercom Access Token | intercom_access_token
@@ -104,10 +99,8 @@ Ionic | Ionic {% data variables.product.pat_generic %} | ionic_personal_access_t
 Ionic | Ionic Refresh Token | ionic_refresh_token
 {%- ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4 %}
 JD Cloud | JD Cloud Access Key | jd_cloud_access_key{% endif %}
-{%- ifversion fpt or ghec or ghes > 3.2 or ghae %}
-JFrog | JFrog Platform Access Token | jfrog_platform_access_token{% endif %}
-{%- ifversion fpt or ghec or ghes > 3.2 or ghae %}
-JFrog | JFrog Platform API Key | jfrog_platform_api_key{% endif %}
+JFrog | JFrog Platform Access Token | jfrog_platform_access_token
+JFrog | JFrog Platform API Key | jfrog_platform_api_key
 Linear | Linear API Key | linear_api_key
 Linear | Linear OAuth Access Token | linear_oauth_access_token
 Lob | Lob Live API Key | lob_live_api_key
@@ -125,14 +118,10 @@ Meta | Facebook Access Token | facebook_access_token
 Midtrans | Midtrans Production Server Key | midtrans_production_server_key{% endif %}
 {%- ifversion fpt or ghec or ghes > 3.3 or ghae > 3.3 %}
 Midtrans | Midtrans Sandbox Server Key | midtrans_sandbox_server_key{% endif %}
-{%- ifversion fpt or ghec or ghes > 3.2 or ghae %}
-New Relic | New Relic Personal API Key | new_relic_personal_api_key{% endif %}
-{%- ifversion fpt or ghec or ghes > 3.2 or ghae %}
-New Relic | New Relic REST API Key | new_relic_rest_api_key{% endif %}
-{%- ifversion fpt or ghec or ghes > 3.2 or ghae %}
-New Relic | New Relic Insights Query Key | new_relic_insights_query_key{% endif %}
-{%- ifversion fpt or ghec or ghes > 3.2 or ghae %}
-New Relic | New Relic License Key | new_relic_license_key{% endif %}
+New Relic | New Relic Personal API Key | new_relic_personal_api_key
+New Relic | New Relic REST API Key | new_relic_rest_api_key
+New Relic | New Relic Insights Query Key | new_relic_insights_query_key
+New Relic | New Relic License Key | new_relic_license_key
 {%- ifversion fpt or ghec or ghes > 3.3 or ghae > 3.3 %}
 Notion | Notion Integration Token | notion_integration_token{% endif %}
 {%- ifversion fpt or ghec or ghes > 3.3 or ghae > 3.3 %}
@@ -145,14 +134,10 @@ Onfido | Onfido Live API Token | onfido_live_api_token
 Onfido | Onfido Sandbox API Token | onfido_sandbox_api_token
 OpenAI | OpenAI API Key | openai_api_key
 Palantir | Palantir JSON Web Token | palantir_jwt
-{%- ifversion fpt or ghec or ghes > 3.2 or ghae %}
-PlanetScale | PlanetScale Database Password | planetscale_database_password{% endif %}
-{%- ifversion fpt or ghec or ghes > 3.2 or ghae %}
-PlanetScale | PlanetScale OAuth Token | planetscale_oauth_token{% endif %}
-{%- ifversion fpt or ghec or ghes > 3.2 or ghae %}
-PlanetScale | PlanetScale Service Token | planetscale_service_token{% endif %}
-{%- ifversion fpt or ghec or ghes > 3.2 or ghae %}
-Plivo | Plivo Auth ID with Plivo Auth Token | plivo_auth_id </br>plivo_auth_token{% endif %}
+PlanetScale | PlanetScale Database Password | planetscale_database_password
+PlanetScale | PlanetScale OAuth Token | planetscale_oauth_token
+PlanetScale | PlanetScale Service Token | planetscale_service_token
+Plivo | Plivo Auth ID with Plivo Auth Token | plivo_auth_id </br>plivo_auth_token
 Postman | Postman API Key | postman_api_key
 {%- ifversion fpt or ghec or ghes > 3.6 or ghae > 3.6 %}
 Prefect | Prefect Server API Key | prefect_server_api_key
@@ -173,10 +158,8 @@ Samsara | Samsara OAuth Access Token | samsara_oauth_access_token
 {%- ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4 %}
 Segment | Segment Public API Token | segment_public_api_token{% endif %}
 SendGrid | SendGrid API Key | sendgrid_api_key
-{%- ifversion fpt or ghec or ghes > 3.2 or ghae %}
-Sendinblue | Sendinblue API Key | sendinblue_api_key{% endif %}
-{%- ifversion fpt or ghec or ghes > 3.2 or ghae %}
-Sendinblue | Sendinblue SMTP Key | sendinblue_smtp_key{% endif %}
+Sendinblue | Sendinblue API Key | sendinblue_api_key
+Sendinblue | Sendinblue SMTP Key | sendinblue_smtp_key
 Shippo | Shippo Live API Token | shippo_live_api_token
 Shippo | Shippo Test API Token | shippo_test_api_token
 {%- ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4 %}
diff --git a/translations/zh-CN/data/reusables/secret-scanning/push-protection-allow-email.md b/translations/zh-CN/data/reusables/secret-scanning/push-protection-allow-email.md
index 48a65b264a..71a4e3134f 100644
--- a/translations/zh-CN/data/reusables/secret-scanning/push-protection-allow-email.md
+++ b/translations/zh-CN/data/reusables/secret-scanning/push-protection-allow-email.md
@@ -1,10 +1,10 @@
 ---
-ms.openlocfilehash: ba22b3461f3e8bf93257698d2c6f4eb4bc863949
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: 46850cadc908d94d514fde76ee0fecbddce0affe
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: zh-CN
-ms.lasthandoff: 09/05/2022
-ms.locfileid: "147409775"
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148108109"
 ---
 {% ifversion secret-scanning-push-protection-email %}当参与者绕过机密的推送保护块时，{% data variables.product.prodname_dotcom %} 还会向选择接收电子邮件通知的组织所有者、安全管理员和存储库管理员发送电子邮件警报。
-{% endif %}
\ No newline at end of file
+{% endif %}
diff --git a/translations/zh-CN/data/reusables/secret-scanning/push-protection-remove-secret.md b/translations/zh-CN/data/reusables/secret-scanning/push-protection-remove-secret.md
index 48c8bb19c3..906598b19b 100644
--- a/translations/zh-CN/data/reusables/secret-scanning/push-protection-remove-secret.md
+++ b/translations/zh-CN/data/reusables/secret-scanning/push-protection-remove-secret.md
@@ -1,9 +1,9 @@
 ---
-ms.openlocfilehash: d22214ea8eb5bc89912bed3c43a678fba80f014b
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: 3d0f861b8ee9ff6b4e948dee7dfb67a648021404
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: zh-CN
-ms.lasthandoff: 09/05/2022
-ms.locfileid: "147578707"
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148108199"
 ---
-如果确认机密是真实的，则需要将机密从分支和出现机密的所有提交中删除，然后再次推送。
\ No newline at end of file
+如果确认机密是真实的，则需要将机密从分支和出现机密的所有提交中删除，然后再次推送。
diff --git a/translations/zh-CN/data/reusables/secret-scanning/push-protection-web-ui-choice.md b/translations/zh-CN/data/reusables/secret-scanning/push-protection-web-ui-choice.md
index 682eee5ec7..d8b2b44d61 100644
--- a/translations/zh-CN/data/reusables/secret-scanning/push-protection-web-ui-choice.md
+++ b/translations/zh-CN/data/reusables/secret-scanning/push-protection-web-ui-choice.md
@@ -1,13 +1,21 @@
-When you use the web UI to attempt to commit a supported secret to a repository or organization with secret scanning as a push protection enabled, {% data variables.product.prodname_dotcom %} will block the commit. 
+---
+ms.openlocfilehash: 7bb1603715c255f08ac0bfbe7ff2cdbfe99a3134
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: zh-CN
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148108129"
+---
+使用 Web UI 尝试将受支持的机密提交到启用了机密扫描作为推送保护的存储库或组织时，{% data variables.product.prodname_dotcom %} 将阻止提交。 
 
-You will see a banner at the top of the page with information about the secret's location, and the secret will also be underlined in the file so you can easily find it.
+你将在页面顶部看到一个横幅，其中包含有关机密位置的信息，并且文件中的机密将带有下划线，以便你轻松找到它。
 
 {% ifversion push-protection-custom-link-orgs %}
 
-  ![Screenshot showing commit in web ui blocked because of secret scanning push protection](/assets/images/help/repository/secret-scanning-push-protection-web-ui-commit-blocked-banner-with-link.png)
+  ![屏幕截图显示因机密扫描推送保护而阻止在 Web UI 中提交](/assets/images/help/repository/secret-scanning-push-protection-web-ui-commit-blocked-banner-with-link.png)
 
 {% else %}
 
-  ![Screenshot showing commit in web ui blocked because of secret scanning push protection](/assets/images/help/repository/secret-scanning-push-protection-web-ui-commit-blocked-banner.png)
+  ![屏幕截图显示因机密扫描推送保护而阻止在 Web UI 中提交](/assets/images/help/repository/secret-scanning-push-protection-web-ui-commit-blocked-banner.png)
   
-{% endif %}
\ No newline at end of file
+{% endif %}
diff --git a/translations/zh-CN/data/reusables/security-advisory/security-advisory-overview.md b/translations/zh-CN/data/reusables/security-advisory/security-advisory-overview.md
index 82af4533e3..3c4c6a964f 100644
--- a/translations/zh-CN/data/reusables/security-advisory/security-advisory-overview.md
+++ b/translations/zh-CN/data/reusables/security-advisory/security-advisory-overview.md
@@ -1,9 +1 @@
----
-ms.openlocfilehash: aa9f7cd0b911ddfc6e144c7c91cecd0374286b13
-ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
-ms.translationtype: HT
-ms.contentlocale: zh-CN
-ms.lasthandoff: 09/10/2022
-ms.locfileid: "145129574"
----
-{% data variables.product.prodname_security_advisories %} 允许仓库维护员私下讨论并修复项目中的安全漏洞。 协作得到修补程序后，存储库维护人员可发布安全通知，向项目社区公开安全漏洞。 通过发布安全通知，存储库维护人员可使其社区更轻松地更新包依赖项并对安全漏洞的影响进行调查。
+Repository security advisories allow repository maintainers to privately discuss and fix a security vulnerability in a project. After collaborating on a fix, repository maintainers can publish the security advisory to publicly disclose the security vulnerability to the project's community. By publishing security advisories, repository maintainers make it easier for their community to update package dependencies and research the impact of the security vulnerabilities.
diff --git a/translations/zh-CN/data/reusables/security-overview/information-varies-GHAS.md b/translations/zh-CN/data/reusables/security-overview/information-varies-GHAS.md
index ccc09963d6..7cbb06c250 100644
--- a/translations/zh-CN/data/reusables/security-overview/information-varies-GHAS.md
+++ b/translations/zh-CN/data/reusables/security-overview/information-varies-GHAS.md
@@ -1,10 +1,10 @@
 ---
-ms.openlocfilehash: f6fdffa80f99a405c65fc6f536b8a821cc1c334d
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: 55863906d744c997149aa2fffd6541f32e42c0d1
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: zh-CN
-ms.lasthandoff: 09/05/2022
-ms.locfileid: "147525736"
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148108057"
 ---
 {% ifversion security-overview-displayed-alerts %} 安全概览中显示的信息根据你对存储库的访问以及 {% data variables.product.prodname_GH_advanced_security %} 是否由这些存储库使用而有所不同。
-{% endif %}
\ No newline at end of file
+{% endif %}
diff --git a/translations/zh-CN/data/reusables/security-overview/permissions.md b/translations/zh-CN/data/reusables/security-overview/permissions.md
index 2cf85d19c5..43dd55172d 100644
--- a/translations/zh-CN/data/reusables/security-overview/permissions.md
+++ b/translations/zh-CN/data/reusables/security-overview/permissions.md
@@ -1 +1 @@
-Organization owners and security managers can access the security overview for organizations{% ifversion ghec or ghes > 3.4 or ghae > 3.4 %} and view their organization's repositories via the enterprise-level security overview. Enterprise owners can use the enterprise-level security overview to view all repositories in their enterprise's organizations{% endif %}. Members of a team can see the security overview for repositories that the team has admin privileges for.
+{% ifversion not fpt %}Organization owners and security managers can access the organization-level security overview{% ifversion ghec or ghes > 3.4 or ghae > 3.4 %} and view alerts across multiple organizations via the enterprise-level security overview. Enterprise owners can only view repositories and alerts for organizations where they are added as an organization owner or security manager{% endif %}. {% ifversion ghec or ghes > 3.6 or ghae > 3.6 %}Organization members can access the organization-level security overview to view results for repositories where they have admin privileges or have been granted access to security alerts.{% else %}Members of a team can see the security overview for repositories that the team has admin privileges for.{% endif %}{% endif %}
diff --git a/translations/zh-CN/data/reusables/security/displayed-information.md b/translations/zh-CN/data/reusables/security/displayed-information.md
index 755cd567fb..fa5451eb0e 100644
--- a/translations/zh-CN/data/reusables/security/displayed-information.md
+++ b/translations/zh-CN/data/reusables/security/displayed-information.md
@@ -1,16 +1,8 @@
----
-ms.openlocfilehash: c9e2c1bf2b01805ed973effedd219c3552ac2bf4
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
-ms.translationtype: HT
-ms.contentlocale: zh-CN
-ms.lasthandoff: 09/05/2022
-ms.locfileid: "146455667"
----
-当您为现有仓库启用一个或多个安全和分析功能时，您将在几分钟内看到 {% data variables.product.prodname_dotcom %} 上显示的任何结果：
+When you enable one or more security and analysis features for existing repositories, you will see any results displayed on {% data variables.product.prodname_dotcom %} within minutes:
 
-- 所有现有仓库将具有选定的配置。
-- 如果启用了新存储库的复选框，则新存储库将遵循所选配置。{% ifversion fpt or ghec %}
-- 我们使用权限扫描清单文件以应用相关服务。
-- 如果启用，您将在依赖关系图中看到依赖项信息。
-- 如有启用，{% data variables.product.prodname_dotcom %} 将对易受攻击的依赖项或恶意软件生成 {% data variables.product.prodname_dependabot_alerts %}。{% endif %}{% ifversion fpt or ghec or ghes > 3.2 %}
-- 如果启用，{% data variables.product.prodname_dependabot %} 安全更新将在触发 {% data variables.product.prodname_dependabot_alerts %} 时创建拉取请求以升级易受攻击的依赖项。{% endif %}
+- All the existing repositories will have the selected configuration.
+- New repositories will follow the selected configuration if you've enabled the checkbox for new repositories.{% ifversion fpt or ghec %}
+- We use the permissions to scan for manifest files to apply the relevant services.
+- If enabled, you'll see dependency information in the dependency graph.
+- If enabled, {% data variables.product.prodname_dotcom %} will generate {% data variables.product.prodname_dependabot_alerts %} for vulnerable dependencies or malware.{% endif %}{% ifversion fpt or ghec or ghes %}
+- If enabled, {% data variables.product.prodname_dependabot %} security updates will create pull requests to upgrade vulnerable dependencies when {% data variables.product.prodname_dependabot_alerts %} are triggered.{% endif %}
diff --git a/translations/zh-CN/data/reusables/ssh/key-type-support.md b/translations/zh-CN/data/reusables/ssh/key-type-support.md
index 324873282a..2c2295e0ba 100644
--- a/translations/zh-CN/data/reusables/ssh/key-type-support.md
+++ b/translations/zh-CN/data/reusables/ssh/key-type-support.md
@@ -25,4 +25,4 @@ Your site administrator can adjust the cutoff date for connections using RSA-SHA
 
 {% endnote %}
 
-{% endif %}
\ No newline at end of file
+{% endif %}
diff --git a/translations/zh-CN/data/reusables/support/entitlements-note.md b/translations/zh-CN/data/reusables/support/entitlements-note.md
index 3b69137322..4f16b7d505 100644
--- a/translations/zh-CN/data/reusables/support/entitlements-note.md
+++ b/translations/zh-CN/data/reusables/support/entitlements-note.md
@@ -1,13 +1,13 @@
 ---
-ms.openlocfilehash: 52b42a427d098d34e26dc12b20fce44ef15e7458
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: 35ed9fffb50a66b6867f71bf0e7e579284b9ee5d
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: zh-CN
-ms.lasthandoff: 09/05/2022
-ms.locfileid: "147079584"
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148108198"
 ---
 {% note %}
 
 注意：必须拥有企业支持权利才能查看与组织或企业帐户关联的票证。 有关详细信息，请参阅[管理企业的支持权利](/enterprise-cloud@latest/admin/user-management/managing-users-in-your-enterprise/managing-support-entitlements-for-your-enterprise)。
 
-{% endnote %}  
\ No newline at end of file
+{% endnote %}  
diff --git a/translations/zh-CN/data/reusables/support/navigate-to-my-tickets.md b/translations/zh-CN/data/reusables/support/navigate-to-my-tickets.md
index d048de21c5..392454dc36 100644
--- a/translations/zh-CN/data/reusables/support/navigate-to-my-tickets.md
+++ b/translations/zh-CN/data/reusables/support/navigate-to-my-tickets.md
@@ -1,12 +1,12 @@
 ---
-ms.openlocfilehash: 88b8399eab75b7ac5a3c2f0e12eec2fc0000df2d
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: fb2826ec7adf7edcff710866d08654c7f94ab484
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: zh-CN
-ms.lasthandoff: 09/05/2022
-ms.locfileid: "147079582"
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148108044"
 ---
 1. 导航到 [GitHub 支持门户](https://support.github.com/)。
 1. 在标题中，单击“我的工单”。
 
-   ![在 GitHub 支持门户标题中显示“我的工单”链接的屏幕截图。](/assets/images/help/support/my-tickets-header.png)
\ No newline at end of file
+   ![在 GitHub 支持门户标题中显示“我的工单”链接的屏幕截图。](/assets/images/help/support/my-tickets-header.png)
diff --git a/translations/zh-CN/data/reusables/supported-languages/C.md b/translations/zh-CN/data/reusables/supported-languages/C.md
index 4d8a3ec97d..77a301dce0 100644
--- a/translations/zh-CN/data/reusables/supported-languages/C.md
+++ b/translations/zh-CN/data/reusables/supported-languages/C.md
@@ -1,9 +1 @@
----
-ms.openlocfilehash: 586b13b105c32f8b67218cc277af8916dc2c8783
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
-ms.translationtype: HT
-ms.contentlocale: zh-CN
-ms.lasthandoff: 09/05/2022
-ms.locfileid: "147052198"
----
-| C {% ifversion fpt or ghec %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} | {% octicon "x" aria-label="The X icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif ghes %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} {% ifversion ghes > 3.2 %}| {% octicon "x" aria-label="The X icon" %}{% endif %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif ghae %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% endif %}
+| C {% ifversion fpt or ghec %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} | {% octicon "x" aria-label="The X icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif ghes %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} | {% octicon "x" aria-label="The X icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif ghae %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% endif %}
diff --git a/translations/zh-CN/data/reusables/supported-languages/Cpp.md b/translations/zh-CN/data/reusables/supported-languages/Cpp.md
index 15886f297e..5a255a3ae3 100644
--- a/translations/zh-CN/data/reusables/supported-languages/Cpp.md
+++ b/translations/zh-CN/data/reusables/supported-languages/Cpp.md
@@ -1,9 +1 @@
----
-ms.openlocfilehash: 801a3486a32e80dbb0a85cef76c2c6887babd258
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
-ms.translationtype: HT
-ms.contentlocale: zh-CN
-ms.lasthandoff: 09/05/2022
-ms.locfileid: "147052030"
----
-| C++ {% ifversion fpt or ghec %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} | {% octicon "x" aria-label="The X icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif ghes %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} {% ifversion ghes > 3.2 %}| {% octicon "x" aria-label="The X icon" %}{% endif %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif ghae %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% endif %}
+| C++ {% ifversion fpt or ghec %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} | {% octicon "x" aria-label="The X icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif ghes %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} | {% octicon "x" aria-label="The X icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif ghae %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% endif %}
diff --git a/translations/zh-CN/data/reusables/supported-languages/Cs.md b/translations/zh-CN/data/reusables/supported-languages/Cs.md
index 2758300043..dc5fa3e1e8 100644
--- a/translations/zh-CN/data/reusables/supported-languages/Cs.md
+++ b/translations/zh-CN/data/reusables/supported-languages/Cs.md
@@ -1,9 +1 @@
----
-ms.openlocfilehash: 5e148185ae940f67f4137f209ce451f74faa1a7e
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
-ms.translationtype: HT
-ms.contentlocale: zh-CN
-ms.lasthandoff: 09/05/2022
-ms.locfileid: "147052358"
----
-| C# {% ifversion fpt or ghec %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>`dotnet` CLI | {% octicon "check" aria-label="The check icon" %}<br>`dotnet` CLI | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>`dotnet` CLI |{% elsif ghes %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>`dotnet` CLI  {% ifversion ghes > 3.2 %}| {% octicon "check" aria-label="The check icon" %}<br>`dotnet` CLI{% endif %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>`dotnet` CLI |{% elsif ghae %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>`dotnet` CLI |{% endif %}
+| C# {% ifversion fpt or ghec %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>`dotnet` CLI | {% octicon "check" aria-label="The check icon" %}<br>`dotnet` CLI | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>`dotnet` CLI |{% elsif ghes %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>`dotnet` CLI  | {% octicon "check" aria-label="The check icon" %}<br>`dotnet` CLI | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>`dotnet` CLI |{% elsif ghae %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>`dotnet` CLI |{% endif %}
diff --git a/translations/zh-CN/data/reusables/supported-languages/go.md b/translations/zh-CN/data/reusables/supported-languages/go.md
index 63888149e8..2670d677ba 100644
--- a/translations/zh-CN/data/reusables/supported-languages/go.md
+++ b/translations/zh-CN/data/reusables/supported-languages/go.md
@@ -1,9 +1 @@
----
-ms.openlocfilehash: d811deaf63f404f0ded3952a4411fc519d29547a
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
-ms.translationtype: HT
-ms.contentlocale: zh-CN
-ms.lasthandoff: 09/05/2022
-ms.locfileid: "147066976"
----
-| Go {% ifversion fpt or ghec %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>Go 模块 | {% octicon "check" aria-label="The check icon" %}<br> Go 模块 | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif ghes %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>Go 模块 {% ifversion ghes > 3.2 %}| {% octicon "check" aria-label="The check icon" %}<br>Go 模块{% endif %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif ghes %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif ghae %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% endif %}
+| Go {% ifversion fpt or ghec %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>Go modules | {% octicon "check" aria-label="The check icon" %}<br> Go modules | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif ghes %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>Go modules | {% octicon "check" aria-label="The check icon" %}<br>Go modules | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif ghes %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif ghae %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% endif %}
diff --git a/translations/zh-CN/data/reusables/supported-languages/java.md b/translations/zh-CN/data/reusables/supported-languages/java.md
index 1f53a3e007..6c67764246 100644
--- a/translations/zh-CN/data/reusables/supported-languages/java.md
+++ b/translations/zh-CN/data/reusables/supported-languages/java.md
@@ -1,9 +1,9 @@
 ---
-ms.openlocfilehash: 7429b486c393de2a4c5184914b3528d1f189c2a5
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: 2e8ea634a95d2bca03b70aef430be7e638272605
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: zh-CN
-ms.lasthandoff: 09/05/2022
-ms.locfileid: "147052022"
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148108215"
 ---
-| Java {% ifversion fpt or ghec %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>Maven | {% octicon "check" aria-label="The check icon" %}<br>Maven、Gradle | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>Maven、Gradle |{% elsif ghes %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>Maven {% ifversion ghes > 3.2 %} | {% octicon "check" aria-label="The check icon" %}<br>Maven、Gradle{% endif %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>Maven、Gradle |{% elsif ghae %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>Maven、Gradle |{% endif %}
+| Java {% ifversion fpt or ghec %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>Maven | {% octicon "check" aria-label="The check icon" %}<br>Maven、Gradle | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>Maven、Gradle |{% elsif ghes %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>Maven | {% octicon "check" aria-label="The check icon" %}<br>Maven、Gradle | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>Maven、Gradle |{% elsif ghae %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>Maven、Gradle |{% endif %}
diff --git a/translations/zh-CN/data/reusables/supported-languages/javascript.md b/translations/zh-CN/data/reusables/supported-languages/javascript.md
index 1055dd2aae..a3ac5c8458 100644
--- a/translations/zh-CN/data/reusables/supported-languages/javascript.md
+++ b/translations/zh-CN/data/reusables/supported-languages/javascript.md
@@ -1,9 +1,9 @@
 ---
-ms.openlocfilehash: dbf7349c32cb38d666f89d149831f5254e2afee2
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: 9d072e402eca457ea6ebc803c1c56461d909e11a
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: zh-CN
-ms.lasthandoff: 09/05/2022
-ms.locfileid: "147052158"
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148108046"
 ---
-| JavaScript {% ifversion fpt or ghec %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>npm、Yarn | {% octicon "check" aria-label="The check icon" %}<br>npm | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>npm |{% elsif ghes %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>npm、Yarn {% ifversion ghes > 3.2 %}| {% octicon "check" aria-label="The check icon" %}<br>npm{% endif %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>npm |{% elsif ghae %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>npm |{% endif %}
+| JavaScript {% ifversion fpt or ghec %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>npm、Yarn | {% octicon "check" aria-label="The check icon" %}<br>npm | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>npm |{% elsif ghes %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>npm、Yarn | {% octicon "check" aria-label="The check icon" %}<br>npm | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>npm |{% elsif ghae %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>npm |{% endif %}
diff --git a/translations/zh-CN/data/reusables/supported-languages/php.md b/translations/zh-CN/data/reusables/supported-languages/php.md
index 5281182643..a6cde8219a 100644
--- a/translations/zh-CN/data/reusables/supported-languages/php.md
+++ b/translations/zh-CN/data/reusables/supported-languages/php.md
@@ -1,9 +1 @@
----
-ms.openlocfilehash: eb8ee6547c65b4cea6e6528d2f96132f1936e0d6
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
-ms.translationtype: HT
-ms.contentlocale: zh-CN
-ms.lasthandoff: 09/05/2022
-ms.locfileid: "147052239"
----
-| PHP {% ifversion fpt or ghec %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<sup>1</sup> | {% octicon "check" aria-label="The check icon" %}<br>Composer | {% octicon "check" aria-label="The check icon" %}<br>Composer | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif ghes %}| {% octicon "check" aria-label="The check icon" %}<sup>1</sup> | {% octicon "check" aria-label="The check icon" %}<br>Composer {% ifversion ghes > 3.2 %}| {% octicon "check" aria-label="The check icon" %}<br>Composer{% endif %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif ghae %}| {% octicon "check" aria-label="The check icon" %}<sup>1</sup> | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% endif %}
+| PHP {% ifversion fpt or ghec %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<sup>1</sup> | {% octicon "check" aria-label="The check icon" %}<br>Composer | {% octicon "check" aria-label="The check icon" %}<br>Composer | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif ghes %}| {% octicon "check" aria-label="The check icon" %}<sup>1</sup> | {% octicon "check" aria-label="The check icon" %}<br>Composer | {% octicon "check" aria-label="The check icon" %}<br>Composer | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif ghae %}| {% octicon "check" aria-label="The check icon" %}<sup>1</sup> | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% endif %}
diff --git a/translations/zh-CN/data/reusables/supported-languages/products-table-header.md b/translations/zh-CN/data/reusables/supported-languages/products-table-header.md
index 4a33f38e5c..6147ff8b8b 100644
--- a/translations/zh-CN/data/reusables/supported-languages/products-table-header.md
+++ b/translations/zh-CN/data/reusables/supported-languages/products-table-header.md
@@ -1,9 +1,4 @@
----
-ms.openlocfilehash: 2bbdb89e1c3f02014566e38f43cd482cc54af641
-ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d
-ms.translationtype: HT
-ms.contentlocale: zh-CN
-ms.lasthandoff: 09/12/2022
-ms.locfileid: "147052231"
----
-{% ifversion fpt or ghec %}| [GitHub Copilot](/copilot/overview-of-github-copilot/about-github-copilot#about-github-copilot) | [代码导航](/github/managing-files-in-a-repository/navigating-code-on-github) | [{% data variables.product.prodname_code_scanning_capc %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning) | [依赖项关系图、{% data variables.product.prodname_dependabot_alerts %}、{% data variables.product.prodname_dependabot_security_updates %}](/code-security/supply-chain-security/about-the-dependency-graph#supported-package-ecosystems) | [{% data variables.product.prodname_dependabot_version_updates %}](/code-security/supply-chain-security/about-dependabot-version-updates#supported-repositories-and-ecosystems) | [{% data variables.product.prodname_actions %}](/actions/guides/about-continuous-integration#supported-languages) | [{% data variables.product.prodname_registry %}](/packages/learn-github-packages/introduction-to-github-packages#supported-clients-and-formats) | | :-- | :-: | :-: | :-: | :-: | :-: | :-: | :-: |{% elsif ghes %}| [{% data variables.product.prodname_code_scanning_capc %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning) | [依赖项关系图、{% data variables.product.prodname_dependabot_alerts %}{% ifversion ghes > 3.2 %}、{% data variables.product.prodname_dependabot_security_updates %}{% endif %}](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph#supported-package-ecosystems) {% ifversion ghes > 3.2 %}| [{% data variables.product.prodname_dependabot_version_updates %}](/code-security/supply-chain-security/about-dependabot-version-updates#supported-repositories-and-ecosystems){% endif %} | [{% data variables.product.prodname_actions %}](/actions/guides/about-continuous-integration#supported-languages) | [{% data variables.product.prodname_registry %}](/packages/learn-github-packages/introduction-to-github-packages#supported-clients-and-formats) | | :-- | :-: | :-: {% ifversion ghes > 3.2 %}| :-: {% endif %}| :-: | :-: |{% elsif ghae %}| [{% data variables.product.prodname_code_scanning_capc %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning) | [{% data variables.product.prodname_actions %}](/actions/guides/about-continuous-integration#supported-languages) | [{% data variables.product.prodname_registry %}](/packages/learn-github-packages/introduction-to-github-packages#supported-clients-and-formats) | | :-- | :-: | :-: | :-: |{% endif %}
+{% ifversion fpt or ghec %}| [GitHub Copilot](/copilot/overview-of-github-copilot/about-github-copilot#about-github-copilot) | [Code navigation](/github/managing-files-in-a-repository/navigating-code-on-github) | [{% data variables.product.prodname_code_scanning_capc %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning) | [Dependency graph, {% data variables.product.prodname_dependabot_alerts %}, {% data variables.product.prodname_dependabot_security_updates %}](/code-security/supply-chain-security/about-the-dependency-graph#supported-package-ecosystems) | [{% data variables.product.prodname_dependabot_version_updates %}](/code-security/supply-chain-security/about-dependabot-version-updates#supported-repositories-and-ecosystems) | [{% data variables.product.prodname_actions %}](/actions/guides/about-continuous-integration#supported-languages) | [{% data variables.product.prodname_registry %}](/packages/learn-github-packages/introduction-to-github-packages#supported-clients-and-formats) |
+| :-- | :-: | :-: | :-: | :-: | :-: | :-: | :-: |{% elsif ghes %}| [{% data variables.product.prodname_code_scanning_capc %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning) | [Dependency graph, {% data variables.product.prodname_dependabot_alerts %}, {% data variables.product.prodname_dependabot_security_updates %}](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph#supported-package-ecosystems) {% ifversion ghes %}| [{% data variables.product.prodname_dependabot_version_updates %}](/code-security/supply-chain-security/about-dependabot-version-updates#supported-repositories-and-ecosystems){% endif %} | [{% data variables.product.prodname_actions %}](/actions/guides/about-continuous-integration#supported-languages) | [{% data variables.product.prodname_registry %}](/packages/learn-github-packages/introduction-to-github-packages#supported-clients-and-formats) |
+| :-- | :-: | :-: {% ifversion ghes %}| :-: {% endif %}| :-: | :-: |{% elsif ghae %}| [{% data variables.product.prodname_code_scanning_capc %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning) | [{% data variables.product.prodname_actions %}](/actions/guides/about-continuous-integration#supported-languages) | [{% data variables.product.prodname_registry %}](/packages/learn-github-packages/introduction-to-github-packages#supported-clients-and-formats) |
+| :-- | :-: | :-: | :-: |{% endif %}
diff --git a/translations/zh-CN/data/reusables/supported-languages/python.md b/translations/zh-CN/data/reusables/supported-languages/python.md
index 564d2c1ebb..d8df9a72ba 100644
--- a/translations/zh-CN/data/reusables/supported-languages/python.md
+++ b/translations/zh-CN/data/reusables/supported-languages/python.md
@@ -1,9 +1 @@
----
-ms.openlocfilehash: 0e9bc62ae013232cf0a15ebb3dfd1948b672480e
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
-ms.translationtype: HT
-ms.contentlocale: zh-CN
-ms.lasthandoff: 09/05/2022
-ms.locfileid: "147052334"
----
-| Python {% ifversion fpt or ghec %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} <br>precise| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>pip | {% octicon "check" aria-label="The check icon" %}<br>pip | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif ghes %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>pip {% ifversion ghes > 3.2 %}| {% octicon "check" aria-label="The check icon" %}<br>pip{% endif %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif ghae %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% endif %}
+| Python {% ifversion fpt or ghec %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} <br>precise| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>pip | {% octicon "check" aria-label="The check icon" %}<br>pip | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif ghes %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>pip | {% octicon "check" aria-label="The check icon" %}<br>pip | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif ghae %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% endif %}
diff --git a/translations/zh-CN/data/reusables/supported-languages/ruby.md b/translations/zh-CN/data/reusables/supported-languages/ruby.md
index ef93f6d8ed..e18901c2ca 100644
--- a/translations/zh-CN/data/reusables/supported-languages/ruby.md
+++ b/translations/zh-CN/data/reusables/supported-languages/ruby.md
@@ -1,9 +1,9 @@
 ---
-ms.openlocfilehash: a740daee0bb180392f099956cf9dc26b6b8c83ed
-ms.sourcegitcommit: 80842b4e4c500daa051eff0ccd7cde91c2d4bb36
+ms.openlocfilehash: 7609bd15d8e77a5da778cfb3a4acd21ea7884e46
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: zh-CN
-ms.lasthandoff: 09/11/2022
-ms.locfileid: "147885042"
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148108195"
 ---
-| Ruby {% ifversion fpt or ghec %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>RubyGems | {% octicon "check" aria-label="The check icon" %}<br>RubyGems | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>RubyGems |{% elsif ghes %}| {% octicon "check" aria-label="The check icon" %}<sup>1</sup> | {% octicon "check" aria-label="The check icon" %}<br>RubyGems {% ifversion ghes > 3.2 %}| {% octicon "check" aria-label="The check icon" %}<br>RubyGems{% endif %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>RubyGems |{% elsif ghae %}| {% octicon "check" aria-label="The check icon" %}<sup>1</sup> | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>RubyGems |{% endif %}
+| Ruby {% ifversion fpt or ghec %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>RubyGems | {% octicon "check" aria-label="The check icon" %}<br>RubyGems | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>RubyGems |{% elsif ghes %}| {% octicon "check" aria-label="The check icon" %}<sup>1</sup> | {% octicon "check" aria-label="The check icon" %}<br>RubyGems | {% octicon "check" aria-label="The check icon" %}<br>RubyGems | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>RubyGems |{% elsif ghae %}| {% octicon "check" aria-label="The check icon" %}<sup>1</sup> | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>RubyGems |{% endif %}
diff --git a/translations/zh-CN/data/reusables/supported-languages/scala.md b/translations/zh-CN/data/reusables/supported-languages/scala.md
index d3376b1972..4da351ea79 100644
--- a/translations/zh-CN/data/reusables/supported-languages/scala.md
+++ b/translations/zh-CN/data/reusables/supported-languages/scala.md
@@ -1,9 +1 @@
----
-ms.openlocfilehash: 3e5390b74f8d438fc7f83cd2f9e1e6917d4282f3
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
-ms.translationtype: HT
-ms.contentlocale: zh-CN
-ms.lasthandoff: 09/05/2022
-ms.locfileid: "147052326"
----
-| Scala {% ifversion fpt or ghec %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} | {% octicon "check" aria-label="The check icon" %}<sup>1</sup> | {% octicon "check" aria-label="The check icon" %}<br>Maven | {% octicon "check" aria-label="The check icon" %}<br>Maven、Gradle | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif ghes %}| {% octicon "check" aria-label="The check icon" %}<sup>1</sup> | {% octicon "check" aria-label="The check icon" %}<br>Maven、Gradle {% ifversion ghes > 3.2 %}| {% octicon "check" aria-label="The check icon" %}<br>Maven、Gradle{% endif %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif ghae %}| {% octicon "check" aria-label="The check icon" %}<sup>1</sup> | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% endif %}
+| Scala {% ifversion fpt or ghec %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} | {% octicon "check" aria-label="The check icon" %}<sup>1</sup> | {% octicon "check" aria-label="The check icon" %}<br>Maven | {% octicon "check" aria-label="The check icon" %}<br>Maven, Gradle | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif ghes %}| {% octicon "check" aria-label="The check icon" %}<sup>1</sup> | {% octicon "check" aria-label="The check icon" %}<br>Maven, Gradle | {% octicon "check" aria-label="The check icon" %}<br>Maven, Gradle | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif ghae %}| {% octicon "check" aria-label="The check icon" %}<sup>1</sup> | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% endif %}
diff --git a/translations/zh-CN/data/reusables/supported-languages/typescript.md b/translations/zh-CN/data/reusables/supported-languages/typescript.md
index 833f35beaf..c46dd856ae 100644
--- a/translations/zh-CN/data/reusables/supported-languages/typescript.md
+++ b/translations/zh-CN/data/reusables/supported-languages/typescript.md
@@ -1,9 +1,9 @@
 ---
-ms.openlocfilehash: 728285dc8fbdfcfa3e6a2f047383bcdc7875b8ff
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.openlocfilehash: 6128eeee4e46b139b78ce717ed3723ba0dbba3ba
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
 ms.translationtype: HT
 ms.contentlocale: zh-CN
-ms.lasthandoff: 09/05/2022
-ms.locfileid: "147052094"
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148108164"
 ---
-| TypeScript {% ifversion fpt or ghec %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>npm、Yarn | {% octicon "check" aria-label="The check icon" %}<br>npm | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>npm |{% elsif ghes %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>npm、Yarn {% ifversion ghes > 3.2 %}| {% octicon "check" aria-label="The check icon" %}<br>npm{% endif %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>npm |{% elsif ghae %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>npm |{% endif %}
+| TypeScript {% ifversion fpt or ghec %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>npm、Yarn | {% octicon "check" aria-label="The check icon" %}<br>npm | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>npm |{% elsif ghes %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>npm、Yarn | {% octicon "check" aria-label="The check icon" %}<br>npm | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>npm |{% elsif ghae %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>npm |{% endif %}
diff --git a/translations/zh-CN/data/reusables/webhooks/webhooks-rest-api-links.md b/translations/zh-CN/data/reusables/webhooks/webhooks-rest-api-links.md
index 28cc571377..51191b7a9e 100644
--- a/translations/zh-CN/data/reusables/webhooks/webhooks-rest-api-links.md
+++ b/translations/zh-CN/data/reusables/webhooks/webhooks-rest-api-links.md
@@ -1,13 +1,5 @@
----
-ms.openlocfilehash: 3e175aefd9a243a098b5c35ca6d4068a651d2f61
-ms.sourcegitcommit: 9a7b3a9ccb983af5df2cd94da7fecf7a8237529b
-ms.translationtype: HT
-ms.contentlocale: zh-CN
-ms.lasthandoff: 09/09/2022
-ms.locfileid: "147876015"
----
-利用 Webhook REST API，你可以管理存储库、组织和应用 Webhook。{% ifversion fpt or ghes > 3.2 or ghae or ghec %} 可使用此 API 列出 Webhook 的 Webhook 交付，或获取并重新交付 Webhook 的个别交付，该交付可以集成到外部应用或服务中。{% endif %} 也可以使用 REST API 来更改 Webhook 的配置。 例如，您可以修改有效负载 URL、内容类型、SSL 验证和机密。 有关详细信息，请参阅：
+The webhook REST APIs enable you to manage repository, organization, and app webhooks. You can use this API to list webhook deliveries for a webhook, or get and redeliver an individual delivery for a webhook, which can be integrated into an external app or service. You can also use the REST API to change the configuration of the webhook. For example, you can modify the payload URL, content type, SSL verification, and secret. For more information, see:
 
-- [存储库 Webhook REST API](/rest/reference/webhooks#repository-webhooks)
-- [组织 Webhook REST API](/rest/reference/orgs#webhooks)
-- [{% data variables.product.prodname_github_app %} Webhook REST API](/rest/reference/apps#webhooks)
+- [Repository Webhooks REST API](/rest/reference/webhooks#repository-webhooks)
+- [Organization Webhooks REST API](/rest/reference/orgs#webhooks)
+- [{% data variables.product.prodname_github_app %} Webhooks REST API](/rest/reference/apps#webhooks)
diff --git a/translations/zh-CN/data/variables/product.yml b/translations/zh-CN/data/variables/product.yml
index 16646ba56b..09ba187929 100644
--- a/translations/zh-CN/data/variables/product.yml
+++ b/translations/zh-CN/data/variables/product.yml
@@ -72,7 +72,7 @@ prodname_codeql_cli: 'CodeQL CLI'
 # CodeQL usually bumps its minor version for each minor version of GHES.
 # Update this whenever a new enterprise version of CodeQL is being prepared.
 codeql_cli_ghes_recommended_version: >-
-  {% ifversion ghes < 3.3 %}2.6.3{% elsif ghes < 3.5 or ghae < 3.5 %}2.7.6{% elsif ghes = 3.5 or ghae = 3.5 %}2.8.5{% elsif ghes = 3.6 or ghae = 3.6 %}2.9.4{% elsif ghes = 3.7 or ghae = 3.7 %}2.10.5{% endif %}
+  {% ifversion ghes < 3.5 or ghae < 3.5 %}2.7.6{% elsif ghes = 3.5 or ghae = 3.5 %}2.8.5{% elsif ghes = 3.6 or ghae = 3.6 %}2.9.4{% elsif ghes = 3.7 or ghae = 3.7 %}2.10.5{% endif %}
 
 # Projects v2
 prodname_projects_v2: 'Projects'