diff --git a/.github/actions-scripts/enable-automerge.js b/.github/actions-scripts/enable-automerge.js
index 649a0e5052..cb4f02f782 100644
--- a/.github/actions-scripts/enable-automerge.js
+++ b/.github/actions-scripts/enable-automerge.js
@@ -17,7 +17,7 @@ async function main() {
   const github = getOctokit(token)
   const pull = await github.rest.pulls.get({
     owner: org,
-    repo: repo,
+    repo,
     pull_number: parseInt(prNumber),
   })
 
diff --git a/.github/actions-scripts/fr-add-docs-reviewers-requests.js b/.github/actions-scripts/fr-add-docs-reviewers-requests.js
index 0772189880..4b67312abb 100644
--- a/.github/actions-scripts/fr-add-docs-reviewers-requests.js
+++ b/.github/actions-scripts/fr-add-docs-reviewers-requests.js
@@ -191,16 +191,16 @@ async function run() {
 
     await graphql(updateProjectNextItemMutation, {
       project: projectID,
-      statusID: statusID,
+      statusID,
       statusValueID: readyForReviewID,
-      datePostedID: datePostedID,
-      reviewDueDateID: reviewDueDateID,
-      contributorTypeID: contributorTypeID,
-      contributorType: contributorType,
-      sizeTypeID: sizeTypeID,
+      datePostedID,
+      reviewDueDateID,
+      contributorTypeID,
+      contributorType,
+      sizeTypeID,
       sizeType: '', // Although we aren't populating size, we are passing the variable so that we can use the shared mutation function
-      featureID: featureID,
-      authorID: authorID,
+      featureID,
+      authorID,
       headers: {
         authorization: `token ${process.env.TOKEN}`,
         'GraphQL-Features': 'projects_next_graphql',
diff --git a/.github/actions-scripts/projects.js b/.github/actions-scripts/projects.js
index 249b8e1aef..df36ee1128 100644
--- a/.github/actions-scripts/projects.js
+++ b/.github/actions-scripts/projects.js
@@ -59,7 +59,7 @@ export async function addItemsToProject(items, project) {
   `
 
   const newItems = await graphql(mutation, {
-    project: project,
+    project,
     headers: {
       authorization: `token ${process.env.TOKEN}`,
       'GraphQL-Features': 'projects_next_graphql',
@@ -221,40 +221,40 @@ export function generateUpdateProjectNextItemFieldMutation({
       $authorID: ID!
     ) {
       ${generateMutationToUpdateField({
-        item: item,
+        item,
         fieldID: '$statusID',
         value: '$statusValueID',
       })}
       ${generateMutationToUpdateField({
-        item: item,
+        item,
         fieldID: '$datePostedID',
         value: formatDateForProject(datePosted),
         literal: true,
       })}
       ${generateMutationToUpdateField({
-        item: item,
+        item,
         fieldID: '$reviewDueDateID',
         value: formatDateForProject(dueDate),
         literal: true,
       })}
       ${generateMutationToUpdateField({
-        item: item,
+        item,
         fieldID: '$contributorTypeID',
         value: '$contributorType',
       })}
       ${generateMutationToUpdateField({
-        item: item,
+        item,
         fieldID: '$sizeTypeID',
         value: '$sizeType',
       })}
       ${generateMutationToUpdateField({
-        item: item,
+        item,
         fieldID: '$featureID',
         value: feature,
         literal: true,
       })}
       ${generateMutationToUpdateField({
-        item: item,
+        item,
         fieldID: '$authorID',
         value: author,
         literal: true,
diff --git a/.github/actions-scripts/ready-for-docs-review.js b/.github/actions-scripts/ready-for-docs-review.js
index 5158d3ed95..636bae554f 100644
--- a/.github/actions-scripts/ready-for-docs-review.js
+++ b/.github/actions-scripts/ready-for-docs-review.js
@@ -171,8 +171,8 @@ async function run() {
   const updateProjectNextItemMutation = generateUpdateProjectNextItemFieldMutation({
     item: newItemID,
     author: firstTimeContributor ? 'first time contributor' : process.env.AUTHOR_LOGIN,
-    turnaround: turnaround,
-    feature: feature,
+    turnaround,
+    feature,
   })
 
   // Determine which variable to use for the contributor type
@@ -192,16 +192,16 @@ async function run() {
 
   await graphql(updateProjectNextItemMutation, {
     project: projectID,
-    statusID: statusID,
+    statusID,
     statusValueID: readyForReviewID,
-    datePostedID: datePostedID,
-    reviewDueDateID: reviewDueDateID,
-    contributorTypeID: contributorTypeID,
-    contributorType: contributorType,
-    sizeTypeID: sizeTypeID,
-    sizeType: sizeType,
-    featureID: featureID,
-    authorID: authorID,
+    datePostedID,
+    reviewDueDateID,
+    contributorTypeID,
+    contributorType,
+    sizeTypeID,
+    sizeType,
+    featureID,
+    authorID,
     headers: {
       authorization: `token ${process.env.TOKEN}`,
       'GraphQL-Features': 'projects_next_graphql',
diff --git a/components/Search.tsx b/components/Search.tsx
index 30ccfcd79f..d3fd548846 100644
--- a/components/Search.tsx
+++ b/components/Search.tsx
@@ -2,7 +2,7 @@ import React, { useState, useEffect, useRef, ReactNode, RefObject } from 'react'
 import { useRouter } from 'next/router'
 import useSWR from 'swr'
 import cx from 'classnames'
-import { ActionList, DropdownMenu, Flash, Label, Overlay } from '@primer/react'
+import { ActionList, DropdownMenu, Flash, Label } from '@primer/react'
 import { ItemInput } from '@primer/react/lib/ActionList/List'
 
 import { useTranslation } from 'components/hooks/useTranslation'
@@ -287,8 +287,6 @@ function useDebounce<T>(value: T, delay?: number): [T, (value: T) => void] {
 
 function ShowSearchError({
   error,
-  isHeaderSearch,
-  isMobileSearch,
 }: {
   error: Error
   isHeaderSearch: boolean
@@ -296,10 +294,7 @@ function ShowSearchError({
 }) {
   const { t } = useTranslation('search')
   return (
-    <Flash
-      variant="danger"
-      sx={{ margin: isMobileSearch || isHeaderSearch ? '2rem 2rem 0 2em' : '1rem' }}
-    >
+    <Flash variant="danger" sx={{ margin: '2rem 2rem 0 2em' }}>
       <p>{t('search_error')}</p>
       {process.env.NODE_ENV === 'development' && (
         <p>
@@ -313,12 +308,9 @@ function ShowSearchError({
 }
 
 function ShowSearchResults({
-  anchorRef,
   isHeaderSearch,
-  isMobileSearch,
   isLoading,
   results,
-  closeSearch,
   debug,
   query,
 }: {
@@ -490,49 +482,7 @@ function ShowSearchResults({
         />
       </div>
     )
-    // When there are search results, it doesn't matter if this is overlay or not.
-    return (
-      <div>
-        {!isHeaderSearch && !isMobileSearch ? (
-          <>
-            <Overlay
-              initialFocusRef={anchorRef}
-              returnFocusRef={anchorRef}
-              ignoreClickRefs={[anchorRef]}
-              onEscape={() => closeSearch()}
-              onClickOutside={() => closeSearch()}
-              aria-labelledby="title"
-              sx={
-                isHeaderSearch
-                  ? {
-                      background: 'none',
-                      boxShadow: 'none',
-                      position: 'static',
-                      overflowY: 'auto',
-                      maxHeight: '80vh',
-                      maxWidth: '96%',
-                      margin: '1.5em 2em 0 0.5em',
-                      scrollbarWidth: 'none',
-                    }
-                  : window.innerWidth < 1012
-                  ? {
-                      marginTop: '28rem',
-                      marginLeft: '5rem',
-                    }
-                  : {
-                      marginTop: '15rem',
-                      marginLeft: '5rem',
-                    }
-              }
-            >
-              {ActionListResults}
-            </Overlay>
-          </>
-        ) : (
-          ActionListResults
-        )}
-      </div>
-    )
+    return <div>{ActionListResults}</div>
   }
 
   // We have no results at all, but perhaps we're waiting.
diff --git a/components/article/ArticleGridLayout.tsx b/components/article/ArticleGridLayout.tsx
index 1bd3cdc877..a5352fc0af 100644
--- a/components/article/ArticleGridLayout.tsx
+++ b/components/article/ArticleGridLayout.tsx
@@ -62,9 +62,9 @@ const SidebarContent = styled(Box)`
   @media (min-width: ${themeGet('breakpoints.3')}) {
     position: sticky;
     padding-top: ${themeGet('space.4')};
-    top: 4em;
-    max-height: 75vh;
+    top: 5em;
+    max-height: calc(100vh - 5em);
     overflow-y: auto;
-    padding-bottom: ${themeGet('space.4')};
+    padding-bottom: ${themeGet('space.6')} !important;
   }
 `
diff --git a/components/homepage/HomePageHero.tsx b/components/homepage/HomePageHero.tsx
index 09cfc5b6cb..570268a97c 100644
--- a/components/homepage/HomePageHero.tsx
+++ b/components/homepage/HomePageHero.tsx
@@ -1,32 +1,22 @@
-import { Search } from 'components/Search'
 import { OctocatHeader } from 'components/landing/OctocatHeader'
 import { useTranslation } from 'components/hooks/useTranslation'
 
 export const HomePageHero = () => {
-  const { t } = useTranslation(['search'])
+  const { t } = useTranslation(['header', 'homepage'])
 
   return (
     <section id="landing" className="color-bg-subtle p-6">
-      {/* eslint-disable-next-line jsx-a11y/no-autofocus */}
-      <Search iconSize={24} variant="expanded">
-        {({ SearchInput, SearchResults }) => {
-          return (
-            <div className="container-xl">
-              <div className="gutter gutter-xl-spacious d-lg-flex flex-row-reverse flex-items-center">
-                <div className="col-lg-7">
-                  <OctocatHeader />
-                </div>
-                <div className="col-lg-5">
-                  <h1 className="text-semibold">{t('search:need_help')}</h1>
-                  {SearchInput}
-                </div>
-              </div>
-
-              <div>{SearchResults}</div>
-            </div>
-          )
-        }}
-      </Search>
+      <div className="container-xl">
+        <div className="gutter gutter-xl-spacious d-lg-flex flex-row-reverse flex-items-center">
+          <div className="col-lg-6 col-xl-7 mb-4 mb-lg-0">
+            <OctocatHeader />
+          </div>
+          <div className="col-lg-6 col-xl-5">
+            <h1>{t('github_docs')}</h1>
+            <p className="color-fg-muted f2 mb-0">{t('description')}</p>
+          </div>
+        </div>
+      </div>
     </section>
   )
 }
diff --git a/components/page-header/Header.tsx b/components/page-header/Header.tsx
index 612cca6965..ddbdc2ede7 100644
--- a/components/page-header/Header.tsx
+++ b/components/page-header/Header.tsx
@@ -17,7 +17,7 @@ import styles from './Header.module.scss'
 
 export const Header = () => {
   const router = useRouter()
-  const { isDotComAuthenticated, relativePath, error } = useMainContext()
+  const { isDotComAuthenticated, error } = useMainContext()
   const { currentVersion } = useVersion()
   const { t } = useTranslation(['header', 'homepage'])
   const [isMenuOpen, setIsMenuOpen] = useState(
@@ -93,7 +93,7 @@ export const Header = () => {
             )}
 
             {/* <!-- GitHub.com homepage and 404 page has a stylized search; Enterprise homepages do not --> */}
-            {relativePath !== 'index.md' && error !== '404' && (
+            {error !== '404' && (
               <div className="d-inline-block ml-3">
                 <Search iconSize={16} isHeaderSearch={true} />
               </div>
@@ -158,7 +158,7 @@ export const Header = () => {
               )}
 
               {/* <!-- GitHub.com homepage and 404 page has a stylized search; Enterprise homepages do not --> */}
-              {relativePath !== 'index.md' && error !== '404' && (
+              {error !== '404' && (
                 <div className="my-2 pt-2">
                   <Search iconSize={16} isMobileSearch={true} />
                 </div>
diff --git a/content/actions/using-github-hosted-runners/about-github-hosted-runners.md b/content/actions/using-github-hosted-runners/about-github-hosted-runners.md
index 3363c667b0..658ec2888e 100644
--- a/content/actions/using-github-hosted-runners/about-github-hosted-runners.md
+++ b/content/actions/using-github-hosted-runners/about-github-hosted-runners.md
@@ -80,6 +80,7 @@ For the overall list of included tools for each runner operating system, see the
 * [Ubuntu 18.04 LTS](https://github.com/actions/virtual-environments/blob/main/images/linux/Ubuntu1804-Readme.md)
 * [Windows Server 2022](https://github.com/actions/virtual-environments/blob/main/images/win/Windows2022-Readme.md)
 * [Windows Server 2019](https://github.com/actions/virtual-environments/blob/main/images/win/Windows2019-Readme.md)
+* [macOS 12](https://github.com/actions/virtual-environments/blob/main/images/macos/macos-12-Readme.md)
 * [macOS 11](https://github.com/actions/virtual-environments/blob/main/images/macos/macos-11-Readme.md)
 * [macOS 10.15](https://github.com/actions/virtual-environments/blob/main/images/macos/macos-10.15-Readme.md)
 
diff --git a/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise.md b/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise.md
index 682a728756..3592f2e834 100644
--- a/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise.md
+++ b/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise.md
@@ -19,7 +19,9 @@ topics:
 
 {% ifversion ghec %}
 
-Enterprise owners on {% data variables.product.product_name %} can control the requirements for authentication and access to the enterprise's resources. You can choose to allow members create and manage user accounts, or your enterprise can create and manage accounts for members. If you allow members to manage their own accounts, you can also configure SAML authentication to both increase security and centralize identity and access for the web applications that your team uses. If you choose to manage your members' user accounts, you must configure SAML authentication.
+Enterprise owners on {% data variables.product.product_name %} can control the requirements for authentication and access to the enterprise's resources. 
+
+You can choose to allow members to create and manage user accounts, or your enterprise can create and manage accounts for members with {% data variables.product.prodname_emus %}. If you allow members to manage their own accounts, you can also configure SAML authentication to both increase security and centralize identity and access for the web applications that your team uses. If you choose to manage your members' user accounts, you must configure SAML authentication.
 
 ## Authentication methods for {% data variables.product.product_name %}
 
diff --git a/content/admin/index.md b/content/admin/index.md
index ae2d06af75..7bafef913e 100644
--- a/content/admin/index.md
+++ b/content/admin/index.md
@@ -71,13 +71,13 @@ changelog:
 featuredLinks:
   guides:
     - '{% ifversion ghae %}/admin/user-management/auditing-users-across-your-enterprise{% endif %}'
+    - /admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise
+    - /admin/policies/enforcing-policies-for-your-enterprise/about-enterprise-policies
     - '{% ifversion ghae %}/admin/configuration/restricting-network-traffic-to-your-enterprise{% endif %}'
     - '{% ifversion ghes %}/admin/configuration/configuring-backups-on-your-appliance{% endif %}'
     - '{% ifversion ghes %}/admin/enterprise-management/creating-a-high-availability-replica{% endif %}'
     - '{% ifversion ghes %}/admin/overview/about-upgrades-to-new-releases{% endif %}'
     - '{% ifversion ghec %}/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise{% endif %}'
-    - '{% ifversion ghec %}/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/about-enterprise-managed-users{% endif %}'
-    - '{% ifversion ghec %}/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-identity-and-access-management-for-your-enterprise{% endif %}'
     - '{% ifversion ghec %}/admin/user-management/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise{% endif %}'
     - /admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-self-hosted-runners-for-your-enterprise
   guideCards:
diff --git a/content/admin/overview/about-enterprise-accounts.md b/content/admin/overview/about-enterprise-accounts.md
index 14571af933..6ebe6cb0fe 100644
--- a/content/admin/overview/about-enterprise-accounts.md
+++ b/content/admin/overview/about-enterprise-accounts.md
@@ -32,18 +32,18 @@ The enterprise account on {% ifversion ghes %}{% data variables.product.product_
 
 {% endif %}
 
-Organizations are shared accounts where enterprise members can collaborate across many projects at once. Organization owners can manage access to the organization's data and projects with sophisticated security and administrative features. For more information, see {% ifversion ghec %}"[About organizations](/organizations/collaborating-with-groups-in-organizations/about-organizations)."{% elsif ghes or ghae %}"[About organizations](/organizations/collaborating-with-groups-in-organizations/about-organizations)" and "[Managing users, organizations, and repositories](/admin/user-management)."{% endif %}
+Organizations are shared accounts where enterprise members can collaborate across many projects at once. Organization owners can manage access to the organization's data and projects with sophisticated security and administrative features. For more information, see "[About organizations](/organizations/collaborating-with-groups-in-organizations/about-organizations)."
+
+{% ifversion ghec %} 
+Enterprise owners can invite existing organizations to join your enterprise account, or create new organizations in the enterprise settings.
+{% endif %}
+
+Your enterprise account allows you to manage and enforce policies for all the organizations owned by the enterprise. {% data reusables.enterprise.about-policies %} For more information, see "[About enterprise policies](/admin/policies/enforcing-policies-for-your-enterprise/about-enterprise-policies)."
 
 {% ifversion ghec %}
 
-Enterprise owners can create organizations and link the organizations to the enterprise. Alternatively, you can invite an existing organization to join your enterprise account. After you add organizations to your enterprise account, you can manage and enforce policies for the organizations. Specific enforcement options vary by setting; generally, you can choose to enforce a single policy for every organization in your enterprise account or allow owners to set policy on the organization level. For more information, see "[Setting policies for your enterprise](/admin/policies)."
-
 {% data reusables.enterprise.create-an-enterprise-account %} For more information, see "[Creating an enterprise account](/admin/overview/creating-an-enterprise-account)."
 
-{% elsif ghes or ghae %}
-
-For more information about the management of policies for your enterprise account, see "[Setting policies for your enterprise](/admin/policies)."
-
 {% endif %}
 
 ## About administration of your enterprise account
diff --git a/content/admin/overview/creating-an-enterprise-account.md b/content/admin/overview/creating-an-enterprise-account.md
index 635ac8a067..c5c9fa711c 100644
--- a/content/admin/overview/creating-an-enterprise-account.md
+++ b/content/admin/overview/creating-an-enterprise-account.md
@@ -16,7 +16,7 @@ shortTitle: Create enterprise account
 
 {% data variables.product.prodname_ghe_cloud %} includes the option to create an enterprise account, which enables collaboration between multiple organizations and gives administrators a single point of visibility and management. For more information, see "[About enterprise accounts](/admin/overview/about-enterprise-accounts)."
 
-{% data reusables.enterprise.create-an-enterprise-account %} If you pay by invoice, you can create an enterprise account yourself on {% data variables.product.prodname_dotcom %}. If not, you can [contact our sales team](https://github.com/enterprise/contact?ref_page=/pricing&ref_cta=Contact%20Sales&ref_loc=cards) to move to invoicing.
+{% data reusables.enterprise.create-an-enterprise-account %} If you pay by invoice, you can create an enterprise account yourself on {% data variables.product.prodname_dotcom %}. If not, you can [contact our sales team](https://github.com/enterprise/contact?ref_page=/pricing&ref_cta=Contact%20Sales&ref_loc=cards) to create an enterprise account for you.
 
 An enterprise account is included in {% data variables.product.prodname_ghe_cloud %}, so creating one will not affect your bill.
 
@@ -29,7 +29,10 @@ If the organization is connected to {% data variables.product.prodname_ghe_serve
 
 ## Creating an enterprise account on {% data variables.product.prodname_dotcom %}
 
-To create an enterprise account on {% data variables.product.prodname_dotcom %}, your organization must be using {% data variables.product.prodname_ghe_cloud %} and paying by invoice.
+To create an enterprise account, your organization must be using {% data variables.product.prodname_ghe_cloud %}.
+
+If you pay by invoice, you can create an enterprise account directly through {% data variables.product.prodname_dotcom %}. If you do not currently pay by invoice, you can [contact our sales team](https://github.com/enterprise/contact?ref_page=/pricing&ref_cta=Contact%20Sales&ref_loc=cards) to create an enterprise account for you.
+
 
 {% data reusables.organizations.billing-settings %}
 1. Click **Upgrade to enterprise account**.
diff --git a/content/admin/policies/enforcing-policies-for-your-enterprise/about-enterprise-policies.md b/content/admin/policies/enforcing-policies-for-your-enterprise/about-enterprise-policies.md
new file mode 100644
index 0000000000..d22d2adc46
--- /dev/null
+++ b/content/admin/policies/enforcing-policies-for-your-enterprise/about-enterprise-policies.md
@@ -0,0 +1,30 @@
+---
+title: About enterprise policies
+intro: 'With enterprise policies, you can manage the policies for all the organizations owned by your enterprise.'
+versions:
+  ghec: '*'
+  ghes: '*'
+  ghae: '*'
+type: overview
+topics:
+  - Enterprise
+  - Policies
+---
+
+To help you enforce business rules and regulatory compliance, policies provide a single point of management for all the organizations owned by an enterprise account. 
+
+{% data reusables.enterprise.about-policies %}
+
+For example, with the "Base permissions" policy, you can allow organization owners to configure the "Base permissions" policy for their organization, or you can enforce a specific base permissions level, such as "Read", for all organizations within the enterprise.
+
+By default, no enterprise policies are enforced. To identify policies that should be enforced to meet the unique requirements of your business, we recommend reviewing all the available policies in your enterprise account, starting with repository management policies. For more information, see "[Enforcing repository management polices in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise)."
+
+While you're configuring enterprise policies, to help you understand the impact of changing each policy, you can view the current configurations for the organizations owned by your enterprise.
+
+{% ifversion ghes %}
+Another way to enforce standards within your enterprise is to use pre-receive hooks, which are scripts that run on {% data variables.product.product_location %} to implement quality checks. For more information, see "[Enforcing policy with pre-receive hooks](/admin/policies/enforcing-policy-with-pre-receive-hooks)."
+{% endif %}
+
+## Further reading
+
+- "[About enterprise accounts](/admin/overview/about-enterprise-accounts)"
\ No newline at end of file
diff --git a/content/admin/policies/enforcing-policies-for-your-enterprise/index.md b/content/admin/policies/enforcing-policies-for-your-enterprise/index.md
index e2bbdac69b..ac630a1b8e 100644
--- a/content/admin/policies/enforcing-policies-for-your-enterprise/index.md
+++ b/content/admin/policies/enforcing-policies-for-your-enterprise/index.md
@@ -13,6 +13,7 @@ topics:
   - Enterprise
   - Policies
 children:
+  - /about-enterprise-policies
   - /enforcing-repository-management-policies-in-your-enterprise
   - /enforcing-team-policies-in-your-enterprise
   - /enforcing-project-board-policies-in-your-enterprise
diff --git a/content/billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise.md b/content/billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise.md
index df96487115..ef0ea220af 100644
--- a/content/billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise.md
+++ b/content/billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise.md
@@ -53,7 +53,7 @@ Each user on {% data variables.product.product_location %} consumes a seat on yo
 
 {% endif %}
 
-{% data reusables.billing.about-invoices-for-enterprises %} For more information about {% ifversion ghes %}licensing, usage, and invoices{% elsif ghec %}usage and invoices{% endif %}, see the following{% ifversion ghes %} in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}.{% endif %}
+{% ifversion ghec %}For {% data variables.product.prodname_ghe_cloud %} customers with an enterprise account, {% data variables.product.company_short %} bills through your enterprise account on {% data variables.product.prodname_dotcom_the_website %}. For invoiced customers, each{% elsif ghes %}For invoiced {% data variables.product.prodname_enterprise %} customers, {% data variables.product.company_short %} bills through an enterprise account on {% data variables.product.prodname_dotcom_the_website %}. Each{% endif %} invoice includes a single bill charge for all of your paid {% data variables.product.prodname_dotcom_the_website %} services and any {% data variables.product.prodname_ghe_server %} instances. For more information about {% ifversion ghes %}licensing, usage, and invoices{% elsif ghec %}usage and invoices{% endif %}, see the following{% ifversion ghes %} in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}.{% endif %}
 
 {%- ifversion ghes %}
 - "[About per-user pricing](/enterprise-cloud@latest/billing/managing-billing-for-your-github-account/about-per-user-pricing)"
diff --git a/content/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account.md b/content/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account.md
index aa3e5d243c..e9eea5a2f7 100644
--- a/content/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account.md
+++ b/content/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account.md
@@ -17,7 +17,7 @@ shortTitle: View subscription & usage
 
 ## About billing for enterprise accounts
 
-You can view an overview of {% ifversion ghec %}your subscription and paid{% elsif ghes %}the license{% endif %} usage for {% ifversion ghec %}your{% elsif ghes %}the{% endif %} enterprise account on {% ifversion ghec %}{% data variables.product.prodname_dotcom_the_website %}{% elsif ghes %}{% data variables.product.product_location %}{% endif %}.
+You can view an overview of {% ifversion ghec %}your subscription and paid{% elsif ghes %}the license{% endif %} usage for {% ifversion ghec %}your{% elsif ghes %}the{% endif %} enterprise account on {% ifversion ghec %}{% data variables.product.prodname_dotcom_the_website %}{% elsif ghes %}{% data variables.product.product_location %}{% endif %}.{% ifversion ghec %} {% data reusables.enterprise.create-an-enterprise-account %} For more information, see "[Creating an enterprise account](/enterprise-cloud@latest/admin/overview/creating-an-enterprise-account)."{% endif %}
 
 For invoiced {% data variables.product.prodname_enterprise %} customers{% ifversion ghes %} who use both {% data variables.product.prodname_ghe_cloud %} and {% data variables.product.prodname_ghe_server %}{% endif %}, each invoice includes details about billed services for all products. For example, in addition to your usage for {% ifversion ghec %}{% data variables.product.prodname_ghe_cloud %}{% elsif ghes %}{% data variables.product.product_name %}{% endif %}, you may have usage for {% data variables.product.prodname_GH_advanced_security %}{% ifversion ghec %}, {% elsif ghes %}. You may also have usage on {% data variables.product.prodname_dotcom_the_website %}, like {% endif %}paid licenses in organizations outside of your enterprise account, data packs for {% data variables.large_files.product_name_long %}, or subscriptions to apps in {% data variables.product.prodname_marketplace %}. For more information about invoices, see "[Managing invoices for your enterprise]({% ifversion ghes %}/enterprise-cloud@latest{% endif %}/billing/managing-billing-for-your-github-account/managing-invoices-for-your-enterprise){% ifversion ghec %}."{% elsif ghes %}" in the {% data variables.product.prodname_dotcom_the_website %} documentation.{% endif %}
 
diff --git a/content/developers/webhooks-and-events/webhooks/webhook-events-and-payloads.md b/content/developers/webhooks-and-events/webhooks/webhook-events-and-payloads.md
index 517f94bf5d..2580027b6f 100644
--- a/content/developers/webhooks-and-events/webhooks/webhook-events-and-payloads.md
+++ b/content/developers/webhooks-and-events/webhooks/webhook-events-and-payloads.md
@@ -1481,6 +1481,17 @@ This event occurs when someone triggers a workflow run on GitHub or sends a `POS
 
 - {% data variables.product.prodname_github_apps %} must have the `contents` permission to receive this webhook.
 
+### Webhook payload object
+
+| Key | Type | Description |
+|-----|-----|-----|
+| `inputs` | `object` | Inputs to the workflow. Each key represents the name of the input while it's value represents the value of that input. |
+{% data reusables.webhooks.org_desc %}
+| `ref` | `string` | The branch ref from which the workflow was run. |
+{% data reusables.webhooks.repo_desc %}
+{% data reusables.webhooks.sender_desc %}
+| `workflow` | `string` | Relative path to the workflow file which contains the workflow. |
+
 ### Webhook payload example
 
 {{ webhookPayloadsForCurrentVersion.workflow_dispatch }}
diff --git a/content/get-started/onboarding/getting-started-with-github-enterprise-cloud.md b/content/get-started/onboarding/getting-started-with-github-enterprise-cloud.md
index 109eb89028..7935a24b28 100644
--- a/content/get-started/onboarding/getting-started-with-github-enterprise-cloud.md
+++ b/content/get-started/onboarding/getting-started-with-github-enterprise-cloud.md
@@ -56,21 +56,23 @@ Your organization's billing settings page allows you to manage settings like you
 Only organization members with the *owner* or *billing manager* role can access or change billing settings for your organization. A billing manager is a user who manages the billing settings for your organization and does not use a paid license in your organization's subscription. For more information on adding a billing manager to your organization, see "[Adding a billing manager to your organization](/organizations/managing-peoples-access-to-your-organization-with-roles/adding-a-billing-manager-to-your-organization)."
 
 ### Setting up an enterprise account with {% data variables.product.prodname_ghe_cloud %}
- {% note %}
-
-To get an enterprise account created for you, contact [{% data variables.product.prodname_dotcom %}'s Sales team](https://enterprise.github.com/contact).
-
- {% endnote %}
 
 #### 1. About enterprise accounts
 
 An enterprise account allows you to centrally manage policy and settings for multiple {% data variables.product.prodname_dotcom %} organizations, including member access, billing and usage and security. For more information, see "[About enterprise accounts](/enterprise-cloud@latest/admin/overview/about-enterprise-accounts)."
-#### 2. Adding organizations to your enterprise account
+
+#### 2. Creating an enterpise account
+
+ {% data variables.product.prodname_ghe_cloud %} customers paying by invoice can create an enterprise account directly through {% data variables.product.prodname_dotcom %}. For more information, see "[Creating an enterprise account](/enterprise-cloud@latest/admin/overview/creating-an-enterprise-account)." 
+ 
+ {% data variables.product.prodname_ghe_cloud %} customers not currently paying by invoice can contact [{% data variables.product.prodname_dotcom %}'s Sales team](https://enterprise.github.com/contact) to create an enterprise account for you.
+
+#### 3. Adding organizations to your enterprise account
 
 You can create new organizations to manage within your enterprise account. For more information, see "[Adding organizations to your enterprise](/enterprise-cloud@latest/admin/user-management/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise)."
 
 Contact your {% data variables.product.prodname_dotcom %} sales account representative if you want to transfer an existing organization to your enterprise account.
-#### 3. Viewing the subscription and usage for your enterprise account
+#### 4. Viewing the subscription and usage for your enterprise account
 You can view your current subscription, license usage, invoices, payment history, and other billing information for your enterprise account at any time. Both enterprise owners and billing managers can access and manage billing settings for enterprise accounts. For more information, see  "[Viewing the subscription and usage for your enterprise account](/enterprise-cloud@latest/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account)."
 
 ## Part 3: Managing your organization or enterprise members and teams with {% data variables.product.prodname_ghe_cloud %}
diff --git a/data/learning-tracks/admin.yml b/data/learning-tracks/admin.yml
index 6ef7226986..a7aa266e92 100644
--- a/data/learning-tracks/admin.yml
+++ b/data/learning-tracks/admin.yml
@@ -135,5 +135,4 @@ get_started_with_your_enterprise_account:
     - /admin/user-management/managing-users-in-your-enterprise/inviting-people-to-manage-your-enterprise
     - /admin/user-management/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise
     - /admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise
-    - /admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise
-    - /admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise
+    - /admin/policies/enforcing-policies-for-your-enterprise/about-enterprise-policies
diff --git a/data/reusables/enterprise/about-policies.md b/data/reusables/enterprise/about-policies.md
new file mode 100644
index 0000000000..7fd5303231
--- /dev/null
+++ b/data/reusables/enterprise/about-policies.md
@@ -0,0 +1 @@
+Each enterprise policy controls the options available for a policy at the organization level. You can choose to not enforce a policy, which allows organization owners to configure the policy for the organization, or you can choose from a set of options to enforce for all organizations owned by your enterprise.
\ No newline at end of file
diff --git a/data/ui.yml b/data/ui.yml
index cb45a12953..5e7f0fd306 100644
--- a/data/ui.yml
+++ b/data/ui.yml
@@ -46,6 +46,7 @@ search:
 homepage:
   explore_by_product: Explore by product
   version_picker: Version
+  description: Help for wherever you are on your GitHub journey.
 toc:
   getting_started: Getting started
   popular: Popular
diff --git a/lib/rest/static/decorated/api.github.com.json b/lib/rest/static/decorated/api.github.com.json
index 2309e3ff6a..433604f23a 100644
--- a/lib/rest/static/decorated/api.github.com.json
+++ b/lib/rest/static/decorated/api.github.com.json
@@ -104254,11 +104254,11 @@
           },
           {
             "type": "boolean",
-            "description": "<p>Blocks creation of new branches which match the branch protection pattern. Set to <code>true</code> to prohibit new branch creation. Default: <code>false</code>.</p>",
+            "description": "<p>If set to <code>true</code>, the <code>restrictions</code> branch protection settings which limits who can push will also block pushes which create new branches, unless the push is initiated by a user, team, or app which has the ability to push. Set to <code>true</code> to restrict new branch creation. Default: <code>false</code>.</p>",
             "name": "block_creations",
             "in": "body",
             "rawType": "boolean",
-            "rawDescription": "Blocks creation of new branches which match the branch protection pattern. Set to `true` to prohibit new branch creation. Default: `false`.",
+            "rawDescription": "If set to `true`, the `restrictions` branch protection settings which limits who can push will also block pushes which create new branches, unless the push is initiated by a user, team, or app which has the ability to push. Set to `true` to restrict new branch creation. Default: `false`.",
             "isRequired": false,
             "childParamsGroups": []
           },
diff --git a/lib/rest/static/decorated/ghes-3.1.json b/lib/rest/static/decorated/ghes-3.1.json
index 948cb26b29..45db3a30ab 100644
--- a/lib/rest/static/decorated/ghes-3.1.json
+++ b/lib/rest/static/decorated/ghes-3.1.json
@@ -85840,11 +85840,11 @@
           },
           {
             "type": "boolean",
-            "description": "<p>Blocks creation of new branches which match the branch protection pattern. Set to <code>true</code> to prohibit new branch creation. Default: <code>false</code>.</p>",
+            "description": "<p>If set to <code>true</code>, the <code>restrictions</code> branch protection settings which limits who can push will also block pushes which create new branches, unless the push is initiated by a user, team, or app which has the ability to push. Set to <code>true</code> to restrict new branch creation. Default: <code>false</code>.</p>",
             "name": "block_creations",
             "in": "body",
             "rawType": "boolean",
-            "rawDescription": "Blocks creation of new branches which match the branch protection pattern. Set to `true` to prohibit new branch creation. Default: `false`.",
+            "rawDescription": "If set to `true`, the `restrictions` branch protection settings which limits who can push will also block pushes which create new branches, unless the push is initiated by a user, team, or app which has the ability to push. Set to `true` to restrict new branch creation. Default: `false`.",
             "isRequired": false,
             "childParamsGroups": []
           },
diff --git a/lib/rest/static/decorated/ghes-3.2.json b/lib/rest/static/decorated/ghes-3.2.json
index 134c682976..58bcf3d094 100644
--- a/lib/rest/static/decorated/ghes-3.2.json
+++ b/lib/rest/static/decorated/ghes-3.2.json
@@ -88984,11 +88984,11 @@
           },
           {
             "type": "boolean",
-            "description": "<p>Blocks creation of new branches which match the branch protection pattern. Set to <code>true</code> to prohibit new branch creation. Default: <code>false</code>.</p>",
+            "description": "<p>If set to <code>true</code>, the <code>restrictions</code> branch protection settings which limits who can push will also block pushes which create new branches, unless the push is initiated by a user, team, or app which has the ability to push. Set to <code>true</code> to restrict new branch creation. Default: <code>false</code>.</p>",
             "name": "block_creations",
             "in": "body",
             "rawType": "boolean",
-            "rawDescription": "Blocks creation of new branches which match the branch protection pattern. Set to `true` to prohibit new branch creation. Default: `false`.",
+            "rawDescription": "If set to `true`, the `restrictions` branch protection settings which limits who can push will also block pushes which create new branches, unless the push is initiated by a user, team, or app which has the ability to push. Set to `true` to restrict new branch creation. Default: `false`.",
             "isRequired": false,
             "childParamsGroups": []
           },
diff --git a/lib/rest/static/decorated/ghes-3.3.json b/lib/rest/static/decorated/ghes-3.3.json
index 0491377ea2..caef9ab60b 100644
--- a/lib/rest/static/decorated/ghes-3.3.json
+++ b/lib/rest/static/decorated/ghes-3.3.json
@@ -89220,11 +89220,11 @@
           },
           {
             "type": "boolean",
-            "description": "<p>Blocks creation of new branches which match the branch protection pattern. Set to <code>true</code> to prohibit new branch creation. Default: <code>false</code>.</p>",
+            "description": "<p>If set to <code>true</code>, the <code>restrictions</code> branch protection settings which limits who can push will also block pushes which create new branches, unless the push is initiated by a user, team, or app which has the ability to push. Set to <code>true</code> to restrict new branch creation. Default: <code>false</code>.</p>",
             "name": "block_creations",
             "in": "body",
             "rawType": "boolean",
-            "rawDescription": "Blocks creation of new branches which match the branch protection pattern. Set to `true` to prohibit new branch creation. Default: `false`.",
+            "rawDescription": "If set to `true`, the `restrictions` branch protection settings which limits who can push will also block pushes which create new branches, unless the push is initiated by a user, team, or app which has the ability to push. Set to `true` to restrict new branch creation. Default: `false`.",
             "isRequired": false,
             "childParamsGroups": []
           },
diff --git a/lib/rest/static/decorated/ghes-3.4.json b/lib/rest/static/decorated/ghes-3.4.json
index 74e0a24f55..2adff1952b 100644
--- a/lib/rest/static/decorated/ghes-3.4.json
+++ b/lib/rest/static/decorated/ghes-3.4.json
@@ -91763,11 +91763,11 @@
           },
           {
             "type": "boolean",
-            "description": "<p>Blocks creation of new branches which match the branch protection pattern. Set to <code>true</code> to prohibit new branch creation. Default: <code>false</code>.</p>",
+            "description": "<p>If set to <code>true</code>, the <code>restrictions</code> branch protection settings which limits who can push will also block pushes which create new branches, unless the push is initiated by a user, team, or app which has the ability to push. Set to <code>true</code> to restrict new branch creation. Default: <code>false</code>.</p>",
             "name": "block_creations",
             "in": "body",
             "rawType": "boolean",
-            "rawDescription": "Blocks creation of new branches which match the branch protection pattern. Set to `true` to prohibit new branch creation. Default: `false`.",
+            "rawDescription": "If set to `true`, the `restrictions` branch protection settings which limits who can push will also block pushes which create new branches, unless the push is initiated by a user, team, or app which has the ability to push. Set to `true` to restrict new branch creation. Default: `false`.",
             "isRequired": false,
             "childParamsGroups": []
           },
diff --git a/lib/rest/static/decorated/ghes-3.5.json b/lib/rest/static/decorated/ghes-3.5.json
index 78cf50d2bf..186ac7699c 100644
--- a/lib/rest/static/decorated/ghes-3.5.json
+++ b/lib/rest/static/decorated/ghes-3.5.json
@@ -100239,11 +100239,11 @@
           },
           {
             "type": "boolean",
-            "description": "<p>Blocks creation of new branches which match the branch protection pattern. Set to <code>true</code> to prohibit new branch creation. Default: <code>false</code>.</p>",
+            "description": "<p>If set to <code>true</code>, the <code>restrictions</code> branch protection settings which limits who can push will also block pushes which create new branches, unless the push is initiated by a user, team, or app which has the ability to push. Set to <code>true</code> to restrict new branch creation. Default: <code>false</code>.</p>",
             "name": "block_creations",
             "in": "body",
             "rawType": "boolean",
-            "rawDescription": "Blocks creation of new branches which match the branch protection pattern. Set to `true` to prohibit new branch creation. Default: `false`.",
+            "rawDescription": "If set to `true`, the `restrictions` branch protection settings which limits who can push will also block pushes which create new branches, unless the push is initiated by a user, team, or app which has the ability to push. Set to `true` to restrict new branch creation. Default: `false`.",
             "isRequired": false,
             "childParamsGroups": []
           },
diff --git a/lib/rest/static/decorated/github.ae.json b/lib/rest/static/decorated/github.ae.json
index d9e5388b2a..c9060b33d9 100644
--- a/lib/rest/static/decorated/github.ae.json
+++ b/lib/rest/static/decorated/github.ae.json
@@ -87153,11 +87153,11 @@
           },
           {
             "type": "boolean",
-            "description": "<p>Blocks creation of new branches which match the branch protection pattern. Set to <code>true</code> to prohibit new branch creation. Default: <code>false</code>.</p>",
+            "description": "<p>If set to <code>true</code>, the <code>restrictions</code> branch protection settings which limits who can push will also block pushes which create new branches, unless the push is initiated by a user, team, or app which has the ability to push. Set to <code>true</code> to restrict new branch creation. Default: <code>false</code>.</p>",
             "name": "block_creations",
             "in": "body",
             "rawType": "boolean",
-            "rawDescription": "Blocks creation of new branches which match the branch protection pattern. Set to `true` to prohibit new branch creation. Default: `false`.",
+            "rawDescription": "If set to `true`, the `restrictions` branch protection settings which limits who can push will also block pushes which create new branches, unless the push is initiated by a user, team, or app which has the ability to push. Set to `true` to restrict new branch creation. Default: `false`.",
             "isRequired": false,
             "childParamsGroups": []
           },
diff --git a/lib/rest/static/dereferenced/api.github.com.deref.json b/lib/rest/static/dereferenced/api.github.com.deref.json
index d7ce54191f..f5e8226be8 100644
--- a/lib/rest/static/dereferenced/api.github.com.deref.json
+++ b/lib/rest/static/dereferenced/api.github.com.deref.json
@@ -201706,7 +201706,7 @@
                   },
                   "block_creations": {
                     "type": "boolean",
-                    "description": "Blocks creation of new branches which match the branch protection pattern. Set to `true` to prohibit new branch creation. Default: `false`."
+                    "description": "If set to `true`, the `restrictions` branch protection settings which limits who can push will also block pushes which create new branches, unless the push is initiated by a user, team, or app which has the ability to push. Set to `true` to restrict new branch creation. Default: `false`."
                   },
                   "required_conversation_resolution": {
                     "type": "boolean",
diff --git a/lib/rest/static/dereferenced/ghes-3.1.deref.json b/lib/rest/static/dereferenced/ghes-3.1.deref.json
index 6aba6f605f..db32278b00 100644
--- a/lib/rest/static/dereferenced/ghes-3.1.deref.json
+++ b/lib/rest/static/dereferenced/ghes-3.1.deref.json
@@ -157898,7 +157898,7 @@
                   },
                   "block_creations": {
                     "type": "boolean",
-                    "description": "Blocks creation of new branches which match the branch protection pattern. Set to `true` to prohibit new branch creation. Default: `false`."
+                    "description": "If set to `true`, the `restrictions` branch protection settings which limits who can push will also block pushes which create new branches, unless the push is initiated by a user, team, or app which has the ability to push. Set to `true` to restrict new branch creation. Default: `false`."
                   },
                   "required_conversation_resolution": {
                     "type": "boolean",
diff --git a/lib/rest/static/dereferenced/ghes-3.2.deref.json b/lib/rest/static/dereferenced/ghes-3.2.deref.json
index b3ee944c2c..4ae63ea101 100644
--- a/lib/rest/static/dereferenced/ghes-3.2.deref.json
+++ b/lib/rest/static/dereferenced/ghes-3.2.deref.json
@@ -162237,7 +162237,7 @@
                   },
                   "block_creations": {
                     "type": "boolean",
-                    "description": "Blocks creation of new branches which match the branch protection pattern. Set to `true` to prohibit new branch creation. Default: `false`."
+                    "description": "If set to `true`, the `restrictions` branch protection settings which limits who can push will also block pushes which create new branches, unless the push is initiated by a user, team, or app which has the ability to push. Set to `true` to restrict new branch creation. Default: `false`."
                   },
                   "required_conversation_resolution": {
                     "type": "boolean",
diff --git a/lib/rest/static/dereferenced/ghes-3.3.deref.json b/lib/rest/static/dereferenced/ghes-3.3.deref.json
index 61850519f2..c7d479cdea 100644
--- a/lib/rest/static/dereferenced/ghes-3.3.deref.json
+++ b/lib/rest/static/dereferenced/ghes-3.3.deref.json
@@ -165701,7 +165701,7 @@
                   },
                   "block_creations": {
                     "type": "boolean",
-                    "description": "Blocks creation of new branches which match the branch protection pattern. Set to `true` to prohibit new branch creation. Default: `false`."
+                    "description": "If set to `true`, the `restrictions` branch protection settings which limits who can push will also block pushes which create new branches, unless the push is initiated by a user, team, or app which has the ability to push. Set to `true` to restrict new branch creation. Default: `false`."
                   },
                   "required_conversation_resolution": {
                     "type": "boolean",
diff --git a/lib/rest/static/dereferenced/ghes-3.4.deref.json b/lib/rest/static/dereferenced/ghes-3.4.deref.json
index 678162b258..6d161983da 100644
--- a/lib/rest/static/dereferenced/ghes-3.4.deref.json
+++ b/lib/rest/static/dereferenced/ghes-3.4.deref.json
@@ -180862,7 +180862,7 @@
                   },
                   "block_creations": {
                     "type": "boolean",
-                    "description": "Blocks creation of new branches which match the branch protection pattern. Set to `true` to prohibit new branch creation. Default: `false`."
+                    "description": "If set to `true`, the `restrictions` branch protection settings which limits who can push will also block pushes which create new branches, unless the push is initiated by a user, team, or app which has the ability to push. Set to `true` to restrict new branch creation. Default: `false`."
                   },
                   "required_conversation_resolution": {
                     "type": "boolean",
diff --git a/lib/rest/static/dereferenced/ghes-3.5.deref.json b/lib/rest/static/dereferenced/ghes-3.5.deref.json
index 54e4fba48a..d4c4459ee7 100644
--- a/lib/rest/static/dereferenced/ghes-3.5.deref.json
+++ b/lib/rest/static/dereferenced/ghes-3.5.deref.json
@@ -192621,7 +192621,7 @@
                   },
                   "block_creations": {
                     "type": "boolean",
-                    "description": "Blocks creation of new branches which match the branch protection pattern. Set to `true` to prohibit new branch creation. Default: `false`."
+                    "description": "If set to `true`, the `restrictions` branch protection settings which limits who can push will also block pushes which create new branches, unless the push is initiated by a user, team, or app which has the ability to push. Set to `true` to restrict new branch creation. Default: `false`."
                   },
                   "required_conversation_resolution": {
                     "type": "boolean",
diff --git a/lib/rest/static/dereferenced/github.ae.deref.json b/lib/rest/static/dereferenced/github.ae.deref.json
index d077c89a40..bc814aff06 100644
--- a/lib/rest/static/dereferenced/github.ae.deref.json
+++ b/lib/rest/static/dereferenced/github.ae.deref.json
@@ -148761,7 +148761,7 @@
                   },
                   "block_creations": {
                     "type": "boolean",
-                    "description": "Blocks creation of new branches which match the branch protection pattern. Set to `true` to prohibit new branch creation. Default: `false`."
+                    "description": "If set to `true`, the `restrictions` branch protection settings which limits who can push will also block pushes which create new branches, unless the push is initiated by a user, team, or app which has the ability to push. Set to `true` to restrict new branch creation. Default: `false`."
                   },
                   "required_conversation_resolution": {
                     "type": "boolean",
diff --git a/lib/search/indexes/github-docs-3.1-cn-records.json.br b/lib/search/indexes/github-docs-3.1-cn-records.json.br
index 4658288b18..30497b65d8 100644
--- a/lib/search/indexes/github-docs-3.1-cn-records.json.br
+++ b/lib/search/indexes/github-docs-3.1-cn-records.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:a66208ba1fa2ea8a715bc333b7e1952a83d7d384a8bc8ce9b3a94c2094b12740
-size 686425
+oid sha256:45eec45e549fa04df760c2d133744cb6696f0733e6feeb8b2faa6e1cc3fbd0a1
+size 686308
diff --git a/lib/search/indexes/github-docs-3.1-cn.json.br b/lib/search/indexes/github-docs-3.1-cn.json.br
index 195b7ed029..0653416271 100644
--- a/lib/search/indexes/github-docs-3.1-cn.json.br
+++ b/lib/search/indexes/github-docs-3.1-cn.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:0b5da36b6dfa491e9f7409ae429fdae25ac00aafc728be65341cd9b026a02a1b
-size 1335439
+oid sha256:0febe199e3ce31c19fc3da32c435a4c788fbca65c2b9b8fad54bdf1320c938ea
+size 1336302
diff --git a/lib/search/indexes/github-docs-3.1-en-records.json.br b/lib/search/indexes/github-docs-3.1-en-records.json.br
index 1a797e6cfe..d56b931185 100644
--- a/lib/search/indexes/github-docs-3.1-en-records.json.br
+++ b/lib/search/indexes/github-docs-3.1-en-records.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:716ae21d1e74221a7ebd7702030b97d79e9bd33d6cdccf6df20cc262bbdfa669
-size 917612
+oid sha256:afed828ae58e9fa821eb868144b460830deab7461ccd008081fe4b939b24c2b4
+size 917755
diff --git a/lib/search/indexes/github-docs-3.1-en.json.br b/lib/search/indexes/github-docs-3.1-en.json.br
index 6f0c1eccd8..e3a10131ae 100644
--- a/lib/search/indexes/github-docs-3.1-en.json.br
+++ b/lib/search/indexes/github-docs-3.1-en.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:1bac79bd428b6093b3112222534c2b3a948b66f6d438e8645db6c24b946f9028
-size 3537196
+oid sha256:9a733fbc3443c6e1825306dfebfefdbdf6e6c63d7296afc3d481b07589020de6
+size 3537523
diff --git a/lib/search/indexes/github-docs-3.1-es-records.json.br b/lib/search/indexes/github-docs-3.1-es-records.json.br
index 4b4e00e4d9..bd28f1cc30 100644
--- a/lib/search/indexes/github-docs-3.1-es-records.json.br
+++ b/lib/search/indexes/github-docs-3.1-es-records.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:aa61ef829e2c908a408e104d5cda442e46e9b5fdc822a9daf46b75dae1962a18
-size 633343
+oid sha256:4ddeef7faeac9aab5e0a06a52f7273ccc5abc28e22f3e8bdde7c19c029f063f1
+size 631967
diff --git a/lib/search/indexes/github-docs-3.1-es.json.br b/lib/search/indexes/github-docs-3.1-es.json.br
index 785347e193..d818638d93 100644
--- a/lib/search/indexes/github-docs-3.1-es.json.br
+++ b/lib/search/indexes/github-docs-3.1-es.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:03b6d7001794bc8e9a2e0c7c07465e55f4c186cd36b4685f48745fc1ba406c22
-size 2674831
+oid sha256:5dcdc5a61778a3c667a3d24da93e1302ba47cae67f1e581341cd0012ce32c1af
+size 2663740
diff --git a/lib/search/indexes/github-docs-3.1-ja-records.json.br b/lib/search/indexes/github-docs-3.1-ja-records.json.br
index 6e704ec8e3..e807c83f56 100644
--- a/lib/search/indexes/github-docs-3.1-ja-records.json.br
+++ b/lib/search/indexes/github-docs-3.1-ja-records.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:b6d1b536d85538d562e0ad314df75ac1740c1a3b42706d184fcd86f8627fa1e0
-size 696504
+oid sha256:25bb27455088ed2c9597dcd533e3a0fb1b803cfcf8eaeb90ea6853be9dea363e
+size 696416
diff --git a/lib/search/indexes/github-docs-3.1-ja.json.br b/lib/search/indexes/github-docs-3.1-ja.json.br
index 56b394cc98..847d87d5f7 100644
--- a/lib/search/indexes/github-docs-3.1-ja.json.br
+++ b/lib/search/indexes/github-docs-3.1-ja.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:5850b62c0452c84f753f9d7629eb03a5b3238d97c379a33e26f231644e910c45
-size 3720567
+oid sha256:103d6d7ffc934d6bcb6bf990b478bbc8473c2f98ba0ab12fa6cef01c537a83d0
+size 3718970
diff --git a/lib/search/indexes/github-docs-3.1-pt-records.json.br b/lib/search/indexes/github-docs-3.1-pt-records.json.br
index 2c62c4c3d7..cf23eaac72 100644
--- a/lib/search/indexes/github-docs-3.1-pt-records.json.br
+++ b/lib/search/indexes/github-docs-3.1-pt-records.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:e42b09fbcf2c685462da7b4393d6c66fe9eed9d4e3f32d87ca72d565b6f1ced0
-size 623615
+oid sha256:e546eae9071262337a4c3f09ede6af8956038913a9899235ed89ce09f623171a
+size 623526
diff --git a/lib/search/indexes/github-docs-3.1-pt.json.br b/lib/search/indexes/github-docs-3.1-pt.json.br
index 84010c55ec..81deea92d9 100644
--- a/lib/search/indexes/github-docs-3.1-pt.json.br
+++ b/lib/search/indexes/github-docs-3.1-pt.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:f37b82aec2eda5ceb7fcd307484276a8a22794fbc76bf57ec487bf20c45a3315
-size 2565493
+oid sha256:b8d350e16212f96742a75a84ca5671c50da8067c564206663a72c69f18dd4921
+size 2569190
diff --git a/lib/search/indexes/github-docs-3.2-cn-records.json.br b/lib/search/indexes/github-docs-3.2-cn-records.json.br
index e69009a9e2..e19a963f37 100644
--- a/lib/search/indexes/github-docs-3.2-cn-records.json.br
+++ b/lib/search/indexes/github-docs-3.2-cn-records.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:2f4ff0cf9dac77bc3d7ac83a2fc53e92c6f10bda8e417ca7ef7561c7a479f848
-size 704046
+oid sha256:aca2ac22c3e40cfd608e1c0bc9505431146e0e37323bd0db902d5a2ff67eab55
+size 704715
diff --git a/lib/search/indexes/github-docs-3.2-cn.json.br b/lib/search/indexes/github-docs-3.2-cn.json.br
index 462b1e5fdd..584b3d37c8 100644
--- a/lib/search/indexes/github-docs-3.2-cn.json.br
+++ b/lib/search/indexes/github-docs-3.2-cn.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:29e6254e857d8b16514eb91f83ff9d3b4ee00a3cb6a6d5838ce7b297a214a024
-size 1363142
+oid sha256:d133ff96847920746364eb76d94f5a15cea284d358cd0874620dec1c57bd3af5
+size 1363408
diff --git a/lib/search/indexes/github-docs-3.2-en-records.json.br b/lib/search/indexes/github-docs-3.2-en-records.json.br
index 2ccb3eb394..7a4a90626f 100644
--- a/lib/search/indexes/github-docs-3.2-en-records.json.br
+++ b/lib/search/indexes/github-docs-3.2-en-records.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:8a1abf8424a1b4f6e31629c9ab42c18caf0f4671baffde76f001ec55ae4dc07f
-size 948339
+oid sha256:e526f098b0c267d8c757131b14ba32252ac0875729fa578e00d2b27905a364eb
+size 948049
diff --git a/lib/search/indexes/github-docs-3.2-en.json.br b/lib/search/indexes/github-docs-3.2-en.json.br
index 1a252305e2..a6d863a166 100644
--- a/lib/search/indexes/github-docs-3.2-en.json.br
+++ b/lib/search/indexes/github-docs-3.2-en.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:348230e14946e713d2bf573ac15a33a60b70a3cae819eb9deecc0d4052b46bcc
-size 3658215
+oid sha256:1ef62c12f1233390dfe303d670ad2cbd2d83d88c0a73c513faaa512c52e7ac84
+size 3659914
diff --git a/lib/search/indexes/github-docs-3.2-es-records.json.br b/lib/search/indexes/github-docs-3.2-es-records.json.br
index 1527c99022..4380f67f80 100644
--- a/lib/search/indexes/github-docs-3.2-es-records.json.br
+++ b/lib/search/indexes/github-docs-3.2-es-records.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:55257c7dc499f1955eac9f0247ccc41045bcf3655dd32dfde73b91f976034b1e
-size 649603
+oid sha256:0938e8d2846ea3b30abf7e70f50bba76dc9d5b263adb2b1e2eab606ab21d05bf
+size 649472
diff --git a/lib/search/indexes/github-docs-3.2-es.json.br b/lib/search/indexes/github-docs-3.2-es.json.br
index 61d616fd1f..5e1f897656 100644
--- a/lib/search/indexes/github-docs-3.2-es.json.br
+++ b/lib/search/indexes/github-docs-3.2-es.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:64516858d16b1dc4c84eaf1c77c025c285138b96226e13d8d8e848de266f547f
-size 2746075
+oid sha256:42ac2ae786f2209445354f579076b95b1b348b5f929f958f1943ff00d7e2c02f
+size 2734937
diff --git a/lib/search/indexes/github-docs-3.2-ja-records.json.br b/lib/search/indexes/github-docs-3.2-ja-records.json.br
index 4cc1f154a5..87f496fdaa 100644
--- a/lib/search/indexes/github-docs-3.2-ja-records.json.br
+++ b/lib/search/indexes/github-docs-3.2-ja-records.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:40e6b1b42d73a765996a1135760044504bcadc3dd6aed4f3bf7910dbac33f83a
-size 714942
+oid sha256:1b403e60ddb4fcfee68b88d593d1579fb44749536a66c110dafd9b11ddc33f6c
+size 714194
diff --git a/lib/search/indexes/github-docs-3.2-ja.json.br b/lib/search/indexes/github-docs-3.2-ja.json.br
index 4742261f66..4f07f76bf9 100644
--- a/lib/search/indexes/github-docs-3.2-ja.json.br
+++ b/lib/search/indexes/github-docs-3.2-ja.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:292bc73640ba59c52c32b383881f005ca21b6395d0b89a66be5ab3f532eea88f
-size 3816365
+oid sha256:1c3b5d8c996d10a92a07badbd3af2ac6fbd8330480f3a768e89633bb4f4f5c03
+size 3816188
diff --git a/lib/search/indexes/github-docs-3.2-pt-records.json.br b/lib/search/indexes/github-docs-3.2-pt-records.json.br
index d9f76656e3..e94f500474 100644
--- a/lib/search/indexes/github-docs-3.2-pt-records.json.br
+++ b/lib/search/indexes/github-docs-3.2-pt-records.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:adfe42390142791edbb3893175d48b52fc0de0dca18e6ff031e14605bfd8be83
-size 639646
+oid sha256:4de3bdc9568cbdd01a03850bae30e04ec53faf87b6ae3a51029e668a2d96053a
+size 640559
diff --git a/lib/search/indexes/github-docs-3.2-pt.json.br b/lib/search/indexes/github-docs-3.2-pt.json.br
index d29a3ee915..207ac860e0 100644
--- a/lib/search/indexes/github-docs-3.2-pt.json.br
+++ b/lib/search/indexes/github-docs-3.2-pt.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:e05f62455ce70f63d58812a5f63e637e63ae608478b8130a6a979a15cbfbebd1
-size 2627809
+oid sha256:4f8c1b147406b4912f029d507799f5d646b8de061f75d34fb2f17cbe9c373a02
+size 2633542
diff --git a/lib/search/indexes/github-docs-3.3-cn-records.json.br b/lib/search/indexes/github-docs-3.3-cn-records.json.br
index defe3a0a35..52a82106e2 100644
--- a/lib/search/indexes/github-docs-3.3-cn-records.json.br
+++ b/lib/search/indexes/github-docs-3.3-cn-records.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:16918518ac1398304028d389618fda1ada8370d791c3c54b63fffe75accfb2b8
-size 727705
+oid sha256:29a1ff64014552565706b09f5bf66503bd79bbb5cd7ad010056d5b8ad9c5d9cb
+size 728034
diff --git a/lib/search/indexes/github-docs-3.3-cn.json.br b/lib/search/indexes/github-docs-3.3-cn.json.br
index 7fb14556b4..8adbdde5ac 100644
--- a/lib/search/indexes/github-docs-3.3-cn.json.br
+++ b/lib/search/indexes/github-docs-3.3-cn.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:a723047ad6c856d9e29170a0aabb8dcc9f8c9c37971e3dd80622053c6212183b
-size 1405522
+oid sha256:69d4fd297beee66e3c0d4e8ab1f0f839a120ba968da3874c9b52aa1174dbce1b
+size 1406961
diff --git a/lib/search/indexes/github-docs-3.3-en-records.json.br b/lib/search/indexes/github-docs-3.3-en-records.json.br
index b71ca373bd..9d67ae15ed 100644
--- a/lib/search/indexes/github-docs-3.3-en-records.json.br
+++ b/lib/search/indexes/github-docs-3.3-en-records.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:3c8f54445243241457bb7b2d95fd2a3d49e6831f678a8c63f09fe108f02a2533
-size 981710
+oid sha256:4863bc45cae5ad5bf59993f2ca447860214e67f12c027489192402482c6d5022
+size 982704
diff --git a/lib/search/indexes/github-docs-3.3-en.json.br b/lib/search/indexes/github-docs-3.3-en.json.br
index 4312e68e4c..00a90a3c6a 100644
--- a/lib/search/indexes/github-docs-3.3-en.json.br
+++ b/lib/search/indexes/github-docs-3.3-en.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:91939cc8e89a109d209e44ebf1cd7cf6a55eef582601ab86df6bcb457d86d1b4
-size 3772890
+oid sha256:97453fcc7d831efe74394980249eb22a4c9eca1ff49270933f6ca22b9dcb546d
+size 3777899
diff --git a/lib/search/indexes/github-docs-3.3-es-records.json.br b/lib/search/indexes/github-docs-3.3-es-records.json.br
index dece225f2a..c2f48bd01d 100644
--- a/lib/search/indexes/github-docs-3.3-es-records.json.br
+++ b/lib/search/indexes/github-docs-3.3-es-records.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:f1e9f260315e7646bf319c94b0a8fbdfc7b0761cede2f995bc9cd8f70c472091
-size 668469
+oid sha256:37577dc3fef9366027b5d958b0df65b083d19a1ed9882dfddf1297052cd9072e
+size 668963
diff --git a/lib/search/indexes/github-docs-3.3-es.json.br b/lib/search/indexes/github-docs-3.3-es.json.br
index 2245da8456..2821a782f3 100644
--- a/lib/search/indexes/github-docs-3.3-es.json.br
+++ b/lib/search/indexes/github-docs-3.3-es.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:c36b86200af62298fc36ce64c775b8bc761405847515e76a5de599eefe9141cd
-size 2831410
+oid sha256:721ab58f8b60909c5c9b920f4fa4bd2e379595591d44664445ed9a3c68668a9b
+size 2820384
diff --git a/lib/search/indexes/github-docs-3.3-ja-records.json.br b/lib/search/indexes/github-docs-3.3-ja-records.json.br
index 96833e3cbc..80be0eb623 100644
--- a/lib/search/indexes/github-docs-3.3-ja-records.json.br
+++ b/lib/search/indexes/github-docs-3.3-ja-records.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:1e851b6104040345a48029a95db4d4ebb0350cea1d831351c212e875164d2ac5
-size 737672
+oid sha256:bd9b184372e7e162c086531b0123be27699f8c67f8ff03460d9f222d942d136c
+size 737692
diff --git a/lib/search/indexes/github-docs-3.3-ja.json.br b/lib/search/indexes/github-docs-3.3-ja.json.br
index 6c6c73121e..1ca5d722cd 100644
--- a/lib/search/indexes/github-docs-3.3-ja.json.br
+++ b/lib/search/indexes/github-docs-3.3-ja.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:8e44918fc1c561b4696a2cbdd85080c51d113974085e53d38cb7653d56fbdfe3
-size 3938506
+oid sha256:7d9405247fd21f8a9b5591a17f62f197e92118d08fa24e63df6162978b0daec5
+size 3941953
diff --git a/lib/search/indexes/github-docs-3.3-pt-records.json.br b/lib/search/indexes/github-docs-3.3-pt-records.json.br
index fc738e37c5..e2bf84df5e 100644
--- a/lib/search/indexes/github-docs-3.3-pt-records.json.br
+++ b/lib/search/indexes/github-docs-3.3-pt-records.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:8d3344d261573eff1aa7cab6320fcff19bb70a8be57f3f3299cc5ea21524dd85
-size 658947
+oid sha256:ad8a7d5a2c56a1069dc2a5666ac6ef68cb4546e437d6a48bfa9950e04c345df9
+size 659846
diff --git a/lib/search/indexes/github-docs-3.3-pt.json.br b/lib/search/indexes/github-docs-3.3-pt.json.br
index 8f4f64c2c8..94c0da6413 100644
--- a/lib/search/indexes/github-docs-3.3-pt.json.br
+++ b/lib/search/indexes/github-docs-3.3-pt.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:9031b31a3f07786f45f866a82b2489ee99adbcd04fd57ea1d4b4ba78a24306d5
-size 2709598
+oid sha256:bab39b1e4fcc01a038e37744127b1b2a33713cefaf453e71b372533f89d7f0a9
+size 2714831
diff --git a/lib/search/indexes/github-docs-3.4-cn-records.json.br b/lib/search/indexes/github-docs-3.4-cn-records.json.br
index 69f8bb3a6c..85703c5bb3 100644
--- a/lib/search/indexes/github-docs-3.4-cn-records.json.br
+++ b/lib/search/indexes/github-docs-3.4-cn-records.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:da18932b4de4bc1dd57514398177f17ab754deb4d022c65ee07a9be4d63cd626
-size 728724
+oid sha256:4fa79a9b69437445aba35386dd72502e6d6ad3644d73b3e38c8f39e27dce5818
+size 727408
diff --git a/lib/search/indexes/github-docs-3.4-cn.json.br b/lib/search/indexes/github-docs-3.4-cn.json.br
index b54b25d6f3..8561ef0b59 100644
--- a/lib/search/indexes/github-docs-3.4-cn.json.br
+++ b/lib/search/indexes/github-docs-3.4-cn.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:cc70198410f88728d0069d46188ac7ac67b5e40f4d27bbba91413c1709201806
-size 1408537
+oid sha256:5cc9f9f82a3ed49fdbe7c14f1f763fcfc95c5e441ebb1a045a19a6096cbf5d56
+size 1407863
diff --git a/lib/search/indexes/github-docs-3.4-en-records.json.br b/lib/search/indexes/github-docs-3.4-en-records.json.br
index a5bd5df6fa..624819822a 100644
--- a/lib/search/indexes/github-docs-3.4-en-records.json.br
+++ b/lib/search/indexes/github-docs-3.4-en-records.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:e9a30340da07d9e909086fb339e22ebe7b3a92c61033ee36cd450540558d94f9
-size 988360
+oid sha256:1b266a7e9adde740ca1f02eefe25b71173d192e25c955da11c6212aeb2bcd6d9
+size 989346
diff --git a/lib/search/indexes/github-docs-3.4-en.json.br b/lib/search/indexes/github-docs-3.4-en.json.br
index 3798aa6cd6..3c722f3a19 100644
--- a/lib/search/indexes/github-docs-3.4-en.json.br
+++ b/lib/search/indexes/github-docs-3.4-en.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:1a68400ad4fd94680c3d8cee81053905cce3b6b564d49096d5e19d18b9c2a7f1
-size 3793946
+oid sha256:08b2cbc76c01790d9c0a21d7b3537651c8c9e1ee6c8c47e4da3758225bd1e1b2
+size 3795623
diff --git a/lib/search/indexes/github-docs-3.4-es-records.json.br b/lib/search/indexes/github-docs-3.4-es-records.json.br
index 286937a6e0..5dcebc769b 100644
--- a/lib/search/indexes/github-docs-3.4-es-records.json.br
+++ b/lib/search/indexes/github-docs-3.4-es-records.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:9753a6dc8c98e34299798c5da3d32e573b7ba6fc51e8877c8492a99847e0ee2e
-size 670166
+oid sha256:1eb571876358aca456c0ebc06c60878839acb453f67c44305fc479a126033a96
+size 670306
diff --git a/lib/search/indexes/github-docs-3.4-es.json.br b/lib/search/indexes/github-docs-3.4-es.json.br
index b240671d6c..fd6543fe47 100644
--- a/lib/search/indexes/github-docs-3.4-es.json.br
+++ b/lib/search/indexes/github-docs-3.4-es.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:65af0eb9a23dd0688f0b104e56a38c3d8c6046e8ae393083317b2214248b9d0b
-size 2836811
+oid sha256:9d73ce1c4b5abf8458e657fb89a05cad48f5e728d3ac79c09965a785b0b262aa
+size 2823777
diff --git a/lib/search/indexes/github-docs-3.4-ja-records.json.br b/lib/search/indexes/github-docs-3.4-ja-records.json.br
index 15f9ae042a..fa9125c99e 100644
--- a/lib/search/indexes/github-docs-3.4-ja-records.json.br
+++ b/lib/search/indexes/github-docs-3.4-ja-records.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:f4ef561ab868aca0d10a1f82262826f586df43f05c0fd9292d1bcaa4e4b7bca7
-size 737560
+oid sha256:fa02977483ccbf2b30fcbef20f8f46900fd0dfb52c5c192d598843e2d1e81451
+size 737847
diff --git a/lib/search/indexes/github-docs-3.4-ja.json.br b/lib/search/indexes/github-docs-3.4-ja.json.br
index d43a1c3df9..8dc4fcb67f 100644
--- a/lib/search/indexes/github-docs-3.4-ja.json.br
+++ b/lib/search/indexes/github-docs-3.4-ja.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:e38b2510d0f9b5ad4399a5b1cad77aa4f697b8355aa14aeccfc23e603fb9f3c1
-size 3945167
+oid sha256:9dad47d23e9f672f6413306857af8dde6bc4550ac93ccf15e001f9e39bd0d207
+size 3945381
diff --git a/lib/search/indexes/github-docs-3.4-pt-records.json.br b/lib/search/indexes/github-docs-3.4-pt-records.json.br
index 355afb8de1..682f59b863 100644
--- a/lib/search/indexes/github-docs-3.4-pt-records.json.br
+++ b/lib/search/indexes/github-docs-3.4-pt-records.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:e5d00cb865090d263fdc2d071bb4a90a72b8f153e5b813c5e5191dce48beb260
-size 660133
+oid sha256:3a53b4e6f826a41a669818649d54797d21192137dcc69ab5213ddd2826bdad3d
+size 660682
diff --git a/lib/search/indexes/github-docs-3.4-pt.json.br b/lib/search/indexes/github-docs-3.4-pt.json.br
index e30df8ba6c..0f0c183dfa 100644
--- a/lib/search/indexes/github-docs-3.4-pt.json.br
+++ b/lib/search/indexes/github-docs-3.4-pt.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:23271e130f461d0cddfff1b4be3673b491ff09f03c5df3e668134725b443d9c9
-size 2714971
+oid sha256:81ff00007e640de85c490c6fb325661b11a48f2fa9b68f61cb7afd2b5271abae
+size 2719190
diff --git a/lib/search/indexes/github-docs-3.5-cn-records.json.br b/lib/search/indexes/github-docs-3.5-cn-records.json.br
index 630ab5078e..81cb284ac3 100644
--- a/lib/search/indexes/github-docs-3.5-cn-records.json.br
+++ b/lib/search/indexes/github-docs-3.5-cn-records.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:91f6463fad9ee673b7f13aa843639a80682d8117cb01e145897c29ef959be3f9
-size 754635
+oid sha256:29eb546287c335a843a19a744191a48a92dd6e02665b1479cead85696b134f30
+size 753677
diff --git a/lib/search/indexes/github-docs-3.5-cn.json.br b/lib/search/indexes/github-docs-3.5-cn.json.br
index 78e4ec52b4..4334036c7f 100644
--- a/lib/search/indexes/github-docs-3.5-cn.json.br
+++ b/lib/search/indexes/github-docs-3.5-cn.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:501b80cf7385045d056ef917e3d930a8d2b53f766e24da7e48bb74d5338edf82
-size 1468991
+oid sha256:cbc8dd9057e03fca80e9bbdb7d97af6accabacadecb223c4c9797f5509a5928c
+size 1467986
diff --git a/lib/search/indexes/github-docs-3.5-en-records.json.br b/lib/search/indexes/github-docs-3.5-en-records.json.br
index a0f6982607..3f4390cc7f 100644
--- a/lib/search/indexes/github-docs-3.5-en-records.json.br
+++ b/lib/search/indexes/github-docs-3.5-en-records.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:5090287d57385b7221c89816732b98941af0f717f1a4a963a6a94ce43e66fd91
-size 1024007
+oid sha256:1b6fae1ff091b382e2d72a90353f5753140581d46d1203e7306a1ed406f329d0
+size 1023930
diff --git a/lib/search/indexes/github-docs-3.5-en.json.br b/lib/search/indexes/github-docs-3.5-en.json.br
index 109fa915f1..c8b5401b87 100644
--- a/lib/search/indexes/github-docs-3.5-en.json.br
+++ b/lib/search/indexes/github-docs-3.5-en.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:e29fceb77dad51280219ca001ae9aa90973a13fd654bf98ec7c3ea48727786f1
-size 3930146
+oid sha256:58c3bbbb27c284b351d1d4e95bc28c8239b21b917f85bb4c950f4ef9c1c4f789
+size 3931163
diff --git a/lib/search/indexes/github-docs-3.5-es-records.json.br b/lib/search/indexes/github-docs-3.5-es-records.json.br
index 938cb37a52..52fd19a50f 100644
--- a/lib/search/indexes/github-docs-3.5-es-records.json.br
+++ b/lib/search/indexes/github-docs-3.5-es-records.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:2fba2dd90aff596be6f87aad6bd45253c72221a703d1792847eb85f97312641c
-size 689966
+oid sha256:3c9ce2d1ba688153d12942af1a645339105a326f21d8f389f0ecb32e0ecd0452
+size 690187
diff --git a/lib/search/indexes/github-docs-3.5-es.json.br b/lib/search/indexes/github-docs-3.5-es.json.br
index d5bf9d72b2..5258048642 100644
--- a/lib/search/indexes/github-docs-3.5-es.json.br
+++ b/lib/search/indexes/github-docs-3.5-es.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:64e1dff20f4e75165a87ff96bea86375d709750e7a4cff11a6c19f6e27c76a48
-size 2943844
+oid sha256:c79d0117f101aef7812c20adb49fbe15430f18ed806c1321a131afe697ad57f6
+size 2927889
diff --git a/lib/search/indexes/github-docs-3.5-ja-records.json.br b/lib/search/indexes/github-docs-3.5-ja-records.json.br
index b5d6d72c50..2246831163 100644
--- a/lib/search/indexes/github-docs-3.5-ja-records.json.br
+++ b/lib/search/indexes/github-docs-3.5-ja-records.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:ae5d2cf3c54b2776fd2aadf19db4b341526df32f98cd6e8e04c1aae8e13ce523
-size 761058
+oid sha256:e44d3997c28600a5ee1f1366f1e587af0951add2c60977eaaeb91ffc14700e79
+size 760866
diff --git a/lib/search/indexes/github-docs-3.5-ja.json.br b/lib/search/indexes/github-docs-3.5-ja.json.br
index 487a7fb773..cd9f04e2d8 100644
--- a/lib/search/indexes/github-docs-3.5-ja.json.br
+++ b/lib/search/indexes/github-docs-3.5-ja.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:56b9ba14b64bc21dfe5eda242bd59ec37997a474414d880e000f20a5c744d864
-size 4089111
+oid sha256:ab94b9a2ee264e027b3d1e9f3e3a87aae1a1dd0086e5afe664fbffed47bb1622
+size 4090364
diff --git a/lib/search/indexes/github-docs-3.5-pt-records.json.br b/lib/search/indexes/github-docs-3.5-pt-records.json.br
index 10db84cadc..05ae1d10f1 100644
--- a/lib/search/indexes/github-docs-3.5-pt-records.json.br
+++ b/lib/search/indexes/github-docs-3.5-pt-records.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:90fea819f440a2aab96efd1d8932d4f8ef3c5c1efa7a99d104b45315a2baa958
-size 681356
+oid sha256:1917c5683c658c895bc1d31b2856fdc73facd43233d5d0ae37cee71f66bdeac0
+size 682872
diff --git a/lib/search/indexes/github-docs-3.5-pt.json.br b/lib/search/indexes/github-docs-3.5-pt.json.br
index ca13673fec..473ff8659a 100644
--- a/lib/search/indexes/github-docs-3.5-pt.json.br
+++ b/lib/search/indexes/github-docs-3.5-pt.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:0970b29ecdc6b080cf05548cacc9f9f1bdaad65a649c2c1ee62099cb46ea3b88
-size 2812185
+oid sha256:419c4861567136b7fc45ad73842a57c3586d180a76c476de6c60d523a7157c46
+size 2819926
diff --git a/lib/search/indexes/github-docs-dotcom-cn-records.json.br b/lib/search/indexes/github-docs-dotcom-cn-records.json.br
index c3fe0a980c..a0a89111bd 100644
--- a/lib/search/indexes/github-docs-dotcom-cn-records.json.br
+++ b/lib/search/indexes/github-docs-dotcom-cn-records.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:0b5c0f2f230e159c3c0979322142579e63cf5b50b9d540a97fe78177dc0464ad
-size 929373
+oid sha256:e0e6042dd1b0ed1a65bd2adb1780ce3e416f105f08fee7d52aefb2fd5dab59b8
+size 928441
diff --git a/lib/search/indexes/github-docs-dotcom-cn.json.br b/lib/search/indexes/github-docs-dotcom-cn.json.br
index d1564976d5..02cbd809a9 100644
--- a/lib/search/indexes/github-docs-dotcom-cn.json.br
+++ b/lib/search/indexes/github-docs-dotcom-cn.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:78fd305915f1f08d6a1957b711a197a4547a5b76c36a2de56056e5a6a0136fc8
-size 1459086
+oid sha256:f00feebe4ac96473ffb7ad1798d501084f358fa12b21cd5feced7998267fe09b
+size 1454908
diff --git a/lib/search/indexes/github-docs-dotcom-en-records.json.br b/lib/search/indexes/github-docs-dotcom-en-records.json.br
index b4cbb4f1e8..56e0b6edfb 100644
--- a/lib/search/indexes/github-docs-dotcom-en-records.json.br
+++ b/lib/search/indexes/github-docs-dotcom-en-records.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:e222fd06059b8e35a690324559b5cbb5c395425f13f8710f716b64ef918400b4
-size 1252080
+oid sha256:33cc19b80cff65517197020cfb0947cfd9db16a0d099c11269eb7514d320e4b0
+size 1252037
diff --git a/lib/search/indexes/github-docs-dotcom-en.json.br b/lib/search/indexes/github-docs-dotcom-en.json.br
index 416d504843..1bd907c4ca 100644
--- a/lib/search/indexes/github-docs-dotcom-en.json.br
+++ b/lib/search/indexes/github-docs-dotcom-en.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:20686be03583a7c56ccaf771e883dcce56e9fa9c7b27d0bf5b3561c996edd59c
-size 4524262
+oid sha256:1a5e9698ebf64c3c1fe7560b7c4db6025dc02a97bd0097f140abe9bd4c087f26
+size 4522806
diff --git a/lib/search/indexes/github-docs-dotcom-es-records.json.br b/lib/search/indexes/github-docs-dotcom-es-records.json.br
index 8f2e054e68..d51e908aa0 100644
--- a/lib/search/indexes/github-docs-dotcom-es-records.json.br
+++ b/lib/search/indexes/github-docs-dotcom-es-records.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:7fda7ce08eefc1c9e461083481a4d806e7fa3c626f15cb1015e4b754b32cc8bf
-size 835316
+oid sha256:e7a292c5c441fbe5c75dbbf48aa9b4a2ec010e45e1460230f5fea7e71ca01e37
+size 833689
diff --git a/lib/search/indexes/github-docs-dotcom-es.json.br b/lib/search/indexes/github-docs-dotcom-es.json.br
index 88c12da44d..b9a2a096c5 100644
--- a/lib/search/indexes/github-docs-dotcom-es.json.br
+++ b/lib/search/indexes/github-docs-dotcom-es.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:c6d82356cf64c3ff1440ad944bec0b7c304c90217bdff26e0c72a8c16af1afb2
-size 3353719
+oid sha256:b31e5ef6356f9865da88d0692e8afd2109ff4fc89fec631389bc7ab348ff67ba
+size 3333239
diff --git a/lib/search/indexes/github-docs-dotcom-ja-records.json.br b/lib/search/indexes/github-docs-dotcom-ja-records.json.br
index c3a8d7cd92..f8fc09c6ac 100644
--- a/lib/search/indexes/github-docs-dotcom-ja-records.json.br
+++ b/lib/search/indexes/github-docs-dotcom-ja-records.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:ce19a74289e4ea9a983f6c7d7a861f46243c8ce507993309452d4e306cca87ae
-size 932651
+oid sha256:5ec60fd1e9640d1221453ad598bab9e95b52c4c0ce4accd0a24b22b5f6c6f99b
+size 932743
diff --git a/lib/search/indexes/github-docs-dotcom-ja.json.br b/lib/search/indexes/github-docs-dotcom-ja.json.br
index 4c10703424..f72e347ea1 100644
--- a/lib/search/indexes/github-docs-dotcom-ja.json.br
+++ b/lib/search/indexes/github-docs-dotcom-ja.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:1a3f2ab31397078f146732b8b34ab62f0b65f34f6a2ac617ec0cc615f27b5813
-size 4762703
+oid sha256:b35a450990236df60dc0434042b90ab2bd2ecfe0bd8d2e032bb583393d0b0d23
+size 4763020
diff --git a/lib/search/indexes/github-docs-dotcom-pt-records.json.br b/lib/search/indexes/github-docs-dotcom-pt-records.json.br
index 5bada01440..32438a7324 100644
--- a/lib/search/indexes/github-docs-dotcom-pt-records.json.br
+++ b/lib/search/indexes/github-docs-dotcom-pt-records.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:67e216d183037f4efd16ef4b8205449826e147af3dc5b1fea0f11b46b46c2982
-size 822186
+oid sha256:cf708bded4b8a6729a6268c300d078ece4c82af0c23be6160c3ffa5c60c78e3b
+size 822545
diff --git a/lib/search/indexes/github-docs-dotcom-pt.json.br b/lib/search/indexes/github-docs-dotcom-pt.json.br
index 2716b03f2b..86b3591708 100644
--- a/lib/search/indexes/github-docs-dotcom-pt.json.br
+++ b/lib/search/indexes/github-docs-dotcom-pt.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:95910ad31dee7d3866afe8802a612ab9bc7562b9208988cbb96cbeb80a51ea8d
-size 3223463
+oid sha256:ff700b14c2bf330c49af9bb6a961cea7b93d80fa68812ec6c9406cfd460846d8
+size 3225198
diff --git a/lib/search/indexes/github-docs-ghae-cn-records.json.br b/lib/search/indexes/github-docs-ghae-cn-records.json.br
index bff3e39df4..1261bd4501 100644
--- a/lib/search/indexes/github-docs-ghae-cn-records.json.br
+++ b/lib/search/indexes/github-docs-ghae-cn-records.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:01b8181e65f9855025e1db92b4b899521777db408cd1a52d337826859b44d65b
-size 566760
+oid sha256:7d4b3a8d4983b45f8694bd6986d544f7dc81c76a4c2edb04be25c7ae305410d7
+size 567063
diff --git a/lib/search/indexes/github-docs-ghae-cn.json.br b/lib/search/indexes/github-docs-ghae-cn.json.br
index af0a60c638..01ff846606 100644
--- a/lib/search/indexes/github-docs-ghae-cn.json.br
+++ b/lib/search/indexes/github-docs-ghae-cn.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:ae6f9ca1cc53a4513ffe5c66f8b14550ec8c32c5c4eb1c7cae424be86a3087ac
-size 1042819
+oid sha256:4ddbb163e38d61db50edd755776da45f8d19a951f08c16feb9f9ac050bf18edf
+size 1043194
diff --git a/lib/search/indexes/github-docs-ghae-en-records.json.br b/lib/search/indexes/github-docs-ghae-en-records.json.br
index 36d79074ad..27e1487600 100644
--- a/lib/search/indexes/github-docs-ghae-en-records.json.br
+++ b/lib/search/indexes/github-docs-ghae-en-records.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:1687ae0c76edc979f614867ffb3c906d2bed78e0194b6305c23d1c41def0a6aa
-size 780186
+oid sha256:c01f114c557d789936033b2628213bd875c2bae7c04c1a1836195744f51d4f37
+size 780600
diff --git a/lib/search/indexes/github-docs-ghae-en.json.br b/lib/search/indexes/github-docs-ghae-en.json.br
index 10656ce707..150446506f 100644
--- a/lib/search/indexes/github-docs-ghae-en.json.br
+++ b/lib/search/indexes/github-docs-ghae-en.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:bee2ed9d3a58c59fbff07763eaea57f8a0d0e3c1eb5f68f0ed8dfc0c4c28cacf
-size 2956093
+oid sha256:34fe783f59565f4bcda5e382ba4dab39bedce438828697b046e0828d20ac8cf9
+size 2956675
diff --git a/lib/search/indexes/github-docs-ghae-es-records.json.br b/lib/search/indexes/github-docs-ghae-es-records.json.br
index 50b0761839..1f550424be 100644
--- a/lib/search/indexes/github-docs-ghae-es-records.json.br
+++ b/lib/search/indexes/github-docs-ghae-es-records.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:68147bdd75ec5a228760a0426e999317d9955fe76c81b03bb251c9126a3e8667
-size 526556
+oid sha256:1ed3f204603a5c4f78cba91a084250b807bc44cb1f17b8c42514f1c5038e98a9
+size 527100
diff --git a/lib/search/indexes/github-docs-ghae-es.json.br b/lib/search/indexes/github-docs-ghae-es.json.br
index b2856aa9f2..f894fb4992 100644
--- a/lib/search/indexes/github-docs-ghae-es.json.br
+++ b/lib/search/indexes/github-docs-ghae-es.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:b9b8dc88080fdcbe68d2b80378a36d2984678317985d4e5ca896dc185333e086
-size 2141613
+oid sha256:838f4199923c66f873342e085c1c10cfbf2c9a2d32b5d9e185adacdb437889fc
+size 2134882
diff --git a/lib/search/indexes/github-docs-ghae-ja-records.json.br b/lib/search/indexes/github-docs-ghae-ja-records.json.br
index bc4cf6867c..daaec802c5 100644
--- a/lib/search/indexes/github-docs-ghae-ja-records.json.br
+++ b/lib/search/indexes/github-docs-ghae-ja-records.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:7b544ddc63c1bf257a84d6377ff0b3b397cd3f50093178a71ed731853fed63f6
-size 578048
+oid sha256:06687592719970d4ca1b639ee44eedf155f02e9eac54eb1f9d9fd7daae22a2b3
+size 577341
diff --git a/lib/search/indexes/github-docs-ghae-ja.json.br b/lib/search/indexes/github-docs-ghae-ja.json.br
index 58a00ea3c1..dfaf036ebe 100644
--- a/lib/search/indexes/github-docs-ghae-ja.json.br
+++ b/lib/search/indexes/github-docs-ghae-ja.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:14c303c426869d31ead795f09d5520d38c55779f2595f66d640ba35a4a25b654
-size 2955688
+oid sha256:8aaaffc82a79aac3cc876986d1e17b91300c5c5432a403ec9357e580f83be78e
+size 2953720
diff --git a/lib/search/indexes/github-docs-ghae-pt-records.json.br b/lib/search/indexes/github-docs-ghae-pt-records.json.br
index 0b5bbfdd09..43425d371a 100644
--- a/lib/search/indexes/github-docs-ghae-pt-records.json.br
+++ b/lib/search/indexes/github-docs-ghae-pt-records.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:852fba9ebc2857de8acf314d6b4ce13f1027b41f43e4a4c10cab3132c256cbdb
-size 519577
+oid sha256:36c86dc380a62ad99a7982d0980bf7e60e97164bf21399fae43b574b6f23a1bd
+size 519125
diff --git a/lib/search/indexes/github-docs-ghae-pt.json.br b/lib/search/indexes/github-docs-ghae-pt.json.br
index 768f1d3f16..dcb245c078 100644
--- a/lib/search/indexes/github-docs-ghae-pt.json.br
+++ b/lib/search/indexes/github-docs-ghae-pt.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:a26ca979e5dd96a1b518f2107daf77684d3b3b9b5d6386ee82cc881e091fb201
-size 2035993
+oid sha256:263b658414f063a5fb472824f39e0fc73b3d0964b3855280010e734d1b768767
+size 2039269
diff --git a/lib/search/indexes/github-docs-ghec-cn-records.json.br b/lib/search/indexes/github-docs-ghec-cn-records.json.br
index 6b0f81aa2e..bcd904cd7c 100644
--- a/lib/search/indexes/github-docs-ghec-cn-records.json.br
+++ b/lib/search/indexes/github-docs-ghec-cn-records.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:69ee9c7fd9853b25f2fd152f425ff3c2a94562b7cfc74f164de50bb956f96677
-size 877064
+oid sha256:c2c5b99f2d1cd187f44385ce3c3b159f9e4e365172286b8e6de471b9c225c948
+size 876339
diff --git a/lib/search/indexes/github-docs-ghec-cn.json.br b/lib/search/indexes/github-docs-ghec-cn.json.br
index d7beeb1a8c..0e5c87bbfc 100644
--- a/lib/search/indexes/github-docs-ghec-cn.json.br
+++ b/lib/search/indexes/github-docs-ghec-cn.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:f84650546f101d9a21733af089024d1c3e209880b338a5a436313218d1e2adbe
-size 1551366
+oid sha256:1a89503f2d199c66b2f88cf3e33c947184b9c3a78fa2dcadcecd37240ac6a2d2
+size 1549197
diff --git a/lib/search/indexes/github-docs-ghec-en-records.json.br b/lib/search/indexes/github-docs-ghec-en-records.json.br
index 1cde4bd797..869bda44e6 100644
--- a/lib/search/indexes/github-docs-ghec-en-records.json.br
+++ b/lib/search/indexes/github-docs-ghec-en-records.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:83224d12ebd9e386c28d668fa4e44856010af411801555ecb7223ebc56460f9b
-size 1160980
+oid sha256:bf587adf7d0d1b6afb2935eaa6535579cdf13ebbb5f8688518ac4d19d154702f
+size 1164295
diff --git a/lib/search/indexes/github-docs-ghec-en.json.br b/lib/search/indexes/github-docs-ghec-en.json.br
index 6efc32c3fc..271bc486ba 100644
--- a/lib/search/indexes/github-docs-ghec-en.json.br
+++ b/lib/search/indexes/github-docs-ghec-en.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:37867286d8f10c807a675ef73d2416d0e99d82bea762493c37065f3fb791500f
-size 4436903
+oid sha256:7231746844094844703e940c4e000deb09ae7af012e1a42d6f8b812f8ebb33d8
+size 4440062
diff --git a/lib/search/indexes/github-docs-ghec-es-records.json.br b/lib/search/indexes/github-docs-ghec-es-records.json.br
index 4876488862..db200d95cc 100644
--- a/lib/search/indexes/github-docs-ghec-es-records.json.br
+++ b/lib/search/indexes/github-docs-ghec-es-records.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:dad630b8ca46180937a9bf3c078f42e2de3144fe682d8b9b0ca741d4994c4e0c
-size 808299
+oid sha256:5376c55b5b4766f63fb41e50409a7d883a0381cf9b3ec5f204c19e47bdf95c70
+size 808373
diff --git a/lib/search/indexes/github-docs-ghec-es.json.br b/lib/search/indexes/github-docs-ghec-es.json.br
index 86308d7bb3..d5b47be48c 100644
--- a/lib/search/indexes/github-docs-ghec-es.json.br
+++ b/lib/search/indexes/github-docs-ghec-es.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:6a1940a23b3c5e24ed9098d28f85e2f934f4d0eddbcffc9eab0352118c9d6cbf
-size 3408211
+oid sha256:f37dddf49df2b84b31df5e25c14e5b0e9a7575a98cbc014b0dd6ad389e32f1d7
+size 3391824
diff --git a/lib/search/indexes/github-docs-ghec-ja-records.json.br b/lib/search/indexes/github-docs-ghec-ja-records.json.br
index 022fb2ed57..bfce9fd8c5 100644
--- a/lib/search/indexes/github-docs-ghec-ja-records.json.br
+++ b/lib/search/indexes/github-docs-ghec-ja-records.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:be2952786f5b1305ca5cc423719ebd625dfed6c65ad8980988c3988e0765c6b1
-size 884217
+oid sha256:04ccfdc9cba8dad7c633fd41df16c636422fd3d2332a91d47b385bd575053ee0
+size 884982
diff --git a/lib/search/indexes/github-docs-ghec-ja.json.br b/lib/search/indexes/github-docs-ghec-ja.json.br
index baee58f140..ef13dff257 100644
--- a/lib/search/indexes/github-docs-ghec-ja.json.br
+++ b/lib/search/indexes/github-docs-ghec-ja.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:555e87cefba9b76b233a66899dabcff902485afb8b0db8c1964fed45e8bcde28
-size 4740499
+oid sha256:dc342e47ff36caf7fb5d43f27d1eac52709453a90c9c8469dc4da6447fba7fa5
+size 4743824
diff --git a/lib/search/indexes/github-docs-ghec-pt-records.json.br b/lib/search/indexes/github-docs-ghec-pt-records.json.br
index 7d646f697c..c79d28c435 100644
--- a/lib/search/indexes/github-docs-ghec-pt-records.json.br
+++ b/lib/search/indexes/github-docs-ghec-pt-records.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:18faa94ff3f10e7e4ad7381a530e03d1e5c9982648fed65ee3f232fc69a92772
-size 795788
+oid sha256:2ded52b4ac81ba39e60af9a59679872fd9cb5b38317ef356eca978a7ae725fd5
+size 796014
diff --git a/lib/search/indexes/github-docs-ghec-pt.json.br b/lib/search/indexes/github-docs-ghec-pt.json.br
index c5e0cd2b67..9ba1db69a2 100644
--- a/lib/search/indexes/github-docs-ghec-pt.json.br
+++ b/lib/search/indexes/github-docs-ghec-pt.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:a152e0be94ae0b1f2d37600e85c1b7060963ef9483b57de0ee684a8297522543
-size 3272001
+oid sha256:3591e3232239178ca55a380ba6169406d9b6bbe1e477844aacc19a438ad62944
+size 3274151
diff --git a/package-lock.json b/package-lock.json
index b32bf4ad71..3337f44814 100644
--- a/package-lock.json
+++ b/package-lock.json
@@ -82,7 +82,7 @@
         "slash": "^4.0.0",
         "strip-html-comments": "^1.0.0",
         "styled-components": "^5.3.3",
-        "swr": "1.2.2",
+        "swr": "1.3.0",
         "ts-dedent": "^2.2.0",
         "unified": "^10.1.0",
         "unist-util-visit": "^4.1.0",
@@ -21115,9 +21115,9 @@
       }
     },
     "node_modules/swr": {
-      "version": "1.2.2",
-      "resolved": "https://registry.npmjs.org/swr/-/swr-1.2.2.tgz",
-      "integrity": "sha512-ky0BskS/V47GpW8d6RU7CPsr6J8cr7mQD6+do5eky3bM0IyJaoi3vO8UhvrzJaObuTlGhPl2szodeB2dUd76Xw==",
+      "version": "1.3.0",
+      "resolved": "https://registry.npmjs.org/swr/-/swr-1.3.0.tgz",
+      "integrity": "sha512-dkghQrOl2ORX9HYrMDtPa7LTVHJjCTeZoB1dqTbnnEDlSvN8JEKpYIYurDfvbQFUUS8Cg8PceFVZNkW0KNNYPw==",
       "peerDependencies": {
         "react": "^16.11.0 || ^17.0.0 || ^18.0.0"
       }
@@ -38980,9 +38980,9 @@
       }
     },
     "swr": {
-      "version": "1.2.2",
-      "resolved": "https://registry.npmjs.org/swr/-/swr-1.2.2.tgz",
-      "integrity": "sha512-ky0BskS/V47GpW8d6RU7CPsr6J8cr7mQD6+do5eky3bM0IyJaoi3vO8UhvrzJaObuTlGhPl2szodeB2dUd76Xw==",
+      "version": "1.3.0",
+      "resolved": "https://registry.npmjs.org/swr/-/swr-1.3.0.tgz",
+      "integrity": "sha512-dkghQrOl2ORX9HYrMDtPa7LTVHJjCTeZoB1dqTbnnEDlSvN8JEKpYIYurDfvbQFUUS8Cg8PceFVZNkW0KNNYPw==",
       "requires": {}
     },
     "symbol-tree": {
diff --git a/package.json b/package.json
index b4b9dfa09f..354a8996f8 100644
--- a/package.json
+++ b/package.json
@@ -84,7 +84,7 @@
     "slash": "^4.0.0",
     "strip-html-comments": "^1.0.0",
     "styled-components": "^5.3.3",
-    "swr": "1.2.2",
+    "swr": "1.3.0",
     "ts-dedent": "^2.2.0",
     "unified": "^10.1.0",
     "unist-util-visit": "^4.1.0",
diff --git a/tests/browser/browser.js b/tests/browser/browser.js
index 55eba3218f..a89ee2e75b 100644
--- a/tests/browser/browser.js
+++ b/tests/browser/browser.js
@@ -17,15 +17,6 @@ describe('homepage', () => {
 describe('browser search', () => {
   jest.setTimeout(60 * 1000)
 
-  it('works on the homepage', async () => {
-    await page.goto('http://localhost:4000/en')
-    await page.click('[data-testid=site-search-input]')
-    await page.type('[data-testid=site-search-input]', 'actions')
-    await page.waitForSelector('[data-testid=search-results]')
-    const hits = await page.$$('[data-testid=search-result]')
-    expect(hits.length).toBeGreaterThan(5)
-  })
-
   it('works on mobile landing pages', async () => {
     await page.goto('http://localhost:4000/en/actions')
     await page.click('[data-testid=mobile-menu-button]')
diff --git a/tests/rendering/server.js b/tests/rendering/server.js
index aab3c7f5e6..c9634f9459 100644
--- a/tests/rendering/server.js
+++ b/tests/rendering/server.js
@@ -968,20 +968,6 @@ describe('search', () => {
   function findDupesInArray(arr) {
     return lodash.filter(arr, (val, i, iteratee) => lodash.includes(iteratee, val, i + 1))
   }
-
-  it('homepage does not render any elements with duplicate IDs', async () => {
-    const $ = await getDOM('/en')
-    const ids = $('body')
-      .find('[id]')
-      .map((i, el) => $(el).attr('id'))
-      .get()
-      .sort()
-    const dupes = findDupesInArray(ids)
-    const message = `Oops found duplicate DOM id(s): ${dupes.join(', ')}`
-    expect(ids.length).toBeGreaterThan(0)
-    expect(dupes.length === 0, message).toBe(true)
-  })
-
   // SKIPPING: Can we have duplicate IDs? search-input-container and search-results-container are duplicated for mobile and desktop
   // Docs Engineering issue: 969
   it.skip('articles pages do not render any elements with duplicate IDs', async () => {
diff --git a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/about-your-organizations-profile.md b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/about-your-organizations-profile.md
index 3aeb3ec964..4d49a93bf7 100644
--- a/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/about-your-organizations-profile.md
+++ b/translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/about-your-organizations-profile.md
@@ -16,12 +16,12 @@ topics:
 shortTitle: Perfil de la organización
 ---
 
-You can optionally choose to add a description, location, website, and email address for your organization, and pin important repositories.{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-4749 %} You can customize your organization's public profile by adding a README.md file. Para obtener más información, consulta la sección "[Personalizar el perfil de tu organización ](/organizations/collaborating-with-groups-in-organizations/customizing-your-organizations-profile)".{% endif %}
+Opcionalmente, puedes elegir agregar una descripción, ubicación, sitio web y dirección de correo electrónico para tu organización y fijar los repositorios importantes.{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-4749 %} Puedes personalizar el perfil público de tu organización agregando un archivo README.md. Para obtener más información, consulta la sección "[Personalizar el perfil de tu organización ](/organizations/collaborating-with-groups-in-organizations/customizing-your-organizations-profile)".{% endif %}
 
 {% ifversion fpt %}
-Organizations that use {% data variables.product.prodname_ghe_cloud %} can confirm their organization's identity and display a "Verified" badge on their organization's profile page by verifying the organization's domains with {% data variables.product.product_name %}. For more information, see "[Verifying or approving a domain for your organization](/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization)" in the {% data variables.product.prodname_ghe_cloud %} documenatation.
+Las organizaciones que utilizan {% data variables.product.prodname_ghe_cloud %} pueden confirmar la identidad de la organización y mostrar una insignia de "Verificado" en la página de perfil de la misma si verifican los dominios de la organización con {% data variables.product.product_name %}. Para obtener más información, consulta la sección "[Verificar o aprobar un dominio para tu organización](/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization)" en la documentación de {% data variables.product.prodname_ghe_cloud %}.
 {% elsif ghec or ghes > 3.1 %}
-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 %}. Para obtener más información, consulta la sección "[Verificar o aprobar un dominio para tu organización](/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization)."
+Para confirmar la identidad de tu organización y mostrar una insignia de "Verificado" en su página de perfil, puedes verificar sus dominios con {% data variables.product.prodname_dotcom %}. Para obtener más información, consulta la sección "[Verificar o aprobar un dominio para tu organización](/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization)."
 {% endif %}
 
 {% ifversion fpt or ghes > 3.2 or ghec %}
diff --git a/translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-java-with-gradle.md b/translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-java-with-gradle.md
index 3f35990feb..8b964db3d0 100644
--- a/translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-java-with-gradle.md
+++ b/translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-java-with-gradle.md
@@ -22,7 +22,7 @@ shortTitle: Crear & probar con Java & Gradle
 
 ## Introducción
 
-Esta guía te muestra cómo crear un flujo de trabajo que realiza la integración continua (CI) para tu proyecto Java usando el sistema de construcción Gradle. El flujo de trabajo que creas te permitirá ver cuándo las confirmaciones de una solicitud de extracción causan la construcción o las fallas de prueba en tu rama por defecto; este enfoque puede ayudar a garantizar que tu código siempre sea correcto. You can extend your CI workflow to {% if actions-caching %}cache files and{% endif %} upload artifacts from a workflow run.
+Esta guía te muestra cómo crear un flujo de trabajo que realiza la integración continua (CI) para tu proyecto Java usando el sistema de construcción Gradle. El flujo de trabajo que creas te permitirá ver cuándo las confirmaciones de una solicitud de extracción causan la construcción o las fallas de prueba en tu rama por defecto; este enfoque puede ayudar a garantizar que tu código siempre sea correcto. Puedes extender tu flujo de trabajo de IC para {% if actions-caching %}guardar archivos en caché y{% endif %} cargar los artefactos desde una ejecución de flujo de trabajo.
 
 {% ifversion ghae %}
 {% data reusables.actions.self-hosted-runners-software %}
@@ -114,7 +114,7 @@ steps:
 
 ## Almacenar dependencias en caché
 
-Your build dependencies can be cached to speed up your workflow runs. Después de una ejecución exitosa, la `gradle/gradle-build-action` guarda en caché las partes importantes del directorio principal del usuario de Gradle. En los jobs futuros, el caché se restablecerá para que los scripts de compilación no necesiten recompilarse y las dependencias no necesiten descargarse desde los repositorios de paquetes remotos.
+Tus dependencias de compilación se pueden guardar en caché para acelerar tus ejecuciones de flujo de trabajo. Después de una ejecución exitosa, la `gradle/gradle-build-action` guarda en caché las partes importantes del directorio principal del usuario de Gradle. En los jobs futuros, el caché se restablecerá para que los scripts de compilación no necesiten recompilarse y las dependencias no necesiten descargarse desde los repositorios de paquetes remotos.
 
 El almacenamiento en caché se habilita predeterminadamente cuando se utiliza la acción `gradle/gradle-build-action`. Para obtener más información, consulta [`gradle/gradle-build-action`](https://github.com/gradle/gradle-build-action#caching).
 
diff --git a/translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-java-with-maven.md b/translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-java-with-maven.md
index 50665caa04..9248172dd6 100644
--- a/translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-java-with-maven.md
+++ b/translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-java-with-maven.md
@@ -22,7 +22,7 @@ shortTitle: Crear & probar en Java con Maven
 
 ## Introducción
 
-Esta guía te muestra cómo crear un flujo de trabajo que realiza la integración continua (CI) para tu proyecto Java utilizando la herramienta de gestión de proyectos de software Maven. El flujo de trabajo que creas te permitirá ver cuándo las confirmaciones de una solicitud de extracción causan la construcción o las fallas de prueba en tu rama por defecto; este enfoque puede ayudar a garantizar que tu código siempre sea correcto. You can extend your CI workflow to {% if actions-caching %}cache files and{% endif %} upload artifacts from a workflow run.
+Esta guía te muestra cómo crear un flujo de trabajo que realiza la integración continua (CI) para tu proyecto Java utilizando la herramienta de gestión de proyectos de software Maven. El flujo de trabajo que creas te permitirá ver cuándo las confirmaciones de una solicitud de extracción causan la construcción o las fallas de prueba en tu rama por defecto; este enfoque puede ayudar a garantizar que tu código siempre sea correcto. Puedes extender tu flujo de trabajo de IC para {% if actions-caching %}guardar archivos en caché y{% endif %} cargar los artefactos desde una ejecución de flujo de trabajo.
 
 {% ifversion ghae %}
 {% data reusables.actions.self-hosted-runners-software %}
diff --git a/translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-nodejs.md b/translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-nodejs.md
index 3f07f34fbc..fb54eda4ef 100644
--- a/translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-nodejs.md
+++ b/translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-nodejs.md
@@ -134,7 +134,7 @@ Si no especificas una versión de Node.js, {% data variables.product.prodname_do
 
 Los ejecutores alojados en {% data variables.product.prodname_dotcom %} tienen instalados administradores de dependencias de npm y Yarn. Puedes usar npm y Yarn para instalar dependencias en tu flujo de trabajo antes de construir y probar tu código. Los ejecutores Windows y Linux alojados en {% data variables.product.prodname_dotcom %} también tienen instalado Grunt, Gulp y Bower.
 
-{% if actions-caching %}You can also cache dependencies to speed up your workflow. For more information, see "[Caching dependencies to speed up workflows](/actions/using-workflows/caching-dependencies-to-speed-up-workflows)."{% endif %}
+{% if actions-caching %}también puedes guardar las dependencias en caché para acelerar tu flujo de trabajo. Para obtener más información, consulta la sección "[Almacenar las dependencias en caché para agilizar los flujos de trabajo](/actions/using-workflows/caching-dependencies-to-speed-up-workflows)".{% endif %}
 
 ### Ejemplo con npm
 
@@ -179,7 +179,7 @@ steps:
   run: yarn
 ```
 
-Alternatively, you can pass `--frozen-lockfile` to install the versions in the `yarn.lock` file and prevent updates to the `yarn.lock` file.
+Como alternativa, puedes pasar `--frozen-lockfile` para instalar las versiones en el archivo `yarn.lock` y prevenir las actualizaciones al archivo `yarn.lock`.
 
 ```yaml{:copy}
 steps:
@@ -230,7 +230,7 @@ always-auth=true
 
 ### Ejemplo de dependencias en caché
 
-You can cache and restore the dependencies using the [`setup-node` action](https://github.com/actions/setup-node).
+Puedes guardar en caché y restablecer las dependencias utilizando la [acción `setup-node`](https://github.com/actions/setup-node).
 
 El siguiente ejemplo guarda las dependencias en caché para npm.
 
diff --git a/translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-ruby.md b/translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-ruby.md
index bf942102c4..d75f0514c7 100644
--- a/translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-ruby.md
+++ b/translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-ruby.md
@@ -148,7 +148,7 @@ steps:
 
 ### Almacenar dependencias en caché
 
-The `setup-ruby` actions provides a method to automatically handle the caching of your gems between runs.
+La acción `setup-ruby` proporciona un método para manejar automáticamente el almacenamiento en caché de tus gemas entre ejecuciones.
 
 Para habilitar el guardado en caché, configura lo siguiente.
 
@@ -161,11 +161,11 @@ steps:
 ```
 {% endraw %}
 
-Esto configurará a bundler para que instale tus gemas en `vendor/cache`. For each successful run of your workflow, this folder will be cached by {% data variables.product.prodname_actions %} and re-downloaded for subsequent workflow runs. Se utiliza un hash de tu gemfile.lock y de la versión de Ruby como la clave de caché. Si instalas cualquier gema nueva o cambias una versión, el caché se invalidará y bundler realizará una instalación desde cero.
+Esto configurará a bundler para que instale tus gemas en `vendor/cache`. Para cada ejecución exitosa de tu flujo de trabajo, {% data variables.product.prodname_actions %} almacenará esta carpeta en caché y volverá a descargarla para ejecuciones de flujo de trabajo posteriores. Se utiliza un hash de tu gemfile.lock y de la versión de Ruby como la clave de caché. Si instalas cualquier gema nueva o cambias una versión, el caché se invalidará y bundler realizará una instalación desde cero.
 
 **Guardar en caché sin setup-ruby**
 
-For greater control over caching, you can use the `actions/cache` action directly. Para obtener más información, consulta la sección "[Almacenar las dependencias en caché para agilizar los flujos de trabajo](/actions/using-workflows/caching-dependencies-to-speed-up-workflows)".
+Para tener un mejor control sobre el almacenamiento en caché, puedes utilizar la acción de `actions/cache` directamente. Para obtener más información, consulta la sección "[Almacenar las dependencias en caché para agilizar los flujos de trabajo](/actions/using-workflows/caching-dependencies-to-speed-up-workflows)".
 
 ```yaml
 steps:
diff --git a/translations/es-ES/content/actions/creating-actions/metadata-syntax-for-github-actions.md b/translations/es-ES/content/actions/creating-actions/metadata-syntax-for-github-actions.md
index 48a2553ec4..f623ccb66c 100644
--- a/translations/es-ES/content/actions/creating-actions/metadata-syntax-for-github-actions.md
+++ b/translations/es-ES/content/actions/creating-actions/metadata-syntax-for-github-actions.md
@@ -88,6 +88,8 @@ Por ejemplo, si un flujo de trabajo definió las entradas de `numOctocats` y `oc
 
 **Opcional** Los parámetros de salida te permiten declarar datos que una acción establece. Las acciones que se ejecutan más tarde en un flujo de trabajo pueden usar el conjunto de datos de salida en acciones de ejecución anterior.  Por ejemplo, si tuviste una acción que realizó la adición de dos entradas (x + y = z), la acción podría dar como resultado la suma (z) para que otras acciones la usen como entrada.
 
+{% data reusables.actions.output-limitations %}
+
 Si no declaras una salida en tu archivo de metadatos de acción, todavía puedes configurar las salidas y utilizarlas en un flujo de trabajo. Para obtener más información acerca de la configuración de salidas en una acción, consulta "[Comandos de flujo de trabajo para {% data variables.product.prodname_actions %}](/actions/reference/workflow-commands-for-github-actions/#setting-an-output-parameter)".
 
 ### Ejemplo: Declarar las salidas para las acciones de contenedores de Docker y JavaScript
@@ -110,6 +112,8 @@ outputs:
 
 Las `outputs` **opcionales** utilizan los mismos parámetros que `outputs.<output_id>` y `outputs.<output_id>.description` (consulta la sección de "[`outputs` para acciones de contenedores de Docker y JavaScript](#outputs-for-docker-container-and-javascript-actions)"), pero también incluye el token `value`.
 
+{% data reusables.actions.output-limitations %}
+
 ### Ejemplo: Declarar las salidas para las acciones compuestas
 
 {% raw %}
diff --git a/translations/es-ES/content/actions/deployment/about-deployments/deploying-with-github-actions.md b/translations/es-ES/content/actions/deployment/about-deployments/deploying-with-github-actions.md
index 0f1b28a8b6..e6deccdee7 100644
--- a/translations/es-ES/content/actions/deployment/about-deployments/deploying-with-github-actions.md
+++ b/translations/es-ES/content/actions/deployment/about-deployments/deploying-with-github-actions.md
@@ -156,7 +156,7 @@ También puedes crear una app que utilice despliegues y webhooks de estados de d
 
 ## Elegir un ejecutor
 
-Puedes ejecutar tu flujo de trabajo de despliegue en los ejecutores hospedados en {% data variables.product.company_short %} o en los auto-hospedados. El tráfico de los ejecutores hospedados en {% data variables.product.company_short %} puede venir desde un [rango amplio de direcciones de red](/rest/reference/meta#get-github-meta-information). If you are deploying to an internal environment and your company restricts external traffic into private networks, {% data variables.product.prodname_actions %} workflows running on {% data variables.product.company_short %}-hosted runners may not be able to communicate with your internal services or resources. Para superar esto, puedes hospedar tus propios ejecutores. Para obtener más información, consulta las secciones "[Acerca de los ejecutores auto-hospedados](/actions/hosting-your-own-runners/about-self-hosted-runners)" y "[Acercad e los ejecutores hospedados en GitHub](/actions/using-github-hosted-runners/about-github-hosted-runners)".
+Puedes ejecutar tu flujo de trabajo de despliegue en los ejecutores hospedados en {% data variables.product.company_short %} o en los auto-hospedados. El tráfico de los ejecutores hospedados en {% data variables.product.company_short %} puede venir desde un [rango amplio de direcciones de red](/rest/reference/meta#get-github-meta-information). Si estás desplegando hacia un ambiente interno y tu empresa restringe el tráfico externo en las redes privadas, los flujos de trabajo de {% data variables.product.prodname_actions %} que se ejecutan en los ejecutores hospedados en {% data variables.product.company_short %} podrían no tener la capacidad de comunicarse con tus recursos o servicios internos. Para superar esto, puedes hospedar tus propios ejecutores. Para obtener más información, consulta las secciones "[Acerca de los ejecutores auto-hospedados](/actions/hosting-your-own-runners/about-self-hosted-runners)" y "[Acercad e los ejecutores hospedados en GitHub](/actions/using-github-hosted-runners/about-github-hosted-runners)".
 
 {% endif %}
 
diff --git a/translations/es-ES/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-nodejs-to-azure-app-service.md b/translations/es-ES/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-nodejs-to-azure-app-service.md
index 80527d4667..fdf2d98c93 100644
--- a/translations/es-ES/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-nodejs-to-azure-app-service.md
+++ b/translations/es-ES/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-nodejs-to-azure-app-service.md
@@ -134,4 +134,4 @@ Los siguientes recursos también pueden ser útiles:
 * Para encontrar el flujo de trabajo inicial original, consulta el archivo [`azure-webapps-node.yml`](https://github.com/actions/starter-workflows/blob/main/deployments/azure-webapps-node.yml) en el repositorio `starter-workflows` de {% data variables.product.prodname_actions %}.
 * La acción que se utilizó para desplegar la app web es la acción oficial [`Azure/webapps-deploy`](https://github.com/Azure/webapps-deploy) de Azure.
 * Para encontrar más ejemplos de flujos de trabajo de GitHub Actions que desplieguen a Azure, consulta el repositorio [actions-workflow-samples](https://github.com/Azure/actions-workflow-samples).
-* The "[Create a Node.js web app in Azure](https://docs.microsoft.com/azure/app-service/quickstart-nodejs)" quickstart in the Azure web app documentation demonstrates using {% data variables.product.prodname_vscode %} with the [Azure App Service extension](https://marketplace.visualstudio.com/items?itemName=ms-azuretools.vscode-azureappservice).
+* La guía de inicio rápido de "[Crear una app web con Node.js en Azure](https://docs.microsoft.com/azure/app-service/quickstart-nodejs)" en la documentación de la app web de Azure demuestra cómo se utiliza {% data variables.product.prodname_vscode %} con la [extensión de servicio de la app de Azure](https://marketplace.visualstudio.com/items?itemName=ms-azuretools.vscode-azureappservice).
diff --git a/translations/es-ES/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-google-cloud-platform.md b/translations/es-ES/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-google-cloud-platform.md
index d8a3ad0908..c6a511802b 100644
--- a/translations/es-ES/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-google-cloud-platform.md
+++ b/translations/es-ES/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-google-cloud-platform.md
@@ -40,7 +40,7 @@ Orientación adicional para configurar el proveedor de identidad:
 
 - Para fortalecer la seguridad, asegúrate de haber revisado la sección ["Configurar la confianza de OIDC con la nube"](/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect#configuring-the-oidc-trust-with-the-cloud). Por ejemplo, consulta ["Configurar el tema en tu proveedor de servicios en la nube"](/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect#configuring-the-subject-in-your-cloud-provider).
 - Para que la cuenta de servicio esté disponible para su configuración, esta necesita estar asignada al rol `roles/iam.workloadIdentityUser`. Para obtener más información, consulta la "[Documentación de GCP](https://cloud.google.com/iam/docs/workload-identity-federation?_ga=2.114275588.-285296507.1634918453#conditions)".
-- The Issuer URL to use: {% ifversion ghes %}`https://HOSTNAME/_services/token`{% else %}`https://token.actions.githubusercontent.com`{% endif %}
+- La URL del emisor a utilizar: {% ifversion ghes %}`https://HOSTNAME/_services/token`{% else %}`https://token.actions.githubusercontent.com`{% endif %}
 
 ## Actualizar tu flujo de trabajo de {% data variables.product.prodname_actions %}
 
diff --git a/translations/es-ES/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-hashicorp-vault.md b/translations/es-ES/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-hashicorp-vault.md
index 879d2b60bb..decbb3fdfb 100644
--- a/translations/es-ES/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-hashicorp-vault.md
+++ b/translations/es-ES/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-hashicorp-vault.md
@@ -33,8 +33,8 @@ Esta guía te proporciona un resumen de cómo configurar HashiCorp Vault para qu
 Para utilizar OIDC con HashiCorp Vault, necesitarás agregar una configuración de confianza para el proveedor de OIDC de {% data variables.product.prodname_dotcom %}. Para obtener más información, consulta la [documentación](https://www.vaultproject.io/docs/auth/jwt) de HashiCorp Vault.
 
 Configura la bóveda para que acepte Tokens Web JSON (JWT) para la autenticación:
-- For the `oidc_discovery_url`, use {% ifversion ghes %}`https://HOSTNAME/_services/token`{% else %}`https://token.actions.githubusercontent.com`{% endif %}
-- For `bound_issuer`, use {% ifversion ghes %}`https://HOSTNAME/_services/token`{% else %}`https://token.actions.githubusercontent.com`{% endif %}
+- Para el `oidc_discovery_url`, utiliza {% ifversion ghes %}`https://HOSTNAME/_services/token`{% else %}`https://token.actions.githubusercontent.com`{% endif %}
+- Para `bound_issuer`, utiliza {% ifversion ghes %}`https://HOSTNAME/_services/token`{% else %}`https://token.actions.githubusercontent.com`{% endif %}
 - Asegúrate de que `bound_subject` se defina correctamente para tus requisitos de seguridad. Para obtener más información, consulta la sección ["Configurar la confianza de OIDC con la nube"](/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect#configuring-the-oidc-trust-with-the-cloud) y [`hashicorp/vault-action`](https://github.com/hashicorp/vault-action).
 
 ## Actualizar tu flujo de trabajo de {% data variables.product.prodname_actions %}
diff --git a/translations/es-ES/content/actions/deployment/targeting-different-environments/using-environments-for-deployment.md b/translations/es-ES/content/actions/deployment/targeting-different-environments/using-environments-for-deployment.md
index f89fe9dd90..1c1b566953 100644
--- a/translations/es-ES/content/actions/deployment/targeting-different-environments/using-environments-for-deployment.md
+++ b/translations/es-ES/content/actions/deployment/targeting-different-environments/using-environments-for-deployment.md
@@ -74,7 +74,7 @@ Los secretos que se almacenan en un ambiente sólo se encuentran disponibles par
 {% ifversion fpt or ghec %}
 {% note %}
 
-**Note:** To create an environment in a private repository, your organization must use {% data variables.product.prodname_ghe_cloud %}. {% data reusables.enterprise.link-to-ghec-trial %}
+**Nota:** Para crear un ambiente en un repositorio privado, tu organización debe utilizar {% data variables.product.prodname_ghe_cloud %}. {% data reusables.enterprise.link-to-ghec-trial %}
 
 {% endnote %}
 {% endif %}
diff --git a/translations/es-ES/content/actions/learn-github-actions/expressions.md b/translations/es-ES/content/actions/learn-github-actions/expressions.md
index 562e342fe2..369d815ac8 100644
--- a/translations/es-ES/content/actions/learn-github-actions/expressions.md
+++ b/translations/es-ES/content/actions/learn-github-actions/expressions.md
@@ -368,7 +368,7 @@ Por ejemplo, considera una matriz de objetos llamada `fruits`.
 
 El filtro `fruits.*.name` devuelve la matriz `[ "apple", "orange", "pear" ]`.
 
-You may also use the `*` syntax on an object. For example, suppose you have an object named `vegetables`.
+También puedes utilizar la sintaxis `*` en un objeto. Por ejemplo, supón que tienes un objeto que se llama `vegetables`.
 
 ```json
 
@@ -391,7 +391,7 @@ You may also use the `*` syntax on an object. For example, suppose you have an o
 }
 ```
 
-The filter `vegetables.*.ediblePortions` could evaluate to:
+El filtro `vegetables.*.ediblePortions` puede evaluarse como:
 
 ```json
 
@@ -402,4 +402,4 @@ The filter `vegetables.*.ediblePortions` could evaluate to:
 ]
 ```
 
-Since objects don't preserve order, the order of the output can not be guaranteed.
+Ya que los objetos no preservan el orden, el orden de salida no se puede garantizar.
diff --git a/translations/es-ES/content/actions/managing-issues-and-pull-requests/moving-assigned-issues-on-project-boards.md b/translations/es-ES/content/actions/managing-issues-and-pull-requests/moving-assigned-issues-on-project-boards.md
index e81fd64b81..e792669b3a 100644
--- a/translations/es-ES/content/actions/managing-issues-and-pull-requests/moving-assigned-issues-on-project-boards.md
+++ b/translations/es-ES/content/actions/managing-issues-and-pull-requests/moving-assigned-issues-on-project-boards.md
@@ -63,7 +63,7 @@ En el tutorial, primero crearás un archivo de flujo de trabajo que utilice la [
 
 Cada vez que se asigne una propuesta en tu repositorio, dicha propuesta se moverá al tablero de proyecto especificado. Si la propuesta no estaba ya en el tablero de proyecto, se agregará a este.
 
-If your repository is user-owned, the `alex-page/github-project-automation-plus` action will act on all projects in your repository or personal account that have the specified project name and column. De la misma forma, si tu repositorio pertenece a una organización, la acción actuará en todos los poryectos de tu repositorio u organización que tengan el nombre y columna especificadas.
+Si tu repositorio le pertenece a un usuario, la acción `alex-page/github-project-automation-plus` actuará en todos los proyectos de tu repositorio o cuenta personal que tengan el nombre de proyecto y columna específicos. De la misma forma, si tu repositorio pertenece a una organización, la acción actuará en todos los poryectos de tu repositorio u organización que tengan el nombre y columna especificadas.
 
 Prueba tu flujo de trabajo asignando una propuesta en tu repositorio.
 
diff --git a/translations/es-ES/content/actions/managing-workflow-runs/skipping-workflow-runs.md b/translations/es-ES/content/actions/managing-workflow-runs/skipping-workflow-runs.md
index 54142d6e9f..7e89c0b0fb 100644
--- a/translations/es-ES/content/actions/managing-workflow-runs/skipping-workflow-runs.md
+++ b/translations/es-ES/content/actions/managing-workflow-runs/skipping-workflow-runs.md
@@ -14,7 +14,7 @@ shortTitle: Omitir ejecuciones de flujo de trabajo
 
 {% note %}
 
-**Note:** If a workflow is skipped due to [path filtering](/actions/using-workflows/workflow-syntax-for-github-actions#onpushpull_requestpull_request_targetpathspaths-ignore), [branch filtering](/actions/using-workflows/workflow-syntax-for-github-actions#onpull_requestpull_request_targetbranchesbranches-ignore) or a commit message (see below), then checks associated with that workflow will remain in a "Pending" state. A pull request that requires those checks to be successful will be blocked from merging.
+**Nota:** Si un flujo de trabajo se omite debido a un [filtrado de ruta](/actions/using-workflows/workflow-syntax-for-github-actions#onpushpull_requestpull_request_targetpathspaths-ignore), [filtrado de rama](/actions/using-workflows/workflow-syntax-for-github-actions#onpull_requestpull_request_targetbranchesbranches-ignore) o a un mensaje de confirmación (consultar a continuación), entonces las verificaciones asociadas con dicho flujo de trabajo permanecerán en un estado de "Pendiente". Las solicitudes de cambios que requieran que esas verificaciones tengan éxito quedarán bloqueadas para fusión.
 
 {% endnote %}
 
diff --git a/translations/es-ES/content/actions/migrating-to-github-actions/migrating-from-travis-ci-to-github-actions.md b/translations/es-ES/content/actions/migrating-to-github-actions/migrating-from-travis-ci-to-github-actions.md
index 39504c57ce..22705ca730 100644
--- a/translations/es-ES/content/actions/migrating-to-github-actions/migrating-from-travis-ci-to-github-actions.md
+++ b/translations/es-ES/content/actions/migrating-to-github-actions/migrating-from-travis-ci-to-github-actions.md
@@ -59,9 +59,9 @@ Travis CI puede utilizar `stages` para ejecutar jobs en paralelo. De forma simil
 
 Tanto Travis CI como {% data variables.product.prodname_actions %} son compatibles con las insignias de estado, lo cual te permite indicar si una compilación pasa o falla. Para obtener más información, consulta la sección "[Agregar una insignia de estado de un flujo de trabajo a tu repositorio](/actions/managing-workflow-runs/adding-a-workflow-status-badge)".
 
-### Using a matrix
+### Utilizar una matriz
 
-Travis CI and {% data variables.product.prodname_actions %} both support a matrix, allowing you to perform testing using combinations of operating systems and software packages. For more information, see "[Using a matrix for your jobs](/actions/using-jobs/using-a-matrix-for-your-jobs)."
+Tanto Travis CI como {% data variables.product.prodname_actions %} son compatibles con una matriz, lo cual te permite llevar a cabo pruebas utilizando combinaciones de sistemas operativos y paquetes de software. Para obtener más información, consulta la sección "[Utilizar una matriz para tus jobs](/actions/using-jobs/using-a-matrix-for-your-jobs)".
 
 A continuación podrás encontrar un ejemplo que compara la sintaxis para cada sistema:
 
diff --git a/translations/es-ES/content/actions/publishing-packages/publishing-docker-images.md b/translations/es-ES/content/actions/publishing-packages/publishing-docker-images.md
index 316dd918f0..e3af43af3b 100644
--- a/translations/es-ES/content/actions/publishing-packages/publishing-docker-images.md
+++ b/translations/es-ES/content/actions/publishing-packages/publishing-docker-images.md
@@ -114,10 +114,10 @@ El flujo de trabajo anterior verifica el repositorio de {% data variables.produc
 
 {% data reusables.actions.release-trigger-workflow %}
 
-In the example workflow below, we use the Docker `login-action`{% ifversion fpt or ghec %}, `metadata-action`,{% endif %} and `build-push-action` actions to build the Docker image, and if the build succeeds, push the built image to {% data variables.product.prodname_registry %}.
+En el siguiente ejemplo de flujo de trabajo, utilizamos las acciones `login-action` {% ifversion fpt or ghec %}, `metadata-action`,{% endif %} y `build-push-action` de Docker para crear la imagen de Docker y, si la compilación tiene éxito, sube la imagen cargada al {% data variables.product.prodname_registry %}.
 
 Las opciones de `login-action` que se requieren para el {% data variables.product.prodname_registry %} son:
-* `registry`: Must be set to {% ifversion fpt or ghec %}`ghcr.io`{% elsif ghes > 3.4 %}`{% data reusables.package_registry.container-registry-hostname %}`{% else %}`docker.pkg.github.com`{% endif %}.
+* `registry`: Debe configurarse en {% ifversion fpt or ghec %}`ghcr.io`{% elsif ghes > 3.4 %}`{% data reusables.package_registry.container-registry-hostname %}`{% else %}`docker.pkg.github.com`{% endif %}.
 * `username`: Puedes utilizar el contexto {% raw %}`${{ github.actor }}`{% endraw %} para utilizar automáticamente el nombre de usuario del usuario que desencadenó la ejecución del flujo de trabajo. Para obtener más información, consulta "[Contextos](/actions/learn-github-actions/contexts#github-context)".
 * `password`: Puedes utilizar el secreto generado automáticamente `GITHUB_TOKEN` para la contraseña. Para más información, consulta "[Autenticando con el GITHUB_TOKEN](/actions/automating-your-workflow-with-github-actions/authenticating-with-the-github_token)."
 
@@ -126,15 +126,15 @@ La opción de `metadata-action` que se requiere para el {% data variables.produc
 * `images`: El designador de nombre de la imagen de Docker que estás compilando.
 {% endif %}
 
-The `build-push-action` options required for {% data variables.product.prodname_registry %} are:{% ifversion fpt or ghec %}
+Las opciones de `build-push-action` requeridas para el {% data variables.product.prodname_registry %} son:{% ifversion fpt or ghec %}
 * `context`: Define el contexto de la compilación como el conjunto de archivos que se ubican en la ruta especificada.{% endif %}
 * `push`: Si se configura en `true`, la imagen se cargará al registro si se compila con éxito.{% ifversion fpt or ghec %}
 * `tags` y `labels`: Estos se llenan con la salida de la `metadata-action`.{% else %}
-* `tags`: Must be set in the format {% ifversion ghes > 3.4 %}`{% data reusables.package_registry.container-registry-hostname %}/OWNER/REPOSITORY/IMAGE_NAME:VERSION`.
+* `tags`: Debe configurarse en el formato {% ifversion ghes > 3.4 %}`{% data reusables.package_registry.container-registry-hostname %}/OWNER/REPOSITORY/IMAGE_NAME:VERSION`.
 
-   For example, for an image named `octo-image` stored on {% data variables.product.prodname_ghe_server %} at `https://HOSTNAME/octo-org/octo-repo`, the `tags` option should be set to `{% data reusables.package_registry.container-registry-hostname %}/octo-org/octo-repo/octo-image:latest`{% else %}`docker.pkg.github.com/OWNER/REPOSITORY/IMAGE_NAME:VERSION`.
+   Por ejemplo, para una imagen que se llama `octo-image` y se almacena en {% data variables.product.prodname_ghe_server %} en `https://HOSTNAME/octo-org/octo-repo`, la opción de `tags` debe configurarse como `{% data reusables.package_registry.container-registry-hostname %}/octo-org/octo-repo/octo-image:latest`{% else %}`docker.pkg.github.com/OWNER/REPOSITORY/IMAGE_NAME:VERSION`.
 
-   For example, for an image named `octo-image` stored on {% data variables.product.prodname_dotcom %} at `http://github.com/octo-org/octo-repo`, the `tags` option should be set to `docker.pkg.github.com/octo-org/octo-repo/octo-image:latest`{% endif %}. Puedes configurar una tarjeta sencilla como se muestra a continuación o especificar etiquetas múltiples en una lista.{% endif %}
+   Por ejemplo, para el caso de una imagen que se llame `octo-image` y esté almacenada en {% data variables.product.prodname_dotcom %} en `http://github.com/octo-org/octo-repo`, la opción `tags` debe configurarse como `docker.pkg.github.com/octo-org/octo-repo/octo-image:latest`{% endif %}. Puedes configurar una tarjeta sencilla como se muestra a continuación o especificar etiquetas múltiples en una lista.{% endif %}
 
 {% ifversion fpt or ghec or ghes > 3.4 %}
 {% data reusables.package_registry.publish-docker-image %}
@@ -178,7 +178,7 @@ jobs:
             {% ifversion ghae %}docker.YOUR-HOSTNAME.com{% else %}docker.pkg.github.com{% endif %}{% raw %}/${{ github.repository }}/octo-image:${{ github.event.release.tag_name }}{% endraw %}
 ```
 
-The above workflow checks out the {% data variables.product.product_name %} repository, uses the `login-action` to log in to the registry, and then uses the `build-push-action` action to: build a Docker image based on your repository's `Dockerfile`; push the image to the Docker registry, and apply the commit SHA and release version as image tags.
+El flujo de trabajo anterior verifica el repositorio de {% data variables.product.product_name %}, utiliza la `login-action` para iniciar sesión en el registro y luego utiliza la acción `build-push-action` para: compilar una imagen de Docker con base en el `Dockerfile` de tu repositorio; subir la imagen al registro de Docker y aplicar el SHA de confirmación y versión de lanzamiento como etiquetas de imagen.
 {% endif %}
 
 ## Publicar imágenes en Docker Hub y en {% data variables.product.prodname_registry %}
@@ -241,4 +241,4 @@ jobs:
           labels: {% raw %}${{ steps.meta.outputs.labels }}{% endraw %}
 ```
 
-The above workflow checks out the {% data variables.product.product_name %} repository, uses the `login-action` twice to log in to both registries and generates tags and labels with the `metadata-action` action. Then the `build-push-action` action builds and pushes the Docker image to Docker Hub and the {% ifversion fpt or ghec or ghes > 3.4 %}{% data variables.product.prodname_container_registry %}{% else %}Docker registry{% endif %}.
+El flujo de trabajo anterior verifica el repositorio de {% data variables.product.product_name %}, utiliza `login-action` dos veces para iniciar sesión en ambos registros y genera etiquetas y marcadores con la acción `metadata-action`. Entonces, la acción `build-push-action` crea y sube la imagen de Docker a Docker Hub y al {% ifversion fpt or ghec or ghes > 3.4 %}{% data variables.product.prodname_container_registry %}{% else %}registro de Docker{% endif %}.
diff --git a/translations/es-ES/content/actions/security-guides/security-hardening-for-github-actions.md b/translations/es-ES/content/actions/security-guides/security-hardening-for-github-actions.md
index 73b09f3508..5ef8b89547 100644
--- a/translations/es-ES/content/actions/security-guides/security-hardening-for-github-actions.md
+++ b/translations/es-ES/content/actions/security-guides/security-hardening-for-github-actions.md
@@ -206,7 +206,7 @@ El mismo principio que se describió anteriormente para utilizar acciones de ter
 
 {% data reusables.actions.workflow-pr-approval-permissions-intro %} Allowing workflows, or any other automation, to {% if allow-actions-to-approve-pr-with-ent-repo %}create or {% endif %}approve pull requests could be a security risk if the pull request is merged without proper oversight.
 
-For more information on how to configure this setting, see {% if allow-actions-to-approve-pr-with-ent-repo %}{% ifversion ghes or ghec or ghae %}"[Enforcing policies for {% data variables.product.prodname_actions %} in your enterprise](/enterprise-cloud@latest/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise#preventing-github-actions-from-creating-or-approving-pull-requests)",{% endif %}{% endif %} "[Disabling or limiting {% data variables.product.prodname_actions %} for your organization](/github/setting-up-and-managing-organizations-and-teams/disabling-or-limiting-github-actions-for-your-organization#preventing-github-actions-from-{% if allow-actions-to-approve-pr-with-ent-repo %}creating-or-{% endif %}approving-pull-requests)"{% if allow-actions-to-approve-pr-with-ent-repo %}, and "[Managing {% data variables.product.prodname_actions %} settings for a repository](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#preventing-github-actions-from-creating-or-approving-pull-requests)"{% endif %}.
+Para obtener más información sobre cómo configurar este ajuste, consulta la secciones {% if allow-actions-to-approve-pr-with-ent-repo %}{% ifversion ghes or ghec or ghae %}"[Requerir políticas para las {% data variables.product.prodname_actions %} en tu empresa](/enterprise-cloud@latest/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise#preventing-github-actions-from-creating-or-approving-pull-requests)",{% endif %}{% endif %} "[Inhabilitar o limitar las {% data variables.product.prodname_actions %} para tu organización](/github/setting-up-and-managing-organizations-and-teams/disabling-or-limiting-github-actions-for-your-organization#preventing-github-actions-from-{% if allow-actions-to-approve-pr-with-ent-repo %}creating-or-{% endif %}approving-pull-requests)"{% if allow-actions-to-approve-pr-with-ent-repo %} y "[Administrar los ajustes de las {% data variables.product.prodname_actions %} para un repositorio](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#preventing-github-actions-from-creating-or-approving-pull-requests)"{% endif %}.
 {% endif %}
 
 ## Utilizar las tarjetas de puntuación para asegurar los flujos de trabajo
@@ -267,7 +267,7 @@ Esta lista describe los acercamientos recomendatos para acceder alos datos de un
     - Jamás debes utilizar tokens de acceso personal desde tu propia cuenta. These tokens grant access to all repositories within the organizations that you have access to, as well as all personal repositories in your personal account. Esto otorga indirectamente un acceso amplio a todos los usuarios con acceso de escritura en el repositorio en el cual está el flujo de trabajo. Adicionalmente, si sales de una organización más adelante, los flujos de trabajo que utilicen este token fallarán inmediatamente, y depurar este problema puede ser difícil.
     - Si se utiliza un token de acceso personal, debe ser uno que se haya generado para una cuenta nueva a la que solo se le haya otorgado acceso para los repositorios específicos que se requieren para el flujo de trabajo. Nota que este acercamiento no es escalable y debe evitarse para favorecer otras alternativas, tales como las llaves de despliegue.
 5. **SSH keys on a personal account**
-    - Workflows should never use the SSH keys on a personal account. De forma similar a los tokens de acceso personal, estas otorgan permisos de lectura/escritura a todos tus repositorios personales así como a todos los repositorios a los que tengas acceso mediante la membercía de organización.  Esto otorga indirectamente un acceso amplio a todos los usuarios con acceso de escritura en el repositorio en el cual está el flujo de trabajo. Si pretendes utilizar una llave SSH porque solo necesitas llevar a cabo clonados de repositorio o subidas a éste, y no necesitas interactuar con una API pública, entonces mejor deberías utilizar llaves de despliegue individuales.
+    - Los flujos de trabajo jamás deben utilizar las llaves SSH en una cuenta personal. De forma similar a los tokens de acceso personal, estas otorgan permisos de lectura/escritura a todos tus repositorios personales así como a todos los repositorios a los que tengas acceso mediante la membercía de organización.  Esto otorga indirectamente un acceso amplio a todos los usuarios con acceso de escritura en el repositorio en el cual está el flujo de trabajo. Si pretendes utilizar una llave SSH porque solo necesitas llevar a cabo clonados de repositorio o subidas a éste, y no necesitas interactuar con una API pública, entonces mejor deberías utilizar llaves de despliegue individuales.
 
 ## Fortalecimiento para los ejecutores auto-hospedados
 
@@ -308,7 +308,7 @@ Si estás utilizando las {% data variables.product.prodname_actions %} para desp
 
 ## Auditar eventos de {% data variables.product.prodname_actions %}
 
-Puedes utilizar la bitácora de auditoría para monitorear las tareas administrativas en una organización. The audit log records the type of action, when it was run, and which personal account performed the action.
+Puedes utilizar la bitácora de auditoría para monitorear las tareas administrativas en una organización. La bitácora de auditoría registra el tipo de acción, cuándo se ejecutó y qué cuenta personal la llevó a cabo.
 
 Por ejemplo, puedes utilizar la bitácora de auditoría para rastrear el evento `org.update_actions_secret`, el cual rastrea los cambios en los secretos de la organización: ![Entradas de la bitácora de auditoría](/assets/images/help/repository/audit-log-entries.png)
 
@@ -330,7 +330,7 @@ Las siguientes tablas describen los eventos de {% data variables.product.prodnam
 | Acción                                | Descripción                                                                                                                                                                                                                                                                                                                           |
 | ------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
 | `repo.actions_enabled`                | Se activa cuando {% data variables.product.prodname_actions %} se habilita en un repositorio. Puede visualizarse utilizando la IU. Este evento no es visible cuando accedes a la bitácora de auditoría utilizando la API de REST. Para obtener más información, consulta la sección "[Utilizar la API de REST](#using-the-rest-api)". |
-| `repo.update_actions_access_settings` | Triggered when the setting to control how your repository is used by {% data variables.product.prodname_actions %} workflows in other repositories is changed.                                                                                                                                                                        |
+| `repo.update_actions_access_settings` | Se activa cuando se cambia el ajuste para controlar cómo los flujos de trabajo de {% data variables.product.prodname_actions %} utilizan tu repositorio en otros repositorios.                                                                                                                                                        |
 {% endif %}
 
 ### Eventos para la administración de secretos
diff --git a/translations/es-ES/content/actions/using-github-hosted-runners/about-github-hosted-runners.md b/translations/es-ES/content/actions/using-github-hosted-runners/about-github-hosted-runners.md
index 6b10663dfe..d391247e97 100644
--- a/translations/es-ES/content/actions/using-github-hosted-runners/about-github-hosted-runners.md
+++ b/translations/es-ES/content/actions/using-github-hosted-runners/about-github-hosted-runners.md
@@ -80,6 +80,7 @@ For the overall list of included tools for each runner operating system, see the
 * [Ubuntu 18.04 LTS](https://github.com/actions/virtual-environments/blob/main/images/linux/Ubuntu1804-Readme.md)
 * [Windows Server 2022](https://github.com/actions/virtual-environments/blob/main/images/win/Windows2022-Readme.md)
 * [Windows Server 2019](https://github.com/actions/virtual-environments/blob/main/images/win/Windows2019-Readme.md)
+* [macOS 12](https://github.com/actions/virtual-environments/blob/main/images/macos/macos-12-Readme.md)
 * [macOS 11](https://github.com/actions/virtual-environments/blob/main/images/macos/macos-11-Readme.md)
 * [macOS 10.15](https://github.com/actions/virtual-environments/blob/main/images/macos/macos-10.15-Readme.md)
 
diff --git a/translations/es-ES/content/actions/using-jobs/running-jobs-in-a-container.md b/translations/es-ES/content/actions/using-jobs/running-jobs-in-a-container.md
index b69559f069..5bdf8816a3 100644
--- a/translations/es-ES/content/actions/using-jobs/running-jobs-in-a-container.md
+++ b/translations/es-ES/content/actions/using-jobs/running-jobs-in-a-container.md
@@ -17,27 +17,27 @@ miniTocMaxHeadingLevel: 4
 
 {% data reusables.actions.jobs.section-running-jobs-in-a-container %}
 
-## Defining the container image
+## Definir la imagen de contenedor
 
 {% data reusables.actions.jobs.section-running-jobs-in-a-container-image %}
 
-## Defining credentials for a container registry
+## Definir las credenciales para un registro de contenedores
 
 {% data reusables.actions.jobs.section-running-jobs-in-a-container-credentials %}
 
-## Using environment variables with a container
+## Utilziar variables de ambiente con un contenedor
 
 {% data reusables.actions.jobs.section-running-jobs-in-a-container-env %}
 
-## Exposing network ports on a container
+## Exponer puertos de red en un contenedor
 
 {% data reusables.actions.jobs.section-running-jobs-in-a-container-ports %}
 
-## Mounting volumes in a container
+## Montar volúmenes en un contenedor
 
 {% data reusables.actions.jobs.section-running-jobs-in-a-container-volumes %}
 
-## Setting container resource options
+## Configurar las opciones de recursos de contenedor
 
 {% data reusables.actions.jobs.section-running-jobs-in-a-container-options %}
 
diff --git a/translations/es-ES/content/actions/using-jobs/using-a-matrix-for-your-jobs.md b/translations/es-ES/content/actions/using-jobs/using-a-matrix-for-your-jobs.md
index 40615bed48..ade55073ae 100644
--- a/translations/es-ES/content/actions/using-jobs/using-a-matrix-for-your-jobs.md
+++ b/translations/es-ES/content/actions/using-jobs/using-a-matrix-for-your-jobs.md
@@ -1,6 +1,6 @@
 ---
 title: Using a matrix for your jobs
-shortTitle: Using a matrix
+shortTitle: Utilizar una matriz
 intro: Create a matrix to define variations for each job.
 versions:
   fpt: '*'
diff --git a/translations/es-ES/content/actions/using-jobs/using-conditions-to-control-job-execution.md b/translations/es-ES/content/actions/using-jobs/using-conditions-to-control-job-execution.md
index 9741b4f7c6..b43efb5b7b 100644
--- a/translations/es-ES/content/actions/using-jobs/using-conditions-to-control-job-execution.md
+++ b/translations/es-ES/content/actions/using-jobs/using-conditions-to-control-job-execution.md
@@ -17,12 +17,12 @@ miniTocMaxHeadingLevel: 4
 
 {% note %}
 
-**Note:** A job that is skipped will report its status as "Success". It will not prevent a pull request from merging, even if it is a required check.
+**Nota:** Un job que se omita reportará su estado como "Exitoso". No prevendrá que se fusione una solicitud de cambios, incluso si es una verificación requerida.
 
 {% endnote %}
 
 {% data reusables.actions.jobs.section-using-conditions-to-control-job-execution %}
 
-You would see the following status on a skipped job:
+Verías el siguiente estado en un job omitido:
 
 ![Skipped-required-run-details](/assets/images/help/repository/skipped-required-run-details.png)
diff --git a/translations/es-ES/content/actions/using-workflows/about-workflows.md b/translations/es-ES/content/actions/using-workflows/about-workflows.md
index 63fb7e3cb7..5a0e78a3d6 100644
--- a/translations/es-ES/content/actions/using-workflows/about-workflows.md
+++ b/translations/es-ES/content/actions/using-workflows/about-workflows.md
@@ -105,7 +105,7 @@ jobs:
 
 Para obtener más información, consulta la sección "[Definir los jobs de prerrequisito](/actions/using-jobs/using-jobs-in-a-workflow#defining-prerequisite-jobs)".
 
-### Using a matrix
+### Utilizar una matriz
 
 {% data reusables.actions.jobs.about-matrix-strategy %} The matrix is created using the `strategy` keyword, which receives the build options as an array. For example, this matrix will run the job multiple times, using different versions of Node.js:
 
@@ -122,7 +122,7 @@ jobs:
           node-version: {% raw %}${{ matrix.node }}{% endraw %}
 ```
 
-For more information, see "[Using a matrix for your jobs](/actions/using-jobs/using-a-matrix-for-your-jobs)."
+Para obtener más información, consulta la sección "[Utilizar una matriz para tus jobs](/actions/using-jobs/using-a-matrix-for-your-jobs)".
 
 {% if actions-caching %}
 ### Almacenar dependencias en caché
diff --git a/translations/es-ES/content/actions/using-workflows/events-that-trigger-workflows.md b/translations/es-ES/content/actions/using-workflows/events-that-trigger-workflows.md
index a4c75c31b1..e45bd5e4e3 100644
--- a/translations/es-ES/content/actions/using-workflows/events-that-trigger-workflows.md
+++ b/translations/es-ES/content/actions/using-workflows/events-that-trigger-workflows.md
@@ -16,9 +16,9 @@ versions:
 shortTitle: Eventos que desencadenan flujos de trabajo
 ---
 
-## About events that trigger workflows
+## Acerca de los eventos que activan flujos de trabajo
 
-Los activadores de los flujos de trabajo son eventos que ocasionan que se ejecute un flujo de trabajo. For more information about how to use workflow triggers, see "[Triggering a workflow](/actions/using-workflows/triggering-a-workflow)."
+Los activadores de los flujos de trabajo son eventos que ocasionan que se ejecute un flujo de trabajo. Para obtener más información sobre cómo utilizar activadores de flujo de trabajo, consulta la sección "[Activar un flujo de trabajo](/actions/using-workflows/triggering-a-workflow)".
 
 ## Eventos disponibles
 
@@ -686,7 +686,7 @@ on:
 
 #### Ejecutar tu flujo de trabajo cuando se fusiona una solicitud de cambios
 
-Cuando se fusiona una solicitud de cambios, esta se cierra automáticamente. To run a workflow when a pull request merges, use the `pull_request` `closed` event type along with a conditional that checks the `merged` value of the event. Por ejemplo, el siguiente flujo de trabajo se ejecutará cada que se cierre una solicitud de cambios. El job `if_merged` solo se ejecutará si la solicitud de cambios también se fusionó.
+Cuando se fusiona una solicitud de cambios, esta se cierra automáticamente. Para ejecutar un flujo de trabajo cuando se fusiona una solicitud de cambios, utiliza el tipo de evento `pull_request` `closed` junto con una condicional que verifique el valor `merged` del mismo. Por ejemplo, el siguiente flujo de trabajo se ejecutará cada que se cierre una solicitud de cambios. El job `if_merged` solo se ejecutará si la solicitud de cambios también se fusionó.
 
 ```yaml
 on:
@@ -1081,7 +1081,7 @@ on:
 
 {% note %}
 
-**Note:** The `event_type` value is limited to 100 characters.
+**Nota:** El valor `event_type` se limita a 100 caracteres.
 
 {% endnote %}
 
@@ -1343,7 +1343,7 @@ jobs:
 
 {% note %}
 
-**Note**: {% data reusables.developer-site.multiple_activity_types %} The `requested` activity type does not occur when a workflow is re-run. Para obtener más información sobre cada tipo de actividad, consulta la sección "[Cargas útiles y eventos de webhook](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#workflow_run)". {% data reusables.developer-site.limit_workflow_to_activity_types %}
+**Nota**: {% data reusables.developer-site.multiple_activity_types %} El tipo de actividad `requested` no ocurre cuando se vuelve a ejecutar un flujo de trabajo. Para obtener más información sobre cada tipo de actividad, consulta la sección "[Cargas útiles y eventos de webhook](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#workflow_run)". {% data reusables.developer-site.limit_workflow_to_activity_types %}
 
 {% endnote %}
 
diff --git a/translations/es-ES/content/actions/using-workflows/reusing-workflows.md b/translations/es-ES/content/actions/using-workflows/reusing-workflows.md
index 2d89a8f03a..ad0d176d2b 100644
--- a/translations/es-ES/content/actions/using-workflows/reusing-workflows.md
+++ b/translations/es-ES/content/actions/using-workflows/reusing-workflows.md
@@ -48,7 +48,7 @@ Para obtener más información, consulta la sección "[Crear flujos de trabajo i
 Un flujo de trabajo reutilizable puede utilizar otro de ellos si {% ifversion ghes or ghec or ghae %}alguna{% else %}cualquiera{% endif %} de las siguientes condiciones es verdadera:
 
 * Ambos flujos de trabajo están en el mismo repositorio.
-* The called workflow is stored in a public repository{% if actions-workflow-policy %}, and your {% ifversion ghec %}enterprise{% else %}organization{% endif %} allows you to use public reusable workflows{% endif %}.{% ifversion ghes or ghec or ghae %}
+* El flujo de trabajo llamado se almacena en un repositorio público{% if actions-workflow-policy %} y tu {% ifversion ghec %}empresa{% else %}organización{% endif %} te permite utilizar flujos de trabajo reutilizables y públicos{% endif %}.{% ifversion ghes or ghec or ghae %}
 * El flujo de trabajo llamado se almacena en un repositorio interno y los ajustes de dicho repositorio permiten que se acceda a él. Para obtener más información, consulta la sección {% if internal-actions %}"[Compartir acciones y flujos de trabajo con tu empresa](/actions/creating-actions/sharing-actions-and-workflows-with-your-enterprise){% else %}"[Administrar los ajustes de las {% data variables.product.prodname_actions %} en un repositorio](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#allowing-access-to-components-in-an-internal-repository){% endif %}".{% endif %}
 
 ## Utilizar ejecutores
@@ -104,11 +104,11 @@ Puedes definir entradas y secretos, las cuales pueden pasarse desde el flujo de
    ```
    {% endraw %}
    {% if actions-inherit-secrets-reusable-workflows %}
-   For details of the syntax for defining inputs and secrets, see [`on.workflow_call.inputs`](/actions/reference/workflow-syntax-for-github-actions#onworkflow_callinputs), [`on.workflow_call.secrets`](/actions/reference/workflow-syntax-for-github-actions#onworkflow_callsecrets) and [`on.workflow_call.secrets.inherit`](/actions/using-workflows/workflow-syntax-for-github-actions#onworkflow_callsecretsinherit).
-1. In the reusable workflow, reference the input or secret that you defined in the `on` key in the previous step. If the secrets are inherited using `secrets: inherit`, you can reference them even if they are not defined in the `on` key.
+   Para encontrar más detalles sobre la sintaxis para definir entradas y secretos, consulta [`on.workflow_call.inputs`](/actions/reference/workflow-syntax-for-github-actions#onworkflow_callinputs), [`on.workflow_call.secrets`](/actions/reference/workflow-syntax-for-github-actions#onworkflow_callsecrets) y [`on.workflow_call.secrets.inherit`](/actions/using-workflows/workflow-syntax-for-github-actions#onworkflow_callsecretsinherit).
+1. En el flujo de trabajo reutilizable, referencia la entrada o secreto que definiste en la clave `on` en el paso anterior. Si los secretos se heredan utilizando `secrets: inherit`, puedes referenciarlos incluso si no se definen en la clave `on`.
    {%- else %}
    Para encontrar los detalles de la sintaxis para definir entradas y secretos, consulta [`on.workflow_call.inputs`](/actions/reference/workflow-syntax-for-github-actions#onworkflow_callinputs) y [`on.workflow_call.secrets`](/actions/reference/workflow-syntax-for-github-actions#onworkflow_callsecrets).
-1. In the reusable workflow, reference the input or secret that you defined in the `on` key in the previous step.
+1. En el flujo de trabajo reutilizable, referencia la entrada o secreto que definiste en la clave `on` en el paso anterior.
    {%- endif %}
 
    {% raw %}
@@ -128,7 +128,7 @@ Puedes definir entradas y secretos, las cuales pueden pasarse desde el flujo de
 
    {% note %}
 
-   **Note**: Los secretos de ambiente son secuencias cifradas que se almacenan en un ambiente que hayas definido para un repositorio. Los secretos de ambiente solo se encuentran disponibles para los jobs de flujo de trabajo que referencian al ambiente adecuado. For more information, see "[Using environments for deployment](/actions/deployment/targeting-different-environments/using-environments-for-deployment#environment-secrets)."
+   **Note**: Los secretos de ambiente son secuencias cifradas que se almacenan en un ambiente que hayas definido para un repositorio. Los secretos de ambiente solo se encuentran disponibles para los jobs de flujo de trabajo que referencian al ambiente adecuado. Para obtener más información, consulta la sección "[Utilizar ambientes para despliegue](/actions/deployment/targeting-different-environments/using-environments-for-deployment#environment-secrets)".
 
    {% endnote %}
 
diff --git a/translations/es-ES/content/actions/using-workflows/storing-workflow-data-as-artifacts.md b/translations/es-ES/content/actions/using-workflows/storing-workflow-data-as-artifacts.md
index 290e885d45..9912a736e3 100644
--- a/translations/es-ES/content/actions/using-workflows/storing-workflow-data-as-artifacts.md
+++ b/translations/es-ES/content/actions/using-workflows/storing-workflow-data-as-artifacts.md
@@ -41,7 +41,7 @@ Almacenar artefactos consume espacio de almacenamiento en {% data variables.prod
 
 {% else %}
 
-Artifacts consume storage space on the external blob storage that is configured for {% data variables.product.prodname_actions %} on {% data variables.product.product_location %}.
+Los artefactos consumen espacio de almacenamiento en el almacenamiento de blobs externo que se configura para {% data variables.product.prodname_actions %} en {% data variables.product.product_location %}.
 
 {% endif %}
 
@@ -60,7 +60,7 @@ Los pasos de un job comparten el mismo ambiente en la máquina ejecutora, pero s
 
 {% data reusables.actions.comparing-artifacts-caching %}
 
-For more information on dependency caching, see "[Caching dependencies to speed up workflows](/actions/using-workflows/caching-dependencies-to-speed-up-workflows#comparing-artifacts-and-dependency-caching)."
+Para obtener más información sobre el almacenamiento de dependencias en caché, consulta la sección "[Almacenar dependencias en caché para agilizar los flujos de trabajo](/actions/using-workflows/caching-dependencies-to-speed-up-workflows#comparing-artifacts-and-dependency-caching)".
 
 {% endif %}
 
diff --git a/translations/es-ES/content/actions/using-workflows/triggering-a-workflow.md b/translations/es-ES/content/actions/using-workflows/triggering-a-workflow.md
index 079715adbb..057d3e5399 100644
--- a/translations/es-ES/content/actions/using-workflows/triggering-a-workflow.md
+++ b/translations/es-ES/content/actions/using-workflows/triggering-a-workflow.md
@@ -36,7 +36,7 @@ Los siguientes pasos se producen para activar una ejecución de flujo de trabajo
 
 {% data reusables.actions.actions-do-not-trigger-workflows %} Para obtener más información, consulta la sección "[Autenticarse con el GITHUB_TOKEN](/actions/configuring-and-managing-workflows/authenticating-with-the-github_token)".
 
-Si no quieres activar un flujo de trabajo dentro una ejecución de flujo de trabajo, puedes utilizar un token de acceso personal en vez de un `GITHUB_TOKEN` para activar los eventos que requieren tu token. Necesitaras crear un token de acceso personal y almacenarlo como un secreto. Para minimizar tus costos de uso de {% data variables.product.prodname_actions %}, asegúrate de no crear ejecuciones de flujo de trabajo recurrentes o involuntarias. For more information about creating a personal access token, see "[Creating a personal access token](/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)." Para obtener más información sobre cómo almacenr un token de acceso personal como secreto, consulta la sección "[Crear y almacenar secretos cifrados](/actions/configuring-and-managing-workflows/creating-and-storing-encrypted-secrets)".
+Si no quieres activar un flujo de trabajo dentro una ejecución de flujo de trabajo, puedes utilizar un token de acceso personal en vez de un `GITHUB_TOKEN` para activar los eventos que requieren tu token. Necesitaras crear un token de acceso personal y almacenarlo como un secreto. Para minimizar tus costos de uso de {% data variables.product.prodname_actions %}, asegúrate de no crear ejecuciones de flujo de trabajo recurrentes o involuntarias. Para obtener más información acerca de cómo crear un token de acceso personal, consulta la sección "[Crear un token de acceso personal](/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)". Para obtener más información sobre cómo almacenr un token de acceso personal como secreto, consulta la sección "[Crear y almacenar secretos cifrados](/actions/configuring-and-managing-workflows/creating-and-storing-encrypted-secrets)".
 
 Por ejemplo, el siguiente flujo de trabajo utiliza un token de acceso personal (almacenado como secreto y llamado `MY_TOKEN`) para agregar una etiqueta a una propuesta de cambios a través del cli.{% data variables.product.prodname_cli %}. Cualquier flujo de trabajo que se ejecute cuando una etiqueta se agrega se ejecutará una vez mediante este espejo.
 
diff --git a/translations/es-ES/content/actions/using-workflows/using-starter-workflows.md b/translations/es-ES/content/actions/using-workflows/using-starter-workflows.md
index e4b8a7473e..197400b6d5 100644
--- a/translations/es-ES/content/actions/using-workflows/using-starter-workflows.md
+++ b/translations/es-ES/content/actions/using-workflows/using-starter-workflows.md
@@ -39,10 +39,10 @@ Cualquiera con permiso de escritura en un repositorio puede configurar flujos de
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.actions-tab %}
 1. Si ya tienes un flujo de trabajo en tu repositorio, haz clic en **Flujo de trabajo nuevo**.
-1. The "{% if actions-starter-template-ui %}Choose a workflow{% else %}Choose a workflow template{% endif %}" page shows a selection of recommended starter workflows. Encuentra el flujo de trabajo inicial que quieras utilizar, luego haz clic en {% if actions-starter-template-ui %}**Configurar**{% else %}**Configurar este flujo de trabajo**{% endif %}.{% if actions-starter-template-ui %} Para ayudarte a encontrar el flujo de trabajo inicial que quieres, puedes buscar las palabras clave o filtrar por categoría.{% endif %}
+1. La página "{% if actions-starter-template-ui %}Elige un flujo de trabajo{% else %}Elige una plantilla de flujo de trabajo{% endif %}" muestra una selección de flujos de trabajo iniciales recomendados. Encuentra el flujo de trabajo inicial que quieras utilizar, luego haz clic en {% if actions-starter-template-ui %}**Configurar**{% else %}**Configurar este flujo de trabajo**{% endif %}.{% if actions-starter-template-ui %} Para ayudarte a encontrar el flujo de trabajo inicial que quieres, puedes buscar las palabras clave o filtrar por categoría.{% endif %}
 
    {% if actions-starter-template-ui %}![Configure this workflow](/assets/images/help/settings/actions-create-starter-workflow-updated-ui.png){% else %}![Set up this workflow](/assets/images/help/settings/actions-create-starter-workflow.png){% endif %}
-1. Si el flujo de trabajo inicial contiene comentarios que detallen pasos de configuración adicional, sigue estos pasos. Muchos de los flujos de trabajo iniciales tienen guías correspondientes. For more information, see the [{% data variables.product.prodname_actions %} guides](/actions/guides).
+1. Si el flujo de trabajo inicial contiene comentarios que detallen pasos de configuración adicional, sigue estos pasos. Muchos de los flujos de trabajo iniciales tienen guías correspondientes. Para obtener más información, consulta las [guías de {% data variables.product.prodname_actions %}](/actions/guides).
 1. Algunos flujos de trabajo iniciales utilizan secretos. Por ejemplo, {% raw %}`${{ secrets.npm_token }}`{% endraw %}. Si el flujo de trabajo inicial utiliza un secreto, almacena el valor descrito en el nombre del secreto como un secreto en tu repositorio. Para obtener más información, consulta "[Secretos cifrados](/actions/reference/encrypted-secrets)".
 1. Opcionalmente, haz cambios adicionales. Por ejemplo, puede que quieras cambiar el valor de `on` para que este cambie cuando se ejecute el flujo de trabajo.
 1. Haz clic en **Iniciar confirmación**.
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 f8e633ce06..8969f0eddf 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
@@ -112,9 +112,9 @@ La siguiente tabla muestra qué funciones del toolkit se encuentran disponibles
 | `core.getState`       | Accesible utilizando la variable de ambiente`STATE_{NAME}`  |
 | `core.isDebug`        | Accesible utilizando la variable de ambiente `RUNNER_DEBUG` |
 {%- if actions-job-summaries %}
-| `core.summary` | Accessible using environment variable `GITHUB_STEP_SUMMARY` |
+| `core.summary` | Se puede acceder a este utilizando la variable de ambiente `GITHUB_STEP_SUMMARY` |
 {%- endif %}
-| `core.saveState`  | `save-state` | | `core.setCommandEcho` | `echo` | | `core.setFailed`  | Used as a shortcut for `::error` and `exit 1` | | `core.setOutput`  | `set-output` | | `core.setSecret`  | `add-mask` | | `core.startGroup` | `group` | | `core.warning`    | `warning` |
+| `core.saveState`  | `save-state` | | `core.setCommandEcho` | `echo` | | `core.setFailed`  | Se utiliza como un atajo para `::error` y `exit 1` | | `core.setOutput`  | `set-output` | | `core.setSecret`  | `add-mask` | | `core.startGroup` | `group` | | `core.warning`    | `warning` |
 
 ## Configurar un parámetro de salida
 
@@ -307,7 +307,7 @@ jobs:
 ::add-mask::{value}
 ```
 
-El enmascaramiento de un valor impide que una cadena o variable se imprima en el registro. Cada palabra enmascarada separada por un espacio en blanco se reemplaza con el carácter `*`. Puedes usar una variable de entorno o cadena para el `valor` de la máscara. When you mask a value, it is treated as a secret and will be redacted on the runner. For example, after you mask a value, you won't be able to set that value as an output.
+El enmascaramiento de un valor impide que una cadena o variable se imprima en el registro. Cada palabra enmascarada separada por un espacio en blanco se reemplaza con el carácter `*`. Puedes usar una variable de entorno o cadena para el `valor` de la máscara. Cuando enmascaras un valor, se le trata como un secreto y se redactará en el ejecutor. Por ejemplo, después de que enmascaras un valor, no podrás configurarlo como una salida.
 
 ### Ejemplo: Enmascarar una secuencia
 
@@ -625,7 +625,7 @@ Para las secuencias de lìnea mùltiple, puedes utilizar un delimitador con la s
 
 #### Ejemplo
 
-This example uses `EOF` as a delimiter, and sets the `JSON_RESPONSE` environment variable to the value of the `curl` response.
+Este ejemplo utiliza `EOF` como un delimitador y configura la variable de ambiente `JSON_RESPONSE` al valor de la respuesta de `curl`.
 
 {% bash %}
 
@@ -658,7 +658,7 @@ steps:
 
 {% if actions-job-summaries %}
 
-## Adding a job summary
+## Agregar un resumen del job
 
 {% bash %}
 
@@ -676,11 +676,11 @@ echo "{markdown content}" >> $GITHUB_STEP_SUMMARY
 
 {% endpowershell %}
 
-You can set some custom Markdown for each job so that it will be displayed on the summary page of a workflow run. You can use job summaries to display and group unique content, such as test result summaries, so that someone viewing the result of a workflow run doesn't need to go into the logs to see important information related to the run, such as failures.
+Puedes configurar algo de lenguaje de marcado personalizado para cada job, para que se muestre en la página de resumen de una ejecución de flujo de trabajo. Puedes utilizar resúmenes de jobs para mostrar y agrupar contenido único, tal como resúmenes de resultados de prueba, para que quien sea que esté viendo dicho resultado de una ejecución de flujo de trabajo no necesite ir a las bitácoras para ver la información importante relacionada con la ejecución, tal como las fallas.
 
-Job summaries support [{% data variables.product.prodname_dotcom %} flavored Markdown](https://github.github.com/gfm/), and you can add your Markdown content for a step to the `GITHUB_STEP_SUMMARY` environment file. `GITHUB_STEP_SUMMARY` is unique for each step in a job. For more information about the per-step file that `GITHUB_STEP_SUMMARY` references, see "[Environment files](#environment-files)."
+Los resúmenes de jobs son compatibles con [el lenguaje de marcado enriquecido de {% data variables.product.prodname_dotcom %}](https://github.github.com/gfm/) y puedes agregar tu contenido de lenguaje de marcado para un paso al archivo de ambiente de `GITHUB_STEP_SUMMARY`. El `GITHUB_STEP_SUMMARY` es único para cada paso en un job. Para obtener más información sobre el archivo por paso al que referencia el `GITHUB_STEP_SUMMARY`, consulta la sección "[Archivos de ambiente](#environment-files)".
 
-When a job finishes, the summaries for all steps in a job are grouped together into a single job summary and are shown on the workflow run summary page. If multiple jobs generate summaries, the job summaries are ordered by job completion time.
+Cuando finaliza un job, los resúmenes de todos los pasos en este se agrupan en un solo resumen de job y se muestran en la página de resumen de la ejecución de flujo de trabajo. If multiple jobs generate summaries, the job summaries are ordered by job completion time.
 
 ### Ejemplo
 
diff --git a/translations/es-ES/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/about-supply-chain-security-for-your-enterprise.md b/translations/es-ES/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/about-supply-chain-security-for-your-enterprise.md
index 2b4be13bda..8fa269d1f3 100644
--- a/translations/es-ES/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/about-supply-chain-security-for-your-enterprise.md
+++ b/translations/es-ES/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/about-supply-chain-security-for-your-enterprise.md
@@ -1,6 +1,6 @@
 ---
-title: About supply chain security for your enterprise
-intro: You can enable features that help your developers understand and update the dependencies their code relies on.
+title: Acerca de la seguridad de la cadena de suministro para tu empresa
+intro: Puedes habilitar las características que ayudan a tus desarrolladores a entender y actualizar las dependencias de las cuales depende su código.
 shortTitle: Acerca de la seguridad de la cadena de suministro
 permissions: ''
 versions:
@@ -13,8 +13,8 @@ topics:
   - Dependency graph
 ---
 
-You can allow users to identify their projects' dependencies by {% ifversion ghes %}enabling{% elsif ghae %}using{% endif %} the dependency graph for {% data variables.product.product_location %}. Para obtener más información, consulta la sección "{% ifversion ghes %}[Habilitar la gráfica de dependencias para tu empresa](/admin/code-security/managing-supply-chain-security-for-your-enterprise/enabling-the-dependency-graph-for-your-enterprise){% elsif ghae %}[Acerca de la gráfica de dependencias](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph){% endif %}".
+Puedes permitir que los usuarios identifiquen las dependencias de sus proyectos si {% ifversion ghes %}habilitas{% elsif ghae %}utilizas{% endif %} la gráfica de dependencias para {% data variables.product.product_location %}. Para obtener más información, consulta la sección "{% ifversion ghes %}[Habilitar la gráfica de dependencias para tu empresa](/admin/code-security/managing-supply-chain-security-for-your-enterprise/enabling-the-dependency-graph-for-your-enterprise){% elsif ghae %}[Acerca de la gráfica de dependencias](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph){% endif %}".
 
-You can also allow users on {% data variables.product.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 %}. Para obtener más información, consulta la sección "[Habilitar la {% data variables.product.prodname_dependabot %} en tu empresa](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise)".
+También puedes permitir que los usuarios de {% data variables.product.product_location %} encuentren y corrijan las vulnerabilidades en las dependencias de su código si habilitas las {% data variables.product.prodname_dependabot_alerts %}{% ifversion ghes > 3.2 %} y las {% data variables.product.prodname_dependabot_updates %}{% endif %}. Para obtener más información, consulta la sección "[Habilitar la {% data variables.product.prodname_dependabot %} en tu empresa](/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.product.product_location %} and manually sync the data. Para obtener más información, consulta la sección "[Ver los datos de vulnerabilidad de tu empresa](/admin/code-security/managing-supply-chain-security-for-your-enterprise/viewing-the-vulnerability-data-for-your-enterprise)".
+Después de que habilites las {% data variables.product.prodname_dependabot_alerts %}, puedes ver los datos de las vulnerabilidades desde la {% data variables.product.prodname_advisory_database %} en {% data variables.product.product_location %} y sincronizar los datos manualmente. Para obtener más información, consulta la sección "[Ver los datos de vulnerabilidad de tu empresa](/admin/code-security/managing-supply-chain-security-for-your-enterprise/viewing-the-vulnerability-data-for-your-enterprise)".
diff --git a/translations/es-ES/content/admin/configuration/configuring-network-settings/enabling-subdomain-isolation.md b/translations/es-ES/content/admin/configuration/configuring-network-settings/enabling-subdomain-isolation.md
index 75b03ffebd..de6b356dc6 100644
--- a/translations/es-ES/content/admin/configuration/configuring-network-settings/enabling-subdomain-isolation.md
+++ b/translations/es-ES/content/admin/configuration/configuring-network-settings/enabling-subdomain-isolation.md
@@ -41,7 +41,7 @@ Cuando el aislamiento de subdominio está habilitado, {% data variables.product.
 | `https://HOSTNAME/_registry/rubygems/` | `https://rubygems.HOSTNAME/`                                   |
 | `https://HOSTNAME/_registry/maven/`    | `https://maven.HOSTNAME/`                                      |
 | `https://HOSTNAME/_registry/nuget/`    | `https://nuget.HOSTNAME/`{% endif %}{% ifversion ghes > 3.4 %}
-| Not supported                          | `https://containers.HOSTNAME/` 
+| No compatible                          | `https://containers.HOSTNAME/` 
 {% endif %}
 
 ## Prerrequisitos
diff --git a/translations/es-ES/content/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance.md b/translations/es-ES/content/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance.md
index 01e6b601ef..4a6c8c5cc4 100644
--- a/translations/es-ES/content/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance.md
+++ b/translations/es-ES/content/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance.md
@@ -131,7 +131,7 @@ $ ghe-restore -c 169.154.1.1
 ```
 
 {% if ip-exception-list %}
-Optionally, to validate the restore, configure an IP exception list to allow access to a specified list of IP addresses. For more information, see "[Validating changes in maintenance mode using the IP exception list](/admin/configuration/configuring-your-enterprise/enabling-and-scheduling-maintenance-mode#validating-changes-in-maintenance-mode-using-the-ip-exception-list)."
+Opcionalmente, para validar la restauración, configura una lista de excepción de IP para permitir el acceso una lista de direcciones IP específicas. Para obtener más información, consulta la sección "[Validar los cambios en modo de mantenimiento utilizando la lista de excepción de IP](/admin/configuration/configuring-your-enterprise/enabling-and-scheduling-maintenance-mode#validating-changes-in-maintenance-mode-using-the-ip-exception-list)".
 {% endif %}
 
 {% note %}
diff --git a/translations/es-ES/content/admin/configuration/configuring-your-enterprise/configuring-email-for-notifications.md b/translations/es-ES/content/admin/configuration/configuring-your-enterprise/configuring-email-for-notifications.md
index deeb6d81aa..59718420ef 100644
--- a/translations/es-ES/content/admin/configuration/configuring-your-enterprise/configuring-email-for-notifications.md
+++ b/translations/es-ES/content/admin/configuration/configuring-your-enterprise/configuring-email-for-notifications.md
@@ -35,9 +35,9 @@ Los propietarios de las empresas pueden configurar los correos electrónicos par
       - Selecciona el menú desplegable de **Autenticación** y elige el tipo de cifrado que utiliza tu servidor SMTP.
       - En el campo **Dirección de correo electrónico sin respuesta**, escribe la dirección de correo electrónico para usar en los campos De y Para para todos los correos electrónicos para notificaciones.
 6. Si quieres descartar todos los correos electrónicos entrantes que estén dirigidos al correo electrónico sin respuesta, selecciona **Descartar correo electrónico dirigido a la dirección de correo electrónico sin respuesta**. ![Casilla de verificación para descartar los correos electrónicos dirigidos a la dirección de correo electrónico sin respuesta](/assets/images/enterprise/management-console/discard-noreply-emails.png)
-7. Under **Support**, choose a type of link to offer additional support to your users.
-    - **Email:** An internal email address.
-    - **URL:** A link to an internal support site. Debes incluir tanto `http://` como `https://`. ![Correo de soporte técnico o URL](/assets/images/enterprise/management-console/support-email-url.png)
+7. Debajo de **Soporte**, elige un tipo de enlace para ofrecer soporte adicional a tus usuarios.
+    - **Correo electrónico:** una dirección de correo electrónico interna.
+    - **URL:** Un enlace a un sitio de soporte interno. Debes incluir tanto `http://` como `https://`. ![Correo de soporte técnico o URL](/assets/images/enterprise/management-console/support-email-url.png)
 8. [Prueba de entrega del correo electrónico](#testing-email-delivery).
 {% elsif ghae %}
 {% data reusables.enterprise-accounts.access-enterprise %}
@@ -86,7 +86,7 @@ Si quieres permitir respuestas de correo electrónico para las notificaciones, d
 
 ### Crea un Paquete de soporte
 
-If you cannot determine what is wrong from the displayed error message, you can download a [support bundle](/enterprise/{{ currentVersion }}/admin/guides/enterprise-support/providing-data-to-github-support) containing the entire SMTP conversation between your mail server and {% data variables.product.prodname_ghe_server %}. Once you've downloaded and extracted the bundle, check the entries in *enterprise-manage-logs/unicorn.log* for the entire SMTP conversation log and any related errors.
+Si no puedes determinar qué es lo que está mal desde el mensaje de error que se muestra, puedes descargar un [paquete de soporte](/enterprise/{{ currentVersion }}/admin/guides/enterprise-support/providing-data-to-github-support) que contiene toda la conversación de SMTP entre tu servidor de correo y {% data variables.product.prodname_ghe_server %}. Una vez que hayas descargado y extraído el paquete, verifica las entradas en *enterprise-manage-logs/unicorn.log* para toda la bitácora de conversaciones de SMTP y cualquier error relacionado.
 
 El registro unicornio debería mostrar una transacción similar a la siguiente:
 
@@ -161,7 +161,7 @@ Para procesar los correos electrónicos entrantes de manera adecuada, debes conf
 
 ### Controlar los parámetros de AWS Security Group o firewall
 
-If {% data variables.product.product_location %} is behind a firewall or is being served through an AWS Security Group, make sure port 25 is open to all mail servers that send emails to `reply@reply.[hostname]`.
+Si {% data variables.product.product_location %} está detrás de un cortafuegos o se le está sirviendo a través de un AWS Security Group, asegúrate de que el puerto 25 esté abierto a todos los servidores de correo que envíen correos electrónicos a `reply@reply.[hostname]`.
 
 ### Contactar con soporte técnico
 {% ifversion ghes %}
diff --git a/translations/es-ES/content/admin/configuration/configuring-your-enterprise/configuring-web-commit-signing.md b/translations/es-ES/content/admin/configuration/configuring-your-enterprise/configuring-web-commit-signing.md
index 27a34f12b0..5867a44e4e 100644
--- a/translations/es-ES/content/admin/configuration/configuring-your-enterprise/configuring-web-commit-signing.md
+++ b/translations/es-ES/content/admin/configuration/configuring-your-enterprise/configuring-web-commit-signing.md
@@ -37,7 +37,7 @@ You can enable web commit signing, rotate the private key used for web commit si
    ```bash{:copy}
    ghe-config-apply
    ```
-1. Create a new user on {% data variables.product.product_location %} via built-in authentication or external authentication. For more information, see "[About authentication for your enterprise](/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise)."
+1. Create a new user on {% data variables.product.product_location %} via built-in authentication or external authentication. Para obtener más información, consulta la sección "[Acerca de la autenticación para tu empresa](/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise)".
    - The user's username must be `web-flow`.
    - The user's email address must be the same address you used for the PGP key.
 {% data reusables.enterprise_site_admin_settings.add-key-to-web-flow-user %}
diff --git a/translations/es-ES/content/admin/configuration/configuring-your-enterprise/enabling-and-scheduling-maintenance-mode.md b/translations/es-ES/content/admin/configuration/configuring-your-enterprise/enabling-and-scheduling-maintenance-mode.md
index ede3b243a4..ea2fd4cb93 100644
--- a/translations/es-ES/content/admin/configuration/configuring-your-enterprise/enabling-and-scheduling-maintenance-mode.md
+++ b/translations/es-ES/content/admin/configuration/configuring-your-enterprise/enabling-and-scheduling-maintenance-mode.md
@@ -60,18 +60,18 @@ Puedes llevar a cabo una validación inicial de tu operación de mantenimiento s
 
 {% if ip-exception-list %}
 
-## Validating changes in maintenance mode using the IP exception list
+## Validar los cambios en el modo de mantenimiento utilizando la lista de excepciones de IP
 
-The IP exception list provides controlled and restricted access to {% data variables.product.product_location %}, which is ideal for initial validation of server health following a maintenance operation. Once enabled, {% data variables.product.product_location %} will be taken out of maintenance mode and available only to the configured IP addresses. The maintenance mode checkbox will be updated to reflect the change in state.
+La lista de excepciones de IP proporciona un acceso restringido y controlado a {% data variables.product.product_location %}, el cual es ideal para una validación inicial de la salud del servidor después de una operación de mantenimiento. Una vez que se habilita, {% data variables.product.product_location %} saldrá del modo de mantenimiento y estará disponible únicamente para las direcciones IP configuradas. La casilla de modo de mantenimiento se actualizará para reflejar el cambio en el estado.
 
-If you re-enable maintenance mode, the IP exception list will be disabled and {% data variables.product.product_location %} will return to maintenance mode. If you just disable the IP exception list, {% data variables.product.product_location %} will return to normal operation.
+Si vuelves a habilitar el modo de mantenimiento, se inhabilitará la lista de excepción de IP se y {% data variables.product.product_location %} regresará al modo de mantenimiento. Si simplemente inhabilitas la lista de excepción de IP, {% data variables.product.product_location %} regresará a su operación normal.
 
 {% data reusables.enterprise_site_admin_settings.access-settings %}
 {% data reusables.enterprise_site_admin_settings.management-console %}
-1. At the top of the {% data variables.enterprise.management_console %}, click **Maintenance**, and confirm maintenance mode is already enabled. ![Pestaña de mantenimiento](/assets/images/enterprise/management-console/maintenance-tab.png)
-1. Select **Enable IP exception list**. ![Checkbox for enabling ip exception list](/assets/images/enterprise/maintenance/enable-ip-exception-list.png)
-1. In the text box, type a valid list of space-separated IP addresses or CIDR blocks that should be allowed to access {% data variables.product.product_location %}. ![completed field for IP addresses](/assets/images/enterprise/maintenance/ip-exception-list-ip-addresses.png)
-1. Haz clic en **Save ** (guardar). ![after IP excetpion list has saved](/assets/images/enterprise/maintenance/ip-exception-save.png)
+1. En la parte superior de la {% data variables.enterprise.management_console %}, haz clic en **Mantenimiento** y confirma que el modo de mantenimiento ya esté habilitado. ![Pestaña de mantenimiento](/assets/images/enterprise/management-console/maintenance-tab.png)
+1. Selecciona **Habilitar la lista de excepción de IP**. ![Casilla de verificación para habilitar la lista de excepción de IP](/assets/images/enterprise/maintenance/enable-ip-exception-list.png)
+1. En la caja de texto, teclea una lista válida de direcciones IP separadas por espacios o bloques de CDIR a los que se les debería permitir el acceso a {% data variables.product.product_location %}. ![campo completado para las direcciones IP](/assets/images/enterprise/maintenance/ip-exception-list-ip-addresses.png)
+1. Haz clic en **Save ** (guardar). ![después de que se guarda la lista de excepción de IP](/assets/images/enterprise/maintenance/ip-exception-save.png)
 
 {% endif %}
 
diff --git a/translations/es-ES/content/admin/configuration/configuring-your-enterprise/managing-github-mobile-for-your-enterprise.md b/translations/es-ES/content/admin/configuration/configuring-your-enterprise/managing-github-mobile-for-your-enterprise.md
index 1e81f44e87..6978b2016b 100644
--- a/translations/es-ES/content/admin/configuration/configuring-your-enterprise/managing-github-mobile-for-your-enterprise.md
+++ b/translations/es-ES/content/admin/configuration/configuring-your-enterprise/managing-github-mobile-for-your-enterprise.md
@@ -1,6 +1,6 @@
 ---
 title: Administrar GitHub Móvil para tu empresa
-intro: 'You can decide whether people can use {% data variables.product.prodname_mobile %} to connect to {% data variables.product.product_location %}.'
+intro: 'Puedes decidir si las personas pueden utilizar {% data variables.product.prodname_mobile %} para conectarse a {% data variables.product.product_location %}.'
 permissions: 'Enterprise owners can manage {% data variables.product.prodname_mobile %} for a {% data variables.product.product_name %} instance.'
 versions:
   ghes: '*'
@@ -16,14 +16,14 @@ shortTitle: Administrar GitHub Móvil
 
 ## Acerca de {% data variables.product.prodname_mobile %}
 
-{% data variables.product.prodname_mobile %} allows people to triage, collaborate, and manage work on {% data variables.product.product_location %} from a mobile device after successful authentication. {% data reusables.mobile.about-mobile %} Para obtener más información, consulta la sección "[{% data variables.product.prodname_mobile %}](/get-started/using-github/github-mobile)".
+{% data variables.product.prodname_mobile %} permite que las personas clasifiquen, colaboren y administren el trabajo de {% data variables.product.product_location %} desde un dispositivo móvil después de autenticarse con éxito. {% data reusables.mobile.about-mobile %} Para obtener más información, consulta la sección "[{% data variables.product.prodname_mobile %}](/get-started/using-github/github-mobile)".
 
-You can allow or disallow people from using {% data variables.product.prodname_mobile %} to authenticate to {% data variables.product.product_location %} and access your instance's data. By default, {% data variables.product.prodname_mobile %} is{% ifversion ghes > 3.3 %} enabled for people who use {% data variables.product.product_location %}.{% else %} not enabled for people who use {% data variables.product.product_location %}. To allow connection to your instance with {% data variables.product.prodname_mobile %}, you must enable the feature for your instance.{% endif %}
+Puedes permitir o dejar de permitir que las personas utilicen {% data variables.product.prodname_mobile %} para autenticarse en {% data variables.product.product_location %} y que accedan a los datos de tu instancia. Predeterminadamente, {% data variables.product.prodname_mobile %} está {% ifversion ghes > 3.3 %} habilitado para las personas que utilizan {% data variables.product.product_location %}.{% else %} inhabilitado para las personas que utilizan {% data variables.product.product_location %}. Para permitir la conexión a tu instancia con {% data variables.product.prodname_mobile %}, debes habilitar la característica para esta.{% endif %}
 
 {% ifversion ghes < 3.6 and ghes > 3.1 %}
 {% note %}
 
-**Note:** If you upgrade to {% data variables.product.prodname_ghe_server %} 3.4.0 or later and have not previously disabled or enabled {% data variables.product.prodname_mobile %}, {% data variables.product.prodname_mobile %} will be enabled by default. If you previously disabled or enabled {% data variables.product.prodname_mobile %} for your instance, your preference will be preserved upon upgrade. For more information about upgrading your instance, see "[Upgrading {% data variables.product.product_name %}](/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server)."
+**Nota:** Si mejoras a {% data variables.product.prodname_ghe_server %} 3.4.0 o posterior y no has inhabilitado o habilitado {% data variables.product.prodname_mobile %} previamente, {% data variables.product.prodname_mobile %} se habilitará predeterminadamente. Si previamente inhabilitaste o habilitaste {% data variables.product.prodname_mobile %} para tu instancia, tu preferencia se preservará cuando lo mejores. Para obtener más información sobre cómo mejorar tu instancia, consulta la sección "[Mejorar {% data variables.product.product_name %}](/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server)".
 
 {% endnote %}
 {% endif %}
diff --git a/translations/es-ES/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/increasing-storage-capacity.md b/translations/es-ES/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/increasing-storage-capacity.md
index 2247072f72..af08e10053 100644
--- a/translations/es-ES/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/increasing-storage-capacity.md
+++ b/translations/es-ES/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/increasing-storage-capacity.md
@@ -24,7 +24,7 @@ A medida que se suman usuarios {% data variables.product.product_location %}, es
 
 {% note %}
 
-**Note:** Before resizing any storage volume, put your instance in maintenance mode.{% if ip-exception-list %} You can validate changes by configuring an IP exception list to allow access from specified IP addresses. {% endif %} For more information, see "[Enabling and scheduling maintenance mode](/enterprise/{{ currentVersion }}/admin/guides/installation/enabling-and-scheduling-maintenance-mode)."
+**Nota:** Antes de cambiar el tamaño de cualquier volumen de almacenamiento, coloca tu instancia en modo de mantenimiento.{% if ip-exception-list %} Puedes validar los cambios si configuras una lista de excepción de IP para permitir el acceso desde direcciones IP específicas. {% endif %} Para obtener más información, consulta la sección "[Habilitar y programar el modo de mantenimiento](/enterprise/{{ currentVersion }}/admin/guides/installation/enabling-and-scheduling-maintenance-mode)".
 
 {% endnote %}
 
diff --git a/translations/es-ES/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/enabling-github-actions-with-amazon-s3-storage.md b/translations/es-ES/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/enabling-github-actions-with-amazon-s3-storage.md
index 29d1ce337e..991692f048 100644
--- a/translations/es-ES/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/enabling-github-actions-with-amazon-s3-storage.md
+++ b/translations/es-ES/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/enabling-github-actions-with-amazon-s3-storage.md
@@ -1,6 +1,6 @@
 ---
 title: Habilitar las GitHub Actions con el almacenamiento de Amazon S3
-intro: 'You can enable {% data variables.product.prodname_actions %} on {% data variables.product.prodname_ghe_server %} and use Amazon S3 storage to store data generated by workflow runs.'
+intro: 'Puedes habilitar las {% data variables.product.prodname_actions %} en {% data variables.product.prodname_ghe_server %} y utilizar el almacenamiento de Amazon S3 para almacenar los datos que generan las ejecuciones de flujo de trabajo.'
 permissions: 'Site administrators can enable {% data variables.product.prodname_actions %} and configure enterprise settings.'
 versions:
   ghes: '*'
@@ -21,7 +21,7 @@ shortTitle: Almacenamiento de Amazon S3
 
 Antes de que habilites las {% data variables.product.prodname_actions %}, asegúrate de que has completado los siguientes pasos:
 
-* Create your Amazon S3 bucket for storing data generated by workflow runs. {% indented_data_reference reusables.actions.enterprise-s3-permission spaces=2 %}
+* Crea tu bucket de Amazon S3 para almacenar los datos que generan las ejecuciones de flujo de trabajo. {% indented_data_reference reusables.actions.enterprise-s3-permission spaces=2 %}
 
 {% data reusables.actions.enterprise-common-prereqs %}
 
diff --git a/translations/es-ES/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/enabling-github-actions-with-azure-blob-storage.md b/translations/es-ES/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/enabling-github-actions-with-azure-blob-storage.md
index 36d2b35826..0e40983429 100644
--- a/translations/es-ES/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/enabling-github-actions-with-azure-blob-storage.md
+++ b/translations/es-ES/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/enabling-github-actions-with-azure-blob-storage.md
@@ -1,6 +1,6 @@
 ---
 title: Habilitar las GitHub Actions con el almacenamiento de Azure Blob
-intro: 'You can enable {% data variables.product.prodname_actions %} on {% data variables.product.prodname_ghe_server %} and use Azure Blob storage to store data generated by workflow runs.'
+intro: 'Puedes habilitar las {% data variables.product.prodname_actions %} en {% data variables.product.prodname_ghe_server %} y utilizar el almacenamiento de blobs de Azure para almacenar los datos que generan las ejecuciones de flujo de trabajo.'
 permissions: 'Site administrators can enable {% data variables.product.prodname_actions %} and configure enterprise settings.'
 versions:
   ghes: '*'
@@ -19,7 +19,7 @@ shortTitle: Azure Blob storage
 
 Antes de que habilites las {% data variables.product.prodname_actions %}, asegúrate de que has completado los siguientes pasos:
 
-* Create your Azure storage account for storing workflow data. {% data variables.product.prodname_actions %} almacena sus datos como blobs de bloque y son compatibles dos tipos de cuenta de almacenamiento:
+* Crea tu cuenta de almacenamiento de Azure para almacenar datos de flujo de trabajo. {% data variables.product.prodname_actions %} almacena sus datos como blobs de bloque y son compatibles dos tipos de cuenta de almacenamiento:
   * Una cuenta de almacenamiento para ** propósitos generales** (también conocida como `general-purpose v1` o `general-purpose v2`) que utiliza el nivel de rendimiento **estándar**.
 
     {% warning %}
diff --git a/translations/es-ES/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/enabling-github-actions-with-minio-gateway-for-nas-storage.md b/translations/es-ES/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/enabling-github-actions-with-minio-gateway-for-nas-storage.md
index aa0035bd7f..36f731dae5 100644
--- a/translations/es-ES/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/enabling-github-actions-with-minio-gateway-for-nas-storage.md
+++ b/translations/es-ES/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/enabling-github-actions-with-minio-gateway-for-nas-storage.md
@@ -1,6 +1,6 @@
 ---
 title: Habilitar las GitHub Actions con la puerta de enlace de MinIO para el almacenamiento en NAS
-intro: 'You can enable {% data variables.product.prodname_actions %} on {% data variables.product.prodname_ghe_server %} and use MinIO Gateway for NAS storage to store data generated by workflow runs.'
+intro: 'Puedes habilitar las {% data variables.product.prodname_actions %} en {% data variables.product.prodname_ghe_server %} y utilizar MinIO Gateway para almacenamiento de NAS para almacenar los datos que generan las ejecuciones de flujo de trabajo.'
 permissions: 'Site administrators can enable {% data variables.product.prodname_actions %} and configure enterprise settings.'
 versions:
   ghes: '*'
@@ -22,7 +22,7 @@ shortTitle: Puerta de enlace de MinIO para el almacenamiento en NAS
 Antes de que habilites las {% data variables.product.prodname_actions %}, asegúrate de que has completado los siguientes pasos:
 
 * Para evitar la contención de recursos en el aplicativo, te recomendamos que hospedes a MinIO separado de {% data variables.product.product_location %}.
-* Create your bucket for storing workflow data. Para configurar tu bucket y clave de acceso, consulta la [Documentación de MinIO](https://docs.min.io/docs/minio-gateway-for-nas.html). {% indented_data_reference reusables.actions.enterprise-s3-permission spaces=2 %}
+* Crea tu bucket para almacenar datos de flujo de trabajo. Para configurar tu bucket y clave de acceso, consulta la [Documentación de MinIO](https://docs.min.io/docs/minio-gateway-for-nas.html). {% indented_data_reference reusables.actions.enterprise-s3-permission spaces=2 %}
 
 {% data reusables.actions.enterprise-common-prereqs %}
 
diff --git a/translations/es-ES/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/managing-self-hosted-runners-for-dependabot-updates.md b/translations/es-ES/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/managing-self-hosted-runners-for-dependabot-updates.md
index aa9228fe11..b92b778145 100644
--- a/translations/es-ES/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/managing-self-hosted-runners-for-dependabot-updates.md
+++ b/translations/es-ES/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/managing-self-hosted-runners-for-dependabot-updates.md
@@ -1,5 +1,5 @@
 ---
-title: Managing self-hosted runners for Dependabot updates on your enterprise
+title: Administrar los ejecutores auto-hospedados para las actualizaciones del Dependabot en tu empresa
 intro: 'Puedes crear ejecutores dedicados para {% data variables.product.product_location %} que utilice el {% data variables.product.prodname_dependabot %} para crear solicitudes de cambio para ayudar a asegurar y mantener las dependencias que se utilizan en los repositorios de tu empresa.'
 redirect_from:
   - /admin/github-actions/enabling-github-actions-for-github-enterprise-server/setting-up-dependabot-updates
@@ -12,45 +12,45 @@ topics:
   - Security
   - Dependabot
   - Dependencies
-shortTitle: Dependabot updates
+shortTitle: Actualizaciones del dependabot
 ---
 
 {% data reusables.dependabot.beta-security-and-version-updates %}
 
-## About self-hosted runners for {% data variables.product.prodname_dependabot_updates %}
+## Acerca de los ejecutores auto-hospedados para las {% data variables.product.prodname_dependabot_updates %}
 
-You can help users of {% data variables.product.product_location %} to create and maintain secure code by setting up {% data variables.product.prodname_dependabot %} security and version updates. With {% data variables.product.prodname_dependabot_updates %}, developers can configure repositories so that their dependencies are updated and kept secure automatically. Para obtener más información, consulta la sección "[Habilitar la {% data variables.product.prodname_dependabot %} en tu empresa](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise)".
+Puedes ayudar a que los usuarios de {% data variables.product.product_location %} creen y mantengan un código seguro si configuras la seguridad y las actualizaciones de versión del {% data variables.product.prodname_dependabot %}. Con las {% data variables.product.prodname_dependabot_updates %}, los desarrolladores pueden configurar repositorios para que sus dependencias se actualicen y se mantengan seguras automáticamente. Para obtener más información, consulta la sección "[Habilitar la {% data variables.product.prodname_dependabot %} en tu empresa](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise)".
 
-To use {% data variables.product.prodname_dependabot_updates %} on {% data variables.product.product_location %}, you must configure self-hosted runners to create the pull requests that will update dependencies.
+Para utilizar las {% data variables.product.prodname_dependabot_updates %} en {% data variables.product.product_location %}, debes configurar los ejecutores auto-hospedados para crear las solicitudes de cambios que actualizarán las dependencias.
 
 ## Prerrequisitos
 
 {% if dependabot-updates-github-connect %}
-Configuring self-hosted runners is only one step in the middle of the process for enabling {% data variables.product.prodname_dependabot_updates %}. There are several steps you must follow before these steps, including configuring {% data variables.product.product_location %} to use {% data variables.product.prodname_actions %} with self-hosted runners. Para obtener más información, consulta la sección "[Habilitar la {% data variables.product.prodname_dependabot %} en tu empresa](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise)".
+El configurar los ejecutores auto-hospedados es solo un paso en medio del proceso para habilitar las {% data variables.product.prodname_dependabot_updates %}. Hay varios pasos que debes seguir antes de estos, incluyendo el configurar a {% data variables.product.product_location %} para utilizar {% data variables.product.prodname_actions %} con ejecutores auto-hospedados. Para obtener más información, consulta la sección "[Habilitar la {% data variables.product.prodname_dependabot %} en tu empresa](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise)".
 {% else %}
-Before you configure self-hosted runners for {% data variables.product.prodname_dependabot_updates %}, you must:
+Antes de que configures los ejecutores auto-hospedados para {% data variables.product.prodname_dependabot_updates %}, debes:
 
-- Configure {% data variables.product.product_location %} to use {% data variables.product.prodname_actions %} with self-hosted runners. Para obtener más información, consulta la sección "[Iniciar con las {% data variables.product.prodname_actions %} para GitHub Enterprise Server](/admin/github-actions/enabling-github-actions-for-github-enterprise-server/getting-started-with-github-actions-for-github-enterprise-server)".
-- Enable {% data variables.product.prodname_dependabot_alerts %} for your enterprise. Para obtener más información, consulta la sección "[Habilitar la {% data variables.product.prodname_dependabot %} en tu empresa](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise)".
+- Configurar {% data variables.product.product_location %} para utilizar las {% data variables.product.prodname_actions %} con ejecutores auto-hospedados. Para obtener más información, consulta la sección "[Iniciar con las {% data variables.product.prodname_actions %} para GitHub Enterprise Server](/admin/github-actions/enabling-github-actions-for-github-enterprise-server/getting-started-with-github-actions-for-github-enterprise-server)".
+- Habilitar las {% data variables.product.prodname_dependabot_alerts %} para tu empresa. Para obtener más información, consulta la sección "[Habilitar la {% data variables.product.prodname_dependabot %} en tu empresa](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise)".
 {% endif %}
 
-## Configuring self-hosted runners for {% data variables.product.prodname_dependabot_updates %}
+## Configurar los ejecutores auto-hospedados para las {% data variables.product.prodname_dependabot_updates %}
 
-After you configure {% data variables.product.product_location %} to use {% data variables.product.prodname_actions %}, you need to add self-hosted runners for {% data variables.product.prodname_dependabot_updates %}.
+Después de que configuras {% data variables.product.product_location %} para que utilice las {% data variables.product.prodname_actions %}, necesitas agregar ejecutores auto-hospedados para las {% data variables.product.prodname_dependabot_updates %}.
 
-### System requirements for {% data variables.product.prodname_dependabot %} runners
+### Requisitos de sistema para los ejecutores del {% data variables.product.prodname_dependabot %}
 
-Any VM that you use for {% data variables.product.prodname_dependabot %} runners must meet the requirements for self-hosted runners. In addition, they must meet the following requirements.
+Cualquier máquina virtual que utilices para los ejecutores del {% data variables.product.prodname_dependabot %} debe cumplir con los requisitos de los ejecutores auto-hospedados. Adicionalmente, deben cumplir con los siguientes requisitos.
 
-- Linux operating system
-- Git installed
-- Docker installed with access for the runner users:
-  - We recommend installing Docker in rootless mode and configuring the runners to access Docker without `root` privileges.
-  - Alternatively, install Docker and give the runner users raised privileges to run Docker.
+- Sistema operativo Linux
+- Git instalado
+- Docker instalado con acceso para los usuarios del ejecutor:
+  - Recomendamos instalar Docker en modo sin raíz y configurar los ejecutores para acceder a Docker sin privilegios de `root`.
+  - Como alternativa, instala Docker y otorga a los usuarios del ejecutor privilegios superiores para ejecutarlo.
 
-The CPU and memory requirements will depend on the number of concurrent runners you deploy on a given VM. As guidance, we have successfully set up 20 runners on a single 2 CPU 8GB machine, but ultimately, your CPU and memory requirements will heavily depend on the repositories being updated. Some ecosystems will require more resources than others.
+Los requisitos de memoria y CPU dependerán de la cantidad de ejecutores simultáneos que despliegues en una MV determinada. Como orientación, configuramos exitosamente 20 ejecutores en una sola máquina de 2 CPU y 8 GB pero, en última instancia, tus requisitos de memoria y CPU dependerán fuertemente de los repositorios que se vayan a actualizar. Algunos ecosistemas requerirán más recursos que otros.
 
-If you specify more than 14 concurrent runners on a VM, you must also update the Docker `/etc/docker/daemon.json` configuration to increase the default number of networks Docker can create.
+Si especificas más de 14 ejecutores simultáneos en una MV, también debes actualizar la configuración de `/etc/docker/daemon.json` de Docker para incrementar la cantidad predeterminada de redes que Docker puede crear.
 
 ```
 {
@@ -60,23 +60,23 @@ If you specify more than 14 concurrent runners on a VM, you must also update the
 }
 ```
 
-### Network requirements for {% data variables.product.prodname_dependabot %} runners
+### Requisitos de red para los ejecutores del {% data variables.product.prodname_dependabot %}
 
-Los ejecutores del {% data variables.product.prodname_dependabot %} necesitan acceso al internet público, a {% data variables.product.prodname_dotcom_the_website %} y a cualquier registro interno que se utilizará en las actualizaciones del {% data variables.product.prodname_dependabot %}. To minimize the risk to your internal network, you should limit access from the Virtual Machine (VM) to your internal network. This reduces the potential for damage to internal systems if a runner were to download a hijacked dependency.
+Los ejecutores del {% data variables.product.prodname_dependabot %} necesitan acceso al internet público, a {% data variables.product.prodname_dotcom_the_website %} y a cualquier registro interno que se utilizará en las actualizaciones del {% data variables.product.prodname_dependabot %}. Para minimizar el riesgo de tu red interna, debes limitar el acceso desde la máquina virtual (MV) a tu red interna. Esto reduce el potencial de daño a los sistemas internos si un ejecutor descargara una dependencia secuestrada.
 
-### Adding self-hosted runners for {% data variables.product.prodname_dependabot %} updates
+### Agregar ejecutores auto-hospedados para las actualizaciones del {% data variables.product.prodname_dependabot %}
 
-1. Provision self-hosted runners, at the repository, organization, or enterprise account level. Para obtener más información, consulta las secciones "[Acerca de los ejecutores auto-hospedados](/actions/hosting-your-own-runners/about-self-hosted-runners)" y "[Agregar ejecutores auto-hospedados](/actions/hosting-your-own-runners/adding-self-hosted-runners)".
+1. Aprovisionar los ejecutores auto-hospedados a nivel de cuenta empresarial, organizacional o de repositorio. Para obtener más información, consulta las secciones "[Acerca de los ejecutores auto-hospedados](/actions/hosting-your-own-runners/about-self-hosted-runners)" y "[Agregar ejecutores auto-hospedados](/actions/hosting-your-own-runners/adding-self-hosted-runners)".
 
-2. Set up the self-hosted runners with the requirements described above. For example, on a VM running Ubuntu 20.04 you would:
+2. Configurar los ejecutores auto hospedados con los requisitos que se describen anteriormente. Por ejemplo, en una MV que ejecuta Ubuntu 20.04, lo que harías sería:
 
-   - Verify that Git is installed: `command -v git`
-   - Install Docker and ensure that the runner users have access to Docker. For more information, see the Docker documentation.
-     - [Install Docker Engine on Ubuntu](https://docs.docker.com/engine/install/ubuntu/)
-     - Recommended approach: [Run the Docker daemon as a non-root user (Rootless mode)](https://docs.docker.com/engine/security/rootless/)
-     - Alternative approach: [Manage Docker as a non-root user](https://docs.docker.com/engine/install/linux-postinstall/#manage-docker-as-a-non-root-user)
-   - Verify that the runners have access to the public internet and can only access the internal networks that {% data variables.product.prodname_dependabot %} needs.
+   - Verificar que Git esté instalado: `command -v git`
+   - Instalar Docker y asegurarte de que los usuarios del ejecutor tengan acceso a él. Para obtener más información, consulta la documentación de Docker.
+     - [Instalar Docker Engine en Ubuntu](https://docs.docker.com/engine/install/ubuntu/)
+     - Enfoque recomendado: [Ejecuta el Docker daemon como un usuario no raíz (Modo sin raíz)](https://docs.docker.com/engine/security/rootless/)
+     - Enfoque alterno: [Administra Docker como un usuario sin raíz](https://docs.docker.com/engine/install/linux-postinstall/#manage-docker-as-a-non-root-user)
+   - Verificar que los ejecutores tengan acceso al internet público y solo puedan acceder a las redes internas que necesita el {% data variables.product.prodname_dependabot %}.
 
-3. Assign a `dependabot` label to each runner you want {% data variables.product.prodname_dependabot %} to use. Para obtener más información, consulta la sección "[Utilizar etiquetas con ejecutores auto-hospedados](/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners#assigning-a-label-to-a-self-hosted-runner)".
+3. Asignar una etiqueta del `dependabot` a cada ejecutor que quieras que utilice el {% data variables.product.prodname_dependabot %}. Para obtener más información, consulta la sección "[Utilizar etiquetas con ejecutores auto-hospedados](/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners#assigning-a-label-to-a-self-hosted-runner)".
 
-4. Optionally, enable workflows triggered by {% data variables.product.prodname_dependabot %} to use more than read-only permissions and to have access to any secrets that are normally available. Para obtener más información, consulta la sección "[Solucionar los problemas de las {% data variables.product.prodname_actions %} en tu empresa](/admin/github-actions/advanced-configuration-and-troubleshooting/troubleshooting-github-actions-for-your-enterprise#enabling-workflows-triggered-by-dependabot-access-to-dependabot-secrets-and-increased-permissions)".
+4. Opcionalmente, habilitar los flujos de trabajo que activa el {% data variables.product.prodname_dependabot %} para utilizar más que los permisos de solo lectura y para tener acceso a cualquier secreto que esté disponible habitualmente. Para obtener más información, consulta la sección "[Solucionar los problemas de las {% data variables.product.prodname_actions %} en tu empresa](/admin/github-actions/advanced-configuration-and-troubleshooting/troubleshooting-github-actions-for-your-enterprise#enabling-workflows-triggered-by-dependabot-access-to-dependabot-secrets-and-increased-permissions)".
diff --git a/translations/es-ES/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server.md b/translations/es-ES/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server.md
index 5849e1e2b7..d68eca04af 100644
--- a/translations/es-ES/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server.md
+++ b/translations/es-ES/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server.md
@@ -26,7 +26,7 @@ Este artículo explica cómo los administradores de sitio pueden habilitar {% da
 
 {% data reusables.enterprise.upgrade-ghes-for-actions %}
 
-{% data reusables.actions.ghes-actions-not-enabled-by-default %} Necesitarás determinar si tu instancia tiene recursos de CPU y memoria adecuados para manejar la carga de {% data variables.product.prodname_actions %} sin causar una pérdida de rendimiento e incrementar esos recursos posiblemente. You'll also need to decide which storage provider you'll use for the blob storage required to store artifacts{% if actions-caching %} and caches{% endif %} generated by workflow runs. Entonces, habilitarás las {% data variables.product.prodname_actions %} para tu empresa, administrarás los permisos de acceso y agregarás los ejecutores auto-hospedados para ejecutar los flujos de trabajo.
+{% data reusables.actions.ghes-actions-not-enabled-by-default %} Necesitarás determinar si tu instancia tiene recursos de CPU y memoria adecuados para manejar la carga de {% data variables.product.prodname_actions %} sin causar una pérdida de rendimiento e incrementar esos recursos posiblemente. También necesitarás decidir qué proveedor de almacenamiento utilizarás para el almacenamiento de blobs que se requiere para almacenar los artefactos{% if actions-caching %} y cachés{% endif %} que se generan con las ejecuciones de trabajo. Entonces, habilitarás las {% data variables.product.prodname_actions %} para tu empresa, administrarás los permisos de acceso y agregarás los ejecutores auto-hospedados para ejecutar los flujos de trabajo.
 
 {% data reusables.actions.introducing-enterprise %}
 
@@ -85,11 +85,11 @@ La simultaneidad máxima se midió utilizando repositorios múltiples, una durac
 
 {% data reusables.actions.hardware-requirements-3.5 %}
 
-{% data variables.product.company_short %} measured maximum concurrency using multiple repositories, job duration of approximately 10 minutes, and 10 MB artifact uploads. Puedes experimentar rendimientos diferentes dependiendo de los niveles de actividad generales de tu instancia.
+{% data variables.product.company_short %} midió la concurrencia máxima utilizando repositorios múltiples, duraciones de job de aproximadamente 10 minutos y cargas de artefactos de 10 MB. Puedes experimentar rendimientos diferentes dependiendo de los niveles de actividad generales de tu instancia.
 
 {% note %}
 
-**Note:** Beginning with {% data variables.product.prodname_ghe_server %} 3.5, {% data variables.product.company_short %}'s internal testing uses 3rd generation CPUs to better reflect a typical customer configuration. This change in CPU represents a small portion of the changes to performance targets in this version of {% data variables.product.prodname_ghe_server %}.
+**Nota:** Comenzando con {% data variables.product.prodname_ghe_server %} 3.5, las pruebas internas de {% data variables.product.company_short %} utilizan CPU de tercera generación para reflejar mejor una configuración de cliente habitual. Este cambio en el CPU representa una porción pequeña de los cambios a los objetivos de desempeño en esta versión de {% data variables.product.prodname_ghe_server %}.
 
 {% endnote %}
 
@@ -111,7 +111,7 @@ Para obtener más información acerca de los requisitos mínimos de {% data vari
 
 {% ifversion ghes > 3.4 %}
 
-Optionally, you can limit resource consumption on {% data variables.product.product_location %} by configuring a rate limit for {% data variables.product.prodname_actions %}. Para obtener más información, consulta "[Configurar límites de tasa](/admin/configuration/configuring-your-enterprise/configuring-rate-limits#configuring-rate-limits-for-github-actions)."
+Opcionalmente, puedes limitar el consumo de recursos en {% data variables.product.product_location %} si configuras un límite de tasa para {% data variables.product.prodname_actions %}. Para obtener más información, consulta "[Configurar límites de tasa](/admin/configuration/configuring-your-enterprise/configuring-rate-limits#configuring-rate-limits-for-github-actions)."
 
 {% endif %}
 
@@ -119,7 +119,7 @@ Optionally, you can limit resource consumption on {% data variables.product.prod
 
 Para habilitar {% data variables.product.prodname_actions %} en {% data variables.product.prodname_ghe_server %}, debes tener acceso al almacenamiento externo de blobs.
 
-{% data variables.product.prodname_actions %} uses blob storage to store data generated by workflow runs, such as workflow logs{% if actions-caching %}, caches,{% endif %} and user-uploaded build artifacts. La cantidad de almacenamiento requerida dependerá de tu uso de {% data variables.product.prodname_actions %}. Sólo se admite una sola configuración de almacenamiento externo y no puedes utilizar varios proveedores de almacenamiento al mismo tiempo.
+{% data variables.product.prodname_actions %} utiliza el almacenamiento de blobs para almacenar los datos que generan las ejecuciones de flujo de trabajo, tales como las bitácoras de flujos de trabajo{% if actions-caching %}, los cachés{% endif %} y los artefactos de compilación que suben los usuarios. La cantidad de almacenamiento requerida dependerá de tu uso de {% data variables.product.prodname_actions %}. Sólo se admite una sola configuración de almacenamiento externo y no puedes utilizar varios proveedores de almacenamiento al mismo tiempo.
 
 {% data variables.product.prodname_actions %} es compatible con estos proveedores de almacenamiento:
 
diff --git a/translations/es-ES/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise.md b/translations/es-ES/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise.md
index f8296f4137..99f1f3cf38 100644
--- a/translations/es-ES/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise.md
+++ b/translations/es-ES/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise.md
@@ -26,9 +26,9 @@ Antes de que incluyas las {% data variables.product.prodname_actions %} en una e
 
 Deberías crear un plan que rija el uso de las {% data variables.product.prodname_actions %} en tu empersa y logre tus obligaciones de cumplimiento.
 
-Determine which actions {% if actions-workflow-policy %}and reusable workflows{% endif %} your developers will be allowed to use. {% ifversion ghes %}First, decide whether you'll enable access to actions {% if actions-workflow-policy %}and reusable workflows{% endif %} from outside your instance. {% data reusables.actions.access-actions-on-dotcom %} Para obtener más información, consulta la sección "[Acerca de utilizar acciones en tu empresa](/admin/github-actions/managing-access-to-actions-from-githubcom/about-using-actions-in-your-enterprise)".
+Determina qué acciones {% if actions-workflow-policy %}y flujos de trabajo reutilizables{% endif %} se permitirán para que las utilicen tus desarrolladores. {% ifversion ghes %}Primero, decide si habilitarás el acceso a las acciones {% if actions-workflow-policy %}y flujos de trabajo reutilizables{% endif %} desde fuera de tu instancia. {% data reusables.actions.access-actions-on-dotcom %} Para obtener más información, consulta la sección "[Acerca de utilizar acciones en tu empresa](/admin/github-actions/managing-access-to-actions-from-githubcom/about-using-actions-in-your-enterprise)".
 
-Then,{% else %}First,{% endif %} decide whether you'll allow third-party actions {% if actions-workflow-policy %}and reusable workflows{% endif %} that were not created by {% data variables.product.company_short %}. You can configure the actions {% if actions-workflow-policy %}and reusable workflows{% endif %} that are allowed to run at the repository, organization, and enterprise levels and can choose to only allow actions that are created by {% data variables.product.company_short %}. If you do allow third-party actions{% if actions-workflow-policy %} and reusable workflows{% endif %}, you can limit allowed actions to those created by verified creators or a list of specific actions{% if actions-workflow-policy %} and reusable workflows{% endif %}. Para obtener más información, consulta las secciones "[Administrar los ajustes de {% data variables.product.prodname_actions %} para un repositorio](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#managing-github-actions-permissions-for-your-repository)", "[Inhabilitar o limitar las {% data variables.product.prodname_actions %} para tu organización](/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization#managing-github-actions-permissions-for-your-organization)" y "[Requerir políticas para las {% data variables.product.prodname_actions %} en tu empresa](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise#enforcing-a-policy-to-restrict-the-use-of-github-actions-in-your-enterprise)".
+Después, {% else %}Primero,{% endif %} decide si permitirás acciones {% if actions-workflow-policy %}y flujos de trabajo reutilizables{% endif %} de terceros que no haya creado {% data variables.product.company_short %}. Puedes configurar las acciones {% if actions-workflow-policy %}y flujos de trabajo reutilizables{% endif %} que se permitirán para ejecutar a nivel de repositorio, organización y empresa y elegir únicamente las acciones que haya creado {% data variables.product.company_short %}. Si permites acciones{% if actions-workflow-policy %} y flujos de trabajo reutilizables{% endif %} de terceros, puedes limitar las acciones permitidas a aquellas de los creadores verificados o una lista de acciones{% if actions-workflow-policy %} y flujos de trabajo reutilizables{% endif %} específicos. Para obtener más información, consulta las secciones "[Administrar los ajustes de {% data variables.product.prodname_actions %} para un repositorio](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#managing-github-actions-permissions-for-your-repository)", "[Inhabilitar o limitar las {% data variables.product.prodname_actions %} para tu organización](/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization#managing-github-actions-permissions-for-your-organization)" y "[Requerir políticas para las {% data variables.product.prodname_actions %} en tu empresa](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise#enforcing-a-policy-to-restrict-the-use-of-github-actions-in-your-enterprise)".
 
 {% if actions-workflow-policy %}
 ![Captura de pantalla de las políticas de {% data variables.product.prodname_actions %}](/assets/images/help/organizations/enterprise-actions-policy-with-workflows.png)
@@ -111,15 +111,15 @@ Finalmente, deberías considerar el fortalecimiento de seguridad para los ejecut
 
 {% data reusables.actions.about-artifacts %} Para obtener más información, consulta la sección "[Almacenar datos de flujo de trabajo como artefactos](/actions/advanced-guides/storing-workflow-data-as-artifacts)".
 
-{% if actions-caching %}{% data variables.product.prodname_actions %} also has a caching system that you can use to cache dependencies to speed up workflow runs. For more information, see "[Caching dependencies to speed up workflows](/actions/using-workflows/caching-dependencies-to-speed-up-workflows)."{% endif %}
+{% if actions-caching %}{% data variables.product.prodname_actions %} también tiene un sistema de almacenamiento en caché que puedes utilizar para guardar las dependencias en caché y acelerar las ejecuciones de flujo de trabajo. Para obtener más información, consulta la sección "[Almacenar las dependencias en caché para agilizar los flujos de trabajo](/actions/using-workflows/caching-dependencies-to-speed-up-workflows)".{% endif %}
 
 {% ifversion ghes %}
-You must configure external blob storage for workflow artifacts{% if actions-caching %}, caches,{% endif %} and other workflow logs. Decide qué proveedor de almacenamiento compatible utilizará tu empresa. Para obtener más información, consulta la sección "[Iniciar con las {% data variables.product.prodname_actions %} para {% data variables.product.product_name %}](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server#external-storage-requirements)".
+Debes configurar el almacenamiento de blobs externo para los artefactos de flujos de trabajo{% if actions-caching %}, cachés, {% endif %} y otras bitácoras de flujo de trabajo. Decide qué proveedor de almacenamiento compatible utilizará tu empresa. Para obtener más información, consulta la sección "[Iniciar con las {% data variables.product.prodname_actions %} para {% data variables.product.product_name %}](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server#external-storage-requirements)".
 {% endif %}
 
 {% ifversion ghec or ghes %}
 
-You can use policy settings for {% data variables.product.prodname_actions %} to customize the storage of workflow artifacts{% if actions-caching %}, caches,{% endif %} and log retention. Para obtener más información, consulta la sección "[Requerir políticas para las {% data variables.product.prodname_actions %} en tu empresa](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise)".
+Puedes utilizar los ajustes de política para que {% data variables.product.prodname_actions %} personalice el almacenamiento de los artefactos de flujo de trabajo{% if actions-caching %}, cachés{% endif %} y retención de bitácoras. Para obtener más información, consulta la sección "[Requerir políticas para las {% data variables.product.prodname_actions %} en tu empresa](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise)".
 
 {% endif %}
 
diff --git a/translations/es-ES/content/admin/identity-and-access-management/index.md b/translations/es-ES/content/admin/identity-and-access-management/index.md
index 4c7491bced..3537525ef2 100644
--- a/translations/es-ES/content/admin/identity-and-access-management/index.md
+++ b/translations/es-ES/content/admin/identity-and-access-management/index.md
@@ -1,6 +1,6 @@
 ---
 title: Administración de accesos y de identidad
-intro: 'You can configure how people access {% ifversion ghec or ghae %}your enterprise on {% data variables.product.product_name %}{% elsif ghes %}{% data variables.product.product_location %}{% endif %}.'
+intro: 'Puedes configurar la forma en la que las personas acceden {% ifversion ghec or ghae %}a tu empresa en {% data variables.product.product_name %}{% elsif ghes %}{% data variables.product.product_location %}{% endif %}.'
 redirect_from:
   - /enterprise/admin/authentication
   - /admin/authentication
diff --git a/translations/es-ES/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise.md b/translations/es-ES/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise.md
index 2ab41a06c4..2c79eeed6a 100644
--- a/translations/es-ES/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise.md
+++ b/translations/es-ES/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise.md
@@ -1,5 +1,5 @@
 ---
-title: About authentication for your enterprise
+title: Acerca de la autenticación para tu empresa
 shortTitle: Acerca de la autenticación
 intro: 'Debes {% ifversion ghae %}configurar el inicio de sesión único (SSO) de SAML para que las personas puedan{% else %}puedes elegir cómo las personas pueden{% endif %} autenticarse para acceder a {% ifversion ghec %}los recursos de tu empresa en {% data variables.product.product_name %}{% elsif ghes %}{% data variables.product.product_location %}{% elsif ghae %}tu empresa de {% data variables.product.product_name %}{% endif %}.'
 versions:
@@ -19,15 +19,17 @@ topics:
 
 {% ifversion ghec %}
 
-Enterprise owners on {% data variables.product.product_name %} can control the requirements for authentication and access to the enterprise's resources. You can choose to allow members create and manage user accounts, or your enterprise can create and manage accounts for members. If you allow members to manage their own accounts, you can also configure SAML authentication to both increase security and centralize identity and access for the web applications that your team uses. If you choose to manage your members' user accounts, you must configure SAML authentication.
+Enterprise owners on {% data variables.product.product_name %} can control the requirements for authentication and access to the enterprise's resources.
 
-## Authentication methods for {% data variables.product.product_name %}
+You can choose to allow members to create and manage user accounts, or your enterprise can create and manage accounts for members with {% data variables.product.prodname_emus %}. If you allow members to manage their own accounts, you can also configure SAML authentication to both increase security and centralize identity and access for the web applications that your team uses. If you choose to manage your members' user accounts, you must configure SAML authentication.
+
+## Métodos de autenticación para {% data variables.product.product_name %}
 
 The following options are available for account management and authentication on {% data variables.product.product_name %}.
 
-- [Authentication through {% data variables.product.product_location %}](#authentication-through-githubcom)
-- [Authentication through {% data variables.product.product_location %} with additional SAML access restriction](#authentication-through-githubcom-with-additional-saml-access-restriction)
-- [Authentication with {% data variables.product.prodname_emus %} and SAML SSO](#authentication-with-enterprise-managed-users-and-saml-sso)
+- [Autenticación mediante {% data variables.product.product_location %}](#authentication-through-githubcom)
+- [Autenticación mediante {% data variables.product.product_location %} con restricción de acceso adicional de SAML](#authentication-through-githubcom-with-additional-saml-access-restriction)
+- [Autenticación con las {% data variables.product.prodname_emus %} y el SSO de SAML](#authentication-with-enterprise-managed-users-and-saml-sso)
 
 ### Autenticación mediante {% data variables.product.product_location %}
 
@@ -51,8 +53,8 @@ Site administrators can decide how people authenticate to access a {% data varia
 
 The following authentication methods are available for {% data variables.product.product_name %}.
 
-- [Built-in authentication](#built-in-authentication)
-- [External authentication](#external-authentication)
+- [Autenticación incorporada](#built-in-authentication)
+- [Autenticación externa](#external-authentication)
 
 ### Autenticación incorporada
 
@@ -62,11 +64,11 @@ The following authentication methods are available for {% data variables.product
 
 If you use an external directory or identity provider (IdP) to centralize access to multiple web applications, you may be able to configure external authentication for {% data variables.product.product_location %}. Para obtener más información, consulta lo siguiente.
 
-- "[Using CAS for enterprise IAM](/admin/identity-and-access-management/using-cas-for-enterprise-iam)"
-- "[Using LDAP for enterprise IAM](/admin/identity-and-access-management/using-ldap-for-enterprise-iam)"
-- "[Using SAML for enterprise IAM](/admin/identity-and-access-management/using-saml-for-enterprise-iam)"
+- "[Utilizar CAS para el IAM empresarial](/admin/identity-and-access-management/using-cas-for-enterprise-iam)"
+- "[Utilizar LDAP para el IAM empresarial](/admin/identity-and-access-management/using-ldap-for-enterprise-iam)"
+- "[Utilizar SAML para el IAM empresarial](/admin/identity-and-access-management/using-saml-for-enterprise-iam)"
 
-If you choose to use external authentication, you can also configure fallback authentication for people who don't have an account on your external authentication provider. For example, you may want to grant access to a contractor or machine user. Para obtener más información, consulta la sección "[Permitir la autenticación integrada para los usuarios fuera de tu proveedor](/admin/identity-and-access-management/managing-iam-for-your-enterprise/allowing-built-in-authentication-for-users-outside-your-provider)".
+If you choose to use external authentication, you can also configure fallback authentication for people who don't have an account on your external authentication provider. For example, you may want to grant access to a contractor or machine user. For more information, see "[Allowing built-in authentication for users outside your provider](/admin/identity-and-access-management/managing-iam-for-your-enterprise/allowing-built-in-authentication-for-users-outside-your-provider)."
 
 {% elsif ghae %}
 
diff --git a/translations/es-ES/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/index.md b/translations/es-ES/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/index.md
index 9d5c80ef2c..c97f877b08 100644
--- a/translations/es-ES/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/index.md
+++ b/translations/es-ES/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/index.md
@@ -2,11 +2,11 @@
 title: Administrar el IAM para tu empresa
 intro: |
   {%- ifversion ghec %}
-  You can invite existing personal accounts on {% data variables.product.product_location %} to be members of your enterprise, and you can optionally enable SAML single sign-on (SSO) to centrally manage access. Alternatively, you can use {% data variables.product.prodname_emus %} with SAML SSO to create and control the accounts of your enterprise members.
+  Puedes invitar a las cuentas personales existentes de {% data variables.product.product_location %} para que se conviertan en miembros de tu empresa y, opcionalmente, puedes habilitar el inicio de sesión único (SSO) de SAML para administrar el acceso centralmente. Como alternativa, puedes utilizar las {% data variables.product.prodname_emus %} con el SSO de SAML para crear y controlar las cuentas de los miembros de tu empresa.
   {%- elsif ghes %}
-  You can use {% data variables.product.product_name %}'s built-in authentication, or you can centrally manage authentication and access to your instance with CAS, LDAP, or SAML.
+  Puedes utilizar la autenticación integrada de {% data variables.product.product_name %} o puedes administrar la autenticación centralmente y acceder a tu instancia con CAS, LDAP o SAML.
   {%- elsif ghae %}
-  You must use SAML single sign-on (SSO) to centrally manage authentication and access to your enterprise on {% data variables.product.product_name %}. Optionally, you can use System for Cross-domain Identity Management (SCIM) to automatically provision accounts and access on {% data variables.product.product_name %} when you make changes on your identity provider (IdP).
+  Debes utilizar el inicio de sesión único (SSO) de SAML para administrar centralmente la administración y el acceso a tu empresa de {% data variables.product.product_name %}. Opcionalmente, puedes utilizar el Sistema para Administración de Identidades entre Dominios (SCIM) para aprovisionar automáticamente las cuentas y acceder a {% data variables.product.product_name %} cuando hagas cambios en tu proveedor de identidad (IdP).
   {%- endif %}
 redirect_from:
   - /enterprise/admin/categories/authentication
@@ -30,6 +30,6 @@ children:
   - /username-considerations-for-external-authentication
   - /changing-authentication-methods
   - /allowing-built-in-authentication-for-users-outside-your-provider
-shortTitle: Manage IAM for your enterprise
+shortTitle: Administrar IAM para tu empresa
 ---
 
diff --git a/translations/es-ES/content/admin/identity-and-access-management/using-enterprise-managed-users-and-saml-for-iam/about-enterprise-managed-users.md b/translations/es-ES/content/admin/identity-and-access-management/using-enterprise-managed-users-and-saml-for-iam/about-enterprise-managed-users.md
index b9b8ebd554..6d70cafa66 100644
--- a/translations/es-ES/content/admin/identity-and-access-management/using-enterprise-managed-users-and-saml-for-iam/about-enterprise-managed-users.md
+++ b/translations/es-ES/content/admin/identity-and-access-management/using-enterprise-managed-users-and-saml-for-iam/about-enterprise-managed-users.md
@@ -88,7 +88,7 @@ Los {% data variables.product.prodname_managed_users_caps %} se deben autenticar
 
 ## Nombres de usuario e información de perfil
 
-{% data variables.product.product_name %} automatically creates a username for each person by normalizing an identifier provided by your IdP. For more information, see "[Username considerations for external authentication](/admin/identity-and-access-management/managing-iam-for-your-enterprise/username-considerations-for-external-authentication)."
+{% data variables.product.product_name %} automatically creates a username for each person by normalizing an identifier provided by your IdP. Para obtener más información, consulta la sección "[Consideraciones de nombre de usuario para la autenticación externa](/admin/identity-and-access-management/managing-iam-for-your-enterprise/username-considerations-for-external-authentication)".
 
 A conflict may occur when provisioning users if the unique parts of the identifier provided by your IdP are removed during normalization. If you're unable to provision a user due to a username conflict, you should modify the username provided by your IdP. For more information, see "[Resolving username conflicts](/admin/identity-and-access-management/managing-iam-for-your-enterprise/username-considerations-for-external-authentication#resolving-username-conflicts)."
 
diff --git a/translations/es-ES/content/admin/index.md b/translations/es-ES/content/admin/index.md
index 748106f050..0893395b8c 100644
--- a/translations/es-ES/content/admin/index.md
+++ b/translations/es-ES/content/admin/index.md
@@ -71,13 +71,13 @@ changelog:
 featuredLinks:
   guides:
     - '{% ifversion ghae %}/admin/user-management/auditing-users-across-your-enterprise{% endif %}'
+    - /admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise
+    - /admin/policies/enforcing-policies-for-your-enterprise/about-enterprise-policies
     - '{% ifversion ghae %}/admin/configuration/restricting-network-traffic-to-your-enterprise{% endif %}'
     - '{% ifversion ghes %}/admin/configuration/configuring-backups-on-your-appliance{% endif %}'
     - '{% ifversion ghes %}/admin/enterprise-management/creating-a-high-availability-replica{% endif %}'
     - '{% ifversion ghes %}/admin/overview/about-upgrades-to-new-releases{% endif %}'
     - '{% ifversion ghec %}/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise{% endif %}'
-    - '{% ifversion ghec %}/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/about-enterprise-managed-users{% endif %}'
-    - '{% ifversion ghec %}/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-identity-and-access-management-for-your-enterprise{% endif %}'
     - '{% ifversion ghec %}/admin/user-management/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise{% endif %}'
     - /admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-self-hosted-runners-for-your-enterprise
   guideCards:
diff --git a/translations/es-ES/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-azure.md b/translations/es-ES/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-azure.md
index eba0d42442..dd50990a57 100644
--- a/translations/es-ES/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-azure.md
+++ b/translations/es-ES/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-azure.md
@@ -1,6 +1,6 @@
 ---
 title: Instalar el servidor de GitHub Enterprise en Azure
-intro: 'To install {% data variables.product.prodname_ghe_server %} on Azure, you must deploy onto a memory-optimized instance that supports premium storage.'
+intro: 'Para instalar {% data variables.product.prodname_ghe_server %} en Azure, debes desplegar en una instancia optimizada en memoria que sea compatible con el almacenamiento premium.'
 redirect_from:
   - /enterprise/admin/guides/installation/installing-github-enterprise-on-azure
   - /enterprise/admin/installation/installing-github-enterprise-server-on-azure
@@ -30,7 +30,7 @@ Puedes implementar {% data variables.product.prodname_ghe_server %} en Azure mun
 
 ## Determinar el tipo de máquina virtual
 
-Antes de iniciar {% data variables.product.product_location %} en Azure, deberás determinar el tipo de máquina que mejor se adapte a las necesidades de tu organización. For more information about memory optimized machines, see "[Memory optimized virtual machine sizes](https://docs.microsoft.com/en-gb/azure/virtual-machines/sizes-memory)" in the Microsoft Azure documentation. To review the minimum resource requirements for {% data variables.product.product_name %}, see "[Minimum requirements](#minimum-requirements)."
+Antes de iniciar {% data variables.product.product_location %} en Azure, deberás determinar el tipo de máquina que mejor se adapte a las necesidades de tu organización. Para obtener más información sobre las máquinas con memoria optimizada, consulta la sección "[tamaños de máquina virtual con memoria optimizada](https://docs.microsoft.com/en-gb/azure/virtual-machines/sizes-memory)" en la documentación de Microsoft Azure. Para revisar los requisitos mínimos de recursos para {% data variables.product.product_name %}, consulta la sección "[Requisitos mínimos](#minimum-requirements)".
 
 
 {% data reusables.enterprise_installation.warning-on-scaling %}
diff --git a/translations/es-ES/content/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/exporting-server-statistics.md b/translations/es-ES/content/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/exporting-server-statistics.md
index dc31d65616..29c38c3256 100644
--- a/translations/es-ES/content/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/exporting-server-statistics.md
+++ b/translations/es-ES/content/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/exporting-server-statistics.md
@@ -10,7 +10,7 @@ redirect_from:
 
 {% data reusables.server-statistics.release-phase %}
 
-You can download up to the last 365 days of {% data variables.product.prodname_server_statistics %} data in a CSV or JSON file. This data, which includes aggregate metrics on repositories, issues, and pull requests, can help you anticipate the needs of your organization, understand how your team works, and show the value you get from {% data variables.product.prodname_ghe_server %}.
+You can download up to the last 365 days of {% data variables.product.prodname_server_statistics %} data in a CSV or JSON file. Estos datos, los cuales incluyen métricas agregadas en los repositorios, propuestas y solicitudes de cambio pueden ayudarte a anticipar las necesidades de tu organización, entender cómo funciona tu equipo y mostrarte el valor que obtienes de {% data variables.product.prodname_ghe_server %}.
 
 Before you can download this data, you must enable {% data variables.product.prodname_server_statistics %}. Para obtener más información, consulta la sección "[Habilitar la {% data variables.product.prodname_server_statistics %} en tu empresa](/admin/configuration/configuring-github-connect/enabling-server-statistics-for-your-enterprise)".
 
diff --git a/translations/es-ES/content/admin/overview/about-enterprise-accounts.md b/translations/es-ES/content/admin/overview/about-enterprise-accounts.md
index 14571af933..6ebe6cb0fe 100644
--- a/translations/es-ES/content/admin/overview/about-enterprise-accounts.md
+++ b/translations/es-ES/content/admin/overview/about-enterprise-accounts.md
@@ -32,18 +32,18 @@ The enterprise account on {% ifversion ghes %}{% data variables.product.product_
 
 {% endif %}
 
-Organizations are shared accounts where enterprise members can collaborate across many projects at once. Organization owners can manage access to the organization's data and projects with sophisticated security and administrative features. For more information, see {% ifversion ghec %}"[About organizations](/organizations/collaborating-with-groups-in-organizations/about-organizations)."{% elsif ghes or ghae %}"[About organizations](/organizations/collaborating-with-groups-in-organizations/about-organizations)" and "[Managing users, organizations, and repositories](/admin/user-management)."{% endif %}
+Organizations are shared accounts where enterprise members can collaborate across many projects at once. Organization owners can manage access to the organization's data and projects with sophisticated security and administrative features. For more information, see "[About organizations](/organizations/collaborating-with-groups-in-organizations/about-organizations)."
+
+{% ifversion ghec %} 
+Enterprise owners can invite existing organizations to join your enterprise account, or create new organizations in the enterprise settings.
+{% endif %}
+
+Your enterprise account allows you to manage and enforce policies for all the organizations owned by the enterprise. {% data reusables.enterprise.about-policies %} For more information, see "[About enterprise policies](/admin/policies/enforcing-policies-for-your-enterprise/about-enterprise-policies)."
 
 {% ifversion ghec %}
 
-Enterprise owners can create organizations and link the organizations to the enterprise. Alternatively, you can invite an existing organization to join your enterprise account. After you add organizations to your enterprise account, you can manage and enforce policies for the organizations. Specific enforcement options vary by setting; generally, you can choose to enforce a single policy for every organization in your enterprise account or allow owners to set policy on the organization level. For more information, see "[Setting policies for your enterprise](/admin/policies)."
-
 {% data reusables.enterprise.create-an-enterprise-account %} For more information, see "[Creating an enterprise account](/admin/overview/creating-an-enterprise-account)."
 
-{% elsif ghes or ghae %}
-
-For more information about the management of policies for your enterprise account, see "[Setting policies for your enterprise](/admin/policies)."
-
 {% endif %}
 
 ## About administration of your enterprise account
diff --git a/translations/es-ES/content/admin/overview/creating-an-enterprise-account.md b/translations/es-ES/content/admin/overview/creating-an-enterprise-account.md
index 635ac8a067..c5c9fa711c 100644
--- a/translations/es-ES/content/admin/overview/creating-an-enterprise-account.md
+++ b/translations/es-ES/content/admin/overview/creating-an-enterprise-account.md
@@ -16,7 +16,7 @@ shortTitle: Create enterprise account
 
 {% data variables.product.prodname_ghe_cloud %} includes the option to create an enterprise account, which enables collaboration between multiple organizations and gives administrators a single point of visibility and management. For more information, see "[About enterprise accounts](/admin/overview/about-enterprise-accounts)."
 
-{% data reusables.enterprise.create-an-enterprise-account %} If you pay by invoice, you can create an enterprise account yourself on {% data variables.product.prodname_dotcom %}. If not, you can [contact our sales team](https://github.com/enterprise/contact?ref_page=/pricing&ref_cta=Contact%20Sales&ref_loc=cards) to move to invoicing.
+{% data reusables.enterprise.create-an-enterprise-account %} If you pay by invoice, you can create an enterprise account yourself on {% data variables.product.prodname_dotcom %}. If not, you can [contact our sales team](https://github.com/enterprise/contact?ref_page=/pricing&ref_cta=Contact%20Sales&ref_loc=cards) to create an enterprise account for you.
 
 An enterprise account is included in {% data variables.product.prodname_ghe_cloud %}, so creating one will not affect your bill.
 
@@ -29,7 +29,10 @@ If the organization is connected to {% data variables.product.prodname_ghe_serve
 
 ## Creating an enterprise account on {% data variables.product.prodname_dotcom %}
 
-To create an enterprise account on {% data variables.product.prodname_dotcom %}, your organization must be using {% data variables.product.prodname_ghe_cloud %} and paying by invoice.
+To create an enterprise account, your organization must be using {% data variables.product.prodname_ghe_cloud %}.
+
+If you pay by invoice, you can create an enterprise account directly through {% data variables.product.prodname_dotcom %}. If you do not currently pay by invoice, you can [contact our sales team](https://github.com/enterprise/contact?ref_page=/pricing&ref_cta=Contact%20Sales&ref_loc=cards) to create an enterprise account for you.
+
 
 {% data reusables.organizations.billing-settings %}
 1. Click **Upgrade to enterprise account**.
diff --git a/translations/es-ES/content/admin/policies/enforcing-policies-for-your-enterprise/about-enterprise-policies.md b/translations/es-ES/content/admin/policies/enforcing-policies-for-your-enterprise/about-enterprise-policies.md
new file mode 100644
index 0000000000..b356459150
--- /dev/null
+++ b/translations/es-ES/content/admin/policies/enforcing-policies-for-your-enterprise/about-enterprise-policies.md
@@ -0,0 +1,30 @@
+---
+title: About enterprise policies
+intro: 'With enterprise policies, you can manage the policies for all the organizations owned by your enterprise.'
+versions:
+  ghec: '*'
+  ghes: '*'
+  ghae: '*'
+type: overview
+topics:
+  - Enterprise
+  - Policies
+---
+
+To help you enforce business rules and regulatory compliance, policies provide a single point of management for all the organizations owned by an enterprise account.
+
+{% data reusables.enterprise.about-policies %}
+
+For example, with the "Base permissions" policy, you can allow organization owners to configure the "Base permissions" policy for their organization, or you can enforce a specific base permissions level, such as "Read", for all organizations within the enterprise.
+
+By default, no enterprise policies are enforced. To identify policies that should be enforced to meet the unique requirements of your business, we recommend reviewing all the available policies in your enterprise account, starting with repository management policies. For more information, see "[Enforcing repository management polices in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise)."
+
+While you're configuring enterprise policies, to help you understand the impact of changing each policy, you can view the current configurations for the organizations owned by your enterprise.
+
+{% ifversion ghes %}
+Another way to enforce standards within your enterprise is to use pre-receive hooks, which are scripts that run on {% data variables.product.product_location %} to implement quality checks. For more information, see "[Enforcing policy with pre-receive hooks](/admin/policies/enforcing-policy-with-pre-receive-hooks)."
+{% endif %}
+
+## Leer más
+
+- "[Acerca de las cuentas de empresa](/admin/overview/about-enterprise-accounts)"
diff --git a/translations/es-ES/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise.md b/translations/es-ES/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise.md
index ac8de2f8e5..fa8fa9979e 100644
--- a/translations/es-ES/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise.md
+++ b/translations/es-ES/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise.md
@@ -121,35 +121,35 @@ Si se habilita una política para una empresa, esta puede inhabilitarse selectiv
 
 {% data reusables.actions.workflow-permissions-intro %}
 
-Puedes configurar los permisos predeterminados para del `GITHUB_TOKEN` en la configuración de tu empresa, organización o repositorio. If you choose a restricted option as the default in your enterprise settings, this prevents the more permissive setting being chosen in the organization or repository settings.
+Puedes configurar los permisos predeterminados para del `GITHUB_TOKEN` en la configuración de tu empresa, organización o repositorio. Si eliges la opción restringida como la predeterminada en tus ajustes de empresa, esto prevendrá que se elija el ajuste más permisivo en los ajustes de repositorio u organización.
 
 {% data reusables.actions.workflow-permissions-modifying %}
 
 ### Configuring the default `GITHUB_TOKEN` permissions
 
 {% if allow-actions-to-approve-pr-with-ent-repo %}
-By default, when you create a new enterprise, `GITHUB_TOKEN` only has read access for the `contents` scope.
+Predeterminadamente, cuando creas una empresa nueva, el `GITHUB_TOKEN` solo tendrá acceso de lectura para el alcance `contents`.
 {% endif %}
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.policies-tab %}
 {% data reusables.enterprise-accounts.actions-tab %}
-1. Under "Workflow permissions", choose whether you want the `GITHUB_TOKEN` to have read and write access for all scopes, or just read access for the `contents` scope.
+1. Debajo de "Permisos de flujo de trabajo", elige si quieres que el `GITHUB_TOKEN` tenga acceso de lectura y escritura para todos los alcances o solo acceso de lectura para el alcance `contents`.
 
    ![Configurar los permisos del GITHUB_TOKEN para esta empresa](/assets/images/help/settings/actions-workflow-permissions-enterprise{% if allow-actions-to-approve-pr-with-ent-repo %}-with-pr-approval{% endif %}.png)
 1. Da clic en **Guardar** para aplicar la configuración.
 
 {% if allow-actions-to-approve-pr-with-ent-repo %}
-### Preventing {% data variables.product.prodname_actions %} from creating or approving pull requests
+### Prevenir que las {% data variables.product.prodname_actions %} creen o aprueben solicitudes de cambio
 
 {% data reusables.actions.workflow-pr-approval-permissions-intro %}
 
-By default, when you create a new enterprise, workflows are not allowed to create or approve pull requests.
+Predeterminadamente, cuando creas una empresa nueva, no se permite que los flujos de trabajo creen o aprueben las solicitudes de cambio.
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.policies-tab %}
 {% data reusables.enterprise-accounts.actions-tab %}
-1. Under "Workflow permissions", use the **Allow GitHub Actions to create and approve pull requests** setting to configure whether `GITHUB_TOKEN` can create and approve pull requests.
+1. Debajo de "Permisos de flujo de trabajo", utiliza el ajuste **Permitir que las GitHub Actions creen y aprueben solicitudes de cambios** para configurar si el `GITHUB_TOKEN` puede crear y aprobar solicitudes de cambios.
 
    ![Configurar los permisos del GITHUB_TOKEN para esta empresa](/assets/images/help/settings/actions-workflow-permissions-enterprise-with-pr-approval.png)
 1. Da clic en **Guardar** para aplicar la configuración.
@@ -159,18 +159,18 @@ By default, when you create a new enterprise, workflows are not allowed to creat
 
 {% if actions-cache-policy-apis %}
 
-## Enforcing a policy for cache storage in your enterprise
+## Requerir una política para almacenamiento en caché dentro de tu empresa
 
 {% data reusables.actions.cache-default-size %} {% data reusables.actions.cache-eviction-process %}
 
-However, you can set an enterprise policy to customize both the default total cache size for each repository, as well as the maximum total cache size allowed for a repository. For example, you might want the default total cache size for each repository to be 5 GB, but also allow repository administrators to configure a total cache size up to 15 GB if necessary.
+Sin embargo, puedes configurar una política de empresa para personalizar tanto el tamaño total predeterminado de almacenamiento en caché para cada repositorio como el tamaño total máximo de almacenamiento en caché permitido para un repositorio individual. Por ejemplo, podrías querer que el tamaño de caché total predeterminado para cada repositorio sea de 5GB, pero también permitir que los administradores configuren un tamaño total de almacenamiento en caché de 15 GB de ser necesario.
 
-People with admin access to a repository can set a total cache size for their repository up to the maximum cache size allowed by the enterprise policy setting.
+Las personas con acceso administrativo a un repositorio pueden configurar un tamaño total de almacenamiento en caché para su repositorio de has el tamaño máximo permitido por el ajuste de la política empresarial.
 
-The policy settings for {% data variables.product.prodname_actions %} cache storage can currently only be modified using the REST API:
+Los ajustes de política para el almacenamiento en caché de {% data variables.product.prodname_actions %} actualmente solo pueden modificarse utilizando la API de REST:
 
-* To view the current enterprise policy settings, see "[Get GitHub Actions cache usage policy for an enterprise](/rest/actions/cache#get-github-actions-cache-usage-policy-for-an-enterprise)."
-* To change the enterprise policy settings, see "[Set GitHub Actions cache usage policy for an enterprise](/rest/actions/cache#get-github-actions-cache-usage-policy-for-an-enterprise)."
+* Para ver los ajustes de política empresarial actuales, consulta la sección "[Obtener una política de uso del caché de GitHub Actions para una empresa](/rest/actions/cache#get-github-actions-cache-usage-policy-for-an-enterprise)".
+* Para cambiar los ajustes de la política empresarial, consulta la sección "[Configurar la política de uso de caché de GitHub Actions para una empresa](/rest/actions/cache#get-github-actions-cache-usage-policy-for-an-enterprise)".
 
 {% data reusables.actions.cache-no-org-policy %}
 
diff --git a/translations/es-ES/content/admin/policies/enforcing-policies-for-your-enterprise/index.md b/translations/es-ES/content/admin/policies/enforcing-policies-for-your-enterprise/index.md
index e76cef5b89..6eb840baeb 100644
--- a/translations/es-ES/content/admin/policies/enforcing-policies-for-your-enterprise/index.md
+++ b/translations/es-ES/content/admin/policies/enforcing-policies-for-your-enterprise/index.md
@@ -13,6 +13,7 @@ topics:
   - Enterprise
   - Policies
 children:
+  - /about-enterprise-policies
   - /enforcing-repository-management-policies-in-your-enterprise
   - /enforcing-team-policies-in-your-enterprise
   - /enforcing-project-board-policies-in-your-enterprise
diff --git a/translations/es-ES/content/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token.md b/translations/es-ES/content/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token.md
index 921eddc4d0..366778dfcf 100644
--- a/translations/es-ES/content/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token.md
+++ b/translations/es-ES/content/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token.md
@@ -1,6 +1,6 @@
 ---
 title: Crear un token de acceso personal
-intro: You can create a personal access token to use in place of a password with the command line or with the API.
+intro: Puedes crear un token de acceso personal para utilizar en vez de una contraseña con la línea de comandos o con la API.
 redirect_from:
   - /articles/creating-an-oauth-token-for-command-line-use
   - /articles/creating-an-access-token-for-command-line-use
@@ -24,8 +24,8 @@ shortTitle: Crear un PAT
 
 **Notas:**
 
-- If you use {% data variables.product.prodname_cli %} to authenticate to {% data variables.product.product_name %} on the command line, you can skip generating a personal access token and authenticate via the web browser instead. Para obtener más información sobre cómo autenticarte con el {% data variables.product.prodname_cli %}, consulta la sección [`gh auth login`](https://cli.github.com/manual/gh_auth_login).
--  [Git Credential Manager](https://github.com/GitCredentialManager/git-credential-manager/blob/main/README.md) is a secure, cross-platform alternative to using personal access tokens (PATs) and eliminates the need to manage PAT scope and expiration. For installation instructions, see [Download and install](https://github.com/GitCredentialManager/git-credential-manager/blob/main/README.md#download-and-install) in the GitCredentialManager/git-credential-manager repository.
+- Si utilizas el {% data variables.product.prodname_cli %} para autenticarte en {% data variables.product.product_name %} a través de la línea de comandos, puedes omitir el generar un token de acceso personal y autenticarte a través del buscador web en su lugar. Para obtener más información sobre cómo autenticarte con el {% data variables.product.prodname_cli %}, consulta la sección [`gh auth login`](https://cli.github.com/manual/gh_auth_login).
+-  El [Administrador de Credenciales de Git](https://github.com/GitCredentialManager/git-credential-manager/blob/main/README.md) es una alternativa segura y multiplataforma a utilizar los tokens de acceso personal (PAT), la cual elimina la necesidad de administrar el alcance y el vencimiento de estos. Para obtener las instrucciones de instalación, consulta la sección [Descargar e instalar](https://github.com/GitCredentialManager/git-credential-manager/blob/main/README.md#download-and-install) en el repositorio GitCredentialManager/git-credential-manager.
 
 {% endnote %}
 
@@ -80,5 +80,5 @@ En vez de ingresar tu PAT manualmente para cada operación de HTTPS de Git, pued
 
 ## Leer más
 
-- "[About authentication to GitHub](/github/authenticating-to-github/about-authentication-to-github)"{% ifversion fpt or ghae or ghes > 3.2 or ghec %}
+- "[Acerca de la autenticación en GitHub](/github/authenticating-to-github/about-authentication-to-github)"{% ifversion fpt or ghae or ghes > 3.2 or ghec %}
 - "[Vencimiento y revocación de token](/github/authenticating-to-github/keeping-your-account-and-data-secure/token-expiration-and-revocation)"{% endif %}
diff --git a/translations/es-ES/content/authentication/keeping-your-account-and-data-secure/removing-sensitive-data-from-a-repository.md b/translations/es-ES/content/authentication/keeping-your-account-and-data-secure/removing-sensitive-data-from-a-repository.md
index 758735fc15..b721422915 100644
--- a/translations/es-ES/content/authentication/keeping-your-account-and-data-secure/removing-sensitive-data-from-a-repository.md
+++ b/translations/es-ES/content/authentication/keeping-your-account-and-data-secure/removing-sensitive-data-from-a-repository.md
@@ -25,9 +25,9 @@ Puedes eliminar el archivo desde la última confirmación con `git rm`. Para obt
 
 {% warning %}
 
-**Warning**: This article tells you how to make commits with sensitive data unreachable from any branches or tags in your repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}. However, those commits may still be accessible in any clones or forks of your repository, directly via their SHA-1 hashes in cached views on {% data variables.product.product_name %}, and through any pull requests that reference them. No puedes eliminar los datos sensibles desde los clones o bifurcaciones de tu repositorio que tengan otros usuarios, pero puedes eliminar las vistas almacenadas en caché permanentemente, así como las referencias a los datos sensibles en las solicitudes de cambios en {% data variables.product.product_name %} si contactas al {% data variables.contact.contact_support %}.
+**Advertencia**: Este artículo te dice cómo hacer confirmaciones con datos sensibles que son inalcanzables desde cualquier rama o etiqueta en tu repositorio de {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}. Sin embargo, aún se podría tener acceso a estas confirmaciones en cualquier clon o bifurcación de tu repositorio, directamente a través de los hashes SHA-1 en las vistas de caché en {% data variables.product.product_name %} y a través de cualquier solicitud de cambio que las referencie. No puedes eliminar los datos sensibles desde los clones o bifurcaciones de tu repositorio que tengan otros usuarios, pero puedes eliminar las vistas almacenadas en caché permanentemente, así como las referencias a los datos sensibles en las solicitudes de cambios en {% data variables.product.product_name %} si contactas al {% data variables.contact.contact_support %}.
 
-**Once you have pushed a commit to {% data variables.product.product_name %}, you should consider any sensitive data in the commit compromised.** If you committed a password, change it! Si confirmaste una clave, genera una nueva. El eliminar los datos puestos en riesgo no resuelve su exposición inicial, especialmente en clones o bifurcaciones de tu repositorio existentes. Considera estas limitaciones en tu decisión para reescribir el historial de tu repositorio.
+**Una vez que hayas subido una confirmación a {% data variables.product.product_name %}, deberías considerar cualquier dato sensible en la confirmación que se puso en riesgo.** Si confirmaste una contraseña, ¡cámbiala! Si confirmaste una clave, genera una nueva. El eliminar los datos puestos en riesgo no resuelve su exposición inicial, especialmente en clones o bifurcaciones de tu repositorio existentes. Considera estas limitaciones en tu decisión para reescribir el historial de tu repositorio.
 
 {% endwarning %}
 
@@ -152,7 +152,7 @@ Para ilustrar cómo funciona `git filter-repo`, te mostraremos cómo eliminar tu
 
 Después de utilizar ya sea la herramienta de BFG o `git filter-repo` para eliminar los datos sensibles y subir tus cambios a {% data variables.product.product_name %}, debes tomar algunos pasos adicionales para eliminar los datos de {% data variables.product.product_name %} completamente.
 
-1. Contáctate con {% data variables.contact.contact_support %} y pregúntale cómo eliminar visualizaciones cacheadas y referencias a los datos confidenciales en las solicitudes de extracción en {% data variables.product.product_name %}. Please provide the name of the repository and/or a link to the commit you need removed.{% ifversion ghes %} For more information about how site administrators can remove unreachable Git objects, see "[Command line utilities](/admin/configuration/configuring-your-enterprise/command-line-utilities#ghe-repo-gc)."{% endif %}
+1. Contáctate con {% data variables.contact.contact_support %} y pregúntale cómo eliminar visualizaciones cacheadas y referencias a los datos confidenciales en las solicitudes de extracción en {% data variables.product.product_name %}. Por favor, proporciona el nombre de un repositorio o un enlace a la confirmación que necesitas que se elimine.{% ifversion ghes %} Para obtener más información sobre cómo los administradores de sitio pueden eliminar objetos inalcanzables de Git, consulta la sección "[Utilidades de línea de comandos](/admin/configuration/configuring-your-enterprise/command-line-utilities#ghe-repo-gc)".{% endif %}
 
 2. Pídeles a tus colaboradores que [rebasen](https://git-scm.com/book/en/Git-Branching-Rebasing), *no* fusionen, cualquier rama que hayan creado fuera del historial de tu repositorio antiguo (contaminado). Una confirmación de fusión podría volver a introducir algo o todo el historial contaminado sobre el que acabas de tomarte el trabajo de purgar.
 
diff --git a/translations/es-ES/content/authentication/keeping-your-account-and-data-secure/reviewing-your-security-log.md b/translations/es-ES/content/authentication/keeping-your-account-and-data-secure/reviewing-your-security-log.md
index 0e84bf911a..39ee249499 100644
--- a/translations/es-ES/content/authentication/keeping-your-account-and-data-secure/reviewing-your-security-log.md
+++ b/translations/es-ES/content/authentication/keeping-your-account-and-data-secure/reviewing-your-security-log.md
@@ -108,7 +108,7 @@ Un resumen de algunas de las acciones más frecuentes que se registran como even
 | Acción               | Descripción                                                                                                                                                                                                                                                                                                                                                                                |
 | -------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
 | `create (crear)`     | Se activa cuando [obtienes acceso a una {% data variables.product.prodname_oauth_app %}](/github/authenticating-to-github/keeping-your-account-and-data-secure/authorizing-oauth-apps).                                                                                                                                                                                                  |
-| `destroy (destruir)` | 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 (destruir)` | Se activa cuando [revocas un acceso a {% data variables.product.prodname_oauth_app %} a de tu cuenta](/articles/reviewing-your-authorized-integrations){% ifversion fpt or ghae or ghes > 3.2 or ghec %} y cuando [las autorizaciones se revocan o vencen](/github/authenticating-to-github/keeping-your-account-and-data-secure/token-expiration-and-revocation).{% else %}.{% endif %}
 
 {% ifversion fpt or ghec %}
 
@@ -174,37 +174,37 @@ Un resumen de algunas de las acciones más frecuentes que se registran como even
 {% ifversion fpt or ghec %}
 ### acciones de la categoría `sponsors`
 
-| Acción                                                                                                            | Descripción                                                                                                                                                                                                                                                                                                             |
-| ----------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `custom_amount_settings_change`                                                                                   | Se activa cuando habilitas o inhabilitas las cantidades personalizadas o cuando cambias la cantidad personalizada sugerida (consulta la secicón "[Administrar tus niveles de patrocinio](/github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship-tiers)")                           |
-| `repo_funding_links_file_action (acción de archivo de enlaces de financiamiento del repositorio)`                 | Se activa cuando cambias el archivo FUNDING de tu repositorio (consulta "[Mostrar un botón de patrocinador en tu repositorio](/articles/displaying-a-sponsor-button-in-your-repository)")                                                                                                                               |
-| `sponsor_sponsorship_cancel (cancelación del patrocinio del patrocinador)`                                        | Se activa cuando cancelas un patrocinio (consulta "[Bajar de categoría un patrocinio](/articles/downgrading-a-sponsorship)")                                                                                                                                                                                            |
-| `sponsor_sponsorship_create (creación de un patrocinio de patrocinador)`                                          | Se activa cuando patrocinas una cuenta (consulta la sección "[Patrocinar a un contribuyente de código abierto](/sponsors/sponsoring-open-source-contributors/sponsoring-an-open-source-contributor)")                                                                                                                   |
-| `sponsor_sponsorship_payment_complete`                                                                            | Se activa después de que patrocinas una cuenta y se procesa tu pago (consulta la sección "[Patrocinar a un contribuyente de código abierto](/sponsors/sponsoring-open-source-contributors/sponsoring-an-open-source-contributor)")                                                                                      |
-| `sponsor_sponsorship_preference_change (cambio de preferencia de patrocinio de patrocinador)`                     | Se activa cuando cambias si deseas recibir actualizaciones por correo electrónico de un programador patrocinado o no (consulta la sección "[Administrar tu patrocinio](/sponsors/sponsoring-open-source-contributors/managing-your-sponsorship)")                                                                       |
-| `sponsor_sponsorship_tier_change (cambiar nivel de patrocinio de patrocinador)`                                   | Se activa cuando subes o bajas de categoría tu patrocinio (consulta "[Subir de categoría un patrocinio](/articles/upgrading-a-sponsorship)" y "[Bajar de categoría un patrocinio](/articles/downgrading-a-sponsorship)")                                                                                                |
-| `sponsored_developer_approve (aprobación de programador patrocinado)`                                             | Triggered when your {% data variables.product.prodname_sponsors %} account is approved (see "[Setting up {% data variables.product.prodname_sponsors %} for your personal account](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-personal-account)")                     |
-| `sponsored_developer_create (creación de programador patrocinado)`                                                | Triggered when your {% data variables.product.prodname_sponsors %} account is created (see "[Setting up {% data variables.product.prodname_sponsors %} for your personal account](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-personal-account)")                      |
+| Acción                                                                                                            | Descripción                                                                                                                                                                                                                                                                                                                               |
+| ----------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `custom_amount_settings_change`                                                                                   | Se activa cuando habilitas o inhabilitas las cantidades personalizadas o cuando cambias la cantidad personalizada sugerida (consulta la secicón "[Administrar tus niveles de patrocinio](/github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship-tiers)")                                             |
+| `repo_funding_links_file_action (acción de archivo de enlaces de financiamiento del repositorio)`                 | Se activa cuando cambias el archivo FUNDING de tu repositorio (consulta "[Mostrar un botón de patrocinador en tu repositorio](/articles/displaying-a-sponsor-button-in-your-repository)")                                                                                                                                                 |
+| `sponsor_sponsorship_cancel (cancelación del patrocinio del patrocinador)`                                        | Se activa cuando cancelas un patrocinio (consulta "[Bajar de categoría un patrocinio](/articles/downgrading-a-sponsorship)")                                                                                                                                                                                                              |
+| `sponsor_sponsorship_create (creación de un patrocinio de patrocinador)`                                          | Se activa cuando patrocinas una cuenta (consulta la sección "[Patrocinar a un contribuyente de código abierto](/sponsors/sponsoring-open-source-contributors/sponsoring-an-open-source-contributor)")                                                                                                                                     |
+| `sponsor_sponsorship_payment_complete`                                                                            | Se activa después de que patrocinas una cuenta y se procesa tu pago (consulta la sección "[Patrocinar a un contribuyente de código abierto](/sponsors/sponsoring-open-source-contributors/sponsoring-an-open-source-contributor)")                                                                                                        |
+| `sponsor_sponsorship_preference_change (cambio de preferencia de patrocinio de patrocinador)`                     | Se activa cuando cambias si deseas recibir actualizaciones por correo electrónico de un programador patrocinado o no (consulta la sección "[Administrar tu patrocinio](/sponsors/sponsoring-open-source-contributors/managing-your-sponsorship)")                                                                                         |
+| `sponsor_sponsorship_tier_change (cambiar nivel de patrocinio de patrocinador)`                                   | Se activa cuando subes o bajas de categoría tu patrocinio (consulta "[Subir de categoría un patrocinio](/articles/upgrading-a-sponsorship)" y "[Bajar de categoría un patrocinio](/articles/downgrading-a-sponsorship)")                                                                                                                  |
+| `sponsored_developer_approve (aprobación de programador patrocinado)`                                             | Se activa cuando tu cuenta de {% data variables.product.prodname_sponsors %} se aprueba (consulta la sección "[Configurar {% data variables.product.prodname_sponsors %} para tu cuenta personal](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-personal-account)")                        |
+| `sponsored_developer_create (creación de programador patrocinado)`                                                | Se activa cuando tu cuenta de {% data variables.product.prodname_sponsors %} se crea (consulta la sección "[Configurar a {% data variables.product.prodname_sponsors %} para tu cuenta personal](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-personal-account)")                         |
 | `sponsored_developer_disable`                                                                                     | Se activa cuando se inhabilita tu cuenta de {% data variables.product.prodname_sponsors %}
-| `sponsored_developer_redraft`                                                                                     | Se activa cuando tu cuenta de {% data variables.product.prodname_sponsors %} se devuelve a un estado de borrador desde un estado aprobado                                                                                                                                                                               |
-| `sponsored_developer_profile_update (actualización del perfil de programador patrocinado)`                        | Se activa cuando editas tu perfil de desarrollador patrocinado (consulta la sección "[Editar tus detalles de perfil para {% data variables.product.prodname_sponsors %}](/sponsors/receiving-sponsorships-through-github-sponsors/editing-your-profile-details-for-github-sponsors)")                                   |
-| `sponsored_developer_request_approval (aprobación de solicitud de programador patrocinado)`                       | Triggered when you submit your application for {% data variables.product.prodname_sponsors %} for approval (see "[Setting up {% data variables.product.prodname_sponsors %} for your personal account](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-personal-account)") |
-| `sponsored_developer_tier_description_update (actualización de descripción del nivel de programador patrocinado)` | Se activa cuando cambias la descripción de un nivel de patrocinio (consulta la sección "[Administrar tus niveles de patrocinio](/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers)")                                                                                             |
-| `sponsored_developer_update_newsletter_send (envío de boletín de actualización del programador patrocinado)`      | Se activa cuando envías una actualización de correo electrónico a tus patrocinadores (consulta la sección "[Contactar a tus patrocinadores](/sponsors/receiving-sponsorships-through-github-sponsors/contacting-your-sponsors)")                                                                                        |
-| `waitlist_invite_sponsored_developer (invitación a la lista de espera de programadores patrocinados)`             | Triggered when you are invited to join {% data variables.product.prodname_sponsors %} from the waitlist (see "[Setting up {% data variables.product.prodname_sponsors %} for your personal account](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-personal-account)")    |
-| `waitlist_join (incorporación a la lista de espera)`                                                              | Triggered when you join the waitlist to become a sponsored developer (see "[Setting up {% data variables.product.prodname_sponsors %} for your personal account](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-personal-account)")                                       |
+| `sponsored_developer_redraft`                                                                                     | Se activa cuando tu cuenta de {% data variables.product.prodname_sponsors %} se devuelve a un estado de borrador desde un estado aprobado                                                                                                                                                                                                 |
+| `sponsored_developer_profile_update (actualización del perfil de programador patrocinado)`                        | Se activa cuando editas tu perfil de desarrollador patrocinado (consulta la sección "[Editar tus detalles de perfil para {% data variables.product.prodname_sponsors %}](/sponsors/receiving-sponsorships-through-github-sponsors/editing-your-profile-details-for-github-sponsors)")                                                     |
+| `sponsored_developer_request_approval (aprobación de solicitud de programador patrocinado)`                       | Se activa cuando emites tu solicitud de {% data variables.product.prodname_sponsors %} para su aprobación (consulta la sección "[Configurar {% data variables.product.prodname_sponsors %} para tu cuenta personal](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-personal-account)")      |
+| `sponsored_developer_tier_description_update (actualización de descripción del nivel de programador patrocinado)` | Se activa cuando cambias la descripción de un nivel de patrocinio (consulta la sección "[Administrar tus niveles de patrocinio](/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers)")                                                                                                               |
+| `sponsored_developer_update_newsletter_send (envío de boletín de actualización del programador patrocinado)`      | Se activa cuando envías una actualización de correo electrónico a tus patrocinadores (consulta la sección "[Contactar a tus patrocinadores](/sponsors/receiving-sponsorships-through-github-sponsors/contacting-your-sponsors)")                                                                                                          |
+| `waitlist_invite_sponsored_developer (invitación a la lista de espera de programadores patrocinados)`             | Se activa cuando te invitan a unirte a {% data variables.product.prodname_sponsors %} desde la lista de espera (consulta la sección "[Configurar {% data variables.product.prodname_sponsors %} para tu cuenta personal](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-personal-account)") |
+| `waitlist_join (incorporación a la lista de espera)`                                                              | Se activa cuando te unes a la lista de espera para convertirte en un desarrollador patrocinado (consulta la sección "[Configurar {% data variables.product.prodname_sponsors %} para tu cuenta personal](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-personal-account)")                 |
 {% endif %}
 
 {% ifversion fpt or ghec %}
 ### acciones de la categoría `successor_invitation`
 
-| Acción           | Descripción                                                                                                                                                                                                                                                         |
-| ---------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `accept`         | Triggered when you accept a succession invitation (see "[Maintaining ownership continuity of your personal account's repositories](/github/setting-up-and-managing-your-github-user-account/maintaining-ownership-continuity-of-your-user-accounts-repositories)")  |
-| `cancel`         | Triggered when you cancel a succession invitation (see "[Maintaining ownership continuity of your personal account's repositories](/github/setting-up-and-managing-your-github-user-account/maintaining-ownership-continuity-of-your-user-accounts-repositories)")  |
-| `create (crear)` | Triggered when you create a succession invitation (see "[Maintaining ownership continuity of your personal account's repositories](/github/setting-up-and-managing-your-github-user-account/maintaining-ownership-continuity-of-your-user-accounts-repositories)")  |
-| `decline`        | Triggered when you decline a succession invitation (see "[Maintaining ownership continuity of your personal account's repositories](/github/setting-up-and-managing-your-github-user-account/maintaining-ownership-continuity-of-your-user-accounts-repositories)") |
-| `revoke`         | Triggered when you revoke a succession invitation (see "[Maintaining ownership continuity of your personal account's repositories](/github/setting-up-and-managing-your-github-user-account/maintaining-ownership-continuity-of-your-user-accounts-repositories)")  |
+| Acción           | Descripción                                                                                                                                                                                                                                                                                   |
+| ---------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `accept`         | Se activa cuando aceptas una invitación de sucesión (consulta la secicón "[Mantener continuidad en la titularidad de los repositorios de tu cuenta personal](/github/setting-up-and-managing-your-github-user-account/maintaining-ownership-continuity-of-your-user-accounts-repositories)")  |
+| `cancel`         | Se activa cuando cancelas una invitación de sucesión (consulta la secicón "[Mantener continuidad en la titularidad de los repositorios de tu cuenta personal](/github/setting-up-and-managing-your-github-user-account/maintaining-ownership-continuity-of-your-user-accounts-repositories)") |
+| `create (crear)` | Se activa cuando creas una invitación de sucesión (consulta la secicón "[Mantener continuidad en la titularidad de los repositorios de tu cuenta personal](/github/setting-up-and-managing-your-github-user-account/maintaining-ownership-continuity-of-your-user-accounts-repositories)")    |
+| `decline`        | Se activa cuando rechazas una invitación de sucesión (consulta la secicón "[Mantener continuidad en la titularidad de los repositorios de tu cuenta personal](/github/setting-up-and-managing-your-github-user-account/maintaining-ownership-continuity-of-your-user-accounts-repositories)") |
+| `revoke`         | Se activa cuando revocas una invitación de sucesión (consulta la secicón "[Mantener continuidad en la titularidad de los repositorios de tu cuenta personal](/github/setting-up-and-managing-your-github-user-account/maintaining-ownership-continuity-of-your-user-accounts-repositories)")  |
 {% endif %}
 
 {% ifversion ghes or ghae %}
@@ -233,16 +233,16 @@ Un resumen de algunas de las acciones más frecuentes que se registran como even
 
 ### acciones de la categoría `user`
 
-| Acción                                                                                                                                                                                                                       | Descripción                                                                                                                                                                                                                  |
-| ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `add_email (agregar correo electrónico)`                                                                                                                                                                                     | Se activa cuando                                                                                                                                                                                                             |
-| {% ifversion not ghae %}[agregas una dirección de correo electrónico nueva](/articles/changing-your-primary-email-address){% else %}agregas una dirección de correo electrónico nueva{% endif %}.{% ifversion fpt or ghec %} |                                                                                                                                                                                                                              |
-| `codespaces_trusted_repo_access_granted`                                                                                                                                                                                     | Triggered when you [allow the codespaces you create for a repository to access other repositories owned by your personal account](/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces).    |
-| `codespaces_trusted_repo_access_revoked`                                                                                                                                                                                     | Triggered when you [disallow the codespaces you create for a repository to access other repositories owned by your personal account](/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces). |{% endif %}
-| `create (crear)`                                                                                                                                                                                                             | Triggered when you create a new personal account.{% ifversion not ghae %}
-| `change_password (cambiar contraseña)`                                                                                                                                                                                       | Se activa cuando cambias tu contraseña.                                                                                                                                                                                      |
+| Acción                                                                                                                                                                                                                       | Descripción                                                                                                                                                                                                                                           |
+| ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `add_email (agregar correo electrónico)`                                                                                                                                                                                     | Se activa cuando                                                                                                                                                                                                                                      |
+| {% ifversion not ghae %}[agregas una dirección de correo electrónico nueva](/articles/changing-your-primary-email-address){% else %}agregas una dirección de correo electrónico nueva{% endif %}.{% ifversion fpt or ghec %} |                                                                                                                                                                                                                                                       |
+| `codespaces_trusted_repo_access_granted`                                                                                                                                                                                     | Se activa cuando [permites que los codespaces que creas para que un repositorio accedan a otros repositorios que le pertenecen a tu cuenta personal](/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces).          |
+| `codespaces_trusted_repo_access_revoked`                                                                                                                                                                                     | Se activa cuando [dejas de permitir que los codespaces que creas para que un repositorio accedan a otros repositorios que le pertenecen a tu cuenta personal](/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces). |{% endif %}
+| `create (crear)`                                                                                                                                                                                                             | Se activa cuando creas una cuenta personal nueva.{% ifversion not ghae %}
+| `change_password (cambiar contraseña)`                                                                                                                                                                                       | Se activa cuando cambias tu contraseña.                                                                                                                                                                                                               |
 | `forgot_password (olvidé la contraseña)`                                                                                                                                                                                     | Se activa cuando pides [un restablecimiento de contraseña](/articles/how-can-i-reset-my-password).{% endif %}
-| `hide_private_contributions_count (ocultar conteo de contribuciones privadas)`                                                                                                                                               | Se activa cuando [ocultas contribuciones privadas en tu perfil](/articles/publicizing-or-hiding-your-private-contributions-on-your-profile).                                                                                 |
+| `hide_private_contributions_count (ocultar conteo de contribuciones privadas)`                                                                                                                                               | Se activa cuando [ocultas contribuciones privadas en tu perfil](/articles/publicizing-or-hiding-your-private-contributions-on-your-profile).                                                                                                          |
 | `login`                                                                                                                                                                                                                      | Se activa cuando inicias sesión en {% data variables.product.product_location %}.{% ifversion ghes or ghae %}
 
 
diff --git a/translations/es-ES/content/authentication/keeping-your-account-and-data-secure/token-expiration-and-revocation.md b/translations/es-ES/content/authentication/keeping-your-account-and-data-secure/token-expiration-and-revocation.md
index 85f11a5597..bb5cb6daa8 100644
--- a/translations/es-ES/content/authentication/keeping-your-account-and-data-secure/token-expiration-and-revocation.md
+++ b/translations/es-ES/content/authentication/keeping-your-account-and-data-secure/token-expiration-and-revocation.md
@@ -54,7 +54,7 @@ Una vez que se revoca una autorización, cualquier token asociado con la autoriz
 
 El propietario de una {% data variables.product.prodname_oauth_app %} puede revocar una autorización de su app en una cuenta, esto también revocará cualquier token asociado con esa autorización. Para obtener más información sobre cómo revocar las autorizaciones de tu app de OAuth, consulta la sección "[Borrar una autorización de una app](/rest/reference/apps#delete-an-app-authorization)".
 
-{% data variables.product.prodname_oauth_app %} owners can also revoke individual tokens associated with an authorization. For more information about revoking individual tokens for your OAuth app, see "[Delete an app token](/rest/apps/oauth-applications#delete-an-app-token)".
+Los propietarios de {% data variables.product.prodname_oauth_app %} también pueden revocar los tokens individuales asociados con una autorización. Para obtener más información sobre cómo revocar tokens individuales para tu app de OAuth, consulta la sección "[Borrar el token de una app](/rest/apps/oauth-applications#delete-an-app-token)".
 
 ## El token se revocó debido a un exceso de tokens para una {% data variables.product.prodname_oauth_app %} con el mismo alcance
 
diff --git a/translations/es-ES/content/authentication/keeping-your-account-and-data-secure/updating-your-github-access-credentials.md b/translations/es-ES/content/authentication/keeping-your-account-and-data-secure/updating-your-github-access-credentials.md
index 3b3d8f5201..5d5f4d1bc0 100644
--- a/translations/es-ES/content/authentication/keeping-your-account-and-data-secure/updating-your-github-access-credentials.md
+++ b/translations/es-ES/content/authentication/keeping-your-account-and-data-secure/updating-your-github-access-credentials.md
@@ -57,7 +57,7 @@ Consulta "[Revisar tus integraciones autorizadas](/articles/reviewing-your-autho
 
 {% ifversion not ghae %}
 
-If you have reset your account password and would also like to trigger a sign-out from the {% data variables.product.prodname_mobile %} app, you can revoke your authorization of the "GitHub iOS" or "GitHub Android" OAuth App. This will sign out all instances of the {% data variables.product.prodname_mobile %} app associated with your account. Para obtener información adicional, consulta la sección "[Revisar tus integraciones autorizadas](/authentication/keeping-your-account-and-data-secure/reviewing-your-authorized-integrations)".
+Si restableciste tu contraseña de cuenta y te gustaría activar un cierre de sesión desde la aplicación de {% data variables.product.prodname_mobile %}, puedes revocar tu autorización de la App de OAuth de "GitHub iOS" o "GitHub Android". Esto saldrá de sesión en todas las instancias de la app de {% data variables.product.prodname_mobile %} asociada con tu cuenta. Para obtener información adicional, consulta la sección "[Revisar tus integraciones autorizadas](/authentication/keeping-your-account-and-data-secure/reviewing-your-authorized-integrations)".
 
 {% endif %}
 
diff --git a/translations/es-ES/content/authentication/managing-commit-signature-verification/adding-a-new-gpg-key-to-your-github-account.md b/translations/es-ES/content/authentication/managing-commit-signature-verification/adding-a-new-gpg-key-to-your-github-account.md
index fad90eb30c..ac545de72f 100644
--- a/translations/es-ES/content/authentication/managing-commit-signature-verification/adding-a-new-gpg-key-to-your-github-account.md
+++ b/translations/es-ES/content/authentication/managing-commit-signature-verification/adding-a-new-gpg-key-to-your-github-account.md
@@ -20,7 +20,7 @@ Antes de agregar una llave GPG nueva a tu cuenta de {% ifversion ghae %}{% data
 - [Comprobado tus llaves GPG existentes](/articles/checking-for-existing-gpg-keys)
 - [Generado y copiado una nueva llave GPG](/articles/generating-a-new-gpg-key)
 
-You can add multiple public keys to your GitHub account. Commits signed by any of the corresponding private keys will show as verified. If you remove a public key, any commits signed by the corresponding private key will no longer show as verified.
+Puedes agregar varias llaves públicas a tu cuenta de GitHub. Las confirmaciones que haya firmado cualquiera de las llaves privadas correspondientes se mostrarán como verificadas. Si eliminas una llave pública, cualquier confirmación que firme la llave privada correspondiente ya no se mostrará como verificada.
 
 {% data reusables.gpg.supported-gpg-key-algorithms %}
 
diff --git a/translations/es-ES/content/authentication/securing-your-account-with-two-factor-authentication-2fa/about-two-factor-authentication.md b/translations/es-ES/content/authentication/securing-your-account-with-two-factor-authentication-2fa/about-two-factor-authentication.md
index 1decd38499..11aa6ea3d3 100644
--- a/translations/es-ES/content/authentication/securing-your-account-with-two-factor-authentication-2fa/about-two-factor-authentication.md
+++ b/translations/es-ES/content/authentication/securing-your-account-with-two-factor-authentication-2fa/about-two-factor-authentication.md
@@ -19,7 +19,7 @@ Para {% data variables.product.product_name %}, la segunda forma de autenticaci
 {% data reusables.two_fa.after-2fa-add-security-key %}
 
 {% ifversion fpt or ghec %}
-Adicionalmente a las llaves de seguridad, también puedes utilizar {% data variables.product.prodname_mobile %} para la 2FA después de configurar una app móvil TOTP o mensajes de texto. {% data variables.product.prodname_mobile %} uses public-key cryptography to secure your account, allowing you to use any mobile device that you've used to sign in to {% data variables.product.prodname_mobile %} as your second factor.
+Adicionalmente a las llaves de seguridad, también puedes utilizar {% data variables.product.prodname_mobile %} para la 2FA después de configurar una app móvil TOTP o mensajes de texto. {% data variables.product.prodname_mobile %} utiliza criptografía de llave pública para asegurar tu cuenta, lo que te permite utilizar cualquier dispositivo móvil que hayas utilizado para iniciar sesión en {% data variables.product.prodname_mobile %} como tu segundo factor.
 {% endif %}
 
 También puedes configurar métodos de recuperación adicionales en caso de que pierdas el acceso a tus credenciales de autenticación de dos factores. Para obtener más información acerca de la configuración de la 2FA, consulta "[Configurar autenticación de dos factores](/articles/configuring-two-factor-authentication)" y "[Configurar métodos de recuperación de autenticación de dos factores](/articles/configuring-two-factor-authentication-recovery-methods)".
diff --git a/translations/es-ES/content/authentication/securing-your-account-with-two-factor-authentication-2fa/accessing-github-using-two-factor-authentication.md b/translations/es-ES/content/authentication/securing-your-account-with-two-factor-authentication-2fa/accessing-github-using-two-factor-authentication.md
index 66f70a76be..9c6bf44980 100644
--- a/translations/es-ES/content/authentication/securing-your-account-with-two-factor-authentication-2fa/accessing-github-using-two-factor-authentication.md
+++ b/translations/es-ES/content/authentication/securing-your-account-with-two-factor-authentication-2fa/accessing-github-using-two-factor-authentication.md
@@ -59,13 +59,13 @@ Si instalaste e iniciaste sesión en {% data variables.product.prodname_mobile %
 
 ## Usar autenticación de dos factores con la línea de comando
 
-After you've enabled 2FA, you will no longer use your password to access {% data variables.product.product_name %} on the command line. Instead, use Git Credential Manager, a personal access token, or an SSH key.
+Después de que habilitas la 2FA, ya no utilizarás tu contraseña para acceder a {% data variables.product.product_name %} en la línea de comandos. En vez de esto, utiliza el Administrador de Credenciales de Git, un token de acceso personal o una llave SSH.
 
-### Authenticating on the command line using Git Credential Manager
+### Autenticarse en la línea de comandos utilizando el Administrador de Credenciales de Git
 
-[Git Credential Manager](https://github.com/GitCredentialManager/git-credential-manager/blob/main/README.md) is a secure Git credential helper that runs on Windows, macOS, and Linux. For more information about Git credential helpers, see [Avoiding repetition](https://git-scm.com/docs/gitcredentials#_avoiding_repetition) in the Pro Git book.
+El [Administrador de Credenciales de Git](https://github.com/GitCredentialManager/git-credential-manager/blob/main/README.md) es un asistente seguro de credenciales de Git que se ejecuta en Windows, macOS y Linux. Para obtener más información sobre los asistentes de credenciales de Git, consulta la sección [Evitar la repetición](https://git-scm.com/docs/gitcredentials#_avoiding_repetition) en el libro de Pro Git.
 
-Setup instructions vary based on your computer's operating system. For more information, see [Download and install](https://github.com/GitCredentialManager/git-credential-manager/blob/main/README.md#download-and-install) in the GitCredentialManager/git-credential-manager repository.
+Las instrucciones de configuración pueden variar dependiendo del sistema operativo de tu computadora. Para obtener más información, consulta la sección [Descargar e instalar](https://github.com/GitCredentialManager/git-credential-manager/blob/main/README.md#download-and-install) en el repositorio GitCredentialManager/git-credential-manager.
 
 ### Autenticación en la línea de comando mediante HTTPS
 
diff --git a/translations/es-ES/content/authentication/securing-your-account-with-two-factor-authentication-2fa/changing-two-factor-authentication-delivery-methods-for-your-mobile-device.md b/translations/es-ES/content/authentication/securing-your-account-with-two-factor-authentication-2fa/changing-two-factor-authentication-delivery-methods-for-your-mobile-device.md
index 035d099981..dadb8b1391 100644
--- a/translations/es-ES/content/authentication/securing-your-account-with-two-factor-authentication-2fa/changing-two-factor-authentication-delivery-methods-for-your-mobile-device.md
+++ b/translations/es-ES/content/authentication/securing-your-account-with-two-factor-authentication-2fa/changing-two-factor-authentication-delivery-methods-for-your-mobile-device.md
@@ -22,7 +22,7 @@ shortTitle: Cambiar el método de entrega de 2FA
 
 {% data reusables.user-settings.access_settings %}
 {% data reusables.user-settings.security %}
-3. Next to "Primary two-factor method", click **Change**. ![Edit primary delivery options](/assets/images/help/2fa/edit-primary-delivery-option.png)
+3. Junto al "Método bifactorial principal", haz clic en **Cambiar**. ![Editar las opciones de entrega principal](/assets/images/help/2fa/edit-primary-delivery-option.png)
 4. En "Delivery options" (Opciones de entrega), haz clic en **Reconfigure two-factor authentication** (Reconfirgurar autenticación de dos factores). ![Cambiar tus opciones de entrega 2FA](/assets/images/help/2fa/2fa-switching-methods.png)
 5. Decide si deseas configurar la autenticación de dos factores mediante una app móvil TOTP o un mensaje de texto. Para obtener más información, consulta "[Configurar autenticación de dos factores](/articles/configuring-two-factor-authentication)".
     - Para configurar la autenticación de dos factores mediante una app móvil TOTP, haz clic en **Set up using an app** (Configurar mediante una app).
diff --git a/translations/es-ES/content/billing/managing-billing-for-github-actions/about-billing-for-github-actions.md b/translations/es-ES/content/billing/managing-billing-for-github-actions/about-billing-for-github-actions.md
index 99430e1ffb..4f0b2f52b6 100644
--- a/translations/es-ES/content/billing/managing-billing-for-github-actions/about-billing-for-github-actions.md
+++ b/translations/es-ES/content/billing/managing-billing-for-github-actions/about-billing-for-github-actions.md
@@ -48,7 +48,7 @@ Los jobs que se ejecutan en Windows y macOS y que se hospedan en {% data variabl
 
 El almacenamiento que utilza un repositorio es el total del almacenamiento utilizado por los artefactos de {% data variables.product.prodname_actions %} y por {% data variables.product.prodname_registry %}. Tu costo de almacenamiento es el uso total para todos los repositorios que pertenezcan a tu cuenta. Para obtener más información sobre los costos de {% data variables.product.prodname_registry %}, consulta la sección "[Acerca de la facturación para {% data variables.product.prodname_registry %}](/billing/managing-billing-for-github-packages/about-billing-for-github-packages)".
 
- If your account's usage surpasses these limits and you have set a spending limit above $0 USD, you will pay $0.008 USD per GB of storage per day and per-minute usage depending on the operating system used by the {% data variables.product.prodname_dotcom %}-hosted runner. {% data variables.product.prodname_dotcom %} redondea hacia arriba los minutos que utiliza cada job.
+ Si el uso de tu cuenta sobrepasa estos límites y configuraste un límite de gastos mayor a $0 USD, pagarás $0.008 USD por GB de almacenamiento por uso de día y minuto dependiendo del sistema operativo que utiliza el ejecutor hospedado en {% data variables.product.prodname_dotcom %}. {% data variables.product.prodname_dotcom %} redondea hacia arriba los minutos que utiliza cada job.
 
 {% note %}
 
diff --git a/translations/es-ES/content/billing/managing-billing-for-github-packages/about-billing-for-github-packages.md b/translations/es-ES/content/billing/managing-billing-for-github-packages/about-billing-for-github-packages.md
index d24e5e5ff1..e6f10f5eec 100644
--- a/translations/es-ES/content/billing/managing-billing-for-github-packages/about-billing-for-github-packages.md
+++ b/translations/es-ES/content/billing/managing-billing-for-github-packages/about-billing-for-github-packages.md
@@ -50,9 +50,9 @@ Todos los datos de transferencia saliente, cuando se desencadenan mediante {% da
 
 El uso de almacenamiento se comparte con los artefactos de compilación que produce {% data variables.product.prodname_actions %} para los repositorios que pertenecen a tu cuenta. Para obtener más información, consulta "[Acerca de la facturación para {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions/about-billing-for-github-actions)".
 
-{% data variables.product.prodname_dotcom %} cobra el uso a la cuenta a la que pertenece el repositorio en donde se publica el paquete. If your account's usage surpasses these limits and you have set a spending limit above $0 USD, you will pay $0.008 USD per GB of storage per day and $0.50 USD per GB of data transfer.
+{% data variables.product.prodname_dotcom %} cobra el uso a la cuenta a la que pertenece el repositorio en donde se publica el paquete. Si tu uso de cuenta sobrepasa estos límites y configuraste un límite de gastos mayor a $0 USD, pagarás $0.008 USD por GB de almacenamiento por día y $0.50 USD por GB de transferencia de datos.
 
-Por ejemplo, si tu organización utiliza {% data variables.product.prodname_team %}, permite los gastos ilimitados, utiliza 150GB de almacenamiento, y tiene 50GB de transferencia de datos durante un mes, ésta tendrá un excedente de 148GB en el almacenamiento y de 40GB en transferencia de datos para ese mes. The storage overage would cost $0.008 USD per GB per day or $37 USD. El excedente para transferencia de datos costaría $0.50 USD por GB, o $20 USD.
+Por ejemplo, si tu organización utiliza {% data variables.product.prodname_team %}, permite los gastos ilimitados, utiliza 150GB de almacenamiento, y tiene 50GB de transferencia de datos durante un mes, ésta tendrá un excedente de 148GB en el almacenamiento y de 40GB en transferencia de datos para ese mes. El excedente de almacenamiento costaría $0.008 USD por GB por día o $37 USD. El excedente para transferencia de datos costaría $0.50 USD por GB, o $20 USD.
 
 {% data reusables.dotcom_billing.pricing_calculator.pricing_cal_packages %}
 
diff --git a/translations/es-ES/content/billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise.md b/translations/es-ES/content/billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise.md
index 2b21047126..cebb65edfb 100644
--- a/translations/es-ES/content/billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise.md
+++ b/translations/es-ES/content/billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise.md
@@ -53,7 +53,7 @@ Cada usuario en {% data variables.product.product_location %} consume una plaza
 
 {% endif %}
 
-{% data reusables.billing.about-invoices-for-enterprises %} Para obtener más información sobre {% ifversion ghes %}las licencias, el uso y las facturas{% elsif ghec %}el uso y las facturas{% endif %}, consulta lo siguiente{% ifversion ghes %} en la documentación de {% data variables.product.prodname_ghe_cloud %}.{% else %}.{% endif %}
+{% ifversion ghec %}Para los clientes de {% data variables.product.prodname_ghe_cloud %} con una cuenta empresarial, {% data variables.product.company_short %} se factura mediante su cuenta empresarial en {% data variables.product.prodname_dotcom_the_website %}. Para los clientes que pagan por factura individual, cada {% elsif ghes %}Para los clientes de {% data variables.product.prodname_enterprise %} que pagan por factura individual, {% data variables.product.company_short %} emite las facturas mediante una cuenta empresarial en {% data variables.product.prodname_dotcom_the_website %}. Cada{% endif %} factura incluye un cargo único para todos tus servicios de paga de {% data variables.product.prodname_dotcom_the_website %} y para cualquier instancia de {% data variables.product.prodname_ghe_server %}. Para obtener más información sobre {% ifversion ghes %}las licencias, el uso y las facturas{% elsif ghec %}el uso y las facturas{% endif %}, consulta lo siguiente{% ifversion ghes %} en la documentación de {% data variables.product.prodname_ghe_cloud %}.{% else %}.{% endif %}
 
 {%- ifversion ghes %}
 - "[Acerca del precio por usuario](/enterprise-cloud@latest/billing/managing-billing-for-your-github-account/about-per-user-pricing)"
diff --git a/translations/es-ES/content/billing/managing-billing-for-your-github-account/connecting-an-azure-subscription-to-your-enterprise.md b/translations/es-ES/content/billing/managing-billing-for-your-github-account/connecting-an-azure-subscription-to-your-enterprise.md
index 8522ed106a..d1a644c53d 100644
--- a/translations/es-ES/content/billing/managing-billing-for-your-github-account/connecting-an-azure-subscription-to-your-enterprise.md
+++ b/translations/es-ES/content/billing/managing-billing-for-your-github-account/connecting-an-azure-subscription-to-your-enterprise.md
@@ -1,6 +1,6 @@
 ---
 title: Conectar una suscripción de Azure a tu empresa
-intro: 'You can use your Microsoft Enterprise Agreement to enable and pay for {% data variables.product.prodname_actions %}, {% data variables.product.prodname_registry %}, and {% data variables.product.prodname_codespaces %} usage.'
+intro: 'Puedes utilizar tu Acuerdo de Microsoft Enterprise para habilitar y pagar por el uso de {% data variables.product.prodname_actions %}, del {% data variables.product.prodname_registry %} y de los {% data variables.product.prodname_codespaces %}.'
 redirect_from:
   - /github/setting-up-and-managing-your-enterprise/managing-your-enterprise-account/connecting-an-azure-subscription-to-your-enterprise
   - /github/setting-up-and-managing-billing-and-payments-on-github/connecting-an-azure-subscription-to-your-enterprise
@@ -16,15 +16,15 @@ shortTitle: Conectar una suscripción de Azure
 
 {% note %}
 
-**Note:** If your enterprise account is on a Microsoft Enterprise Agreement, connecting an Azure subscription is the only way to use {% data variables.product.prodname_actions %} and {% data variables.product.prodname_registry %} beyond the included amounts, or to use {% data variables.product.prodname_codespaces %} at all.
+**Nota:** Si tu cuenta empresarial está en un Acuerdo de Microsoft Enterprise, conectar una suscripción de Azure es la única forma de utilizar {% data variables.product.prodname_actions %} y el {% data variables.product.prodname_registry %} más allá de las cantidades incluidas o para utilizar los {% data variables.product.prodname_codespaces %} en general.
 
 {% endnote %}
 
-After you connect an Azure subscription, you can also manage your spending limits.
+Después de que conectes una suscripción de Azure, también podrás administrar tus límites de gastos.
 
-- "[Managing your spending limit for {% data variables.product.prodname_registry %}](/billing/managing-billing-for-github-packages/managing-your-spending-limit-for-github-packages)"
-- "[Managing your spending limit for {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions/managing-your-spending-limit-for-github-actions)"
-- "[Managing your spending limit for {% data variables.product.prodname_codespaces %}](/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-codespaces)"
+- "[Administrar tu límite de gastos para el {% data variables.product.prodname_registry %}](/billing/managing-billing-for-github-packages/managing-your-spending-limit-for-github-packages)"
+- "[Administrar tu límite de gastos para las {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions/managing-your-spending-limit-for-github-actions)"
+- "[Administrar tu límite de gastos para {% data variables.product.prodname_codespaces %}](/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-codespaces)"
 
 ## Conectar tu suscripción de Azure con tu cuenta empresarial
 
diff --git a/translations/es-ES/content/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account.md b/translations/es-ES/content/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account.md
index 715f162495..1225677a1f 100644
--- a/translations/es-ES/content/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account.md
+++ b/translations/es-ES/content/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account.md
@@ -17,7 +17,7 @@ shortTitle: Ver la suscripción & uso
 
 ## Acerca de la facturación para las cuentas de empresa
 
-Puedes ver un resumen de {% ifversion ghec %}tu suscripción y uso de tu {% elsif ghes %}licencia pagada{% endif %} para {% ifversion ghec %}tu{% elsif ghes %}la{% endif %} cuenta empresarial en {% ifversion ghec %}{% data variables.product.prodname_dotcom_the_website %}{% elsif ghes %}{% data variables.product.product_location %}{% endif %}.
+Puedes ver un resumen de {% ifversion ghec %}tu suscripción y del uso de pago{% elsif ghes %}el uso de la licencia{% endif %} para {% ifversion ghec %}tu{% elsif ghes %}la{% endif %} cuenta empresarial de {% ifversion ghec %}{% data variables.product.prodname_dotcom_the_website %}{% elsif ghes %}{% data variables.product.product_location %}{% endif %}.{% ifversion ghec %} {% data reusables.enterprise.create-an-enterprise-account %} Para obtener más información, consulta la sección "[Crear una cuenta empresarial](/enterprise-cloud@latest/admin/overview/creating-an-enterprise-account)".{% endif %}
 
 Para los clientes de {% data variables.product.prodname_enterprise %} a quienes se factura{% ifversion ghes %} quienes usan tanto {% data variables.product.prodname_ghe_cloud %} como {% data variables.product.prodname_ghe_server %}{% endif %}, cada factura incluye detalles sobre los servicios que se cobran de todos los productos. Por ejemplo, adicionalmente a tu uso de {% ifversion ghec %}{% data variables.product.prodname_ghe_cloud %}{% elsif ghes %}{% data variables.product.product_name %}{% endif %}, puedes tener un uso de {% data variables.product.prodname_GH_advanced_security %}{% ifversion ghec %},{% elsif ghes %}. También puedes tener uso en {% data variables.product.prodname_dotcom_the_website %}, como {% endif %}licencias de pago en organizaciones fuera de tu cuenta empresarial, paquetes de datos para {% data variables.large_files.product_name_long %} o suscripciones en apps dentro de {% data variables.product.prodname_marketplace %}. Para obtener más información sobre las facturas, consulta la sección "[Administrar las facturas de tu empresa]({% ifversion ghes %}/enterprise-cloud@latest{% endif %}/billing/managing-billing-for-your-github-account/managing-invoices-for-your-enterprise){% ifversion ghec %}".{% elsif ghes %}" en la documentación de {% data variables.product.prodname_dotcom_the_website %}.{% endif %}
 
diff --git a/translations/es-ES/content/billing/managing-licenses-for-visual-studio-subscriptions-with-github-enterprise/setting-up-visual-studio-subscriptions-with-github-enterprise.md b/translations/es-ES/content/billing/managing-licenses-for-visual-studio-subscriptions-with-github-enterprise/setting-up-visual-studio-subscriptions-with-github-enterprise.md
index 3004a0980f..7cb5a6b82c 100644
--- a/translations/es-ES/content/billing/managing-licenses-for-visual-studio-subscriptions-with-github-enterprise/setting-up-visual-studio-subscriptions-with-github-enterprise.md
+++ b/translations/es-ES/content/billing/managing-licenses-for-visual-studio-subscriptions-with-github-enterprise/setting-up-visual-studio-subscriptions-with-github-enterprise.md
@@ -22,13 +22,13 @@ Si prefieres ver un video, puedes ver [Configurar tus licencias de {% data varia
 
 Antes de configurar {% data variables.product.prodname_vss_ghe %}, es importante entender los roles para esta oferta combinada.
 
-| Rol                                | Servicio                                                | Descripción                                                                                                                                     | Más información                                                                                                                                                              |
-|:---------------------------------- |:------------------------------------------------------- |:----------------------------------------------------------------------------------------------------------------------------------------------- |:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| **Administrador de suscripciones** | Suscripción de {% data variables.product.prodname_vs %} | Persona que asigna licencias para la suscripción de {% data variables.product.prodname_vs %}                                                    | [Vista general de las responsabilidades de administrador](https://docs.microsoft.com/en-us/visualstudio/subscriptions/admin-responsibilities) en los Documentos de Microsoft |
-| **Suscriptor**                     | Suscripción de {% data variables.product.prodname_vs %} | Persona que utiliza una licencia para la suscripción a {% data variables.product.prodname_vs %}                                                 | [Documentación de suscripciones a Visual Studio](https://docs.microsoft.com/en-us/visualstudio/subscriptions/) en los Documentos de Microsoft                                |
-| **Propietario de empresa**         | {% data variables.product.prodname_dotcom %}            | Person who has a personal account that's an administrator of an enterprise on {% data variables.product.product_location %}                     | "[Roles en una empresa](/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise#enterprise-owner)"                                                   |
-| **Propietario de organización**    | {% data variables.product.prodname_dotcom %}            | Person who has a personal account that's an owner of an organization in your team's enterprise on {% data variables.product.product_location %} | "[Roles en una organización](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization#organization-owners)"                           |
-| **Miembro de empresa**             | {% data variables.product.prodname_dotcom %}            | Person who has a personal account that's a member of an enterprise on {% data variables.product.product_location %}                             | "[Roles en una empresa](/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise#enterprise-members)"                                                 |
+| Rol                                | Servicio                                                | Descripción                                                                                                                                              | Más información                                                                                                                                                              |
+|:---------------------------------- |:------------------------------------------------------- |:-------------------------------------------------------------------------------------------------------------------------------------------------------- |:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| **Administrador de suscripciones** | Suscripción de {% data variables.product.prodname_vs %} | Persona que asigna licencias para la suscripción de {% data variables.product.prodname_vs %}                                                             | [Vista general de las responsabilidades de administrador](https://docs.microsoft.com/en-us/visualstudio/subscriptions/admin-responsibilities) en los Documentos de Microsoft |
+| **Suscriptor**                     | Suscripción de {% data variables.product.prodname_vs %} | Persona que utiliza una licencia para la suscripción a {% data variables.product.prodname_vs %}                                                          | [Documentación de suscripciones a Visual Studio](https://docs.microsoft.com/en-us/visualstudio/subscriptions/) en los Documentos de Microsoft                                |
+| **Propietario de empresa**         | {% data variables.product.prodname_dotcom %}            | Persona que tiene una cuenta personal que sea administradora de una empresa en {% data variables.product.product_location %}                             | "[Roles en una empresa](/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise#enterprise-owner)"                                                   |
+| **Propietario de organización**    | {% data variables.product.prodname_dotcom %}            | Persona que tiene una cuenta personal que es propietaria de una organización en la empresa de tu equipo en {% data variables.product.product_location %} | "[Roles en una organización](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization#organization-owners)"                           |
+| **Miembro de empresa**             | {% data variables.product.prodname_dotcom %}            | Persona que tiene una cuenta personal que es miembro de una empresa en {% data variables.product.product_location %}                                     | "[Roles en una empresa](/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise#enterprise-members)"                                                 |
 
 ## Prerrequisitos
 
diff --git a/translations/es-ES/content/billing/managing-your-license-for-github-enterprise/syncing-license-usage-between-github-enterprise-server-and-github-enterprise-cloud.md b/translations/es-ES/content/billing/managing-your-license-for-github-enterprise/syncing-license-usage-between-github-enterprise-server-and-github-enterprise-cloud.md
index a7669742ee..ab245d03f5 100644
--- a/translations/es-ES/content/billing/managing-your-license-for-github-enterprise/syncing-license-usage-between-github-enterprise-server-and-github-enterprise-cloud.md
+++ b/translations/es-ES/content/billing/managing-your-license-for-github-enterprise/syncing-license-usage-between-github-enterprise-server-and-github-enterprise-cloud.md
@@ -26,22 +26,22 @@ Si no quieres habilitar {% data variables.product.prodname_github_connect %}, pu
 
 ## Sincronizar el uso de licencias automáticamente
 
-You can use {% data variables.product.prodname_github_connect %} to automatically synchronize user license count and usage between {% data variables.product.prodname_ghe_server %} and {% data variables.product.prodname_ghe_cloud %} weekly. Para obtener más información, consulta la sección "[Habilitar la sincronización automática de licencias de usuario para tu empresa]({% ifversion ghec %}/enterprise-server@latest{% endif %}/admin/configuration/configuring-github-connect/enabling-automatic-user-license-sync-for-your-enterprise){% ifversion ghec %}" en la documentación de {% data variables.product.prodname_ghe_server %}{% elsif ghes %}".{% endif %}
+Puedes utilizar {% data variables.product.prodname_github_connect %} para sincronizar automáticamente el conteo de licencias de usuario y el uso entre {% data variables.product.prodname_ghe_server %} y {% data variables.product.prodname_ghe_cloud %} semanalmente. Para obtener más información, consulta la sección "[Habilitar la sincronización automática de licencias de usuario para tu empresa]({% ifversion ghec %}/enterprise-server@latest{% endif %}/admin/configuration/configuring-github-connect/enabling-automatic-user-license-sync-for-your-enterprise){% ifversion ghec %}" en la documentación de {% data variables.product.prodname_ghe_server %}{% elsif ghes %}".{% endif %}
 
 {% ifversion ghec or ghes > 3.4 %}
-After you enable {% data variables.product.prodname_github_connect %}, license data will be automatically synchronized weekly. You can also manually synchronize your license data at any time, by triggering a license sync job.
+Después de que habilites {% data variables.product.prodname_github_connect %}, los datos de licencia se sincronizarán automáticamente cada semana. También puedes sincronizar tus datos de licencia manualmente en cualquier momento si activas un job de sincronización de licencia.
 
-### Triggering a license sync job
+### Activar un job de sincronización de licencia
 
-1. Sign in to your {% data variables.product.prodname_ghe_server %} instance.
+1. Inicia sesión en tu instancia de {% data variables.product.prodname_ghe_server %}.
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.settings-tab %}
 {% data reusables.enterprise-accounts.license-tab %}
-1. Under "License sync", click {% octicon "sync" aria-label="The Sync icon" %} **Sync now**. ![Screenshot of "Sync now" button in license sync section](/assets/images/help/enterprises/license-sync-now-ghes.png)
+1. Debajo de "Sincronización de licencia", haz clic en {% octicon "sync" aria-label="The Sync icon" %} **Sincronizar ahora**. ![Captura de pantalla del botón "Sincronizar ahora" en la sección de sincronización de licencia](/assets/images/help/enterprises/license-sync-now-ghes.png)
 
 {% endif %}
 
-## Manually uploading GitHub Enterprise Server license usage
+## Cargar el uso de licencia de GitHub Enterprise Server manualmente
 
 Puedes descargar un archivo JSON desde {% data variables.product.prodname_ghe_server %} y subir el archivo a {% data variables.product.prodname_ghe_cloud %} para sincronizar de forma manual el uso de la licencia de usuario entre dos implementaciones.
 
diff --git a/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/troubleshooting-the-codeql-workflow.md b/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/troubleshooting-the-codeql-workflow.md
index 10182aec4a..aeccac3263 100644
--- a/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/troubleshooting-the-codeql-workflow.md
+++ b/translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/troubleshooting-the-codeql-workflow.md
@@ -68,7 +68,7 @@ Si una compilación automática de código para un lenguaje compilado dentro de
 
 - Elimina el paso de `autobuild` de tu flujo de trabajo de {% data variables.product.prodname_code_scanning %} y agrega los pasos de compilación específicos. Para obtener información sobre cómo editar el flujo de trabajo, consulta la sección "[Configurar el {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/configuring-code-scanning#editing-a-code-scanning-workflow)". Para obtener más información sobre cómo reemplazar el paso de `autobuild`, consulta la sección "[Configurar el flujo de trabajo de {% data variables.product.prodname_codeql %} para los lenguajes compilados](/code-security/secure-coding/configuring-the-codeql-workflow-for-compiled-languages#adding-build-steps-for-a-compiled-language)".
 
-- Si tu flujo de trabajo no especifica explícitamente los lenguajes a analizar, {% data variables.product.prodname_codeql %} detectará implícitamente los lenguajes compatibles en tu código base. En esta configuración, fuera de los lenguajes compilados C/C++, C#, y Java, {% data variables.product.prodname_codeql %} solo analizará el lenguaje presente en la mayoría de los archivos de origen. Edit the workflow and add a matrix specifying the languages you want to analyze. El flujo de análisis predeterminado de CodeQL utiliza dicha matriz.
+- Si tu flujo de trabajo no especifica explícitamente los lenguajes a analizar, {% data variables.product.prodname_codeql %} detectará implícitamente los lenguajes compatibles en tu código base. En esta configuración, fuera de los lenguajes compilados C/C++, C#, y Java, {% data variables.product.prodname_codeql %} solo analizará el lenguaje presente en la mayoría de los archivos de origen. Edita el flujo de trabajo y agrega una matriz que especifique los lenguajes que quieras analizar. El flujo de análisis predeterminado de CodeQL utiliza dicha matriz.
 
   Los siguientes extractos de un flujo de trabajo te muestran cómo puedes utilizar una matriz dentro de la estrategia del job para especificar lenguajes, y luego hace referencia a cada uno de ellos con el paso de "Inicializar {% data variables.product.prodname_codeql %}":
 
@@ -98,7 +98,7 @@ Si una compilación automática de código para un lenguaje compilado dentro de
 
 Si tu flujo de trabajo falla con un error de `No source code was seen during the build` o de `The process '/opt/hostedtoolcache/CodeQL/0.0.0-20200630/x64/codeql/codeql' failed with exit code 32`, esto indica que {% data variables.product.prodname_codeql %} no pudo monitorear tu código. Hay muchas razones que podrían explicar esta falla:
 
-1. The repository may not contain source code that is written in languages supported by {% data variables.product.prodname_codeql %}. Check the list of supported languages and, if this is the case, remove the {% data variables.product.prodname_codeql %} workflow. For more information, see "[About code scanning with CodeQL](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-with-codeql#about-codeql)
+1. Puede que el repositorio no contenga código fuente que esté escrito en los idiomas que son compatibles con {% data variables.product.prodname_codeql %}. Haz clic en la lista de lenguajes compatibles y, si es necesario, elimina el flujo de trabajo de {% data variables.product.prodname_codeql %}. Para obtener más información, consulta la sección "[Acerca del escaneo de código con CodeQL](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-with-codeql#about-codeql)
 
 1. La detección automática del lenguaje identificó un lenguaje compatible, pero no hay código analizable en dicho lenguaje dentro del repositorio. Un ejemplo típico es cuando nuestro servicio de detección de lenguaje encuentra un archivo que se asocia con un lenguaje de programación específico como un archivo `.h`, o `.gyp`, pero no existe el código ejecutable correspondiente a dicho lenguaje en el repositorio. Para resolver el problema, puedes definir manualmente los lenguajes que quieras analizar si actualizas la lista de éstos en la matriz de `language`. Por ejemplo, la siguiente configuración analizará únicamente a Go y a Javascript.
 
@@ -190,7 +190,7 @@ Si utilizas ejecutores auto-hospedados para ejecutar el análisis de {% data var
 
 ### Utilizar matrices de compilación para paralelizar el análisis
 
-The default {% data variables.product.prodname_codeql_workflow %} uses a matrix of languages, which causes the analysis of each language to run in parallel. Si especificaste los lenguajes que quieres analizar directamente en el paso de "Inicializar CodeQL", el análisis de cada lenguaje ocurrirá de forma secuencial. Para agilizar el análisis de lenguajes múltiples, modifica tu flujo de trabajo para utilizar una matriz. Para obtener más información, consulta el extracto de flujo de trabajo en la sección "[Compilación automática para los fallos de un lenguaje compilado](#automatic-build-for-a-compiled-language-fails)" que se trata anteriormente.
+El {% data variables.product.prodname_codeql_workflow %} predeterminado utiliza una matriz de lenguajes, lo cual ocasiona que el análisis de cada uno de ellos se ejecute en paralelo. Si especificaste los lenguajes que quieres analizar directamente en el paso de "Inicializar CodeQL", el análisis de cada lenguaje ocurrirá de forma secuencial. Para agilizar el análisis de lenguajes múltiples, modifica tu flujo de trabajo para utilizar una matriz. Para obtener más información, consulta el extracto de flujo de trabajo en la sección "[Compilación automática para los fallos de un lenguaje compilado](#automatic-build-for-a-compiled-language-fails)" que se trata anteriormente.
 
 ### Reducir la cantidad de código que se está analizando en un solo flujo de trabajo
 
diff --git a/translations/es-ES/content/code-security/dependabot/dependabot-version-updates/about-dependabot-version-updates.md b/translations/es-ES/content/code-security/dependabot/dependabot-version-updates/about-dependabot-version-updates.md
index ee757626eb..ff3f340fc9 100644
--- a/translations/es-ES/content/code-security/dependabot/dependabot-version-updates/about-dependabot-version-updates.md
+++ b/translations/es-ES/content/code-security/dependabot/dependabot-version-updates/about-dependabot-version-updates.md
@@ -30,7 +30,7 @@ shortTitle: Actualizaciones de versión del dependabot
 
 El {% data variables.product.prodname_dependabot %} hace el esfuerzo de mantener tus dependencias. Puedes utilizarlo para garantizar que tu repositorio se mantenga automáticamente con los últimos lanzamientos de los paquetes y aplicaciones de los que depende.
 
-You enable {% data variables.product.prodname_dependabot_version_updates %} by checking a _dependabot.yml_ configuration file into your repository. Este archivo de configuración especifica la ubicación del manifiesto o de otros archivos de definición de paquetes almacenados en tu repositorio. El {% data variables.product.prodname_dependabot %} utiliza esta información para revisar los paquetes y las aplicaciones desactualizadas. El {% data variables.product.prodname_dependabot %} determina si hay una versión nueva de una dependencia al buscar el versionamiento semántico ([semver](https://semver.org/)) de la dependencia para decidir si debería actualizarla a esa versión. Para ciertos administradores de paquetes, {% data variables.product.prodname_dependabot_version_updates %} también es compatible con su delegación a proveedores. Las dependencias delegadas (o almacenadas en caché) son aquellas que se registran en un directorio específico en un repositorio en vez de que se referencien en un manifiesto. Las dependencias delegadas a proveedores están disponibles desde el momento de su creación, incluso si los servidores de paquetes no se encuentran disponibles. Las {% data variables.product.prodname_dependabot_version_updates %} pueden configurarse para verificar las dependencias delegadas a proveedores para las nuevas versiones y también pueden actualizarse de ser necesario.
+You enable {% data variables.product.prodname_dependabot_version_updates %} by checking a `dependabot.yml` configuration file into your repository. Este archivo de configuración especifica la ubicación del manifiesto o de otros archivos de definición de paquetes almacenados en tu repositorio. El {% data variables.product.prodname_dependabot %} utiliza esta información para revisar los paquetes y las aplicaciones desactualizadas. El {% data variables.product.prodname_dependabot %} determina si hay una versión nueva de una dependencia al buscar el versionamiento semántico ([semver](https://semver.org/)) de la dependencia para decidir si debería actualizarla a esa versión. Para ciertos administradores de paquetes, {% data variables.product.prodname_dependabot_version_updates %} también es compatible con su delegación a proveedores. Las dependencias delegadas (o almacenadas en caché) son aquellas que se registran en un directorio específico en un repositorio en vez de que se referencien en un manifiesto. Las dependencias delegadas a proveedores están disponibles desde el momento de su creación, incluso si los servidores de paquetes no se encuentran disponibles. Las {% data variables.product.prodname_dependabot_version_updates %} pueden configurarse para verificar las dependencias delegadas a proveedores para las nuevas versiones y también pueden actualizarse de ser necesario.
 
 Cuando el {% data variables.product.prodname_dependabot %} identifica una dependencia desactualizada, levanta una solicitud de extracción para actualizar el manifiesto a su última versión de la dependencia. Lara las dependencias delegadas a proveedores, el {% data variables.product.prodname_dependabot %} levanta una solicitud de cambios para reemplazar la dependencia desactualizada directamente con la versión nueva. Verificas que tu prueba pase, revisas el registro de cambios y notas de lanzamiento que se incluyan en el resumen de la solicitud de extracción y, posteriormente, lo fusionas. Para obtener más información, consulta la sección "[Configurar las actualizaciones de versión del {% data variables.product.prodname_dependabot %}](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/enabling-and-disabling-dependabot-version-updates)".
 
diff --git a/translations/es-ES/content/code-security/secret-scanning/configuring-secret-scanning-for-your-repositories.md b/translations/es-ES/content/code-security/secret-scanning/configuring-secret-scanning-for-your-repositories.md
index 2aa85ea03c..f15c2e6fbb 100644
--- a/translations/es-ES/content/code-security/secret-scanning/configuring-secret-scanning-for-your-repositories.md
+++ b/translations/es-ES/content/code-security/secret-scanning/configuring-secret-scanning-for-your-repositories.md
@@ -35,7 +35,7 @@ Puedes habilitar el {% data variables.product.prodname_secret_scanning_GHAS %} p
 5. Revisa el impacto de habilitar la {% data variables.product.prodname_advanced_security %} y luego haz clic en **Habilitar la {% data variables.product.prodname_GH_advanced_security %} para este repositorio**.
 6. Cuando habilitas la {% data variables.product.prodname_advanced_security %}, puede que el {% data variables.product.prodname_secret_scanning %} se habilite en el repositorio debido a la configuración de la organización. Si se muestra "{% data variables.product.prodname_secret_scanning_caps %}" con un botón de **Habilitar**, aún necesitarás habilitar el {% data variables.product.prodname_secret_scanning %} si das clic en **Habilitar**. Si ves un botón de **Inhabilitar**, entonces el {% data variables.product.prodname_secret_scanning %} ya se encuentra habilitado. ![Habilitar el {% data variables.product.prodname_secret_scanning %} para tu repositorio](/assets/images/help/repository/enable-secret-scanning-dotcom.png)
 {% if secret-scanning-push-protection %}
-7. Optionally, if you want to enable push protection, click **Enable** to the right of "Push protection." {% data reusables.secret-scanning.push-protection-overview %} For more information, see "[Protecting pushes with {% data variables.product.prodname_secret_scanning %}](/code-security/secret-scanning/protecting-pushes-with-secret-scanning)." ![Enable push protection for your repository](/assets/images/help/repository/secret-scanning-enable-push-protection.png)
+7. Opcionalmente, si quieres habilitar la protección de subida, haz clic en **Habilitar** a la derecha de "Protección de subida". {% data reusables.secret-scanning.push-protection-overview %} Para obtener más información, consulta la sección "[Proteger las subidas con el {% data variables.product.prodname_secret_scanning %}](/code-security/secret-scanning/protecting-pushes-with-secret-scanning)". ![Habilitar la protección de subida para tu repositorio](/assets/images/help/repository/secret-scanning-enable-push-protection.png)
 {% endif %}
 {% ifversion ghae %}
 1. Antes de que puedas habilitar el {% data variables.product.prodname_secret_scanning %}, necesitas habilitar primero la {% data variables.product.prodname_GH_advanced_security %}. A la derecha de "{% data variables.product.prodname_GH_advanced_security %}", da clic en **Habilitar**. ![Habilitar la {% data variables.product.prodname_GH_advanced_security %} para tu repositorio](/assets/images/enterprise/github-ae/repository/enable-ghas-ghae.png)
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 26d4e5a31c..8f1b785578 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
@@ -69,7 +69,7 @@ A nivel organizacional, el resumen de seguridad muestra seguridad agregada y esp
 
 {% ifversion ghec or ghes > 3.4 or ghae-issue-6199 %}
 ### Acerca del resumen de seguridad a nivel empresarial
-En el nivel empresarial, el resumen de seguridad muestra información de seguridad agregada y específica del repositorio para tu empresa. 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.
+En el nivel empresarial, el resumen de seguridad muestra información de seguridad agregada y específica del repositorio para tu empresa. Puedes ver los repositorios que le pertenecen a tu empresa y que tienen alertas de seguridad, ver todas las alertas de seguridad o las alertas de seguridad con características específicas desde cualquier punto de tu empresa.
 
 Los propietarios de organizaciones y administradores de seguridad para las organizaciones de tu empresa también tienen acceso limitado al resumen de seguridad a nivel empresarial. Solo pueden ver los repositorios y alertas de las organizaciones a las cuales tienen acceso completo.
 
diff --git a/translations/es-ES/content/code-security/security-overview/filtering-alerts-in-the-security-overview.md b/translations/es-ES/content/code-security/security-overview/filtering-alerts-in-the-security-overview.md
index 6cc4383862..c304e4fedc 100644
--- a/translations/es-ES/content/code-security/security-overview/filtering-alerts-in-the-security-overview.md
+++ b/translations/es-ES/content/code-security/security-overview/filtering-alerts-in-the-security-overview.md
@@ -118,14 +118,14 @@ Disponible en las vistas de alertas del escaneo de código. Todas las alertas de
 | `severity:note`     | Muestra alertas del {% data variables.product.prodname_code_scanning %} categorizadas como notas.        |
 
 {% if dependabot-alerts-vulnerable-calls %}
-## Filter by {% data variables.product.prodname_dependabot %} alert type
+## Filtrar por tipo de alerta del {% data variables.product.prodname_dependabot %}
 
-Available in the {% data variables.product.prodname_dependabot %} alert views. You can filter the view to show {% data variables.product.prodname_dependabot_alerts %} that are ready to fix or where additional information about exposure is available. You can click any result to see full details of the alert.
+Disponible en las vistas de alerta del {% data variables.product.prodname_dependabot %}. Puedes filtrar la vista para mostrar las {% data variables.product.prodname_dependabot_alerts %} que están listas para arreglarse o donde la información adicional sobre la exposición se encuentre disponible. Puedes hacer clic en cualquier resultado para ver todos los detalles de esa alerta.
 
-| Qualifier              | Descripción                                                                                                                                                                                                                                                                                                                                                       |
-| ---------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `has:patch`            | Displays {% data variables.product.prodname_dependabot %} alerts for vulnerabilities where a secure version is already available.                                                                                                                                                                                                                                 |
-| `has:vulnerable-calls` | Displays {% data variables.product.prodname_dependabot %} alerts where at least one call from the repository to a vulnerable function is detected. For more information, see "[Viewing and updating Dependabot alerts](/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts#about-the-detection-of-calls-to-vulnerable-functions)." |
+| Qualifier              | Descripción                                                                                                                                                                                                                                                                                                                                                                                             |
+| ---------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `has:patch`            | Muestra alertas del {% data variables.product.prodname_dependabot %} para vulnerabilidades en donde una versión segura ya esté disponible.                                                                                                                                                                                                                                                              |
+| `has:vulnerable-calls` | Muestra alertas del {% data variables.product.prodname_dependabot %} en donde se detecta por lo menos una llamada del repositorio a una función vulnerable. Para obtener más información, consulta la sección "[Ver y actualizar las alertas del Dependabot](/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts#about-the-detection-of-calls-to-vulnerable-functions)". |
 {% endif %}
 
 {% endif %}
diff --git a/translations/es-ES/content/code-security/security-overview/viewing-the-security-overview.md b/translations/es-ES/content/code-security/security-overview/viewing-the-security-overview.md
index 61747fb733..66055e71fb 100644
--- a/translations/es-ES/content/code-security/security-overview/viewing-the-security-overview.md
+++ b/translations/es-ES/content/code-security/security-overview/viewing-the-security-overview.md
@@ -42,7 +42,7 @@ shortTitle: Ver el resumen de seguridad
 ## Ver el resumen de seguridad de una empresa
 
 {% data reusables.enterprise-accounts.access-enterprise-on-dotcom %}
-1. In the left sidebar, click {% octicon "shield" aria-label="The shield icon" %} **Code Security**.
+1. En la barra lateral izquierda, haz clic en {% octicon "shield" aria-label="The shield icon" %} **Seguridad de código**.
 {% if security-overview-feature-specific-alert-page %}
 {% data reusables.organizations.security-overview-feature-specific-page %}
 {% endif %}
diff --git a/translations/es-ES/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-supply-chain-security.md b/translations/es-ES/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-supply-chain-security.md
index 88722216e5..a1190d58d4 100644
--- a/translations/es-ES/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-supply-chain-security.md
+++ b/translations/es-ES/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-supply-chain-security.md
@@ -141,7 +141,7 @@ Private repositories:
 {% elsif ghec %}
 - **Dependency review**—available in private repositories owned by organizations provided you have a license for {% data variables.product.prodname_GH_advanced_security %} and the dependency graph enabled. Para obtener más información, consulta las secciones "[Acerca de la {% data variables.product.prodname_GH_advanced_security %}](/get-started/learning-about-github/about-github-advanced-security)" y "[Explorar las dependencias de un repositorio](/code-security/supply-chain-security/understanding-your-software-supply-chain/exploring-the-dependencies-of-a-repository#enabling-and-disabling-the-dependency-graph-for-a-private-repository)"
 {% endif %}
-- **{% data variables.product.prodname_dependabot_alerts %}**—no se habilita predeterminadamente. Los propietarios de los repositorios privados o las personas con acceso administrativo puede habilitar las {% data variables.product.prodname_dependabot_alerts %} si habilitan la gráfica de dependencias y las {% data variables.product.prodname_dependabot_alerts %} para sus repositorios. También puedes habilitar o inhabilitar las alertas del Dependabot para todos los repositorios que pertenezcan a tu cuenta de usuario u organización. For more information, see "[Managing security and analysis settings for your user account](/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)" or "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-security-and-analysis-settings-for-your-organization)."
+- **{% data variables.product.prodname_dependabot_alerts %}**—no se habilita predeterminadamente. Los propietarios de los repositorios privados o las personas con acceso administrativo puede habilitar las {% data variables.product.prodname_dependabot_alerts %} si habilitan la gráfica de dependencias y las {% data variables.product.prodname_dependabot_alerts %} para sus repositorios. También puedes habilitar o inhabilitar las alertas del Dependabot para todos los repositorios que pertenezcan a tu cuenta de usuario u organización. Para obtener más información, consulta la sección "[Administrar los ajustes de análisis y seguridad para tu cuenta de usuario](/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)" o "[Administrar el análisis y seguridad para tu organización](/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-security-and-analysis-settings-for-your-organization)".
 
 Any repository type:
 - **{% data variables.product.prodname_dependabot_security_updates %}**—no se habilita predeterminadamente. Puedes habilitar las {% data variables.product.prodname_dependabot_security_updates %} para cualquier repositorio que utilice {% data variables.product.prodname_dependabot_alerts %} y la gráfica de dependencias. Para obtener más información sobre cómo habilitar las actualizaciones de seguridad, consulta la sección "[Configurar las {% data variables.product.prodname_dependabot_security_updates %}](/code-security/dependabot/dependabot-security-updates/configuring-dependabot-security-updates)".
diff --git a/translations/es-ES/content/codespaces/codespaces-reference/security-in-codespaces.md b/translations/es-ES/content/codespaces/codespaces-reference/security-in-codespaces.md
index a3f28fe184..64129c25d5 100644
--- a/translations/es-ES/content/codespaces/codespaces-reference/security-in-codespaces.md
+++ b/translations/es-ES/content/codespaces/codespaces-reference/security-in-codespaces.md
@@ -34,7 +34,7 @@ Cada codespace tiene su propia red virtual aislada. Utilizamos cortafuegos para
 
 ### Autenticación
 
-You can connect to a codespace using a web browser or from {% data variables.product.prodname_vscode %}. If you connect from {% data variables.product.prodname_vscode_shortname %}, you are prompted to authenticate with {% data variables.product.product_name %}.
+Puedes conectarte a un codespace utilizando un buscador web o desde {% data variables.product.prodname_vscode %}. Si te conectas desde {% data variables.product.prodname_vscode_shortname %}, se te pedirá autenticarte con {% data variables.product.product_name %}.
 
 Cada vez que se cree o reinicie un codespace, se le asignará un token de {% data variables.product.company_short %} nuevo con un periodo de vencimiento automático. Este periodo te permite trabajar en el codespace sin necesitar volver a autenticarte durante un día de trabajo habitual, pero reduce la oportunidad de que dejes la conexión abierta cuando dejas de utilizar el codespace.
 
diff --git a/translations/es-ES/content/codespaces/codespaces-reference/using-github-copilot-in-codespaces.md b/translations/es-ES/content/codespaces/codespaces-reference/using-github-copilot-in-codespaces.md
index ec782fa8ab..95820cc208 100644
--- a/translations/es-ES/content/codespaces/codespaces-reference/using-github-copilot-in-codespaces.md
+++ b/translations/es-ES/content/codespaces/codespaces-reference/using-github-copilot-in-codespaces.md
@@ -17,7 +17,7 @@ redirect_from:
 
 ## Uso de {% data variables.product.prodname_copilot %}
 
-[{% data variables.product.prodname_copilot %}](https://copilot.github.com/), un programador de par de IA, puede utilizarse en cualquier codespace. To start using {% data variables.product.prodname_copilot_short %} in {% data variables.product.prodname_codespaces %}, install the [{% data variables.product.prodname_copilot_short %} extension from the {% data variables.product.prodname_vscode_marketplace %}](https://marketplace.visualstudio.com/items?itemName=GitHub.copilot).
+[{% data variables.product.prodname_copilot %}](https://copilot.github.com/), un programador de par de IA, puede utilizarse en cualquier codespace. Para comenzar a utilizar {% data variables.product.prodname_copilot_short %} en {% data variables.product.prodname_codespaces %}, instala la [extensión de {% data variables.product.prodname_copilot_short %} desde {% data variables.product.prodname_vscode_marketplace %}](https://marketplace.visualstudio.com/items?itemName=GitHub.copilot).
 
-Para incluir al {% data variables.product.prodname_copilot_short %} u otras extensiones en tus codespaces, habilita la sincronización de ajustes. Para obtener más información, consulta la sección "[Personalizar {% data variables.product.prodname_codespaces %} para tu cuenta](/codespaces/customizing-your-codespace/personalizing-codespaces-for-your-account#settings-sync)". Adicionalmente, para incluir al {% data variables.product.prodname_copilot_short %} en algún proyecto específico para todos los usuarios, puedes especificar `GitHub.copilot` como una extensión en tu archivo de `devcontainer.json`. For information about configuring a `devcontainer.json` file, see "[Introduction to dev containers](/codespaces/customizing-your-codespace/configuring-codespaces-for-your-project#creating-a-custom-dev-container-configuration)."
+Para incluir al {% data variables.product.prodname_copilot_short %} u otras extensiones en tus codespaces, habilita la sincronización de ajustes. Para obtener más información, consulta la sección "[Personalizar {% data variables.product.prodname_codespaces %} para tu cuenta](/codespaces/customizing-your-codespace/personalizing-codespaces-for-your-account#settings-sync)". Adicionalmente, para incluir al {% data variables.product.prodname_copilot_short %} en algún proyecto específico para todos los usuarios, puedes especificar `GitHub.copilot` como una extensión en tu archivo de `devcontainer.json`. Para obtener más información sobre cómo configurar un archivo `devcontainer.json`, consulta la sección "[Introducción a los contenedores dev](/codespaces/customizing-your-codespace/configuring-codespaces-for-your-project#creating-a-custom-dev-container-configuration)".
 
diff --git a/translations/es-ES/content/codespaces/codespaces-reference/using-the-vs-code-command-palette-in-codespaces.md b/translations/es-ES/content/codespaces/codespaces-reference/using-the-vs-code-command-palette-in-codespaces.md
index 4f4daa048e..b50460566f 100644
--- a/translations/es-ES/content/codespaces/codespaces-reference/using-the-vs-code-command-palette-in-codespaces.md
+++ b/translations/es-ES/content/codespaces/codespaces-reference/using-the-vs-code-command-palette-in-codespaces.md
@@ -17,7 +17,7 @@ redirect_from:
 
 ## Acerca de {% data variables.product.prodname_vscode_command_palette %}
 
-La paleta de comandos es una de las características focales de {% data variables.product.prodname_vscode %} y está disponible para que la utilices en Codespaces. La {% data variables.product.prodname_vscode_command_palette %} te permite acceder a muchos comandos para {% data variables.product.prodname_codespaces %} y {% data variables.product.prodname_vscode_shortname %}. For more information on using the {% data variables.product.prodname_vscode_command_palette_shortname %}, see "[User Interface](https://code.visualstudio.com/docs/getstarted/userinterface#_command-palette)" in the {% data variables.product.prodname_vscode_shortname %} documentation.
+La paleta de comandos es una de las características focales de {% data variables.product.prodname_vscode %} y está disponible para que la utilices en Codespaces. La {% data variables.product.prodname_vscode_command_palette %} te permite acceder a muchos comandos para {% data variables.product.prodname_codespaces %} y {% data variables.product.prodname_vscode_shortname %}. Para obtener más información sobre cómo utilizar la {% data variables.product.prodname_vscode_command_palette_shortname %}, consulta la sección "[Interfaz de usuario](https://code.visualstudio.com/docs/getstarted/userinterface#_command-palette)" en la documentación de {% data variables.product.prodname_vscode_shortname %}.
 
 ## Acceder a la {% data variables.product.prodname_vscode_command_palette_shortname %}
 
diff --git a/translations/es-ES/content/codespaces/customizing-your-codespace/changing-the-machine-type-for-your-codespace.md b/translations/es-ES/content/codespaces/customizing-your-codespace/changing-the-machine-type-for-your-codespace.md
index 071ac2e6d6..799f7acce7 100644
--- a/translations/es-ES/content/codespaces/customizing-your-codespace/changing-the-machine-type-for-your-codespace.md
+++ b/translations/es-ES/content/codespaces/customizing-your-codespace/changing-the-machine-type-for-your-codespace.md
@@ -20,7 +20,7 @@ topics:
 
 {% endnote %}
 
-{% data reusables.codespaces.codespaces-machine-types %} You can choose an alternative machine type either when you create a codespace or at any time after you've created a codespace.
+{% data reusables.codespaces.codespaces-machine-types %} Puedes elegir un tipo de máquina alterno ya sea cuando creas un codespace o en cualquier momento después de que hayas creado un codespace.
 
 Para obtener más información sobre cómo elegir un tio de máquina cuando creas un codespace, consulta la sección "[Crear un codespace](/codespaces/developing-in-codespaces/creating-a-codespace#creating-a-codespace)". Para obtener más información sobre cómo cambiar el tipo de máquina dentro de {% data variables.product.prodname_vscode %}, consulta la sección "[Utilizar los {% data variables.product.prodname_codespaces %} en {% data variables.product.prodname_vscode %}](/codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code#changing-the-machine-type-in-visual-studio-code)".
 
diff --git a/translations/es-ES/content/codespaces/customizing-your-codespace/setting-your-timeout-period-for-codespaces.md b/translations/es-ES/content/codespaces/customizing-your-codespace/setting-your-timeout-period-for-codespaces.md
index c7327145e7..e675e28460 100644
--- a/translations/es-ES/content/codespaces/customizing-your-codespace/setting-your-timeout-period-for-codespaces.md
+++ b/translations/es-ES/content/codespaces/customizing-your-codespace/setting-your-timeout-period-for-codespaces.md
@@ -12,7 +12,7 @@ shortTitle: Configurar el tiempo de inactividad
 
 Un codespace dejará de ejecutarse después de un periodo de inactividad. Puedes especificar la longitud de este periodo. El ajuste actualizado se aplicará a cualquier codespace recién creado.
 
-Some organizations may have a maximum idle timeout policy. If an organization policy sets a maximum timeout which is less than the default timeout you have set, the organization's timeout will be used instead of your setting, and you will be notified of this after the codespace is created. For more information, see "[Restricting the idle timeout period](/codespaces/managing-codespaces-for-your-organization/restricting-the-idle-timeout-period)."
+Algunas organizaciones podrían tener una política de tiempo de inactividad máximo. Si una política de organización configura un tiempo de inactividad máximo, el cual sea menos que el predeterminado que ya hayas configurado, el tiempo de espera de la organización se utilizará en vez de tu ajuste y se te notificará de esto después de que se haya creado el codespace. Para obtener más información, consulta la sección "[Restringir el periodo de tiempo de inactividad](/codespaces/managing-codespaces-for-your-organization/restricting-the-idle-timeout-period)".
 
 {% warning %}
 
diff --git a/translations/es-ES/content/codespaces/getting-started/quickstart.md b/translations/es-ES/content/codespaces/getting-started/quickstart.md
index d6564071cc..62eca433f8 100644
--- a/translations/es-ES/content/codespaces/getting-started/quickstart.md
+++ b/translations/es-ES/content/codespaces/getting-started/quickstart.md
@@ -72,7 +72,7 @@ Ahora que hiciste algunos cambios, puedes utilizar la terminal integrada o la vi
 
 ## Personalizar con una extensión
 
-Within a codespace, you have access to the {% data variables.product.prodname_vscode_marketplace %}. Para este ejemplo, instalarás una extensión que altera el tema, pero puedes instalar cualquier extensión que sea útil para tu flujo de trabajo.
+Dentro de un codespace, tienes acceso a {% data variables.product.prodname_vscode_marketplace %}. Para este ejemplo, instalarás una extensión que altera el tema, pero puedes instalar cualquier extensión que sea útil para tu flujo de trabajo.
 
 1. En la barra lateral, haz clic en el icono de extensiones.
 
@@ -84,7 +84,7 @@ Within a codespace, you have access to the {% data variables.product.prodname_vs
 
   ![Seleccionar el tema de fairyfloss](/assets/images/help/codespaces/fairyfloss.png)
 
-4. Changes you make to your editor setup in the current codespace, such as theme and keyboard bindings, are synced automatically via [Settings Sync](https://code.visualstudio.com/docs/editor/settings-sync) to any other codespaces you open and any instances of {% data variables.product.prodname_vscode %} that are signed into your GitHub account.
+4. Los cambios que hagas a la configuración de tu editor en el codespace actual, tales como el tema y las uniones del teclado, se sincronizarán automáticamente a través de la [Sincornización de ajustes](https://code.visualstudio.com/docs/editor/settings-sync) a cualquier otro codespace que abras y a cualquier instancia de {% data variables.product.prodname_vscode %} que esté firmada en tu cuenta de GitHub.
 
 ## Siguientes pasos
 
diff --git a/translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/enabling-codespaces-for-your-organization.md b/translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/enabling-codespaces-for-your-organization.md
index 740cc0b226..f004b92e44 100644
--- a/translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/enabling-codespaces-for-your-organization.md
+++ b/translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/enabling-codespaces-for-your-organization.md
@@ -35,7 +35,7 @@ Predeterminadamente, un codespace solo puede acceder al repositorio desde el cua
 {% ifversion fpt %}
 {% note %}
 
-**Note:** If you are a verified educator or a teacher, you must enable {% data variables.product.prodname_codespaces %} from a {% data variables.product.prodname_classroom %} to use your {% data variables.product.prodname_codespaces %} Education benefit. For more information, see "[Using GitHub Codespaces with GitHub Classroom](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/using-github-codespaces-with-github-classroom#about-the-codespaces-education-benefit-for-verified-teachers)."
+**Nota:** Si eres un maestro o docente verificado, debes habilitar {% data variables.product.prodname_codespaces %} desde un {% data variables.product.prodname_classroom %} para utilizar tu beneficio de docente de {% data variables.product.prodname_codespaces %}. Para obtener más información, consulta la sección "[Utilizar los Codespaces de GitHub con GitHub Clasroom](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/using-github-codespaces-with-github-classroom#about-the-codespaces-education-benefit-for-verified-teachers)".
 
 {% endnote %}
 {% endif %}
diff --git a/translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/managing-billing-for-codespaces-in-your-organization.md b/translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/managing-billing-for-codespaces-in-your-organization.md
index 15a5b95df1..841ab614bc 100644
--- a/translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/managing-billing-for-codespaces-in-your-organization.md
+++ b/translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/managing-billing-for-codespaces-in-your-organization.md
@@ -41,7 +41,7 @@ Puedes limitar la elección de tipos de máquina que se encuentra disponible par
 
 ## Borrar los codespaces sin utilizar
 
-Your users can delete their codespaces in https://github.com/codespaces and from within {% data variables.product.prodname_vscode %}. To reduce the size of a codespace, users can manually delete files using the terminal or from within {% data variables.product.prodname_vscode_shortname %}.
+Tus usuarios pueden borrar sus codespaces en https://github.com/codespaces y desde dentro de {% data variables.product.prodname_vscode %}. Para reducir el tamaño de un codespace, los usuarios pueden borrar los archivos manualmente utilizando la terminal o desde dentro de {% data variables.product.prodname_vscode_shortname %}.
 
 {% note %}
 
diff --git a/translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types.md b/translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types.md
index 35216c6d1a..60b5ce42a6 100644
--- a/translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types.md
+++ b/translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types.md
@@ -1,6 +1,6 @@
 ---
 title: Restringir el acceso a los tipos de máquina
-shortTitle: Restrict machine types
+shortTitle: Restringir los tipos de máquina
 intro: Puedes configurar restricciones en los tipos de máquina que los usuarios pueden elegir cuando crean codespaces en tu organizción.
 product: '{% data reusables.gated-features.codespaces %}'
 permissions: 'To manage access to machine types for the repositories in an organization, you must be an owner of the organization.'
@@ -57,7 +57,7 @@ Si agregas una política a nivel organizacional, deberías configurarla en la el
    ![Editar la restricción de tipo de máquina](/assets/images/help/codespaces/edit-machine-constraint.png)
 
 {% data reusables.codespaces.codespaces-policy-targets %}
-1. If you want to add another constraint to the policy, click **Add constraint** and choose another constraint. For information about other constraints, see "[Restricting the visibility of forwarded ports](/codespaces/managing-codespaces-for-your-organization/restricting-the-visibility-of-forwarded-ports)" and "[Restricting the idle timeout period](/codespaces/managing-codespaces-for-your-organization/restricting-the-idle-timeout-period)."
+1. If you want to add another constraint to the policy, click **Add constraint** and choose another constraint. Para obtener más información sobre otras restricciones, consulta las secciones "[Restringir la visibilidad de los puertos reenviados](/codespaces/managing-codespaces-for-your-organization/restricting-the-visibility-of-forwarded-ports)" y "[Restringir el periodo de tiempo de inactividad](/codespaces/managing-codespaces-for-your-organization/restricting-the-idle-timeout-period)".
 1. After you have finished adding constraints to your policy, click **Save**.
 ## Editar una política
 
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 1cd41d18f8..4a63bba825 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
@@ -15,9 +15,9 @@ product: '{% data reusables.gated-features.codespaces %}'
 
 ## Resumen
 
-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 (CPUs, memory, storage) and, by default, the machine type with the least resources is used. Para obtener más información, consulta la sección "[Cambiar el tipo de máquina de tu codespace](/codespaces/customizing-your-codespace/changing-the-machine-type-for-your-codespace#about-machine-types)".
+Cada codespace que crees se hospeda en una máquina virtual por separado y, habitualmente, puedes elegir de entre varios tipos diferentes de máquinas virtuales. Cada tipo de máquina tiene recursos diferentes (CPU, memoria, almacenamiento) y, predeterminadamente, se utiliza el tipo de máquina con menos recursos. Para obtener más información, consulta la sección "[Cambiar el tipo de máquina de tu 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.
+Si tu proyecto necesita un nivel específico de potencia de computadora, puedes configurar {% data variables.product.prodname_github_codespaces %} para que solo se puedan usar, predeterminadamente, los tipos de máquina que cumplen con estos requisitos, o aquellos que seleccionen los usuarios. Configurarás esto en un archivo de `devcontainer.json`.
 
 {% note %}
 
@@ -27,7 +27,7 @@ If your project needs a certain level of compute power, you can configure {% dat
 
 ## Configurar una especificación de máquina mínima
 
-1. {% data variables.product.prodname_codespaces %} for your repository are configured in a `devcontainer.json` file. Si tu repositorio no contiene ya un archivo `devcontainer.json`, agrégalo ahora. 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. Los {% data variables.product.prodname_codespaces %} para tu repositorio se configuran en un archivo de `devcontainer.json`. Si tu repositorio no contiene ya un archivo `devcontainer.json`, agrégalo ahora. Consulta la sección "[Agregar una configuración de contenedor dev a tu repositorio](/free-pro-team@latest/codespaces/setting-up-your-project-for-codespaces/setting-up-your-project-for-codespaces)".
 1. Edita el archivo `devcontainer.json` agregando una propiedad de `hostRequirements` tal como esta:
 
    ```json{:copy}
@@ -44,7 +44,7 @@ If your project needs a certain level of compute power, you can configure {% dat
 
 1. Guarda el archivo y confirma tus cambios a la rama requerida del repositorio.
 
-   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.
+   Ahora, cuando crees un codespace para esa rama del repositorio y vayas a las opciones de configuración para la creación, solo podrás seleccionar los tipos de máquina que coincidan con los recursos ampliados que especificaste.
 
    ![Caja de diálogo que muestra una selección limitada de tipos de máquina](/assets/images/help/codespaces/machine-types-limited-choice.png)
 
diff --git a/translations/es-ES/content/codespaces/the-githubdev-web-based-editor.md b/translations/es-ES/content/codespaces/the-githubdev-web-based-editor.md
index b2e751ef1b..4cedd7c63c 100644
--- a/translations/es-ES/content/codespaces/the-githubdev-web-based-editor.md
+++ b/translations/es-ES/content/codespaces/the-githubdev-web-based-editor.md
@@ -49,7 +49,7 @@ Tanto el {% data variables.product.prodname_serverless %} como los {% data varia
 | **Inicio**               | El {% data variables.product.prodname_serverless %} se abre instantáneamente al presionar una tecla y puedes comenzar a usarlo de inmediato sin tener que esperar por configuraciones o instalaciones adicionales.             | Cuando creas o reanudas un codespace, a este se le asigna una MV y el contenedor se configura con base ene l contenido de un archivo de `devcontainer.json`. Esta configuración puede tomar algunos minutos para crear el ambiente. Para obtener más información, consulta la sección "[Crear un Codespace](/codespaces/developing-in-codespaces/creating-a-codespace)". |
 | **Cálculo**              | No hay cálculos asociados, así que no podrás compilar y ejecutar tu código ni utilizar la terminal integrada.                                                                                                                  | Con {%  data   variables.product.prodname_codespaces %}, obtienes el poder de la MV dedicada en ela que ejecutas y depuras tu aplicación.                                                                                                                                                                                                                                |
 | **Acceso a la terminal** | Ninguno.                                                                                                                                                                                                                       | {% data variables.product.prodname_codespaces %} proporciona un conjunto común de herramientas predeterminadamente, lo que significa que puedes utilizar la terminal como lo harías en tu ambiente local.                                                                                                                                                                |
-| **Extensiones**          | Solo un subconjunto de extensiones que pueden ejecutarse en la web aparecerá en la Vista de Extensiones y podrá instalarse. Para obtener más información, consulta la sección "[Utilizar las extensiones](#using-extensions)". | With Codespaces, you can use most extensions from the {% data variables.product.prodname_vscode_marketplace %}.                                                                                                                                                                                                                                                        |
+| **Extensiones**          | Solo un subconjunto de extensiones que pueden ejecutarse en la web aparecerá en la Vista de Extensiones y podrá instalarse. Para obtener más información, consulta la sección "[Utilizar las extensiones](#using-extensions)". | Con los codespaces, puedes utilizar la mayoría de las extensiones de {% data variables.product.prodname_vscode_marketplace %}.                                                                                                                                                                                                                                         |
 
 ### Seguir trabajando en {%  data   variables.product.prodname_codespaces %}
 
diff --git a/translations/es-ES/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/common-validation-errors-when-creating-issue-forms.md b/translations/es-ES/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/common-validation-errors-when-creating-issue-forms.md
index f257b96ca5..d048f96e5c 100644
--- a/translations/es-ES/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/common-validation-errors-when-creating-issue-forms.md
+++ b/translations/es-ES/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/common-validation-errors-when-creating-issue-forms.md
@@ -252,7 +252,7 @@ body:
 
 ## Las casillas de verificación deben tener etiquetas únicas
 
-When a `checkboxes` element is present, each of its nested labels must be unique among its peers, as well as among other input types.
+Cuando está presente un elemento de `checkboxes`, cada una de sus etiquetas anidadas debe ser única entre sus pares, así como entre otros tipos de entrada.
 
 ### Ejemplo
 
@@ -268,7 +268,7 @@ body:
     - label: Name
 ```
 
-The error can be fixed by changing the `label` attribute for one of these inputs.
+El error se puede corregir cambiando el atributo `label` para una de estas entradas.
 
 ```yaml
 name: "Bug report"
@@ -282,7 +282,7 @@ body:
     - label: Your name
 ```
 
-Alternatively, you can supply an `id` to any clashing top-level elements. Nested checkbox elements do not support the `id` attribute.
+Como alternativa, puedes proporcionar una `id` para cualquier elemento en conflicto de nivel superior. Los elementos de casilla de verificación anidada no son compatibles con el atributo `id`.
 
 ```yaml
 name: "Bug report"
@@ -299,9 +299,9 @@ body:
 
 Los atributos de `id` no estuvieron visibles en el cuerpo de la propuesta. Si quieres distinguir los campos en la propuesta resultante, deberías utilizar atributos distintos de `label`.
 
-## Body[i]: required key type is missing
+## Body[i]: no se encuentra el tipo de llave requerido
 
-Each body block must contain the key `type`.
+Cada bloque del cuerpo debe contener el `type` de la llave.
 
 Los errores con `body` tendràn un prefijo de `body[i]` en donde `i` representa el índice cero del bloque de cuerpo que contiene el error. Por ejemplo, `body[0]` nos dice que el error lo ocasionó el primer bloque en la lista `body`.
 
@@ -431,7 +431,7 @@ body:
 
 ## Body[i]: La `id` solo puede contener números, letras, -, o _
 
-`id` attributes can only contain alphanumeric characters, `-`, and `_`. Your template may include non-permitted characters, such as whitespace, in an `id`.
+Los atributos de `id` solo pueden contener caracteres alfanuméricos, `-` y `_`. Tu plantilla podría incluir caracteres no permitidos, tales como el espacio en blanco, en una `id`.
 
 En los errores con `body` se utilizará el prefijo `body[i]`, en donde `i` representa el índice del bloque del cuerpo que contiene el error. Por ejemplo, `body[0]` nos dice que el primer bloque en la lista `body` ocasionó el error.
 
@@ -446,7 +446,7 @@ body:
     label: First name
 ```
 
-The error can be fixed by ensuring that whitespaces and other non-permitted characters are removed from `id` values.
+El error puede corregirse si te aseguras de que se eliminen los espacios en blanco y otros caracteres no permitidos de los valores de la `id`.
 
 ```yaml
 name: "Bug report"
@@ -457,9 +457,9 @@ body:
     label: First name
 ```
 
-## Body[i]: `x` is not a permitted key
+## Body[i]: `x` no es una clave permitida
 
-An unexpected key, `x`, was provided at the same indentation level as `type` and `attributes`.
+Se proporcionó una clave inesperada, `x`, en el mismo nivel de sangría que `type` y `attributes`.
 
 En los errores con `body` se utilizará el prefijo `body[i]`, en donde `i` representa el índice del bloque del cuerpo que contiene el error. Por ejemplo, `body[0]` nos dice que el primer bloque en la lista `body` ocasionó el error.
 
@@ -473,7 +473,7 @@ body:
     value: "Thanks for taking the time to fill out this bug! Si necesitas ayuda en tiempo real, únetenos en Discord."
 ```
 
-The error can be fixed by removing extra keys and only using `type`, `attributes`, and `id`.
+El error se puede corregir eliminando las claves adicionales y utilizando únicamente `type`, `attributes` e `id`.
 
 ```yaml
 body:
@@ -482,9 +482,9 @@ body:
     value: "Thanks for taking the time to fill out this bug! Si necesitas ayuda en tiempo real, únetenos en Discord."
 ```
 
-## Body[i]: `label` contains forbidden word
+## Body[i]: `label` contiene una palabra prohibida
 
-To minimize the risk of private information and credentials being posted publicly in GitHub Issues, some words commonly used by attackers are not permitted in the `label` of input or textarea elements.
+Para disminuir el riesgo de que la información privada y las credenciales se publiquen para todos en general en las propuestas de GitHub, algunas palabras que los atacantes utilizan habitualmente no se permiten en la `label`de entrada ni en los elementos del área de texto.
 
 En los errores con `body` se utilizará el prefijo `body[i]`, en donde `i` representa el índice del bloque del cuerpo que contiene el error. Por ejemplo, `body[0]` nos dice que el primer bloque en la lista `body` ocasionó el error.
 
@@ -500,7 +500,7 @@ body:
     label: Password
 ```
 
-The error can be fixed by removing terms like "password" from any `label` fields.
+El error se puede corregir si se eliminan los términos como "contraseña" de cualquier campo de `label`.
 
 ```yaml
 body:
@@ -512,9 +512,9 @@ body:
     label: Username
 ```
 
-## Body[i]: `x` is not a permitted attribute
+## Body[i]: `x` no es un atributo permitido
 
-An invalid key has been supplied in an `attributes` block.
+Se suministró una clave inválida en un bloque de `attributes`.
 
 En los errores con `body` se utilizará el prefijo `body[i]`, en donde `i` representa el índice del bloque del cuerpo que contiene el error. Por ejemplo, `body[0]` nos dice que el primer bloque en la lista `body` ocasionó el error.
 
@@ -528,7 +528,7 @@ body:
     value: "Thanks for taking the time to fill out this bug!"
 ```
 
-The error can be fixed by removing extra keys and only using permitted attributes.
+El error puede corregirse si eliminas las claves adicionales y solo utilizas los atributos permitidos.
 
 ```yaml
 body:
@@ -537,9 +537,9 @@ body:
     value: "Thanks for taking the time to fill out this bug!"
 ```
 
-## Body[i]: `options` must be unique
+## Body[i]: `options` debe ser único
 
-For checkboxes and dropdown input types, the choices defined in the `options` array must be unique.
+En el caso de los tipos de entrada de casillas de verificación y menús desplegables, las elecciones que se definen en el arreglo `options` deben ser únicas.
 
 En los errores con `body` se utilizará el prefijo `body[i]`, en donde `i` representa el índice del bloque del cuerpo que contiene el error. Por ejemplo, `body[0]` nos dice que el primer bloque en la lista `body` ocasionó el error.
 
@@ -556,7 +556,7 @@ body:
       - pie
 ```
 
-The error can be fixed by ensuring that no duplicate choices exist in the `options` array.
+El error puede corregirse si garantizas que no habrán elecciones duplicadas en el arreglo `options`.
 
 ```
 body:
@@ -568,9 +568,9 @@ body:
       - pie
 ```
 
-## Body[i]: `options` must not include the reserved word, none
+## Body[i]: `options` no debe incluir la palabra reservada "none"
 
-"None" is a reserved word in an `options` set because it is used to indicate non-choice when a `dropdown` is not required.
+"None" es una palabra reservada en un conjunto de `options` ya que se utiliza para indicar que no hay elecciones cuando no se requiere un `dropdown`.
 
 En los errores con `body` se utilizará el prefijo `body[i]`, en donde `i` representa el índice del bloque del cuerpo que contiene el error. Por ejemplo, `body[0]` nos dice que el primer bloque en la lista `body` ocasionó el error.
 
@@ -589,7 +589,7 @@ body:
     required: true
 ```
 
-The error can be fixed by removing "None" as an option. If you want a contributor to be able to indicate that they like none of those types of pies, you can additionally remove the `required` validation.
+El error puede corregirse si se elimina "None" de las opciones. Si quieres que un contribuyente pueda indicar que no le parece ninguno de esos tipos de tarta, puedes eliminar adicionalmente la validación `required`.
 
 ```
 body:
@@ -601,11 +601,11 @@ body:
       - Chicken & Leek
 ```
 
-In this example, "None" will be auto-populated as a selectable option.
+En este ejemplo, "None" se llenará automáticamente como una opción seleccionable.
 
-## Body[i]: `options` must not include booleans. Please wrap values such as 'yes', and 'true' in quotes
+## Body[i]: `options` no debe incluir booleanos. Por favor, pon los valores como 'yes' y 'true' entre comillas
 
-There are a number of English words that become processed into Boolean values by the YAML parser unless they are wrapped in quotes. For dropdown `options`, all items must be strings rather than Booleans.
+Hay varias palabras en inglés que el analizador de YAML procesa como valores Booleanos, a menos de que se pongan entre comillas. Para las `options` de menú desplegable, todos los elementos deben ser secuencias en vez de booleanos.
 
 En los errores con `body` se utilizará el prefijo `body[i]`, en donde `i` representa el índice del bloque del cuerpo que contiene el error. Por ejemplo, `body[0]` nos dice que el primer bloque en la lista `body` ocasionó el error.
 
@@ -622,7 +622,7 @@ body:
       - Maybe
 ```
 
-The error can be fixed by wrapping each offending option in quotes, to prevent them from being processed as Boolean values.
+El error puede corregirse si pones cada opción infractora entre comillas, para prevenir que se procesen como valores booleanos.
 
 ```
 body:
diff --git a/translations/es-ES/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/viewing-a-pull-request-in-github-desktop.md b/translations/es-ES/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/viewing-a-pull-request-in-github-desktop.md
index 5e33415e6f..39cf055f4b 100644
--- a/translations/es-ES/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/viewing-a-pull-request-in-github-desktop.md
+++ b/translations/es-ES/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/viewing-a-pull-request-in-github-desktop.md
@@ -15,7 +15,7 @@ Puedes ver las solicitudes de extracción que tú o tus colaboradores hayan prop
 
 Cuando visualizas una solicitud de extracción en {% data variables.product.prodname_desktop %}, puedes ver un historial de confirmaciones que han hecho los colaboradores. También puedes ver qué archivos modificaron, agregaron o borraron estas confirmaciones. Desde {% data variables.product.prodname_desktop %}, puedes abrir los repositorios en tu editor de texto preferido para ver cualquier cambio o para hacer cambios adicionales. Después de recibir los cambios en una solicitud de extracción, puedes dar retroalimentación en {% data variables.product.prodname_dotcom %}. Para obtener más información, consulta la sección "[Acerca de las revisiones de las solicitudes de extracción](/github/collaborating-with-issues-and-pull-requests/about-pull-request-reviews)".
 
-Si se habilitaron las verificaciones en tu repositorio, {% data variables.product.prodname_desktop %} mostrará el estado de ellas en la solicitud de cambios y te permitirá volver a ejecutarlas. For more information, see "[Viewing and re-running checks in GitHub Desktop](/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/viewing-and-re-running-checks-in-github-desktop)."
+Si se habilitaron las verificaciones en tu repositorio, {% data variables.product.prodname_desktop %} mostrará el estado de ellas en la solicitud de cambios y te permitirá volver a ejecutarlas. Para obtener más información, consulta la sección "[Ver y volver a ejecutar las verificaciones en GitHub Desktop](/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/viewing-and-re-running-checks-in-github-desktop)".
 
 ## Visualizar una solicitud de extracción en {% data variables.product.prodname_desktop %}
 {% data reusables.desktop.current-branch-menu %}
diff --git a/translations/es-ES/content/developers/apps/getting-started-with-apps/about-apps.md b/translations/es-ES/content/developers/apps/getting-started-with-apps/about-apps.md
index 45a3ba13af..a424bcfa14 100644
--- a/translations/es-ES/content/developers/apps/getting-started-with-apps/about-apps.md
+++ b/translations/es-ES/content/developers/apps/getting-started-with-apps/about-apps.md
@@ -85,7 +85,7 @@ Considera estas ideas cuando utilices tokens de acceso personal:
 * Puedes realizar solicitudes cURL de una sola ocasión.
 * Puedes ejecutar scripts personales.
 * No configures un script para que lo utilice todo tu equipo o compañía.
-* Don't set up a shared personal account to act as a bot user.{% ifversion fpt or ghes > 3.2 or ghae or ghec %}
+* No configures una cuenta personal compartida para que actúe como un usuario bot.{% ifversion fpt or ghes > 3.2 or ghae or ghec %}
 * Sí debes establecer un vencimiento para tus tokens de acceso personal para que te ayuden a mantener tu información segura.{% endif %}
 
 ## Determinar qué integración debes crear
diff --git a/translations/es-ES/content/developers/webhooks-and-events/webhooks/webhook-events-and-payloads.md b/translations/es-ES/content/developers/webhooks-and-events/webhooks/webhook-events-and-payloads.md
index d7411f9b56..b74c7b15d0 100644
--- a/translations/es-ES/content/developers/webhooks-and-events/webhooks/webhook-events-and-payloads.md
+++ b/translations/es-ES/content/developers/webhooks-and-events/webhooks/webhook-events-and-payloads.md
@@ -1483,6 +1483,17 @@ Este evento ocurre cuando alguien activa una ejecución de flujo de trabajo en G
 
 - Las {% data variables.product.prodname_github_apps %} deben tener el permiso `contents` para recibir este webhook.
 
+### Objeto de carga útil del webhook
+
+| Clave              | Tipo     | Descripción                                                                                                                       |
+| ------------------ | -------- | --------------------------------------------------------------------------------------------------------------------------------- |
+| `inputs (entrada)` | `objeto` | Entradas al flujo de trabajo. Cada clave representa el nombre de la entrada mientras que su valor representa aquél de la entrada. |
+{% data reusables.webhooks.org_desc %}
+| `ref` | `string` | La ref de la rama desde la cual se ejecutó el flujo de trabajo. |
+{% data reusables.webhooks.repo_desc %}
+{% data reusables.webhooks.sender_desc %}
+| `workflow` | `string` | Ruta relativa al archivo de flujo de trabajo que lo contiene. |
+
 ### Ejemplo de carga útil del webhook
 
 {{ webhookPayloadsForCurrentVersion.workflow_dispatch }}
diff --git a/translations/es-ES/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/about-using-visual-studio-code-with-github-classroom.md b/translations/es-ES/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/about-using-visual-studio-code-with-github-classroom.md
index 43d3f27020..316e4d54c3 100644
--- a/translations/es-ES/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/about-using-visual-studio-code-with-github-classroom.md
+++ b/translations/es-ES/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/about-using-visual-studio-code-with-github-classroom.md
@@ -1,7 +1,7 @@
 ---
 title: Acerca de utilizar visual Studio Code con GitHub Classroom
 shortTitle: Aceca de utilizar Visual Studio Code
-intro: 'You can configure {% data variables.product.prodname_vscode %} as the preferred editor for assignments in {% data variables.product.prodname_classroom %}.'
+intro: 'Puedes configurar {% data variables.product.prodname_vscode %} como el editor preferido para las tareas de {% data variables.product.prodname_classroom %}.'
 versions:
   fpt: '*'
 redirect_from:
@@ -10,30 +10,30 @@ redirect_from:
 
 ## Acerca de {% data variables.product.prodname_vscode %}
 
-{% data variables.product.prodname_vscode %} is a lightweight but powerful source code editor which runs on your desktop and is available for Windows, macOS and Linux. With the [GitHub Classroom extension for {% data variables.product.prodname_vscode_shortname %}](https://aka.ms/classroom-vscode-ext), students can easily browse, edit, submit, collaborate, and test their Classroom Assignments. Para obtener más información sobre los IDe y {% data variables.product.prodname_classroom %}, consulta la sección "[Integrar {% data variables.product.prodname_classroom %} con un IDE](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/integrate-github-classroom-with-an-ide)".
+{% data variables.product.prodname_vscode %} es un editor de código fuente ligero pero poderoso, el cual se ejecuta en tu escritorio y está disponible para Windows, macOS y Linux. Con la [extensión de GitHub Clasroom para {% data variables.product.prodname_vscode_shortname %}](https://aka.ms/classroom-vscode-ext), los alumnos pueden buscar, editar, enviar, colaborar y probar sus tareas de las aulas fácilmente. Para obtener más información sobre los IDe y {% data variables.product.prodname_classroom %}, consulta la sección "[Integrar {% data variables.product.prodname_classroom %} con un IDE](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/integrate-github-classroom-with-an-ide)".
 
 ### El editor predilecto de tus alumnos
-The GitHub Classroom integration with {% data variables.product.prodname_vscode_shortname %} provides students with an extension pack which contains:
+La integración con Github Classroom con {% data variables.product.prodname_vscode_shortname %} proporciona a los estudiantes un paquete de extensiones, el cuál contiene:
 
 1. [La Extensión de GitHub Classroom](https://aka.ms/classroom-vscode-ext) con abstracciones personalizadas que hacen más fácil que los alumnos naveguen en el inicio.
 2. [La Extgensión de Visual Studio Live Share](https://marketplace.visualstudio.com/items?itemName=MS-vsliveshare.vsliveshare-pack) que se integra en una vista de alumnos para dar acceso fácil a los ayudantes para enseñar y a los compañeros de clase para ayudar y colaborar.
 3. [La Extensión de GitHub Pull Request](https://marketplace.visualstudio.com/items?itemName=GitHub.vscode-pull-request-github) que permite a los alumnos ver la retroalimentación de sus instructores dentro del editor.
 
-### How to launch the assignment in {% data variables.product.prodname_vscode_shortname %}
-When creating an assignment, {% data variables.product.prodname_vscode_shortname %} can be added as the preferred editor for an assignment. Para obtener más detalles, consulta la sección "[Integrar a {% data variables.product.prodname_classroom %} con un IDE](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/integrate-github-classroom-with-an-ide)".
+### Cómo lanzar la tarea en {% data variables.product.prodname_vscode_shortname %}
+Cuando creas una tarea, puedes agregar a {% data variables.product.prodname_vscode_shortname %} como el editor predeterminado para ella. Para obtener más detalles, consulta la sección "[Integrar a {% data variables.product.prodname_classroom %} con un IDE](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/integrate-github-classroom-with-an-ide)".
 
-This will include an "Open in {% data variables.product.prodname_vscode_shortname %}" badge in all student repositories. This badge handles installing {% data variables.product.prodname_vscode_shortname %}, the Classroom extension pack, and opening to the active assignment with one click.
+Esto incluirá una insignia de "Abierto en {% data variables.product.prodname_vscode_shortname %}" en todos los repositorios de los alumnos. Esta insignia maneja la instalación de {% data variables.product.prodname_vscode_shortname %}, el paquete de extensión del aula y la apertura para la tarea activa en un solo clic.
 
 {% note %}
 
-**Note:** The student must have Git installed on their computer to push code from {% data variables.product.prodname_vscode_shortname %} to their repository. This is not automatically installed when clicking the **Open in {% data variables.product.prodname_vscode_shortname %}** button. El alumno puede descargar Git desde [aquí](https://git-scm.com/downloads).
+**Nota:** El alumno debe tener Git instalado en su computadora para subir código desde {% data variables.product.prodname_vscode_shortname %} hacia su repositorio. Esto no se instala automáticamente al hacer clic en el botón **Abrir en {% data variables.product.prodname_vscode_shortname %}**. El alumno puede descargar Git desde [aquí](https://git-scm.com/downloads).
 
 {% endnote %}
 
 ### Cómo utilizar el paquete de extensión de GitHub Classroom
 La extensión de GitHub Classroom tiene dos componentes principales: la vista de 'Aulas' y la vista de 'Tarea Activa'.
 
-When the student launches the extension for the first time, they are automatically navigated to the Explorer tab in {% data variables.product.prodname_vscode_shortname %}, where they can see the "Active Assignment" view alongside the tree-view of files in the repository.
+Cuando el alumno lanza la extensión por primera vez, se le lleva automáticamente a la pestaña del explorador en {% data variables.product.prodname_vscode_shortname %}, en donde podrán ver la vista de "Tarea activa" junto con la vista triple de los archivos en el repositorio.
 
 ![Vista de Tarea Activa de GitHub Classroom](/assets/images/help/classroom/vs-code-active-assignment.png)
 
diff --git a/translations/es-ES/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/integrate-github-classroom-with-an-ide.md b/translations/es-ES/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/integrate-github-classroom-with-an-ide.md
index 731d2acbb9..0e61e57eb7 100644
--- a/translations/es-ES/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/integrate-github-classroom-with-an-ide.md
+++ b/translations/es-ES/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/integrate-github-classroom-with-an-ide.md
@@ -1,7 +1,7 @@
 ---
-title: Integrar a GitHub Classroom con un IDE
-shortTitle: Integrar con un IDE
-intro: 'Puedes preconfigurar un ambiente de desarrollo integrado (IDE) compatible para las tareas que crees en {% data variables.product.prodname_classroom %}.'
+title: Integrate GitHub Classroom with an IDE
+shortTitle: Integrate with an IDE
+intro: 'You can preconfigure a supported integrated development environment (IDE) for assignments you create in {% data variables.product.prodname_classroom %}.'
 versions:
   fpt: '*'
 permissions: 'Organization owners who are admins for a classroom can integrate {% data variables.product.prodname_classroom %} with an IDE. {% data reusables.classroom.classroom-admins-link %}'
@@ -10,37 +10,36 @@ redirect_from:
   - /education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-online-ide
   - /education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/integrate-github-classroom-with-an-online-ide
 ---
+## About integration with an IDE
 
-## Acerca de la integración con un IDE
+{% data reusables.classroom.about-online-ides %} 
 
-{% data reusables.classroom.about-online-ides %}
+After a student accepts an assignment with an IDE, the README file in the student's assignment repository will contain a button to open the assignment in the IDE. The student can begin working immediately, and no additional configuration is necessary.
 
-Después de que un alumno acepta una tarea con un IDE, el archivo README en su repositorio de tareas contendrá un botón para abrir dicha tarea en el IDE. El alumno puede comenzar a trabajar de inmediato y no se requiere alguna configuración adicional.
+## Supported IDEs
 
-## IDE compatibles
+{% data variables.product.prodname_classroom %} supports the following IDEs. You can learn more about the student experience for each IDE.
 
-{% data variables.product.prodname_classroom %} es compatible con los siguientes IDE. Puedes aprender más sobre la experiencia del alumno para cada IDE.
-
-| IDE                                                       | Más información                                                                                                                                                                                                                                                   |
-|:--------------------------------------------------------- |:----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| IDE | More information |
+| :- | :- |
 | {% data variables.product.prodname_github_codespaces %} | "[Using {% data variables.product.prodname_github_codespaces %} with {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/using-github-codespaces-with-github-classroom)" |
-| Microsoft MakeCode Arcade                                 | "[Acerca de utilizar MakeCode Arcade con {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/about-using-makecode-arcade-with-github-classroom)"                                                                  |
-| {% data variables.product.prodname_vscode %}              | La [extensión de {% data variables.product.prodname_classroom %}](http://aka.ms/classroom-vscode-ext) en el Mercado de Visual Studio                                                                                                                              |
+| Microsoft MakeCode Arcade | "[About using MakeCode Arcade with {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/about-using-makecode-arcade-with-github-classroom)" |
+| {% data variables.product.prodname_vscode %} | [{% data variables.product.prodname_classroom %} extension](http://aka.ms/classroom-vscode-ext) in the Visual Studio Marketplace |
 
-Sabemos que las integraciones con IDE en la nube son importantes para tu aula y estamos trabajando para traerte más opciones.
+We know cloud IDE integrations are important to your classroom and are working to bring more options. 
 
-## Configurar un IDE para una tarea
+## Configuring an IDE for an assignment
 
-Puedes elegir el IDE que te gustaría utilizar para una tarea cuando la crees. Para aprender cómo crear una tarea nueva que utilice un IDE, consulta la sección "[Crear una tarea individual](/education/manage-coursework-with-github-classroom/create-an-individual-assignment)" o "[Crear una tarea de grupo](/education/manage-coursework-with-github-classroom/create-a-group-assignment)".
+You can choose the IDE you'd like to use for an assignment when you create an assignment. To learn how to create a new assignment that uses an IDE, see "[Create an individual assignment](/education/manage-coursework-with-github-classroom/create-an-individual-assignment)" or "[Create a group assignment](/education/manage-coursework-with-github-classroom/create-a-group-assignment)."
 
 ## Setting up an assignment in a new IDE
 
 The first time you configure an assignment using a different IDE, you must ensure that it is set up correctly.
 
-Unless you use {% data variables.product.prodname_github_codespaces %}, you must authorize the OAuth app for the IDE for your organization. En todos tus repositorios, otorga acceso de **lectura** a la app para metadatos, administración y código, y acceso de **escritura** para administración y código. Para obtener más información, consulta la sección "[Autorizar las Apps de OAuth](/github/authenticating-to-github/authorizing-oauth-apps)".
+Unless you use {% data variables.product.prodname_github_codespaces %}, you must authorize the OAuth app for the IDE for your organization. For all repositories, grant the app **read** access to metadata, administration, and code, and **write** access to administration and code. For more information, see "[Authorizing OAuth Apps](/github/authenticating-to-github/authorizing-oauth-apps)."
 
-{% data variables.product.prodname_github_codespaces %} does not require an OAuth app, but you need to enable {% data variables.product.prodname_github_codespaces %} for your organization to be able to configure an assignment with {% data variables.product.prodname_codespaces %}. Para obtener más información, consulta "[Usar {% data variables.product.prodname_github_codespaces %} con {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/using-github-codespaces-with-github-classroom#enabling-codespaces-for-your-organization)".
+{% data variables.product.prodname_github_codespaces %} does not require an OAuth app, but you need to enable {% data variables.product.prodname_github_codespaces %} for your organization to be able to configure an assignment with {% data variables.product.prodname_codespaces %}. For more information, see "[Using {% data variables.product.prodname_github_codespaces %} with {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/using-github-codespaces-with-github-classroom#enabling-codespaces-for-your-organization)."
 
-## Leer más
+## Further reading
 
-- "[Acerca de los archivos README](/github/creating-cloning-and-archiving-repositories/about-readmes)"
+- "[About READMEs](/github/creating-cloning-and-archiving-repositories/about-readmes)"
diff --git a/translations/es-ES/content/get-started/customizing-your-github-workflow/exploring-integrations/github-extensions-and-integrations.md b/translations/es-ES/content/get-started/customizing-your-github-workflow/exploring-integrations/github-extensions-and-integrations.md
index 89646e219b..6e9b9464af 100644
--- a/translations/es-ES/content/get-started/customizing-your-github-workflow/exploring-integrations/github-extensions-and-integrations.md
+++ b/translations/es-ES/content/get-started/customizing-your-github-workflow/exploring-integrations/github-extensions-and-integrations.md
@@ -14,7 +14,7 @@ shortTitle: Extensiones & integraciones
 
 ## Herramientas del editor
 
-You can connect to {% data variables.product.product_name %} repositories within third-party editor tools, such as Atom, Unity, and {% data variables.product.prodname_vs %}.
+Puedes conectarte a los repositorios de {% data variables.product.product_name %} con herramientas de editor de terceros, tales como Atom, Unity y {% data variables.product.prodname_vs %}.
 
 ### {% data variables.product.product_name %} para Atom
 
@@ -24,13 +24,13 @@ Con el {% data variables.product.product_name %} para la extensión de Atom, pue
 
 Con el {% data variables.product.product_name %} para la extensión del editor de Unity, puedes desarrollar en Unity, la plataforma de código abierto de desarrollo de juegos, y ver tu trabajo en {% data variables.product.product_name %}. Para obtener más información, consulta el [sitio](https://unity.github.com/) oficial de la extensión del editor de Unity o la [documentación](https://github.com/github-for-unity/Unity/tree/master/docs).
 
-### {% data variables.product.product_name %} for {% data variables.product.prodname_vs %}
+### {% data variables.product.product_name %} para {% data variables.product.prodname_vs %}
 
-With the {% data variables.product.product_name %} for {% data variables.product.prodname_vs %} extension, you can work in {% data variables.product.product_name %} repositories without leaving {% data variables.product.prodname_vs %}. For more information, see the official {% data variables.product.prodname_vs %} extension [site](https://visualstudio.github.com/) or [documentation](https://github.com/github/VisualStudio/tree/master/docs).
+Con la extensión de {% data variables.product.product_name %} para {% data variables.product.prodname_vs %}, puedes trabajar en los repositorios de {% data variables.product.product_name %} sin salir de {% data variables.product.prodname_vs %}. Para obtener más información, consulta el [sitio](https://visualstudio.github.com/) de la extensión oficial de {% data variables.product.prodname_vs %} o la [documentación](https://github.com/github/VisualStudio/tree/master/docs).
 
-### {% data variables.product.prodname_dotcom %} for {% data variables.product.prodname_vscode %}
+### {% data variables.product.prodname_dotcom %} para {% data variables.product.prodname_vscode %}
 
-With the {% data variables.product.prodname_dotcom %} for {% data variables.product.prodname_vscode %} extension, you can review and manage {% data variables.product.product_name %} pull requests in {% data variables.product.prodname_vscode_shortname %}. For more information, see the official {% data variables.product.prodname_vscode_shortname %} extension [site](https://vscode.github.com/) or [documentation](https://github.com/Microsoft/vscode-pull-request-github).
+Con la extensión de {% data variables.product.prodname_dotcom %} para {% data variables.product.prodname_vscode %}, puedes revisar y administrar las solicitudes de cambio de {% data variables.product.product_name %} en {% data variables.product.prodname_vscode_shortname %}. Para obtener más información, consulta el [sitio](https://vscode.github.com/) oficial de la extensión de {% data variables.product.prodname_vscode_shortname %} o la [documentación](https://github.com/Microsoft/vscode-pull-request-github).
 
 ## Herramientas de gestión de proyectos
 
@@ -46,12 +46,12 @@ Puedes integrar tu cuenta organizacional o personal en {% data variables.product
 
 ### Integración con Slack y con {% data variables.product.product_name %}
 
-The Slack + {% data variables.product.prodname_dotcom %} app lets you subscribe to your repositories or organizations and get realtime updates about issues, pull requests, commits, discussions, releases, deployment reviews and deployment statuses. You can also perform activities like opening and closing issues, and you can see detailed references to issues and pull requests without leaving Slack. The app will also ping you personally in Slack if you are mentioned as part of any {% data variables.product.prodname_dotcom %} notifications that you receive in your channels or personal chats.
+La app de Slack + {% data variables.product.prodname_dotcom %} permite que te suscribas a tus repositorios y organizaciones y obtengas actualizaciones en tiempo real sobre propuestas, solicitudes de cambio, debates, lanzamientos, revisiones de despliegues y estados de despliegue. También puedes lleva a cabo actividades como abrir y cerrar propuestas y puedes ver referencias detalladas de las propuestas y solicitudes de cambios sin salir de Slack. La app también te notificará personalmente en Slack si se te menciona como parte de cualquier notificación de {% data variables.product.prodname_dotcom %} que recibas en tus canales o chats personales.
 
-The Slack + {% data variables.product.prodname_dotcom %} app is also compatible with [Slack Enterprise Grid](https://slack.com/intl/en-in/help/articles/360000281563-Manage-apps-on-Enterprise-Grid). For more information, visit the [Slack + {% data variables.product.prodname_dotcom %} app](https://github.com/marketplace/slack-github) in the marketplace.
+La app de Slack + {% data variables.product.prodname_dotcom %} también es compatible con [Slack Enterprise Grid](https://slack.com/intl/en-in/help/articles/360000281563-Manage-apps-on-Enterprise-Grid). Para obtener más información, visita la [App de Slack + {% data variables.product.prodname_dotcom %}](https://github.com/marketplace/slack-github) en marketplace.
 
 ### Microsoft Teams y su integración con {% data variables.product.product_name %}
 
-The {% data variables.product.prodname_dotcom %} for Teams app lets you subscribe to your repositories or organizations and get realtime updates about issues, pull requests, commits, discussions, releases, deployment reviews and deployment statuses. You can also perform activities like opening and closing issues, commenting on your issues and pull requests, and you can see detailed references to issues and pull requests without leaving Microsoft Teams. The app will also ping you personally in Teams if you are mentioned as part of any {% data variables.product.prodname_dotcom %} notifications that you receive in your channels or personal chats.
+La app de {% data variables.product.prodname_dotcom %} para equipos te permite suscribirte a tus repositorios u organizaciones y obtener actualizaciones en tiempo real sobre propuestas, solicitudes de cambio, confirmaciones, debates, lanzamientos, revisiones de despliegue y estados de espliegue. También puedes realizar actividades como abrir y cerrar propuestas, comentar en tus propuestas y solicitudes de cambio y puedes ver referencias detalladas a las propuestas y solicitudes de cambio sin salir de Microsoft Teams. La app también te notificará personalmente en Teams si se te menciona como parte de cualquier notificación de {% data variables.product.prodname_dotcom %} que recibas en tus canales o chats personales.
 
-For more information, visit the [{% data variables.product.prodname_dotcom %} for Teams app](https://appsource.microsoft.com/en-us/product/office/WA200002077) in Microsoft AppSource.
+Para obtener más información, visita la [app de {% data variables.product.prodname_dotcom %} para equipos](https://appsource.microsoft.com/en-us/product/office/WA200002077) en Microsoft AppSource.
diff --git a/translations/es-ES/content/get-started/customizing-your-github-workflow/index.md b/translations/es-ES/content/get-started/customizing-your-github-workflow/index.md
index 508c9c5dda..27526e2992 100644
--- a/translations/es-ES/content/get-started/customizing-your-github-workflow/index.md
+++ b/translations/es-ES/content/get-started/customizing-your-github-workflow/index.md
@@ -1,6 +1,6 @@
 ---
 title: Personalizar tu flujo de trabajo de GitHub
-intro: 'Learn how you can customize your {% data variables.product.prodname_dotcom %} workflow with extensions, integrations, {% data variables.product.prodname_marketplace %}, and webhooks.'
+intro: 'Aprende cómo puedes personalizar tu flujo de trabajo de {% data variables.product.prodname_dotcom %} con extensiones, integraciones, {% data variables.product.prodname_marketplace %} y webhooks.'
 redirect_from:
   - /categories/customizing-your-github-workflow
   - /github/customizing-your-github-workflow
diff --git a/translations/es-ES/content/get-started/customizing-your-github-workflow/purchasing-and-installing-apps-in-github-marketplace/installing-an-app-in-your-personal-account.md b/translations/es-ES/content/get-started/customizing-your-github-workflow/purchasing-and-installing-apps-in-github-marketplace/installing-an-app-in-your-personal-account.md
index 62be27d2cc..72626a9862 100644
--- a/translations/es-ES/content/get-started/customizing-your-github-workflow/purchasing-and-installing-apps-in-github-marketplace/installing-an-app-in-your-personal-account.md
+++ b/translations/es-ES/content/get-started/customizing-your-github-workflow/purchasing-and-installing-apps-in-github-marketplace/installing-an-app-in-your-personal-account.md
@@ -8,7 +8,7 @@ redirect_from:
 versions:
   fpt: '*'
   ghec: '*'
-shortTitle: Install app personal account
+shortTitle: Instalar app en cuenta personal
 ---
 
 {% data reusables.marketplace.marketplace-apps-only %}
diff --git a/translations/es-ES/content/get-started/exploring-projects-on-github/finding-ways-to-contribute-to-open-source-on-github.md b/translations/es-ES/content/get-started/exploring-projects-on-github/finding-ways-to-contribute-to-open-source-on-github.md
index d8eb59c3f6..366be88f9a 100644
--- a/translations/es-ES/content/get-started/exploring-projects-on-github/finding-ways-to-contribute-to-open-source-on-github.md
+++ b/translations/es-ES/content/get-started/exploring-projects-on-github/finding-ways-to-contribute-to-open-source-on-github.md
@@ -25,7 +25,7 @@ Si hay un tema en particular que te interese, visita `github.com/topics/<topic>`
 
 Si has tenido actividad en {% data variables.product.product_location %} recientemente, puedes encontrar recomendaciones personalizadas para proyectos e informes de problemas iniciales que se basen en tus contribuciones, estrellas y otras actividades previas en [Explore](https://github.com/explore). También puedes registrarte para el boletín Explore para recibir correos electrónicos sobre las oportunidades disponibles para colaborar con {% data variables.product.product_name %} de acuerdo a tus intereses. Para registrarte, consulta [Boletín Explore por correo](https://github.com/explore/subscribe).
 
-Keep up with recent activity from repositories you watch, as well as people and organizations you follow, with your personal dashboard. Para obtener más información, consulta "[Acerca de tu tablero personal](/articles/about-your-personal-dashboard)".
+Mantente al tanto con la actividad reciente de los repositorios que observas, así como de las personas y organizaciones que sigues con tu tablero personal. Para obtener más información, consulta "[Acerca de tu tablero personal](/articles/about-your-personal-dashboard)".
 
 {% data reusables.support.ask-and-answer-forum %}
 
diff --git a/translations/es-ES/content/get-started/getting-started-with-git/associating-text-editors-with-git.md b/translations/es-ES/content/get-started/getting-started-with-git/associating-text-editors-with-git.md
index 36199b32ee..eb20fa32a6 100644
--- a/translations/es-ES/content/get-started/getting-started-with-git/associating-text-editors-with-git.md
+++ b/translations/es-ES/content/get-started/getting-started-with-git/associating-text-editors-with-git.md
@@ -28,7 +28,7 @@ shortTitle: Editores de texto asociados
   $ git config --global core.editor "atom --wait"
   ```
 
-## Using {% data variables.product.prodname_vscode %} as your editor
+## Utilizar {% data variables.product.prodname_vscode %} como tu editor
 
 1. Omstañar [{% data variables.product.prodname_vscode %}](https://code.visualstudio.com/) ({% data variables.product.prodname_vscode_shortname %}). Para obtener más información, consulta la sección "[Configurar {% data variables.product.prodname_vscode_shortname %}](https://code.visualstudio.com/Docs/setup/setup-overview)" en la documentación de {% data variables.product.prodname_vscode_shortname %}.
 {% data reusables.command_line.open_the_multi_os_terminal %}
@@ -68,7 +68,7 @@ shortTitle: Editores de texto asociados
   $ git config --global core.editor "atom --wait"
   ```
 
-## Using {% data variables.product.prodname_vscode %} as your editor
+## Utilizar {% data variables.product.prodname_vscode %} como tu editor
 
 1. Omstañar [{% data variables.product.prodname_vscode %}](https://code.visualstudio.com/) ({% data variables.product.prodname_vscode_shortname %}). Para obtener más información, consulta la sección "[Configurar {% data variables.product.prodname_vscode_shortname %}](https://code.visualstudio.com/Docs/setup/setup-overview)" en la documentación de {% data variables.product.prodname_vscode_shortname %}.
 {% data reusables.command_line.open_the_multi_os_terminal %}
@@ -107,7 +107,7 @@ shortTitle: Editores de texto asociados
   $ git config --global core.editor "atom --wait"
   ```
 
-## Using {% data variables.product.prodname_vscode %} as your editor
+## Utilizar {% data variables.product.prodname_vscode %} como tu editor
 
 1. Omstañar [{% data variables.product.prodname_vscode %}](https://code.visualstudio.com/) ({% data variables.product.prodname_vscode_shortname %}). Para obtener más información, consulta la sección "[Configurar {% data variables.product.prodname_vscode_shortname %}](https://code.visualstudio.com/Docs/setup/setup-overview)" en la documentación de {% data variables.product.prodname_vscode_shortname %}.
 {% data reusables.command_line.open_the_multi_os_terminal %}
diff --git a/translations/es-ES/content/get-started/importing-your-projects-to-github/importing-source-code-to-github/source-code-migration-tools.md b/translations/es-ES/content/get-started/importing-your-projects-to-github/importing-source-code-to-github/source-code-migration-tools.md
index f2d670b9dd..80be6517ff 100644
--- a/translations/es-ES/content/get-started/importing-your-projects-to-github/importing-source-code-to-github/source-code-migration-tools.md
+++ b/translations/es-ES/content/get-started/importing-your-projects-to-github/importing-source-code-to-github/source-code-migration-tools.md
@@ -22,7 +22,7 @@ Te recomendamos utilizar el [Importador de GitHub](/articles/about-github-import
 
 ## Importar desde Subversion
 
-En un entorno normal de Subversion, se almacenan varios proyectos en un único repositorio raíz. On GitHub, each of these projects will usually map to a separate Git repository for a personal account or organization. Sugerimos importar cada parte de tu repositorio de Subversion a un repositorio de GitHub separado si:
+En un entorno normal de Subversion, se almacenan varios proyectos en un único repositorio raíz. En GitHub, cada uno de estos proyectos se mapearán a menudo en un repositorio separado de Git para una cuenta personal u organización. Sugerimos importar cada parte de tu repositorio de Subversion a un repositorio de GitHub separado si:
 
 * Los colaboradores necesitan revisar o confirmar esa parte del proyecto de forma separada desde las otras partes
 * Deseas que distintas partes tengan sus propios permisos de acceso
diff --git a/translations/es-ES/content/get-started/importing-your-projects-to-github/working-with-subversion-on-github/subversion-properties-supported-by-github.md b/translations/es-ES/content/get-started/importing-your-projects-to-github/working-with-subversion-on-github/subversion-properties-supported-by-github.md
index 401a48bdc3..ebcdea48d8 100644
--- a/translations/es-ES/content/get-started/importing-your-projects-to-github/working-with-subversion-on-github/subversion-properties-supported-by-github.md
+++ b/translations/es-ES/content/get-started/importing-your-projects-to-github/working-with-subversion-on-github/subversion-properties-supported-by-github.md
@@ -12,15 +12,15 @@ versions:
 shortTitle: Propiedades compatibles con GitHub
 ---
 
-## Executable files (`svn:executable`)
+## Archivos ejecutables (`svn:executable`)
 
 Convertimos propiedades `svn:executable` al actualizar el modo archivo directamente antes de agregarlo al repositorio de Git.
 
-## MIME types (`svn:mime-type`)
+## Tipos de MIME (`svn:mime-type`)
 
 {% data variables.product.product_name %} internalmente rastrea las propiedades mime-type de los archivos y las confirmaciones que los agregaron.
 
-## Ignoring unversioned items (`svn:ignore`)
+## Ignorar los elementos sin versión (`svn:ignore`)
 
 Si has configurado que los archivos y los directorios se ignoren en Subversion, {% data variables.product.product_name %} los rastrearemos de manera interna. Los archivos ignorados por los clientes de Subversion son completamente distintos a las entradas en un archivo *.gitignore*.
 
diff --git a/translations/es-ES/content/get-started/onboarding/getting-started-with-github-enterprise-cloud.md b/translations/es-ES/content/get-started/onboarding/getting-started-with-github-enterprise-cloud.md
index 109eb89028..7935a24b28 100644
--- a/translations/es-ES/content/get-started/onboarding/getting-started-with-github-enterprise-cloud.md
+++ b/translations/es-ES/content/get-started/onboarding/getting-started-with-github-enterprise-cloud.md
@@ -56,21 +56,23 @@ Your organization's billing settings page allows you to manage settings like you
 Only organization members with the *owner* or *billing manager* role can access or change billing settings for your organization. A billing manager is a user who manages the billing settings for your organization and does not use a paid license in your organization's subscription. For more information on adding a billing manager to your organization, see "[Adding a billing manager to your organization](/organizations/managing-peoples-access-to-your-organization-with-roles/adding-a-billing-manager-to-your-organization)."
 
 ### Setting up an enterprise account with {% data variables.product.prodname_ghe_cloud %}
- {% note %}
-
-To get an enterprise account created for you, contact [{% data variables.product.prodname_dotcom %}'s Sales team](https://enterprise.github.com/contact).
-
- {% endnote %}
 
 #### 1. About enterprise accounts
 
 An enterprise account allows you to centrally manage policy and settings for multiple {% data variables.product.prodname_dotcom %} organizations, including member access, billing and usage and security. For more information, see "[About enterprise accounts](/enterprise-cloud@latest/admin/overview/about-enterprise-accounts)."
-#### 2. Adding organizations to your enterprise account
+
+#### 2. Creating an enterpise account
+
+ {% data variables.product.prodname_ghe_cloud %} customers paying by invoice can create an enterprise account directly through {% data variables.product.prodname_dotcom %}. For more information, see "[Creating an enterprise account](/enterprise-cloud@latest/admin/overview/creating-an-enterprise-account)." 
+ 
+ {% data variables.product.prodname_ghe_cloud %} customers not currently paying by invoice can contact [{% data variables.product.prodname_dotcom %}'s Sales team](https://enterprise.github.com/contact) to create an enterprise account for you.
+
+#### 3. Adding organizations to your enterprise account
 
 You can create new organizations to manage within your enterprise account. For more information, see "[Adding organizations to your enterprise](/enterprise-cloud@latest/admin/user-management/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise)."
 
 Contact your {% data variables.product.prodname_dotcom %} sales account representative if you want to transfer an existing organization to your enterprise account.
-#### 3. Viewing the subscription and usage for your enterprise account
+#### 4. Viewing the subscription and usage for your enterprise account
 You can view your current subscription, license usage, invoices, payment history, and other billing information for your enterprise account at any time. Both enterprise owners and billing managers can access and manage billing settings for enterprise accounts. For more information, see  "[Viewing the subscription and usage for your enterprise account](/enterprise-cloud@latest/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account)."
 
 ## Part 3: Managing your organization or enterprise members and teams with {% data variables.product.prodname_ghe_cloud %}
diff --git a/translations/es-ES/content/get-started/onboarding/getting-started-with-github-enterprise-server.md b/translations/es-ES/content/get-started/onboarding/getting-started-with-github-enterprise-server.md
index cf17658a3d..94448376f6 100644
--- a/translations/es-ES/content/get-started/onboarding/getting-started-with-github-enterprise-server.md
+++ b/translations/es-ES/content/get-started/onboarding/getting-started-with-github-enterprise-server.md
@@ -67,12 +67,12 @@ Como propietario empresarial o administrador, puedes administrar los ajustes a n
 ## Parte 3: Compilar de forma segura
 Para aumentar la seguridad de {% data variables.product.product_location %}, puedes configurar la autenticación para los miembros empresariales, utilizar herramientas y registro en bitácoras de auditoría para permanecer en cumplimiento, configurar las características de seguridad y análisis para tus organizaciones y, opcionalmente, habilitar la {% data variables.product.prodname_GH_advanced_security %}.
 ### 1. Autenticar a los miembros empresariales
-You can use {% data variables.product.product_name %}'s built-in authentication method, or you can choose between an external authentication provider, such as CAS, LDAP, or SAML, to integrate your existing accounts and centrally manage user access to {% data variables.product.product_location %}. For more information, see "[About authentication for your enterprise](/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise)."
+Puedes utilizar el método de autenticación integrado de {% data variables.product.product_name %} o puedes elegir entre un proveedor de autenticación externo, tal como CAS, LDAP o SAML, para integrar tus cuentas existentes y administrar centralmente el acceso de los usuarios a {% data variables.product.product_location %}. Para obtener más información, consulta la sección "[Acerca de la autenticación para tu empresa](/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise)".
 
 También puedes requerir la autenticación bifactorial para cada una de tus organizaciones. Para obtener más información, consulta la sección "[Requerir la autenticación bifactorial en una organización](/admin/user-management/managing-organizations-in-your-enterprise/requiring-two-factor-authentication-for-an-organization)".
 
 ### 2. Mantenerse en cumplimiento
-Puedes implementar las verificaciones de estado requeridas y confirmar las verificaciones para hacer cumplir los estándares de cumplimiento de tu organización y automatizar los flujos de trabajo de cumplimiento. También puedes utilizar la bitácora de auditoría de tu organización para revisar las acciones que realiza tu equipo. For more information, see "[Enforcing policy with pre-receive hooks](/admin/policies/enforcing-policy-with-pre-receive-hooks)" and "[About the audit log for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/about-the-audit-log-for-your-enterprise)."
+Puedes implementar las verificaciones de estado requeridas y confirmar las verificaciones para hacer cumplir los estándares de cumplimiento de tu organización y automatizar los flujos de trabajo de cumplimiento. También puedes utilizar la bitácora de auditoría de tu organización para revisar las acciones que realiza tu equipo. Para obtener más información, consulta las secciones "[requerir una política con ganchos de pre-recepción](/admin/policies/enforcing-policy-with-pre-receive-hooks)" y "[Acerca de la bitácora de auditoría para tu empresa](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/about-the-audit-log-for-your-enterprise)".
 
 {% ifversion ghes %}
 ### 3. Configurar las características de seguridad para tus organizaciones
diff --git a/translations/es-ES/content/get-started/onboarding/getting-started-with-your-github-account.md b/translations/es-ES/content/get-started/onboarding/getting-started-with-your-github-account.md
index a3f04f886d..ddd77ab1af 100644
--- a/translations/es-ES/content/get-started/onboarding/getting-started-with-your-github-account.md
+++ b/translations/es-ES/content/get-started/onboarding/getting-started-with-your-github-account.md
@@ -75,7 +75,7 @@ Para obtener más información sobre cómo autenticarte en {% data variables.pro
 | ---------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
 | Navega a {% data variables.product.prodname_dotcom_the_website %}                                                                            | Si no necesitas trabajar con archivos localmente, {% data variables.product.product_name %} te permite completar la mayoría de las acciones relacionadas con Git en el buscador, desde crear y bifurcar repositorios hasta editar archivos y abrir solicitudes de cambios.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | Este método es útil si quieres tener una interfaz virtual y necesitas realizar cambios rápidos y simples que no requieran que trabajes localmente.                                                                                                                                                                             |
 | {% data variables.product.prodname_desktop %}                                                                                                  | {% data variables.product.prodname_desktop %} se extiende y simplifica tu flujo de trabajo {% data variables.product.prodname_dotcom_the_website %}, usando una interfaz visual en lugar de comandos de texto en la línea de comandos. Para obtener más información sobre cómo iniciar con {% data variables.product.prodname_desktop %}, consulta la sección "[Iniciar con {% data variables.product.prodname_desktop %}](/desktop/installing-and-configuring-github-desktop/overview/getting-started-with-github-desktop)".                                                                                                                                                                                                                                                                                                                                                                                                         | Este método es le mejor si necesitas o quieres trabajar con archivos localmente, pero prefieres utilizar una interfaz visual para utilizar Git e interactuar con {% data variables.product.product_name %}.                                                                                                                    |
-| IDE o editor de texto                                                                                                                          | You can set a default text editor, like [Atom](https://atom.io/) or [{% data variables.product.prodname_vscode %}](https://code.visualstudio.com/) to open and edit your files with Git, use extensions, and view the project structure. Para obtener más información, consulta la sección "[Asociar los editores de texto con Git](/github/using-git/associating-text-editors-with-git)".                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | Es conveniente si estás trabajando con archivos y proyectos más complejos y quieres todo en un solo lugar, ya que los editores o IDE a menudo te permiten acceder directamente a la línea de comandos en el editor.                                                                                                            |
+| IDE o editor de texto                                                                                                                          | Puedes configurar un editor de texto predeterminado, como [Atom](https://atom.io/) o [{% data variables.product.prodname_vscode %}](https://code.visualstudio.com/) para abrir y editar tus archivos con Git, utilizar extensiones y ver la estructura del proyecto. Para obtener más información, consulta la sección "[Asociar los editores de texto con Git](/github/using-git/associating-text-editors-with-git)".                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | Es conveniente si estás trabajando con archivos y proyectos más complejos y quieres todo en un solo lugar, ya que los editores o IDE a menudo te permiten acceder directamente a la línea de comandos en el editor.                                                                                                            |
 | Línea de comandos, con o sin {% data variables.product.prodname_cli %}                                                                         | Para la mayoría de los controles granulares y personalización de cómo utilizas Git e interactúas con {% data variables.product.product_name %}, puedes utilizar la línea de comandos. Para obtener más información sobre cómo utilizar los comandos de Git, consulta la sección "[Hoja de comandos de Git](/github/getting-started-with-github/quickstart/git-cheatsheet)".<br/><br/> El {% data variables.product.prodname_cli %} es una herramienta de línea de comandos por separado que puedes instalar, la cual agrega solicitudes de cambio, propuestas, {% data variables.product.prodname_actions %} y otras características de {% data variables.product.prodname_dotcom %} a tu terminal para que puedas hacer todo tu trabajo desde un solo lugar. Para obtener más información, consulta la sección "[{% data variables.product.prodname_cli %}](/github/getting-started-with-github/using-github/github-cli)". | Esto es lo más conveniente si ya estás trabajando desde la línea de comandos, lo cual te permite evitar cambiar de contexto o si estás más cómodo utilizando la línea de comandos.                                                                                                                                             |
 | API de {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} | {% data variables.product.prodname_dotcom %} Tiene una API de REST y una de GraphQL que puedes utilizar para interactuar con {% data variables.product.product_name %}. Para obtener más información, consulta la sección "[Comenzar con la API](/github/extending-github/getting-started-with-the-api)".                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | La API de {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} tendrá la mayor utilidad si quisieras automatizar tareas comunes, respaldar tus datos o crear integraciones que se extiendan a {% data variables.product.prodname_dotcom %}. |
 ### 4. Escribir en {% data variables.product.product_name %}
diff --git a/translations/es-ES/content/get-started/privacy-on-github/about-githubs-use-of-your-data.md b/translations/es-ES/content/get-started/privacy-on-github/about-githubs-use-of-your-data.md
index 910070485f..eb9be2d519 100644
--- a/translations/es-ES/content/get-started/privacy-on-github/about-githubs-use-of-your-data.md
+++ b/translations/es-ES/content/get-started/privacy-on-github/about-githubs-use-of-your-data.md
@@ -16,9 +16,9 @@ shortTitle: Cómo utiliza tus datos GitHub
 
 ## Acerca de como {% data variables.product.product_name %} utiliza tus datos
 
-{% data variables.product.product_name %} agrega metadatos y analiza patrones de contenidos con el fin de suministrar información generalizada dentro del producto. It uses data from public repositories, and also uses metadata and aggregate data from private repositories when a repository's owner has chosen to share the data with {% data variables.product.product_name %} by enabling the dependency graph. If you enable the dependency graph for a private repository, then {% data variables.product.product_name %} will perform read-only analysis of that specific private repository.
+{% data variables.product.product_name %} agrega metadatos y analiza patrones de contenidos con el fin de suministrar información generalizada dentro del producto. Este utiliza datos de repositorios públicos y también metadatos y datos agregados de repositorios privados cuando un propietario del repositorio eligió compartir los datos con {% data variables.product.product_name %} al habilitar la gráfica de dependencias. Si habilitas la gráfica de dependencias para un repositorio privado, entonces {% data variables.product.product_name %} llevará acabo un análisis de solo lectura de ese repositorio privado específico.
 
-If you enable data use for a private repository, we will continue to treat your private data, source code, or trade secrets as confidential and private consistent with our [Terms of Service](/free-pro-team@latest/github/site-policy/github-terms-of-service). La información que obtenemos viene solo de los datos agregados. Para obtener más información, consulta la sección "[Administrar la configuración de uso de datos para tu repositorio privado](/get-started/privacy-on-github/managing-data-use-settings-for-your-private-repository)".
+Si habilitas el uso de datos para un repositorio privado, seguiremos tratando tus datos privados, código fuente o intercambiando secretos como confidenciales y privados en consistencia con nuestros [Términos de Servicio](/free-pro-team@latest/github/site-policy/github-terms-of-service). La información que obtenemos viene solo de los datos agregados. Para obtener más información, consulta la sección "[Administrar la configuración de uso de datos para tu repositorio privado](/get-started/privacy-on-github/managing-data-use-settings-for-your-private-repository)".
 
 {% data reusables.repositories.about-github-archive-program %} Para obtener más información, consulta la sección "[Acerca de archivar contenido y datos en {% data variables.product.prodname_dotcom %}](/github/creating-cloning-and-archiving-repositories/about-archiving-content-and-data-on-github#about-the-github-archive-program)".
 
diff --git a/translations/es-ES/content/get-started/privacy-on-github/managing-data-use-settings-for-your-private-repository.md b/translations/es-ES/content/get-started/privacy-on-github/managing-data-use-settings-for-your-private-repository.md
index 478d57479d..ad4b904a22 100644
--- a/translations/es-ES/content/get-started/privacy-on-github/managing-data-use-settings-for-your-private-repository.md
+++ b/translations/es-ES/content/get-started/privacy-on-github/managing-data-use-settings-for-your-private-repository.md
@@ -20,18 +20,18 @@ shortTitle: Administrar el uso de datos para un repositorio privado
 You can control data use for your private repository with the security and analysis features.
 
 - Enable the dependency graph to allow read-only data analysis on your repository.
-- Disable the dependency graph to block read-only data analysis of your repository.
+- Inhabilita la gráfica de dependencias para bloquear el análisis de datos de solo lectura de tu repositorio.
 
-Cuando habilitas el uso de datos para tu repositorio privado, podrás acceder a la gráfica de dependencias, en donde puedes rastrear las dependencias de tus repositorios y recibir las {% data variables.product.prodname_dependabot_alerts %} cuando {% data variables.product.product_name %} detecte las dependencias vulnerables. For more information, see "[About {% data variables.product.prodname_dependabot_alerts %}](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies#dependabot-alerts-for-vulnerable-dependencies)."
+Cuando habilitas el uso de datos para tu repositorio privado, podrás acceder a la gráfica de dependencias, en donde puedes rastrear las dependencias de tus repositorios y recibir las {% data variables.product.prodname_dependabot_alerts %} cuando {% data variables.product.product_name %} detecte las dependencias vulnerables. Para obtener más información, consulta la sección "[Acerca de las {% data variables.product.prodname_dependabot_alerts %}](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies#dependabot-alerts-for-vulnerable-dependencies)".
 
 
 {% note %}
 
-**Note:** If you disable the dependency graph, {% data variables.product.prodname_dependabot_alerts %} and {% data variables.product.prodname_dependabot_security_updates %} are also disabled. Para obtener más información, consulta la sección "[Acerca de la gráfica de dependencias](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph)".
+**Nota:** Si inhabilitas la gráfica de dependencias, también se inhabilitarán las {% data variables.product.prodname_dependabot_alerts %} y las {% data variables.product.prodname_dependabot_security_updates %}. Para obtener más información, consulta la sección "[Acerca de la gráfica de dependencias](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph)".
 
 {% endnote %}
 
-## Enabling or disabling data use through security and analysis features
+## Habilitar o inhabilitar el uso de datos mediante las características de análisis y seguridad
 
 {% data reusables.security.security-and-analysis-features-enable-read-only %}
 
diff --git a/translations/es-ES/content/get-started/using-github/github-mobile.md b/translations/es-ES/content/get-started/using-github/github-mobile.md
index 8a7e665d07..96b5294e26 100644
--- a/translations/es-ES/content/get-started/using-github/github-mobile.md
+++ b/translations/es-ES/content/get-started/using-github/github-mobile.md
@@ -76,9 +76,9 @@ Si configuras el idioma en tu dispositivo para que sea uno de los compatibles, {
 
 {% data variables.product.prodname_mobile %} habilita automáticamente los Enlaces Universales para iOS. Cuando tocas en cualquier enlace de {% data variables.product.product_name %}, la URL destino se abrirá en {% data variables.product.prodname_mobile %} en vez de en Safari. Para obtener más información, consulta la sección[Enlaces Universales](https://developer.apple.com/ios/universal-links/) en el sitio para Desarrolladores de Apple.
 
-To disable Universal Links, long-press any {% data variables.product.product_name %} link, then tap **Open**. Every time you tap a {% data variables.product.product_name %} link in the future, the destination URL will open in Safari instead of {% data variables.product.prodname_mobile %}.
+Para inhabilitar los enlaces universales, deja presionado cualquier enlace de {% data variables.product.product_name %} y luego pulsa en **Abrir**. Cada vez que pulses un enlace de {% data variables.product.product_name %} en el futuro, la URL de destino se abrirá en Safari en vez de en {% data variables.product.prodname_mobile %}.
 
-To re-enable Universal Links, long-press any {% data variables.product.product_name %} link, then tap **Open in {% data variables.product.prodname_dotcom %}**.
+Para volver a habilitar los enlaces universales, deja pulsado cualquier enlace de {% data variables.product.product_name %} y luego pulsa en **Abrir en {% data variables.product.prodname_dotcom %}**.
 
 ## Compartir retroalimentación
 
diff --git a/translations/es-ES/content/get-started/using-github/keyboard-shortcuts.md b/translations/es-ES/content/get-started/using-github/keyboard-shortcuts.md
index cac7bd986d..a8a2111f3d 100644
--- a/translations/es-ES/content/get-started/using-github/keyboard-shortcuts.md
+++ b/translations/es-ES/content/get-started/using-github/keyboard-shortcuts.md
@@ -89,10 +89,12 @@ For more keyboard shortcuts, see the [CodeMirror documentation](https://codemirr
 |-----------|------------
 |<kbd>Command</kbd>+<kbd>B</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>B</kbd> (Windows/Linux) | Inserts Markdown formatting for bolding text
 |<kbd>Command</kbd>+<kbd>I</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>I</kbd> (Windows/Linux) | Inserts Markdown formatting for italicizing text{% ifversion fpt or ghae or ghes > 3.1 or ghec %}
-|<kbd>Command</kbd>+<kbd>E</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>E</kbd> (Windows/Linux) | Inserts Markdown formatting for code or a command within a line{% endif %}
-|<kbd>Command</kbd>+<kbd>K</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>K</kbd> (Windows/Linux) | Inserts Markdown formatting for creating a link
+|<kbd>Command</kbd>+<kbd>E</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>E</kbd> (Windows/Linux) | Inserts Markdown formatting for code or a command within a line{% endif %}{% ifversion fpt or ghae-issue-5434 or ghes > 3.1 or ghec %}
+|<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-issue-7103 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>Opt</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>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>Enter</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>Enter</kbd> (Windows/Linux) | Submits a comment
diff --git a/translations/es-ES/content/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax.md b/translations/es-ES/content/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax.md
index 6ca2cf3bf8..4a2d5955f7 100644
--- a/translations/es-ES/content/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax.md
+++ b/translations/es-ES/content/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax.md
@@ -15,7 +15,7 @@ shortTitle: Sintaxis de formato básica
 
 ## Encabezados
 
-Para crear un encabezado, agrega uno a seis símbolos <kbd>#</kbd> antes del encabezado del texto. The number of <kbd>#</kbd> you use will determine the size of the heading.
+Para crear un encabezado, agrega uno a seis símbolos <kbd>#</kbd> antes del encabezado del texto. La cantidad de <kbd>#</kbd> que utilices determinará el tamaño del encabezado.
 
 ```markdown
 # El encabezado más largo
@@ -25,27 +25,27 @@ Para crear un encabezado, agrega uno a seis símbolos <kbd>#</kbd> antes del enc
 
 ![Encabezados H1, H2 y H6 representados](/assets/images/help/writing/headings-rendered.png)
 
-When you use two or more headings, GitHub automatically generates a table of contents which you can access by clicking {% octicon "list-unordered" aria-label="The unordered list icon" %} within the file header. Each heading title is listed in the table of contents and you can click a title to navigate to the selected section.
+Cuando usas dos o más encabezados, GitHub generará una tabla de contenido automáticamente, a la cual podrás acceder si haces clic en {% octicon "list-unordered" aria-label="The unordered list icon" %} dentro del encabezado del archivo. Cada título de encabezado se lista en la tabla de contenido y puedes hacer clic en un título para navegar a la sección seleccionada.
 
-![Screenshot highlighting the table of contents icon](/assets/images/help/repository/headings_toc.png)
+![Captura de pantalla resaltando el icono de la tabla de contenido](/assets/images/help/repository/headings_toc.png)
 
 ## Estilo de texto
 
-You can indicate emphasis with bold, italic, strikethrough, subscript, or superscript text in comment fields and `.md` files.
+Puedes indicar un énfasis con texto en negritas, itálicas, tachado, subíndice o superíndice en los campos de comentario y archivos `.md`.
 
-| Estilo                       | Sintaxis                   | Atajo del teclado                                                                     | Ejemplo                                             | Resultado                                     |
-| ---------------------------- | -------------------------- | ------------------------------------------------------------------------------------- | --------------------------------------------------- | --------------------------------------------- |
-| Negrita                      | `** **` o `__ __`          | <kbd>Command</kbd>+<kbd>B</kbd> (Mac) or <kbd>Ctrl</kbd>+<kbd>B</kbd> (Windows/Linux) | `**Este texto está en negrita**`                    | **Este texto está en negrita**                |
-| Cursiva                      | `* *` o `_ _`              | <kbd>Command</kbd>+<kbd>I</kbd> (Mac) or <kbd>Ctrl</kbd>+<kbd>I</kbd> (Windows/Linux) | `*Este texto está en cursiva*`                      | *Este texto está en cursiva*                  |
-| Tachado                      | `~~ ~~`                    |                                                                                       | `~~Este texto está equivocado~~`                    | ~~Este texto está equivocado~~                |
-| Cursiva en negrita y anidada | `** **` y `_ _`            |                                                                                       | `**Este texto es _extremadamente_ importante**`     | **Este texto es _extremadamente_ importante** |
-| Todo en negrita y cursiva    | `*** ***`                  |                                                                                       | `***Todo este texto es importante***`               | ***Todo este texto es importante***           |
-| Subscript                    | `<sub> </sub>` |                                                                                       | `<sub>This is a subscript text</sub>`   | <sub>This is a subscript text</sub>           |
-| Superscript                  | `<sup> </sup>` |                                                                                       | `<sup>This is a superscript text</sup>` | <sup>This is a superscript text</sup>         |
+| Estilo                       | Sintaxis                   | Atajo del teclado                                                                    | Ejemplo                                                  | Resultado                                     |
+| ---------------------------- | -------------------------- | ------------------------------------------------------------------------------------ | -------------------------------------------------------- | --------------------------------------------- |
+| Negrita                      | `** **` o `__ __`          | <kbd>Command</kbd>+<kbd>B</kbd> (Mac) o <kbd>Ctrl</kbd>+<kbd>B</kbd> (Windows/Linux) | `**Este texto está en negrita**`                         | **Este texto está en negrita**                |
+| Cursiva                      | `* *` o `_ _`              | <kbd>Command</kbd>+<kbd>I</kbd> (Mac) o <kbd>Ctrl</kbd>+<kbd>I</kbd> (Windows/Linux) | `*Este texto está en cursiva*`                           | *Este texto está en cursiva*                  |
+| Tachado                      | `~~ ~~`                    |                                                                                      | `~~Este texto está equivocado~~`                         | ~~Este texto está equivocado~~                |
+| Cursiva en negrita y anidada | `** **` y `_ _`            |                                                                                      | `**Este texto es _extremadamente_ importante**`          | **Este texto es _extremadamente_ importante** |
+| Todo en negrita y cursiva    | `*** ***`                  |                                                                                      | `***Todo este texto es importante***`                    | ***Todo este texto es importante***           |
+| Subíndice                    | `<sub> </sub>` |                                                                                      | `<sub>Este es un texto en subíndice</sub>`   | <sub>Este es un texto en subíndice</sub>      |
+| Superíndice                  | `<sup> </sup>` |                                                                                      | `<sup>Este es un texto en superíndice</sup>` | <sup>Este es un texto en superíndice</sup>    |
 
 ## Cita de texto
 
-You can quote text with a <kbd>></kbd>.
+Puedes citar texto con un <kbd>></kbd>.
 
 ```markdown
 Texto que no es una cita
@@ -57,13 +57,13 @@ Texto que no es una cita
 
 {% tip %}
 
-**Tip:** When viewing a conversation, you can automatically quote text in a comment by highlighting the text, then typing <kbd>R</kbd>. Puedes citar un comentario completo al hacer clic en {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, y luego en **Quote reply** (Citar respuesta). Para obtener más información sobre atajo del teclado, consulta "[Atajos del teclado](/articles/keyboard-shortcuts/)".
+**Tip:** Cuando ves una conversación, puedes citar texto automáticamente en un comentario si lo resaltas y luego tecleas <kbd>R</kbd>. Puedes citar un comentario completo al hacer clic en {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, y luego en **Quote reply** (Citar respuesta). Para obtener más información sobre atajo del teclado, consulta "[Atajos del teclado](/articles/keyboard-shortcuts/)".
 
 {% endtip %}
 
 ## Código de cita
 
-Puedes indicar un código o un comando dentro de un enunciado con comillas simples. The text within the backticks will not be formatted.{% ifversion fpt or ghae or ghes > 3.1 or ghec %} You can also press the <kbd>Command</kbd>+<kbd>E</kbd> (Mac) or <kbd>Ctrl</kbd>+<kbd>E</kbd> (Windows/Linux) keyboard shortcut to insert the backticks for a code block within a line of Markdown.{% endif %}
+Puedes indicar un código o un comando dentro de un enunciado con comillas simples. El texto dentro de las comillas simples no se formateará.{% ifversion fpt or ghae or ghes > 3.1 or ghec %} También puedes presionar el atajo de teclado <kbd>Command</kbd>+<kbd>E</kbd> (Mac) o <kbd>Ctrl</kbd>+<kbd>E</kbd> (Windows/Linux) para insertar las comillas simples para un bloque de código dentro de una línea de lenguaje de marcado.{% endif %}
 
 ```markdown
 Usa `git status` para enumerar todos los archivos nuevos o modificados que aún no han sido confirmados.
@@ -92,6 +92,8 @@ Para obtener más información, consulta "[Crear y resaltar bloques de código](
 
 Puedes crear un enlace en línea al encerrar el texto del enlace entre corchetes `[ ]`, y luego encerrar la URL entre paréntesis `( )`. {% ifversion fpt or ghae or ghes > 3.1 or ghec %}También puedes utilizar el atajo de teclado <kbd>Command</kbd>+<kbd>K</kbd> para crear un enlace.{% endif %}{% ifversion fpt or ghae-issue-5434 or ghes > 3.3 or ghec %} Cuando tengas texto seleccionado, puedes pegar una URL desde tu portapapeles para crear un enlace automáticamente desde la selección.{% endif %}
 
+{% ifversion fpt or ghae-issue-7103 or ghes > 3.5 or ghec %} También puedes crear un hipervínculo de lenguaje de marcado si resaltas el texto y utilizas el atajo de teclado <kbd>Command</kbd>+<kbd>V</kbd>. Si quieres reemplazar el texto con el enlace, utiliza el atajo de teclado <kbd>Command</kbd>+<kbd>Shift</kbd>+<kbd>V</kbd>.{% endif %}
+
 `Este sitio se construyó usando [GitHub Pages](https://pages.github.com/).`
 
 ![Enlace representado](/assets/images/help/writing/link-rendered.png)
@@ -112,7 +114,7 @@ Puedes crear un enlace en línea al encerrar el texto del enlace entre corchetes
 
 ## Imágenes
 
-You can display an image by adding <kbd>!</kbd> and wrapping the alt text in `[ ]`. Entonces encierra el enlace de la imagen entre paréntesis `()`.
+Puedes mostrar una imagen si agregas <kbd>!</kbd> y pones el texto alternativo entre `[ ]`. Entonces encierra el enlace de la imagen entre paréntesis `()`.
 
 `![Esta es una imagen](https://myoctocat.com/assets/images/base-octocat.svg)`
 
@@ -193,7 +195,7 @@ Para crear una lista anidada mediante el editor web en {% data variables.product
 
 {% tip %}
 
-**Note**: In the web-based editor, you can indent or dedent one or more lines of text by first highlighting the desired lines and then using <kbd>Tab</kbd> or <kbd>Shift</kbd>+<kbd>Tab</kbd> respectively.
+**Nota**: En el editor basado en web, puedes poner o quitar la sangría de una o más líneas de texto si primero las resaltas y luego presionas <kbd>Tab</kbd> o <kbd>Shift</kbd>+<kbd>Tab</kbd> según corresponda.
 
 {% endtip %}
 
@@ -228,7 +230,7 @@ Para conocer más ejemplos, consulta las [Especificaciones de formato Markdown d
 
 {% data reusables.repositories.task-list-markdown %}
 
-If a task list item description begins with a parenthesis, you'll need to escape it with <kbd>\\</kbd>:
+Si una descripción de elementos de lista comienza con un paréntesis, necesitarás escaparla con <kbd>\\</kbd>:
 
 `- [ ] \(Optional) Abre una propuesta de seguimiento`
 
@@ -236,11 +238,11 @@ Para obtener más información, consulta "[Acerca de las listas de tareas](/arti
 
 ## Mencionar personas y equipos
 
-Puedes mencionar a una persona o [equipo](/articles/setting-up-teams/) en {% data variables.product.product_name %} al escribir <kbd>@</kbd> más el nombre de usuario o el nombre del equipo. Esto activará una notificación y llamará su atención hacia la conversación. Las personas también recibirán una notificación si editas un comentario para mencionar su nombre de usuario o el nombre del equipo. For more information about notifications, see "[About notifications](/github/managing-subscriptions-and-notifications-on-github/about-notifications)."
+Puedes mencionar a una persona o [equipo](/articles/setting-up-teams/) en {% data variables.product.product_name %} al escribir <kbd>@</kbd> más el nombre de usuario o el nombre del equipo. Esto activará una notificación y llamará su atención hacia la conversación. Las personas también recibirán una notificación si editas un comentario para mencionar su nombre de usuario o el nombre del equipo. Para obtener más información sobre las notificaciones, consulta la sección "[Acerca de las notificaciones](/github/managing-subscriptions-and-notifications-on-github/about-notifications)".
 
 {% note %}
 
-**Note:** A person will only be notified about a mention if the person has read access to the repository and, if the repository is owned by an organization, the person is a member of the organization.
+**Nota:** Solo se le puede notificar a una persona sobre una mención si esta tiene acceso de lectura en el repositorio y si dicho repositorio le pertenece a una organización de la cuál esta persona sea miembro.
 
 {% endnote %}
 
@@ -325,7 +327,7 @@ La nota al pie se verá así:
 
 **Notae**: La posición de una nota al pie en tu archivo con lenguaje de marcado no influencia la nota al pie que se interpretará. Puedes escribir una nota al pie después de referenciarla y esta aún se interpretará en la parte inferior del archivo con lenguaje de marcado.
 
-Footnotes are not supported in wikis.
+No hay compatibilidad con notas al pie en los wikis.
 
 {% endtip %}
 {% endif %}
@@ -340,7 +342,7 @@ Puedes decirle a {% data variables.product.product_name %} que oculte el conteni
 
 ## Importar formato de Markdown
 
-You can tell {% data variables.product.product_name %} to ignore (or escape) Markdown formatting by using <kbd>\\</kbd> before the Markdown character.
+Puedes pedirle a {% data variables.product.product_name %} que ignore (o escape) el formato de lenguaje de marcado si utilizas <kbd>\\</kbd> antes del carácter de lenguaje de marcado.
 
 `Cambiemos el nombre de \*our-new-project\* a \*our-old-project\*.`
 
diff --git a/translations/es-ES/content/get-started/writing-on-github/working-with-advanced-formatting/creating-and-highlighting-code-blocks.md b/translations/es-ES/content/get-started/writing-on-github/working-with-advanced-formatting/creating-and-highlighting-code-blocks.md
index ebb4acc011..338bdfd8ea 100644
--- a/translations/es-ES/content/get-started/writing-on-github/working-with-advanced-formatting/creating-and-highlighting-code-blocks.md
+++ b/translations/es-ES/content/get-started/writing-on-github/working-with-advanced-formatting/creating-and-highlighting-code-blocks.md
@@ -70,7 +70,7 @@ Usamos [Lingüista](https://github.com/github/linguist) para realizar la detecci
 {% if mermaid %}
 ## Crear diagramas
 
-You can also use code blocks to create diagrams in Markdown. GitHub supports Mermaid, geoJSON, topoJSON, and ASCII STL syntax. Para obtener más información, consulta la sección "[Crear diagramas](/get-started/writing-on-github/working-with-advanced-formatting/creating-diagrams)".
+También puedes usar bloques de código para crear diagramas en el lenguaje de marcado. GitHub es compatible con la sintaxis de Mermaid, geoJSON, topoJSON y ASCII STL. Para obtener más información, consulta la sección "[Crear diagramas](/get-started/writing-on-github/working-with-advanced-formatting/creating-diagrams)".
 
 {% endif %}
 ## Leer más
diff --git a/translations/es-ES/content/get-started/writing-on-github/working-with-advanced-formatting/creating-diagrams.md b/translations/es-ES/content/get-started/writing-on-github/working-with-advanced-formatting/creating-diagrams.md
index 15392c84d0..d5bfa5fdf1 100644
--- a/translations/es-ES/content/get-started/writing-on-github/working-with-advanced-formatting/creating-diagrams.md
+++ b/translations/es-ES/content/get-started/writing-on-github/working-with-advanced-formatting/creating-diagrams.md
@@ -1,22 +1,22 @@
 ---
 title: Crear diagramas
-intro: Create diagrams to convey information through charts and graphs
+intro: Crear diagramas para transmitir información mediante tablas y gráficas
 versions:
   feature: mermaid
-shortTitle: Create diagrams
+shortTitle: Crear diagramas
 ---
 
-## About creating diagrams
+## Acerca de crear diagramas
 
-You can create diagrams in Markdown using three different syntaxes: mermaid, geoJSON and topoJSON, and ASCII STL.
+Puedes crear diagramas en lenguaje de marcado utilizando tres tipos de sintaxis diferentes: mermaid, geoJSON y topoJSON y ASCII STL.
 
-## Creating Mermaid diagrams
+## Crear diagramas de Mermaid
 
-Mermaid is a Markdown-inspired tool that renders text into diagrams. For example, Mermaid can render flow charts, sequence diagrams, pie charts and more. For more information, see the [Mermaid documentation](https://mermaid-js.github.io/mermaid/#/).
+Mermaid es una herramienta inspirada en el lenguaje de marcado que convierte el texto en diagramas. Por ejemplo, Mermaid puede representar diagramas de flujo, diagramas de secuencia, gráficas de pay y más. Para obtener más información, consulta la [documentación de Mermaid](https://mermaid-js.github.io/mermaid/#/).
 
-To create a Mermaid diagram, add Mermaid syntax inside a fenced code block with the `mermaid` language identifier. For more information about creating code blocks, see "[Creating and highlighting code blocks](/get-started/writing-on-github/working-with-advanced-formatting/creating-and-highlighting-code-blocks)."
+Para crear un diagrama de Mermaid, agrega la sintaxis de Mermaid dentro de un bloque de código cercado con el identificador de lenguaje `mermaid`. Para obtener más información sobre cómo crear bloques de código, consulta la sección "[Crear y resaltar bloques de código](/get-started/writing-on-github/working-with-advanced-formatting/creating-and-highlighting-code-blocks)".
 
-For example, you can create a flow chart:
+Por ejemplo, puedes crear un diagrama de flujo:
 
 <pre>
 Here is a simple flow chart:
@@ -30,21 +30,21 @@ graph TD;
 ```
 </pre>
 
-![Rendered Mermaid flow chart](/assets/images/help/writing/mermaid-flow-chart.png)
+![Diagrama de flujo generado con Mermaid](/assets/images/help/writing/mermaid-flow-chart.png)
 
 {% note %}
 
-**Note:** You may observe errors if you run a third-party Mermaid plugin when using Mermaid syntax on {% data variables.product.company_short %}.
+**Nota:** Puedes observar los errores si ejecutas un complemento de Mermaid de terceros cuando utilizas la sintaxis de Mermaid en {% data variables.product.company_short %}.
 
 {% endnote %}
 
-## Creating geoJSON and topoJSON maps
+## Crear mapas de geoJSON y topoJSON
 
-You can use geo/topoJSON syntax to create interactive maps. To create a map, add geoJSON or topoJSON inside a fenced code block with the `geojson` or `topojson` syntax identifier. Para obtener más información, consulta "[Crear y resaltar bloques de código](/get-started/writing-on-github/working-with-advanced-formatting/creating-and-highlighting-code-blocks)".
+Puedes utilizar la sintaxis de geo/topoJSON para crear mapas interactivos. Para crear un mapa, agrega geoJSON o topoJSON dentro de un bloque de código cercado con el identificador de sintaxis de `geojson` o de `topojson`. Para obtener más información, consulta "[Crear y resaltar bloques de código](/get-started/writing-on-github/working-with-advanced-formatting/creating-and-highlighting-code-blocks)".
 
-### Using geoJSON
+### Utilizando geoJSON
 
-For example, you can create a simple map:
+Por ejemplo, puedes crear un mapa simple:
 
 <pre>
 ```geojson
@@ -63,11 +63,11 @@ For example, you can create a simple map:
 ```
 </pre>
 
-![Rendered map](/assets/images/help/writing/fenced-geojson-rendered-map.png)
+![Mapa generado](/assets/images/help/writing/fenced-geojson-rendered-map.png)
 
-### Using topoJSON
+### Utilizando topoJSON
 
-For example, you can create a simple topoJSON map:
+Por ejemplo, puedes crear un mapa simple de topoJSON:
 
 <pre>
 ```topojson
@@ -106,16 +106,16 @@ For example, you can create a simple topoJSON map:
 ```
 </pre>
 
-![Rendered topojson map](/assets/images/help/writing/fenced-topojson-rendered-map.png)
+![Mapa generado con topoJSON](/assets/images/help/writing/fenced-topojson-rendered-map.png)
 
-For more information on working with `.geojson` and `.topojson` files, see "[Working with non-code files](/repositories/working-with-files/using-files/working-with-non-code-files#mapping-geojson-files-on-github)."
+Para obtener más información sobre cómo trabajar con los archivos de `.geojson` y `.topojson`, consulta la sección "[Trabajar con archivos sin código](/repositories/working-with-files/using-files/working-with-non-code-files#mapping-geojson-files-on-github)".
 
 
-## Creating STL 3D models
+## Crear modelos 3D de STL
 
-You can use ASCII STL syntax directly in markdown to create interactive 3D models. To display a model, add ASCII STL syntax inside a fenced code block with the `stl` syntax identifier. Para obtener más información, consulta "[Crear y resaltar bloques de código](/get-started/writing-on-github/working-with-advanced-formatting/creating-and-highlighting-code-blocks)".
+Puedes utilizar la sintaxis de ASCII STL directamente en el lenguaje de marcado para crear modelos 3D interactivos. Para mostrar un modelo, agrega la sintaxis ASCII STL dentro de un bloque de código cercado con el identificador de sintaxis `stl`. Para obtener más información, consulta "[Crear y resaltar bloques de código](/get-started/writing-on-github/working-with-advanced-formatting/creating-and-highlighting-code-blocks)".
 
-For example, you can create a simple 3D model:
+Por ejemplo, puedes crear un modelo 3D simple:
 
 <pre>
 ```stl
@@ -152,7 +152,7 @@ endsolid
 ```
 </pre>
 
-![Rendered 3D model](/assets/images/help/writing/fenced-stl-rendered-object.png)
+![Modelo 3D generado](/assets/images/help/writing/fenced-stl-rendered-object.png)
 
-For more information on working with `.stl` files, see "[Working with non-code files](/repositories/working-with-files/using-files/working-with-non-code-files#3d-file-viewer)."
+Para obtener más información sobre cómo trabajar con los archivos `.stl`, consulta la sección "[Trabajar con archivos sin código](/repositories/working-with-files/using-files/working-with-non-code-files#3d-file-viewer)".
 
diff --git a/translations/es-ES/content/get-started/writing-on-github/working-with-advanced-formatting/using-keywords-in-issues-and-pull-requests.md b/translations/es-ES/content/get-started/writing-on-github/working-with-advanced-formatting/using-keywords-in-issues-and-pull-requests.md
index 80441f6560..4b52622590 100644
--- a/translations/es-ES/content/get-started/writing-on-github/working-with-advanced-formatting/using-keywords-in-issues-and-pull-requests.md
+++ b/translations/es-ES/content/get-started/writing-on-github/working-with-advanced-formatting/using-keywords-in-issues-and-pull-requests.md
@@ -15,7 +15,7 @@ topics:
 
 ## Vincular una solicitud de cambios a una propuesta
 
-To link a pull request to an issue to show that a fix is in progress and to automatically close the issue when someone merges the pull request, type one of the following keywords followed by a reference to the issue. Por ejemplo, `Closes #10` o `Fixes octo-org/octo-repo#100`.
+Para enlazar una solicitud de cambios a una propuesta y mostrar que una corrección está en curso y para cerrar esta propuesta automáticamente cuando alguien fusiona la solicitud de cambios, teclea una de las siguientes palabras clave seguido de una referencia a la propuesta. Por ejemplo, `Closes #10` o `Fixes octo-org/octo-repo#100`.
 
 * close
 * closes
diff --git a/translations/es-ES/content/get-started/writing-on-github/working-with-saved-replies/about-saved-replies.md b/translations/es-ES/content/get-started/writing-on-github/working-with-saved-replies/about-saved-replies.md
index f5d3ac59d3..21ae20fab3 100644
--- a/translations/es-ES/content/get-started/writing-on-github/working-with-saved-replies/about-saved-replies.md
+++ b/translations/es-ES/content/get-started/writing-on-github/working-with-saved-replies/about-saved-replies.md
@@ -16,7 +16,7 @@ versions:
 
 Las respuestas guardadas te permiten crear una respuesta reusable para las propuestas y las solicitudes de extracción. Ahorra tiempo creando una respuesta guardada para las respuestas que usas con mayor frecuencia.
 
-Una vez que has agregado una respuesta guardada, se puede usar tanto en las propuestas como en las solicitudes de extracción. Saved replies are tied to your personal account. Una vez que son creadas, podrás usarlas en todos los repositorios y las organizaciones.
+Una vez que has agregado una respuesta guardada, se puede usar tanto en las propuestas como en las solicitudes de extracción. Las respuestas guardadas se asocian con tu cuenta personal. Una vez que son creadas, podrás usarlas en todos los repositorios y las organizaciones.
 
 Puedes crear un máximo de 100 respuestas guardadas. Si has alcanzado el límite máximo, puedes eliminar las respuestas guardadas que ya no usas o editar las respuestas guardadas existentes.
 
diff --git a/translations/es-ES/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/filtering-cards-on-a-project-board.md b/translations/es-ES/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/filtering-cards-on-a-project-board.md
index 76fb5aeb94..def929cf77 100644
--- a/translations/es-ES/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/filtering-cards-on-a-project-board.md
+++ b/translations/es-ES/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/filtering-cards-on-a-project-board.md
@@ -30,7 +30,7 @@ También puedes usar la barra de búsqueda "Filtrar tarjetas" en la parte superi
 - Filtrar por comprobación de estado usando `status:pending`, `status:success` o `status:failure`
 - Filtrar tarjetas por tipo usando `type:issue`, `type:pr` o `type:note`
 - Filtrar tarjetas por estado y tipo usando `is:open`, `is:closed` o `is:merged` y `is:issue`, `is:pr` o `is:note`
-- Filter cards by issues that are linked to a pull request by a closing reference using `linked:pr`
+- Filtrar las tarjetas por las propuestas que están enlazadas a una solicitud de cambios mediante una referencia de cierre utilizando `linked:pr`
 - Filtrar tarjetas por repositorio en un tablero de proyecto de toda la organización usando `repo:ORGANIZATION/REPOSITORY`
 
 1. Dirígete al tablero de proyecto que contenga las tarjetas que desees filtrar.
diff --git a/translations/es-ES/content/organizations/collaborating-with-groups-in-organizations/customizing-your-organizations-profile.md b/translations/es-ES/content/organizations/collaborating-with-groups-in-organizations/customizing-your-organizations-profile.md
index b8e30fdcb9..87b7914c38 100644
--- a/translations/es-ES/content/organizations/collaborating-with-groups-in-organizations/customizing-your-organizations-profile.md
+++ b/translations/es-ES/content/organizations/collaborating-with-groups-in-organizations/customizing-your-organizations-profile.md
@@ -49,7 +49,7 @@ Puedes formatear el texto e incluir emojis, imágenes y GIFs en el README del pe
 
 ## Agregar un README de perfil de organización solo para miembros
 
-1. If your organization does not already have a `.github-private` repository, create a private repository called `.github-private`.
+1. Si tu organización aún no tiene un repositorio `.github-private`, crea un repositorio privado llamado `.github-private`.
 2. En el repositorio `.github-private` de tu organización, crea un archivo `README.md` en la carpeta `profile`.
 3. Confirma los cambios al archivo `README.md`. El contenido del `README.md` se mostrará en la vista de miembros del perfil de tu organización.
 
diff --git a/translations/es-ES/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/accessing-compliance-reports-for-your-organization.md b/translations/es-ES/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/accessing-compliance-reports-for-your-organization.md
index 5ea126a8c7..69db326946 100644
--- a/translations/es-ES/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/accessing-compliance-reports-for-your-organization.md
+++ b/translations/es-ES/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/accessing-compliance-reports-for-your-organization.md
@@ -1,6 +1,6 @@
 ---
 title: Acceder a los reportes de cumplimiento de tu organización
-intro: 'You can access {% data variables.product.company_short %}''s compliance reports, such as our SOC reports and Cloud Security Alliance CAIQ self-assessment (CSA CAIQ), for your organization.'
+intro: 'Puedes acceder a los reportes de cumplimiento de {% data variables.product.company_short %}, tales como los de SOC y a la autoevaluación del CAIQ de la Alianza de Seguridad en la Nube (CSA CAIQ) para tu organización.'
 versions:
   ghec: '*'
 type: how_to
@@ -13,14 +13,14 @@ shortTitle: Acceso a los reportes de cumplimiento
 
 ## Acerca de los reportes de cumplimiento de {% data variables.product.company_short %}
 
-You can access {% data variables.product.company_short %}'s compliance reports in your organization settings.
+Puedes acceder a los reportes de cumplimiento de {% data variables.product.company_short %} en tus ajustes de organización.
 
 {% data reusables.security.compliance-report-list %}
 
 
 {% note %}
 
-**Note:** To view compliance reports, your organization must use {% data variables.product.prodname_ghe_cloud %}. {% data reusables.enterprise.link-to-ghec-trial %}
+**Nota:** Para ver los reportes de cumplimiento, tu organización debe utilizar {% data variables.product.prodname_ghe_cloud %}. {% data reusables.enterprise.link-to-ghec-trial %}
 
 {% endnote %}
 
diff --git a/translations/es-ES/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-allowed-ip-addresses-for-your-organization.md b/translations/es-ES/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-allowed-ip-addresses-for-your-organization.md
index d4c199720b..dffbe6224a 100644
--- a/translations/es-ES/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-allowed-ip-addresses-for-your-organization.md
+++ b/translations/es-ES/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-allowed-ip-addresses-for-your-organization.md
@@ -1,6 +1,6 @@
 ---
 title: Administrar las direcciones IP permitidas en tu organización
-intro: You can restrict access to your organization's private assets by configuring a list of IP addresses that are allowed to connect.
+intro: Puedes restringir el acceso a los activos privados de tu organización si configuras una lista de direcciones IP a las que se les permite conectarse.
 redirect_from:
   - /github/setting-up-and-managing-organizations-and-teams/managing-allowed-ip-addresses-for-your-organization
   - /organizations/keeping-your-organization-secure/managing-allowed-ip-addresses-for-your-organization
@@ -16,12 +16,12 @@ permissions: Organization owners can manage allowed IP addresses for an organiza
 
 ## Acerca de las direcciones IP permitidas
 
-You can restrict access to private organization assets by configuring an allow list for specific IP addresses. {% data reusables.identity-and-permissions.ip-allow-lists-example-and-restrictions %}
+Puedes restringir el acceso a los activos privados de la organización si configuras una lista de aprendizaje para las direcciones IP específicas. {% data reusables.identity-and-permissions.ip-allow-lists-example-and-restrictions %}
 
 {% ifversion ghec %}
 {% note %}
 
-**Note:** Only organizations that use {% data variables.product.prodname_ghe_cloud %} can use IP allow lists. {% data reusables.enterprise.link-to-ghec-trial %}
+**Nota:** Solo las organizaciones que utilizan {% data variables.product.prodname_ghe_cloud %} pueden utilizar listas de IP permitidas. {% data reusables.enterprise.link-to-ghec-trial %}
 
 {% endnote %}
 {% endif %}
diff --git a/translations/es-ES/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/restricting-email-notifications-for-your-organization.md b/translations/es-ES/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/restricting-email-notifications-for-your-organization.md
index 390a4f4e84..dfbffd1908 100644
--- a/translations/es-ES/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/restricting-email-notifications-for-your-organization.md
+++ b/translations/es-ES/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/restricting-email-notifications-for-your-organization.md
@@ -27,7 +27,7 @@ Cuando se habilitan las notificaciones por correo electrónico restringidas en u
 {% ifversion ghec %}
 {% note %}
 
-**Note:** To restrict email notifications, your organization must use {% data variables.product.prodname_ghe_cloud %}. {% data reusables.enterprise.link-to-ghec-trial %}
+**Nota:** Para restringir las notificaciones por correo electrónico, tu organización debe utilizar {% data variables.product.prodname_ghe_cloud %}. {% data reusables.enterprise.link-to-ghec-trial %}
 
 {% endnote %}
 {% endif %}
diff --git a/translations/es-ES/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization.md b/translations/es-ES/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization.md
index 79a0b10092..4275eef176 100644
--- a/translations/es-ES/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization.md
+++ b/translations/es-ES/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization.md
@@ -43,7 +43,7 @@ Para buscar eventos específicos, utiliza el calificador `action` en tu consulta
 | [`business`](#business-category-actions)                                                                                                                                                                                                                                          | Contiene actividades relacionadas con los ajustes de negocios para una empresa.                                                                                                                                                                                                                                                                                                                                                                                   |
 | [`codespaces`](#codespaces-category-actions)                                                                                                                                                                                                                                      | Contiene todas las actividades relacionadas con los codespaces de tu organización. |{% endif %}{% ifversion fpt or ghec or ghes > 3.2 or ghae %}
 | [`dependabot_alerts`](#dependabot_alerts-category-actions)                                                                                                                                                                                                                        | Contiene las actividades de configuración a nivel organizacional para las {% data variables.product.prodname_dependabot_alerts %} en los repositorios existentes. Para obtener más información, consulta la sección "[Acerca de{% 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)                                                                                                                                                                                                    | Contiene actividades de configuración a nivel organizacional para {% data variables.product.prodname_dependabot_alerts %} en los repositorios nuevos que se crean en la organización.{% endif %}{% ifversion fpt or ghec or ghes > 3.2 %}
 | [`dependabot_security_updates`](#dependabot_security_updates-category-actions)                                                                                                                                                                                                    | Contiene las actividades de configuración a nivel organizacional para las {% data variables.product.prodname_dependabot_security_updates %} en los repositorios existentes. Para obtener más información, consulta la sección "[Configurar las {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/configuring-dependabot-security-updates)".                                                        |
 | [`dependabot_security_updates_new_repos`](#dependabot_security_updates_new_repos-category-actions)                                                                                                                                                                                | Contiene las actividades de configuración a nivel de organización para las {% data variables.product.prodname_dependabot_security_updates %} para los repositorios nuevos que se crean en ella.{% endif %}{% ifversion fpt or ghec %}
 | [`dependency_graph`](#dependency_graph-category-actions)                                                                                                                                                                                                                          | Contiene las actividades de configuración a nivel de organización para las gráficas de dependencia de los repositorios. Para obtener más información, consulta la sección "[Acerca de la gráfica de dependencias](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)".                                                                                                                                                                   |
@@ -53,16 +53,16 @@ Para buscar eventos específicos, utiliza el calificador `action` en tu consulta
 | [`empresa`](#enterprise-category-actions)                                                                                                                                                                                                                                         | Contiene las actividades relacionadas con la configuración de la empresa.                                                                                                                                                                                                                                                                                                                                                                                         |{% endif %}
 | [`gancho`](#hook-category-actions)                                                                                                                                                                                                                                                | Contiene todas las actividades relacionadas con los webhooks.                                                                                                                                                                                                                                                                                                                                                                                                     |
 | [`integration_installation_request`](#integration_installation_request-category-actions)                                                                                                                                                                                          | Contiene todas las actividades relacionadas con las solicitudes de los miembros de la organización para que los propietarios aprueben las integraciones para el uso en la organización. |{% ifversion ghec or ghae %}
-| [`ip_allow_list`](#ip_allow_list-category-actions)                                                                                                                                                                                                                                | Contains activities related to enabling or disabling the IP allow list for an organization.                                                                                                                                                                                                                                                                                                                                                                       |
-| [`ip_allow_list_entry`](#ip_allow_list_entry-category-actions)                                                                                                                                                                                                                    | Contains activities related to the creation, deletion, and editing of an IP allow list entry for an organization.{% endif %}
+| [`ip_allow_list`](#ip_allow_list-category-actions)                                                                                                                                                                                                                                | Contiene todas las actividades relacionadas para habilitar o inhabilitar la lista de IP permitidas de una organización.                                                                                                                                                                                                                                                                                                                                           |
+| [`ip_allow_list_entry`](#ip_allow_list_entry-category-actions)                                                                                                                                                                                                                    | Contiene las actividades relacionadas con la creación, el borrado y la edición de una entrada en una lista de IP permitidas para una organización.{% endif %}
 | [`propuesta`](#issue-category-actions)                                                                                                                                                                                                                                            | Contiene las actividades relacionadas con borrar una propuesta.                                                                                                                                                                                                                                                                                                                                                                                                   |{% ifversion fpt or ghec %}
 | [`marketplace_agreement_signature`](#marketplace_agreement_signature-category-actions)                                                                                                                                                                                            | Contiene todas las actividades relacionadas con la firma del Acuerdo del programador de {% data variables.product.prodname_marketplace %}.                                                                                                                                                                                                                                                                                                                        |
 | [`marketplace_listing`](#marketplace_listing-category-actions)                                                                                                                                                                                                                    | Contiene todas las actividades relacionadas con el listado de apps en {% data variables.product.prodname_marketplace %}.{% endif %}{% ifversion fpt or ghes or ghec %}
 | [`members_can_create_pages`](#members_can_create_pages-category-actions)                                                                                                                                                                                                          | Contiene todas las actividades relacionadas con administrar la publicación de sitios de {% data variables.product.prodname_pages %} para los repositorios en la organización. Para obtener más información, consulta la sección "[Administrar la publicación de sitios de {% data variables.product.prodname_pages %} para tu organización](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)". |{% endif %}
 | [`org`](#org-category-actions)                                                                                                                                                                                                                                                    | Contiene actividades relacionadas con la membrecía organizacional.{% ifversion ghec %}
 | [`org_credential_authorization`](#org_credential_authorization-category-actions)                                                                                                                                                                                                  | Contiene todas las actividades relacionadas con la autorización de credenciales para su uso con el inicio de sesión único de SAML. {% endif %}{% if secret-scanning-audit-log-custom-patterns %}
-| [`org_secret_scanning_custom_pattern`](#org_secret_scanning_custom_pattern-category-actions)                                                                                                                                                                                      | Contains organization-level activities related to secret scanning custom patterns. Para obtener más información, consulta la sección "[Definir los patrones personalizados para el escaneo de secretos](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning)".                                                                                                                                                                            |{% endif %}
-| [`organization_label`](#organization_label-category-actions)                                                                                                                                                                                                                      | Contains all activities related to default labels for repositories in your organization.                                                                                                                                                                                                                                                                                                                                                                          |
+| [`org_secret_scanning_custom_pattern`](#org_secret_scanning_custom_pattern-category-actions)                                                                                                                                                                                      | Contiene actividades a nivel organizacional relacionadas con los patrones personalizados del escaneo de secretos. Para obtener más información, consulta la sección "[Definir los patrones personalizados para el escaneo de secretos](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning)".                                                                                                                                             |{% endif %}
+| [`organization_label`](#organization_label-category-actions)                                                                                                                                                                                                                      | Contiene todas las actividades relacionadas con las etiquetas predeterminadas para los repositorios de tu organización.                                                                                                                                                                                                                                                                                                                                           |
 | [`oauth_application`](#oauth_application-category-actions)                                                                                                                                                                                                                        | Contiene todas las actividades relacionadas con las Apps de OAuth.                                                                                                                                                                                                                                                                                                                                                                                                |
 | [`paquetes`](#packages-category-actions)                                                                                                                                                                                                                                          | Contiene todas las actividades relacionadas con el {% data variables.product.prodname_registry %}.{% ifversion fpt or ghec %}
 | [`payment_method`](#payment_method-category-actions)                                                                                                                                                                                                                              | Contiene todas las actividades relacionadas con la manera en que tu organización le paga a GitHub.{% endif %}
@@ -76,7 +76,7 @@ Para buscar eventos específicos, utiliza el calificador `action` en tu consulta
 | repositorio {% ifversion fpt or ghec %}privado{% endif %}. Para obtener más información, consulta la sección "[Acerca de la gráfica de dependencias](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)".{% endif %}{% ifversion ghes or ghae or ghec %} |                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
 | [`repository_secret_scanning`](#repository_secret_scanning-category-actions)                                                                                                                                                                                                      | Contiene actividades a nivel de repositorio relacionadas con el escaneo de secretos. Para obtener más información, consulta la sección "[Acerca del escaneo de secretos"](/github/administering-a-repository/about-secret-scanning).                                                                                                                                                                                                                              |{% endif %}{% if secret-scanning-audit-log-custom-patterns %}
 | [`repository_secret_scanning_custom_pattern`](#respository_secret_scanning_custom_pattern-category-actions)                                                                                                                                                                       | Contiene actividades a nivel de repositorio relacionadas con los patrones personalizados del escaneo de secretos. Para obtener más información, consulta la sección "[Definir los patrones personalizados para el escaneo de secretos](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning)".                                                                                                                                             |{% endif %}{% if secret-scanning-audit-log-custom-patterns %}
-| [`repository_secret_scanning_push_protection`](#respository_secret_scanning_push_protection)                                                                                                                                                                                      | Contiene actividades a nivel de repositorio relacionadas con los patrones personalizados del escaneo de secretos. For more information, see "[Protecting pushes with secert scanning](/code-security/secret-scanning/protecting-pushes-with-secret-scanning)."                                                                                                                                                                                                    |{% endif %}{% ifversion fpt or ghes or ghae or ghec %}
+| [`repository_secret_scanning_push_protection`](#respository_secret_scanning_push_protection)                                                                                                                                                                                      | Contiene actividades a nivel de repositorio relacionadas con los patrones personalizados del escaneo de secretos. Para obtener más información, consulta la sección "[Proteger las subidas con el escaneo de secretos](/code-security/secret-scanning/protecting-pushes-with-secret-scanning)".                                                                                                                                                                   |{% endif %}{% ifversion fpt or ghes or ghae or ghec %}
 | [`repository_vulnerability_alert`](#repository_vulnerability_alert-category-actions)                                                                                                                                                                                              | Contiene todas las actividades relacionadas con [las {% data variables.product.prodname_dependabot_alerts %} para las dependencias vulnerables](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies).{% endif %}{% ifversion fpt or ghec %}
 | [`repository_vulnerability_alerts`](#repository_vulnerability_alerts-category-actions)                                                                                                                                                                                            | Contiene actividades de configuración a nivel de repositorio para las {% data variables.product.prodname_dependabot_alerts %}.{% endif %}{% if custom-repository-roles %}
 | [`rol`](#role-category-actions)                                                                                                                                                                                                                                                   | Contiene todas las actividades relacionadas con los [roles de repositorio personalziados](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization).{% endif %}{% ifversion ghes or ghae or ghec %}
@@ -135,7 +135,7 @@ Al utilizar el calificador `country`, puedes filtrar los eventos en la bitácora
 
 {% ifversion fpt %}
 
-Organizations that use {% data variables.product.prodname_ghe_cloud %} can interact with the audit log using the GraphQL API and REST API. Para obtener más información, consulta la [documentación de {% data variables.product.prodname_ghe_cloud %}](/enterprise-cloud@latest/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization#using-the-audit-log-api).
+Las organizaciones que utilizan {% data variables.product.prodname_ghe_cloud %} pueden interactuar con la bitácora de auditoría utilizando la API de GraphQL y la de REST. Para obtener más información, consulta la [documentación de {% data variables.product.prodname_ghe_cloud %}](/enterprise-cloud@latest/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization#using-the-audit-log-api).
 
 {% else %}
 
@@ -145,7 +145,7 @@ Puedes interactuar con la bitácora de audotaría si utilizas la API de GraphQL{
 
 {% note %}
 
-**Note:** To use the audit log API, your organization must use {% data variables.product.prodname_ghe_cloud %}. {% data reusables.enterprise.link-to-ghec-trial %}
+**Nota:** Para utilizar la API de bitácora de auditoría, tu organización debe utilizar {% data variables.product.prodname_ghe_cloud %}. {% data reusables.enterprise.link-to-ghec-trial %}
 
 {% endnote %}
 
@@ -173,7 +173,7 @@ Para garantizar que tu propiedad intelectual está segura y que mantienes el cum
 
 {% data reusables.audit_log.audit-log-git-events-retention %}
 
-By default, only events from the past three months are returned. To include older events, you must specify a timestamp in your query.
+Predeterminadamente, solo se devuelven los eventos de los tres meses anteriores. Para incluir eventos más antiguos, debes especificar una marca de tiempo en tu consulta.
 
 Para obtener más información sobre la API de REST del log de auditoría, consulta la sección "[Organizaciones](/rest/reference/orgs#get-the-audit-log-for-an-organization)".
 
@@ -287,10 +287,10 @@ Un resumen de algunas de las acciones más comunes que se registran como eventos
 
 ### acciones de la categoría `discussion_post`
 
-| Acción               | Descripción                                                                                                                 |
-| -------------------- | --------------------------------------------------------------------------------------------------------------------------- |
-| `actualización`      | Se activa cuando se edita [una publicación de debate de equipo](/articles/managing-disruptive-comments/#editing-a-comment). |
-| `destroy (destruir)` | Triggered when [a team discussion post is deleted](/articles/managing-disruptive-comments/#deleting-a-comment).             |
+| Acción               | Descripción                                                                                                                  |
+| -------------------- | ---------------------------------------------------------------------------------------------------------------------------- |
+| `actualización`      | Se activa cuando se edita [una publicación de debate de equipo](/articles/managing-disruptive-comments/#editing-a-comment).  |
+| `destroy (destruir)` | Se activa cuando [se borra una publicación de debate de equipo](/articles/managing-disruptive-comments/#deleting-a-comment). |
 
 ### acciones de la categoría `discussion_post_reply`
 
@@ -428,7 +428,7 @@ Para obtener más información, consulta la sección "[Administrar la publicaci
 
 | Acción                                              | Descripción                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
 | --------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `add_member (agregar miembro)`                      | Triggered when a user joins an organization.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+| `add_member (agregar miembro)`                      | Se activa cuando un usuario se une a una organización.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
 | `advanced_security_policy_selected_member_disabled` | Se activa cuando un propietario de empresa previene que las carcaterísticas de la {% data variables.product.prodname_GH_advanced_security %} se habiliten para los repositorios que pertenecen a la organización. {% data reusables.advanced-security.more-information-about-enforcement-policy %}
 | `advanced_security_policy_selected_member_enabled`  | Se activa cuando un propietario de empresa permite que se habiliten las características de la {% data variables.product.prodname_GH_advanced_security %} en los repositorios que pertenecen a la organización. {% data reusables.advanced-security.more-information-about-enforcement-policy %}{% ifversion fpt or ghec %}
 | `audit_log_export`                                  | Se activa cuando un administrador de la organización [crea una exportación del registro de auditoría de la organización](#exporting-the-audit-log). Si la exportación incluía una consulta, el registro detallará la consulta utilizada y la cantidad de entradas en el registro de auditoría que coinciden con esa consulta.                                                                                                                                                                                                         |
@@ -462,8 +462,8 @@ Para obtener más información, consulta la sección "[Administrar la publicaci
 | `runner_group_runners_added`                        | Se activa cuando se agrega un ejecutor auto-hospedado a un grupo. Para obtener más información, consulta la sección [Mover un ejecutor auto-hospedado a un grupo](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#moving-a-self-hosted-runner-to-a-group).                                                                                                                                                                                                                                      |
 | `runner_group_runner_removed`                       | Se activa cuando se utiliza la API de REST para eliminar un ejecutor auto-hospedado de un grupo. Para obtener más información, consulta la sección "[Eliminar un ejecutor auto-hospedado de un grupo en una organización](/rest/reference/actions#remove-a-self-hosted-runner-from-a-group-for-an-organization)".                                                                                                                                                                                                                     |
 | `runner_group_runners_updated`                      | Se activa cuando se actualiza la lista de miembros de un grupo de ejecutores. Para obtener más información, consulta la sección "[Configurar los ejecutores auto-hospedados en un grupo para una organización](/rest/reference/actions#set-self-hosted-runners-in-a-group-for-an-organization)". {% if secret-scanning-audit-log-custom-patterns %}
-| `secret_scanning_push_protection_disable`           | Triggered when an organization owner or person with admin access to the organization disables push protection for secret scanning. Para obtener más información, consulta la sección "[Proteger las subidas de información con el escaneo de secretos](/enterprise-cloud@latest/code-security/secret-scanning/protecting-pushes-with-secret-scanning)".                                                                                                                                                                               |
-| `secret_scanning_push_protection_enable`            | Triggered when an organization owner or person with admin access to the organization enables push protection for secret scanning.{% endif %}{% ifversion fpt or ghes > 3.1 or ghae or ghec %}
+| `secret_scanning_push_protection_disable`           | Se activa cuando un propietario o persona de una organización con acceso administrativo a esta inhabilita la protección de subida para el escaneo de secretos. Para obtener más información, consulta la sección "[Proteger las subidas de información con el escaneo de secretos](/enterprise-cloud@latest/code-security/secret-scanning/protecting-pushes-with-secret-scanning)".                                                                                                                                                   |
+| `secret_scanning_push_protection_enable`            | Se activa cuando el propietario de la organización o persona con acceso administrativo a la organización habilita la protección de subida para el escaneo de secretos.{% endif %}{% ifversion fpt or ghes > 3.1 or ghae or ghec %}
 | `self_hosted_runner_online`                         | Se activa cuando la aplicación del ejecutor se inicia. Solo se puede ver utilizando la API de REST; no está visible en la IU o en la exportación de JSON/CSV. Para obtener más información, consulta "[Comprobar el estado de un ejecutor autoalojado](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)."                                                                                                                                            |
 | `self_hosted_runner_offline`                        | Se activa cuando se detiene la aplicación del ejecutor. Solo se puede ver utilizando la API de REST; no está visible en la IU o en la exportación de JSON/CSV. Para obtener más información, consulta la sección "[Verificar el estado de un ejecutor auto-hospedado](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)".{% endif %}{% ifversion fpt or ghes or ghec %}
 | `self_hosted_runner_updated`                        | Se activa cuando se actualiza la aplicación ejecutora. Se puede ver utilizando la API de REST y la IU; no se puede ver en la exportación de JSON/CSV. Para obtener más información, consulta la sección "[Acerca de los ejecutores auto-hospedados](/actions/hosting-your-own-runners/about-self-hosted-runners#about-self-hosted-runners)".{% endif %}{% ifversion fpt or ghec %}
diff --git a/translations/es-ES/content/organizations/keeping-your-organization-secure/managing-two-factor-authentication-for-your-organization/index.md b/translations/es-ES/content/organizations/keeping-your-organization-secure/managing-two-factor-authentication-for-your-organization/index.md
index df495a0d4f..57ba3a1818 100644
--- a/translations/es-ES/content/organizations/keeping-your-organization-secure/managing-two-factor-authentication-for-your-organization/index.md
+++ b/translations/es-ES/content/organizations/keeping-your-organization-secure/managing-two-factor-authentication-for-your-organization/index.md
@@ -1,7 +1,7 @@
 ---
-title: Managing two-factor authentication for your organization
-shortTitle: Manage 2FA
-intro: You can view whether users with access to your organization have two-factor authentication (2FA) enabled and require 2FA.
+title: Administrar la autenticación bifactorial para tu organización
+shortTitle: Administrar la 2FA
+intro: Puedes ver si los usuarios con acceso a tu organización tienen habilitada la autenticación bifactorial (2FA) y requerir que la utilicen.
 versions:
   fpt: '*'
   ghes: '*'
diff --git a/translations/es-ES/content/organizations/keeping-your-organization-secure/managing-two-factor-authentication-for-your-organization/viewing-whether-users-in-your-organization-have-2fa-enabled.md b/translations/es-ES/content/organizations/keeping-your-organization-secure/managing-two-factor-authentication-for-your-organization/viewing-whether-users-in-your-organization-have-2fa-enabled.md
index eac001703d..230e9ae215 100644
--- a/translations/es-ES/content/organizations/keeping-your-organization-secure/managing-two-factor-authentication-for-your-organization/viewing-whether-users-in-your-organization-have-2fa-enabled.md
+++ b/translations/es-ES/content/organizations/keeping-your-organization-secure/managing-two-factor-authentication-for-your-organization/viewing-whether-users-in-your-organization-have-2fa-enabled.md
@@ -12,7 +12,7 @@ versions:
 topics:
   - Organizations
   - Teams
-shortTitle: View 2FA usage
+shortTitle: Ver el uso de la 2FA
 ---
 
 {% note %}
diff --git a/translations/es-ES/content/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization.md b/translations/es-ES/content/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization.md
index 112afc6286..b190f87721 100644
--- a/translations/es-ES/content/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization.md
+++ b/translations/es-ES/content/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization.md
@@ -117,7 +117,7 @@ Predeterminadamente, cuando creas una organización nueva, `GITHUB_TOKEN` solo t
 {% data reusables.profile.access_org %}
 {% data reusables.profile.org_settings %}
 {% data reusables.organizations.settings-sidebar-actions-general %}
-1. Under "Workflow permissions", choose whether you want the `GITHUB_TOKEN` to have read and write access for all scopes, or just read access for the `contents` scope.
+1. Debajo de "Permisos de flujo de trabajo", elige si quieres que el `GITHUB_TOKEN` tenga acceso de lectura y escritura para todos los alcances o solo acceso de lectura para el alcance `contents`.
 
    ![Configurar los permisos del GITHUB_TOKEN para esta organización](/assets/images/help/settings/actions-workflow-permissions-organization{% if allow-actions-to-approve-pr %}-with-pr-{% if allow-actions-to-approve-pr-with-ent-repo %}creation-{% endif %}approval{% endif %}.png)
 1. Da clic en **Guardar** para aplicar la configuración.
diff --git a/translations/es-ES/content/organizations/managing-organization-settings/managing-pull-request-reviews-in-your-organization.md b/translations/es-ES/content/organizations/managing-organization-settings/managing-pull-request-reviews-in-your-organization.md
index 6b21910427..a1ab4ef3f4 100644
--- a/translations/es-ES/content/organizations/managing-organization-settings/managing-pull-request-reviews-in-your-organization.md
+++ b/translations/es-ES/content/organizations/managing-organization-settings/managing-pull-request-reviews-in-your-organization.md
@@ -1,6 +1,6 @@
 ---
-title: Managing pull request reviews in your organization
-intro: You can limit which users can approve or request changes to a pull requests in your organization.
+title: Administrar revisiones de solicitudes de cambio en tu organización
+intro: Puedes limitar qué usuarios pueden aprobar o solicitar cambios a una solicitud de cambios en tu organización.
 versions:
   feature: pull-request-approval-limit
 permissions: Organization owners can limit which users can submit reviews that approve or request changes to a pull request.
@@ -14,14 +14,14 @@ shortTitle: Administrar las revisiones de las solicitudes de cambios
 
 Predeterminadamente, en los repositorios públicos, cualquier usuario puede emitir revisiones que aprueben o soliciten cambios a una solicitud de cambios.
 
-You can limit who is able to approve or request changes to pull requests in public repositories owned by your organization. After you enable code review limits, anyone can comment on pull requests in your public repositories, but only people with explicit access to a repository can approve a pull request or request changes.
+Puedes limitar quiénes pueden aprobar o solicitar cambios a las solicitudes de cambios en los repositorios públicos que le pertenezcan a tu organización. Después de que habilitas los límites de revisión de código, cualquiera puede comentar en las solicitudes de cambios en tus repositorios públicos, pero solo las personas con acceso explícito a cualquier repositorio pueden aprobar una solicitud de cambios o solicitar cambios a ella.
 
-You can also enable code review limits for individual repositories. If you enable or limits for your organization, you will override any limits for individual repositories owned by the organization. For more information, see "[Managing pull request reviews in your repository](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-pull-request-reviews-in-your-repository)."
+También puedes habilitar límites de la revisión de código para los repositorios individuales. Si habilitas los límites en tu organización, ignorarás cualquier límite para repositorios individuales que le pertenezcan a ella. Para obtener más información, consulta la sección "[Administrar las revisiones de solicitudes de cambios en tu repositorio](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-pull-request-reviews-in-your-repository)".
 
 ## Habilitar los límites de revisión de código
 
 {% data reusables.profile.access_org %}
 {% data reusables.profile.org_settings %}
-1. In the "Access" section of the sidebar, click **{% octicon "report" aria-label="The report icon" %} Moderation**.
-1. Under "{% octicon "report" aria-label="The report icon" %} Moderation", click **Code review limits**. ![Screenshot of sidebar item for code review limits for organizations](/assets/images/help/organizations/code-review-limits-organizations.png)
-1. Review the information on screen. Click **Limit review on all repositories** to limit reviews to those with explicit access, or click **Remove review limits from all repositories** to remove the limits from every public repository in your organization. ![Screenshot of code review limits settings for organizations](/assets/images/help/organizations/code-review-limits-organizations-settings.png)
+1. En la sección de "Acceso" de la barra lateral, haz clic en **Moderación {% octicon "report" aria-label="The report icon" %}**.
+1. Debajo de "{% octicon "report" aria-label="The report icon" %} Moderación", haz clic en **Límites de la revisión de código**. ![Captura de pantalla del elemento de la barra lateral para los límites de la revisión de código para organizaciones](/assets/images/help/organizations/code-review-limits-organizations.png)
+1. Revisa la información en la pantalla. Haz clic en **Limitar la revisión en todos los repositorios** para limitar las revisiones a aquellos con acceso explícito o haz clic en **Eliminar los límites de revisión de todos los repositorios** para eliminar los límites de todos los repositorios públicos en tu organización. ![Captura de pantalla de los ajustes en los límites de la revisión de código para las organizaciones](/assets/images/help/organizations/code-review-limits-organizations-settings.png)
diff --git a/translations/es-ES/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-security-managers-in-your-organization.md b/translations/es-ES/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-security-managers-in-your-organization.md
index 7cf8eb37fe..e4fa31c195 100644
--- a/translations/es-ES/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-security-managers-in-your-organization.md
+++ b/translations/es-ES/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-security-managers-in-your-organization.md
@@ -28,7 +28,7 @@ Los miembros de un equipo que tengan el rol de administrador de seguridad solo t
 Puedes encontrar funcionalidades adicionales disponibles, incluyendo un resumen de seguridad de la organización, en las organizaciones que utilizan {% data variables.product.prodname_ghe_cloud %} con la {% data variables.product.prodname_advanced_security %}. Para obtener más información, consulta la [documentación de {% data variables.product.prodname_ghe_cloud %}](/enterprise-cloud@latest/organizations/managing-peoples-access-to-your-organization-with-roles/managing-security-managers-in-your-organization).
 {% endif %}
 
-Si un equipo tiene el rol de administrador de seguridad, las personas con acceso administrativo al equipo y a un repositorio específico pueden cambiar el nivel de acceso de dicho equipo al repositorio pero no pueden eliminar el acceso. For more information, see "[Managing team access to an organization repository](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository){% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5974 %}" and "[Managing teams and people with access to your repository](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-teams-and-people-with-access-to-your-repository)."{% else %}."{% endif %}
+Si un equipo tiene el rol de administrador de seguridad, las personas con acceso administrativo al equipo y a un repositorio específico pueden cambiar el nivel de acceso de dicho equipo al repositorio pero no pueden eliminar el acceso. Para obtener más información, consulta las secciones "[Administrar el acceso del equipo al repositorio de una organización](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository){% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5974 %}" y "[Administrar a los equipos y las personas con acceso a tu repositorio](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-teams-and-people-with-access-to-your-repository){% else %}".{% endif %}".
 
   ![Administrar la IU de acceso al repositorio con administradores de seguridad](/assets/images/help/organizations/repo-access-security-managers.png)
 
diff --git a/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-suggestions-to-update-pull-request-branches.md b/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-suggestions-to-update-pull-request-branches.md
index a724a1302b..a2b28405e1 100644
--- a/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-suggestions-to-update-pull-request-branches.md
+++ b/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-suggestions-to-update-pull-request-branches.md
@@ -1,6 +1,6 @@
 ---
-title: Managing suggestions to update pull request branches
-intro: You can give users the ability to always update a pull request branch when it is not up to date with the base branch.
+title: Administrar las sugerencias para actualizar las ramas de las solicitudes de cambios
+intro: Puedes darles a los usuarios la capacidad de que siempre puedan actualizar una rama de una solicitud de cambios cuando no esté actualizada con la rama base.
 versions:
   fpt: '*'
   ghes: '> 3.4'
@@ -8,16 +8,16 @@ versions:
   ghec: '*'
 topics:
   - Repositories
-shortTitle: Manage branch updates
+shortTitle: Administrar las actualizaciones de ramas
 permissions: People with maintainer permissions can enable or disable the setting to suggest updating pull request branches.
 ---
 
-## About suggestions to update a pull request branch
+## Acerca de las sugerencias para actualizar una rama de solicitud de cambios
 
-If you enable the setting to always suggest updating pull request branches in your repository, people with write permissions will always have the ability, on the pull request page, to update a pull request's head branch when it's not up to date with the base branch. When not enabled, the ability to update is only available when the base branch requires branches to be up to date before merging and the branch is not up to date. For more information, see "[Keeping your pull request in sync with the base branch](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/keeping-your-pull-request-in-sync-with-the-base-branch)."
+Si habilitas el ajuste para que siempre sugiera actualizar ramas de solicitudes de cambios en tu repositorio, las personas con permisos de escritura siempre podrán actualizar la rama de encabezado de una solicitud de cambios, en la página de dicha solicitud, cuando no esté actualizada con la rama base. Cuando no se habilita, esta capacidad de actualización solo estará disponible cuando la rama base requiera que las ramas estén actualizadas antes de la fusión y la rama no esté actualizada. Para obtener más información, consulta la sección "[Mantener tu solicitud de cambios sincronizada con la rama base](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/keeping-your-pull-request-in-sync-with-the-base-branch)".
 
-## Managing suggestions to update a pull request branch
+## Administrar las sugerencias para actualizar una rama de una solicitud de cambios
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
-3. Under "Pull Requests", select or unselect **Always suggest updating pull request branches**. ![Checkbox to enable or disable always suggest updating branch](/assets/images/help/repository/always-suggest-updating-branches.png)
+3. Debajo de "Solicitudes de cambio", selecciona o deselecciona **Siempre sugerir actualizar las ramas de las solicitudes de cambio**. ![Casilla de verificación para habilitar o inhabilitar la opción de siempre sugerir actualizar la rama](/assets/images/help/repository/always-suggest-updating-branches.png)
diff --git a/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/troubleshooting-required-status-checks.md b/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/troubleshooting-required-status-checks.md
index 810cf322fa..39623e8ea8 100644
--- a/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/troubleshooting-required-status-checks.md
+++ b/translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/troubleshooting-required-status-checks.md
@@ -47,15 +47,15 @@ Algunas veces, los resultados de las verificaciones de estado para la confirmaci
 
 {% note %}
 
-**Note:** If a workflow is skipped due to [path filtering](/actions/using-workflows/workflow-syntax-for-github-actions#onpushpull_requestpull_request_targetpathspaths-ignore), [branch filtering](/actions/using-workflows/workflow-syntax-for-github-actions#onpull_requestpull_request_targetbranchesbranches-ignore) or a [commit message](/actions/managing-workflow-runs/skipping-workflow-runs), then checks associated with that workflow will remain in a "Pending" state. A pull request that requires those checks to be successful will be blocked from merging.
+**Nota:** Si se omite un flujo de trabajo debido a [filtrado de ruta](/actions/using-workflows/workflow-syntax-for-github-actions#onpushpull_requestpull_request_targetpathspaths-ignore), [filtrado de rama](/actions/using-workflows/workflow-syntax-for-github-actions#onpull_requestpull_request_targetbranchesbranches-ignore) o a un [mensaje de confirmación](/actions/managing-workflow-runs/skipping-workflow-runs), entonces las verificaciones asociadas con este flujo de trabajo permanecerán en un estado de "Pendiente". Las solicitudes de cambios que requieran que esas verificaciones tengan éxito quedarán bloqueadas para fusión.
 
-If a job in a workflow is skipped due to a conditional, it will report its status as "Success". For more information see [Skipping workflow runs](/actions/managing-workflow-runs/skipping-workflow-runs) and [Using conditions to control job execution](/actions/using-jobs/using-conditions-to-control-job-execution).
+Si se omite un job en un flujo de trabajo debido a una condicional, este reportará su estado como "Éxito". Para obtener más información, consulta las secciones de [Omitir las ejecuciones de flujo de trabajo](/actions/managing-workflow-runs/skipping-workflow-runs) y [Utilizar condiciones para controlar la ejecución de jobs](/actions/using-jobs/using-conditions-to-control-job-execution).
 
 {% endnote %}
 
 ### Ejemplo
 
-The following example shows a workflow that requires a "Successful" completion status for the `build` job, but the workflow will be skipped if the pull request does not change any files in the `scripts` directory.
+El siguiente ejemplo muestra un flujo de trabajo que requiere un estado de finalización "Exitoso" para el job `build`, pero el flujo de trabajo se omitirá si la solicitud de cambios no cambia ningún archivo en el directorio `scripts`.
 
 ```yaml
 name: ci
@@ -81,7 +81,7 @@ jobs:
     - run: npm test
 ```
 
-Due to [path filtering](/actions/using-workflows/workflow-syntax-for-github-actions#onpushpull_requestpull_request_targetpathspaths-ignore), a pull request that only changes a file in the root of the repository will not trigger this workflow and is blocked from merging. Verías el siguiente estado en la solicitud de cambios:
+Debido al [filtrado de rutas](/actions/using-workflows/workflow-syntax-for-github-actions#onpushpull_requestpull_request_targetpathspaths-ignore), una solicitud de cambios que solo cambie un archivo en la raíz del repositorio ya no activará este flujo de trabajo y se bloqueará para su fusión. Verías el siguiente estado en la solicitud de cambios:
 
 ![Verificación requerida omitida, pero mostrada como pendiente](/assets/images/help/repository/PR-required-check-skipped.png)
 
diff --git a/translations/es-ES/content/repositories/creating-and-managing-repositories/creating-a-new-repository.md b/translations/es-ES/content/repositories/creating-and-managing-repositories/creating-a-new-repository.md
index d805626f9b..5d6463e4c8 100644
--- a/translations/es-ES/content/repositories/creating-and-managing-repositories/creating-a-new-repository.md
+++ b/translations/es-ES/content/repositories/creating-and-managing-repositories/creating-a-new-repository.md
@@ -33,8 +33,8 @@ topics:
 {% endtip %}
 
 {% data reusables.repositories.create_new %}
-2. Otra opción para crear un repositorio con la estructura del directorio y los archivos de un repositorio existente es usar el menú desplegable **Elegir una plantilla** y seleccionar un repositorio de plantillas. Verás repositorios de plantillas que te pertenecen a ti y a las organizaciones de las que eres miembro o bien repositorios de plantillas que has usado anteriormente. Para obtener más información, consulta "[Crear un repositorio a partir de una plantilla](/articles/creating-a-repository-from-a-template)". ![Template drop-down menu](/assets/images/help/repository/template-drop-down.png)
-3. De manera opcional, si decides utilizar una plantilla, para incluir la estructura del directorio y los archivos de todas las ramas en la misma y no solo la rama predeterminada, selecciona **Incluir todas las ramas**. ![Include all branches checkbox](/assets/images/help/repository/include-all-branches.png)
+2. Otra opción para crear un repositorio con la estructura del directorio y los archivos de un repositorio existente es usar el menú desplegable **Elegir una plantilla** y seleccionar un repositorio de plantillas. Verás repositorios de plantillas que te pertenecen a ti y a las organizaciones de las que eres miembro o bien repositorios de plantillas que has usado anteriormente. Para obtener más información, consulta "[Crear un repositorio a partir de una plantilla](/articles/creating-a-repository-from-a-template)". ![Menú desplegable de la plantilla](/assets/images/help/repository/template-drop-down.png)
+3. De manera opcional, si decides utilizar una plantilla, para incluir la estructura del directorio y los archivos de todas las ramas en la misma y no solo la rama predeterminada, selecciona **Incluir todas las ramas**. ![Casilla de verificación de incluir todas las ramas](/assets/images/help/repository/include-all-branches.png)
 3. En el menú desplegable de Propietario, selecciona la cuenta en la cual quieres crear el repositorio. ![Menú desplegable Propietario](/assets/images/help/repository/create-repository-owner.png)
 {% data reusables.repositories.repo-name %}
 {% data reusables.repositories.choose-repo-visibility %}
diff --git a/translations/es-ES/content/repositories/creating-and-managing-repositories/creating-a-template-repository.md b/translations/es-ES/content/repositories/creating-and-managing-repositories/creating-a-template-repository.md
index 3a034388e6..c2c998ddb2 100644
--- a/translations/es-ES/content/repositories/creating-and-managing-repositories/creating-a-template-repository.md
+++ b/translations/es-ES/content/repositories/creating-and-managing-repositories/creating-a-template-repository.md
@@ -1,6 +1,6 @@
 ---
 title: Crear un repositorio desde una plantilla
-intro: 'You can make an existing repository a template, so you and others can generate new repositories with the same directory structure, branches, and files.'
+intro: 'Puedes convertir un repositorio existente en una plantilla para que tanto tú como otras personas puedan generar repositorios nuevos con la misma estructura de directorios, ramas y archivos.'
 permissions: Anyone with admin permissions to a repository can make the repository a template.
 redirect_from:
   - /articles/creating-a-template-repository
@@ -24,7 +24,7 @@ shortTitle: Crear un repositorio de plantilla
 
 Para crear un repositorio de plantilla, debes crear un repositorio y luego convertirlo en una plantilla. Para obtener más información sobre la creación de repositorios, consulta "[Crear un repositorio nuevo](/articles/creating-a-new-repository)."
 
-After you make your repository a template, anyone with access to the repository can generate a new repository with the same directory structure and files as your default branch. They can also choose to include all the other branches in your repository. Branches created from a template have unrelated histories, so you cannot create pull requests or merge between the branches. Para obtener más información, consulta "[Crear un repositorio a partir de una plantilla](/articles/creating-a-repository-from-a-template)".
+Después de convertir a tu repositorio en plantilla, cualquiera con acceso a dicho repositorio podrá generar uno nuevo con la misma estructura de directorios y archivos que tu rama predeterminada. También pueden elegir incluir el resto de las ramas en tu repositorio. Las ramas que se crean desde una plantilla tienen historias sin relación entre ellas, así que no puedes crear solicitudes de cambio ni hacer fusiones entre las ramas. Para obtener más información, consulta "[Crear un repositorio a partir de una plantilla](/articles/creating-a-repository-from-a-template)".
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
diff --git a/translations/es-ES/content/repositories/creating-and-managing-repositories/deleting-a-repository.md b/translations/es-ES/content/repositories/creating-and-managing-repositories/deleting-a-repository.md
index d5f0bd5058..cb01b2dc85 100644
--- a/translations/es-ES/content/repositories/creating-and-managing-repositories/deleting-a-repository.md
+++ b/translations/es-ES/content/repositories/creating-and-managing-repositories/deleting-a-repository.md
@@ -29,7 +29,7 @@ topics:
 
 {% endwarning %}
 
-Some deleted repositories can be restored within {% ifversion fpt or ghec or ghes > 3.4 %}30{% else %}90{% endif%} days of deletion. {% ifversion ghes or ghae %}Tu administrador de sitio podría ser capaz de restablecer un repositorio borrado para ti. Para obtener más información, consulta "[Restaurar un repositorio eliminado](/admin/user-management/managing-repositories-in-your-enterprise/restoring-a-deleted-repository)". {% else %}Para obtener más información, consulta la sección"[Restaurar un repositorio eliminado](/articles/restoring-a-deleted-repository)".{% endif %}
+Algunos repositorios borrados pueden restablecerse en los sguientes {% ifversion fpt or ghec or ghes > 3.4 %}30{% else %}90{% endif%} días después de haberlos borrado. {% ifversion ghes or ghae %}Tu administrador de sitio podría ser capaz de restablecer un repositorio borrado para ti. Para obtener más información, consulta "[Restaurar un repositorio eliminado](/admin/user-management/managing-repositories-in-your-enterprise/restoring-a-deleted-repository)". {% else %}Para obtener más información, consulta la sección"[Restaurar un repositorio eliminado](/articles/restoring-a-deleted-repository)".{% endif %}
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
diff --git a/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-readmes.md b/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-readmes.md
index 28b623f207..cb086dd3f0 100644
--- a/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-readmes.md
+++ b/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-readmes.md
@@ -29,9 +29,9 @@ Un archivo README suele ser el primer elemento que verá un visitante cuando ent
 - Dónde pueden recibir ayuda los usuarios con tu proyecto
 - Quién mantiene y contribuye con el proyecto.
 
-If you put your README file in your repository's hidden `.github`, root, or `docs` directory, {% data variables.product.product_name %} will recognize and automatically surface your README to repository visitors.
+Si pones tu archivo de README en el `.github` oculto de tu repositorio, en la raíz o en el directorio `docs`, {% data variables.product.product_name %} lo reconocerá y lo hará emerger automáticamente para los visitantes del repositorio.
 
-If a repository contains more than one README file, then the file shown is chosen from locations in the following order: the `.github` directory, then the repository's root directory, and finally the `docs` directory.
+Si un repositorio contiene más de un archivo README, entonces el archivo que se muestra se elegirá de las ubicaciones en el siguiente orden: el directorio de `.github`, luego el directorio raíz del repositorio y, finalmente, el directorio `docs`.
 
 ![Página principal del repositorio github/scientist y su archivo README](/assets/images/help/repository/repo-with-readme.png)
 
diff --git a/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/customizing-your-repositorys-social-media-preview.md b/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/customizing-your-repositorys-social-media-preview.md
index 9a6c64ac43..9c7cf796f2 100644
--- a/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/customizing-your-repositorys-social-media-preview.md
+++ b/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/customizing-your-repositorys-social-media-preview.md
@@ -43,7 +43,7 @@ Cuando utilices una imagen con transparencia, toma en cuenta cómo se vería con
 
 {% tip %}
 
-**Tip:** If you aren't sure, we recommend using an image with a solid background.
+**Tip:** Si no estás seguro, te recomendamos utilizar una imagen con un fondo sólido.
 {% endtip %}
 
-![Social preview transparency](/assets/images/help/repository/social-preview-transparency.png)
+![Transparencia de vista previa social](/assets/images/help/repository/social-preview-transparency.png)
diff --git a/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository.md b/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository.md
index d3e445d2b2..3db8458e3f 100644
--- a/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository.md
+++ b/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository.md
@@ -106,36 +106,36 @@ Si se inhabilita una política para una {% ifversion ghec or ghae or ghes %}empr
 
 {% data reusables.actions.workflow-permissions-intro %}
 
-Los permisos predeterminados también pueden configurarse en los ajustes de la organización. If your repository belongs to an organization and a more restrictive default has been selected in the organization settings, the same option is selected in your repository settings and the permissive option is disabled.
+Los permisos predeterminados también pueden configurarse en los ajustes de la organización. Si tu repositorio le pertenece a una organización y se seleccionó una opción predeterminada más restrictiva en los ajustes de esta, la misma opción se seleccionará en los ajustes de tu repositorio y la opción permisiva se inhabilitará.
 
 {% data reusables.actions.workflow-permissions-modifying %}
 
 ### Configuring the default `GITHUB_TOKEN` permissions
 
 {% if allow-actions-to-approve-pr-with-ent-repo %}
-By default, when you create a new repository in your personal account, `GITHUB_TOKEN` only has read access for the `contents` scope. If you create a new repository in an organization, the setting is inherited from what is configured in the organization settings.
+Predeterminadamente, cuando creas un repositorio nuevo en tu cuenta personal, el `GITHUB_TOKEN` solo tiene acceso para el alcance `contents`. Si creas un repositorio nuevo en una organización, el ajuste se heredará de lo que se configuró en los ajustes de la organización.
 {% endif %}
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
 {% data reusables.repositories.settings-sidebar-actions-general %}
-1. Under "Workflow permissions", choose whether you want the `GITHUB_TOKEN` to have read and write access for all scopes, or just read access for the `contents` scope.
+1. Debajo de "Permisos de flujo de trabajo", elige si quieres que el `GITHUB_TOKEN` tenga acceso de lectura y escritura para todos los alcances o solo acceso de lectura para el alcance `contents`.
 
    ![Configurar los permisos del GITHUB_TOKEN para este repositorio](/assets/images/help/settings/actions-workflow-permissions-repository{% if allow-actions-to-approve-pr-with-ent-repo %}-with-pr-approval{% endif %}.png)
 
 1. Da clic en **Guardar** para aplicar la configuración.
 
 {% if allow-actions-to-approve-pr-with-ent-repo %}
-### Preventing {% data variables.product.prodname_actions %} from creating or approving pull requests
+### Prevenir que las {% data variables.product.prodname_actions %} creen o aprueben solicitudes de cambio
 
 {% data reusables.actions.workflow-pr-approval-permissions-intro %}
 
-By default, when you create a new repository in your personal account, workflows are not allowed to create or approve pull requests. If you create a new repository in an organization, the setting is inherited from what is configured in the organization settings.
+Predeterminadamente, cuando creas un repositorio nuevo en tu cuenta personal, no se permite que los flujos de trabajo creen o aprueben las solicitudes de cambios. Si creas un repositorio nuevo en una organización, el ajuste se heredará de lo que se configuró en los ajustes de la organización.
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
 {% data reusables.repositories.settings-sidebar-actions-general %}
-1. Under "Workflow permissions", use the **Allow GitHub Actions to create and approve pull requests** setting to configure whether `GITHUB_TOKEN` can create and approve pull requests.
+1. Debajo de "Permisos de flujo de trabajo", utiliza el ajuste **Permitir que las GitHub Actions creen y aprueben solicitudes de cambios** para configurar si el `GITHUB_TOKEN` puede crear y aprobar solicitudes de cambios.
 
    ![Configurar los permisos del GITHUB_TOKEN para este repositorio](/assets/images/help/settings/actions-workflow-permissions-repository-with-pr-approval.png)
 1. Da clic en **Guardar** para aplicar la configuración.
@@ -179,16 +179,16 @@ Tambièn puedes definir un periodo de retenciòn personalizado para un artefacto
 
 {% if actions-cache-policy-apis %}
 
-## Configuring cache storage for a repository
+## Configurar el almacenamiento en caché de un repositorio
 
-{% data reusables.actions.cache-default-size %} However, these default sizes might be different if an enterprise owner has changed them. {% data reusables.actions.cache-eviction-process %}
+{% data reusables.actions.cache-default-size %} Sin embargo, estos tamaños predeterminados podrían ser diferentes si un propietario de empresa los cambió. {% data reusables.actions.cache-eviction-process %}
 
-You can set a total cache storage size for your repository up to the maximum size allowed by the enterprise policy setting.
+Puedes configurar un tamaño de almacenamiento en caché total para tu repositorio hasta un tamaño máximo que permita el ajuste de la política empresarial.
 
-The repository settings for {% data variables.product.prodname_actions %} cache storage can currently only be modified using the REST API:
+Los ajustes de repositorio para el almacenamiento en caché de {% data variables.product.prodname_actions %} actualmente solo se pueden modificar utilizando la API de REST:
 
-* To view the current cache storage limit for a repository, see "[Get GitHub Actions cache usage policy for a repository](/rest/actions/cache#get-github-actions-cache-usage-policy-for-a-repository)."
-* To change the cache storage limit for a repository, see "[Set GitHub Actions cache usage policy for a repository](/rest/actions/cache#set-github-actions-cache-usage-policy-for-a-repository)."
+* Para ver el límite actual de almacenamiento en caché para un repositorio, consulta la sección "[Obtener la política de uso de caché de GitHub Actions para un repositorio](/rest/actions/cache#get-github-actions-cache-usage-policy-for-a-repository)".
+* Para cambiar el límite de almacenamiento en caché de un repositorio, consulta la sección "[Configurar la política de uso de caché de GitHub Actions para un repositorio](/rest/actions/cache#set-github-actions-cache-usage-policy-for-a-repository)".
 
 {% data reusables.actions.cache-no-org-policy %}
 
diff --git a/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-pull-request-reviews-in-your-repository.md b/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-pull-request-reviews-in-your-repository.md
index d7c7bc7623..d9c7d20d6b 100644
--- a/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-pull-request-reviews-in-your-repository.md
+++ b/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-pull-request-reviews-in-your-repository.md
@@ -1,6 +1,6 @@
 ---
-title: Managing pull request reviews in your repository
-intro: You can limit which users can approve or request changes to a pull requests in a public repository.
+title: Administrar las revisiones de las solicitudes de cambios en tu repositorio
+intro: Puedes limitar qué usuarios pueden aprobar o solicitar cambios a las solicitudes de cambios en un repositorio público.
 versions:
   feature: pull-request-approval-limit
 permissions: Repository administrators can limit which users can approve or request changes to a pull request in a public repository.
@@ -14,14 +14,14 @@ shortTitle: Administrar las revisiones de las solicitudes de cambios
 
 Predeterminadamente, en los repositorios públicos, cualquier usuario puede emitir revisiones que aprueben o soliciten cambios a una solicitud de cambios.
 
-You can limit which users are able to submit reviews that approve or request changes to pull requests in your public repository. When you enable code review limits, anyone can comment on pull requests in your public repository, but only people with read access or higher can approve pull requests or request changes.
+Puedes limitar qué usuarios pueden emitir revisiones que aprueben o soliciten cambios a una solicitud de cambios en tu repositorio público. Cuando habilitas los límites de la revisión de código, cualquiera puede comentar en las solicitudes de cambios de tu repositorio público, pero solo las personas con acceso de lectura o superior pueden aprobarlas o solicitar cambios a ellas.
 
-You can also enable code review limits for an organization. If you enable limits for an organization, you will override any limits for individual repositories owned by the organization. For more information, see "[Managing pull request reviews in your organization](/organizations/managing-organization-settings/managing-pull-request-reviews-in-your-organization)"
+También puedes habilitar los límites de revisión de código para una organización. Si habilitas los límites para una organización, sobrescribirás cualquiera de ellos para los repositorios individuales que le pertenezcan a esta. Para obtener más información, consulta la sección "[Administrar las revisiones de solicitudes de cambio en tu organización](/organizations/managing-organization-settings/managing-pull-request-reviews-in-your-organization)"
 
 ## Habilitar los límites de revisión de código
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
-1. Under **Access**, click **Moderation options**. ![Moderation options repository settings](/assets/images/help/repository/access-settings-repositories.png)
+1. Under **Access**, click **Moderation options**. ![Ajustes de repositorio para opciones de moderación](/assets/images/help/repository/access-settings-repositories.png)
 1. Under **Moderation options**, click **Code review limits**. ![Code review limits repositories](/assets/images/help/repository/code-review-limits-repositories.png)
 1. Select or deselect **Limit to users explicitly granted read or higher access**. ![Limit review in repository](/assets/images/help/repository/limit-reviews-in-repository.png)
diff --git a/translations/es-ES/content/repositories/working-with-files/using-files/viewing-a-file.md b/translations/es-ES/content/repositories/working-with-files/using-files/viewing-a-file.md
index f1436a4db6..8e7f4ceb2d 100644
--- a/translations/es-ES/content/repositories/working-with-files/using-files/viewing-a-file.md
+++ b/translations/es-ES/content/repositories/working-with-files/using-files/viewing-a-file.md
@@ -1,6 +1,6 @@
 ---
-title: Viewing a file
-intro: You can view raw file content or trace changes to lines in a file and discover how parts of the file evolved over time.
+title: Ver un archivo
+intro: Puedes ver el contenido sin procesar de los archivos o rastrear cambios en las líneas de un archivo y descubrir cómo evolucionaron las partes de este con el tiempo.
 redirect_from:
   - /articles/using-git-blame-to-trace-changes-in-a-file
   - /articles/tracing-changes-in-a-file
@@ -15,19 +15,19 @@ versions:
   ghec: '*'
 topics:
   - Repositories
-shortTitle: View files and track file changes
+shortTitle: Ver los archivos y rastrear los cambios en ellos
 ---
 
-## Viewing or copying the raw file content
+## Ver o copiar el contenido sin procesar de los archivos
 
-With the raw view, you can view or copy the raw content of a file without any styling.
+Con la vista de contenido sin procesar, puedes ver o copiar el contenido sin procesar de un archivo sin ningún tipo de formato.
 
 {% data reusables.repositories.navigate-to-repo %}
-1. Click the file that you want to view.
-2. In the upper-right corner of the file view, click **Raw**. ![Screenshot of the Raw button in the file header](/assets/images/help/repository/raw-file-button.png)
-3. Optionally, to copy the raw file content, in the upper-right corner of the file view, click **{% octicon "copy" aria-label="The copy icon" %}**.
+1. Haz clic en el archivo que quieras ver.
+2. En la esquina superior derecha de la vista de archivo, haz clic en**Sin procesar**. ![Captura de pantalla del botón "sin procesar" en el encabezado del archivo](/assets/images/help/repository/raw-file-button.png)
+3. Opcionalmente, para copiar el contenido sin procesar del archivo, en la esquina superior derecha de la vista de archivo, haz clic en **{% octicon "copy" aria-label="The copy icon" %}**.
 
-## Viewing the line-by-line revision history for a file
+## Ver el historial de revisión línea por línea de un archivo
 
 Con la vista de último responsable, puedes ver el historial de revisión línea por línea para todo un archivo o ver el historial de revisión de una única línea dentro de un archivo haciendo clic en {% octicon "versions" aria-label="The prior blame icon" %}. Cada vez que hagas clic en {% octicon "versions" aria-label="The prior blame icon" %}, verás la información de revisión anterior para esa línea, incluido quién y cuándo confirmó el cambio.
 
@@ -50,17 +50,17 @@ En un archivo o solicitud de extracción, también puedes utilizar el menú {% o
 
 {% if blame-ignore-revs %}
 
-## Ignore commits in the blame view
+## Ignorar las confirmaciones en la vista de último responsable
 {% note %}
 
-**Note:** Ignoring commits in the blame view is currently in public beta and subject to change.
+**Nota:** El ignorar las confirmaciones en la vista de último responsable está actualmente en beta público y está sujeto a cambios.
 
 {% endnote %}
 
-All revisions specified in the `.git-blame-ignore-revs` file, which must be in the root directory of your repository, are hidden from the blame view using Git's `git blame --ignore-revs-file` configuration setting. For more information, see [`git blame --ignore-revs-file`](https://git-scm.com/docs/git-blame#Documentation/git-blame.txt---ignore-revs-fileltfilegt) in the Git documentation.
+Todas las revisiones que se especifican en el archivo `.git-blame-ignore-revs`, el cual debe estar en el directorio raíz de tu repositorio, se ocultan de la vista de último responsable utilizando el ajuste de configuración `git blame --ignore-revs-file` de Git. Para obtener más información, consulta [`git blame --ignore-revs-file`](https://git-scm.com/docs/git-blame#Documentation/git-blame.txt---ignore-revs-fileltfilegt) en la documentación de Git.
 
-1. In the root directory of your repository, create a file named `.git-blame-ignore-revs`.
-2. Add the commit hashes you want to exclude from the blame view to that file. We recommend the file to be structured as follows, including comments:
+1. En el directorio de tu repositorio, crea un archivo llamado `.git-blame-ignore-revs`.
+2. Agrega los hashes de confirmación que quieras excluir de la vista de último responsable a ese archivo. Te recomendamos que el archivo se estructure de la siguiente forma, incluyendo los comentarios:
 
     ```ini
     # .git-blame-ignore-revs
@@ -70,13 +70,13 @@ All revisions specified in the `.git-blame-ignore-revs` file, which must be in t
     69d029cec8337c616552756310748c4a507bd75a
     ```
 
-3. Commit and push the changes.
+3. Confirma y sube los cambios.
 
-Now when you visit the blame view, the listed revisions will not be included in the blame. You'll see an **Ignoring revisions in .git-blame-ignore-revs** banner indicating that some commits may be hidden:
+Ahora, cuando visites la vista de último responsable, las revisiones listadas no se incluirán en ella. Verás un letrero de **ignorando las revisiones en .git-blame-ignore-revs** indicando que algunas confirmaciones podrían estar ocultas:
 
-![Screenshot of a banner on the blame view linking to the .git-blame-ignore-revs file](/assets/images/help/repository/blame-ignore-revs-file.png)
+![Captura de pantalla de un letrero con la vista de último responsable que enlaza al archivo .git-blame-ignore-revs](/assets/images/help/repository/blame-ignore-revs-file.png)
 
-This can be useful when a few commits make extensive changes to your code. You can use the file when running `git blame` locally as well:
+Esto puede ser útil cuando algunas cuantas confirmaciones hacen cambios extensos a tu código. Puedes utilizar el archivo al ejecutar `git blame` localmente también:
 
 ```shell
 git blame --ignore-revs-file .git-blame-ignore-revs
diff --git a/translations/es-ES/content/rest/actions/secrets.md b/translations/es-ES/content/rest/actions/secrets.md
index a83c762ae3..63aebbda21 100644
--- a/translations/es-ES/content/rest/actions/secrets.md
+++ b/translations/es-ES/content/rest/actions/secrets.md
@@ -14,6 +14,6 @@ versions:
 
 ## About the Secrets API
 
-The {% data variables.product.prodname_actions %} Secrets API lets you create, update, delete, and retrieve information about encrypted secrets that can be used in {% data variables.product.prodname_actions %} workflows. {% data reusables.actions.about-secrets %} Para obtener más información, consulta la sección "[Crear y utilizar secretos cifrados](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)".
+La API de secretos de {% data variables.product.prodname_actions %} te permite crear, actualizar, borrar y recuperar la información sobre los secretos cifrados que puede utilizarse en los flujos de trabajo de {% data variables.product.prodname_actions %}. {% data reusables.actions.about-secrets %} Para obtener más información, consulta la sección "[Crear y utilizar secretos cifrados](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)".
 
 La {% data reusables.actions.actions-authentication %} en las {% data variables.product.prodname_github_apps %} debe contar con el permiso de `secrets` para utilizar esta API. Los usuarios autenticados deben tener acceso de colaborador en el repositorio para crear, actualizar o leer los secretos.
diff --git a/translations/es-ES/content/rest/interactions/orgs.md b/translations/es-ES/content/rest/interactions/orgs.md
index 1d41ba5cfe..ed37964350 100644
--- a/translations/es-ES/content/rest/interactions/orgs.md
+++ b/translations/es-ES/content/rest/interactions/orgs.md
@@ -13,7 +13,7 @@ allowTitleToDifferFromFilename: true
 
 ## About the Organization interactions API
 
-The Organization interactions API allows organization owners to temporarily restrict which type of user can comment, open issues, or create pull requests in the organization's public repositories. {% data reusables.interactions.interactions-detail %} Aquí puedes aprender más sobre los tipos de usuario de {% data variables.product.product_name %}:
+La API de interacciones de organización permite que los propietarios de la organización restrinjan temporalmente qué tipo de usuarios pueden comentar, abrir propuestas o crear solicitudes de cambios en los repositorios públicos de dicha organización. {% data reusables.interactions.interactions-detail %} Aquí puedes aprender más sobre los tipos de usuario de {% data variables.product.product_name %}:
 
 * {% data reusables.interactions.existing-user-limit-definition %} en la organización.
 * {% data reusables.interactions.contributor-user-limit-definition %} en la organización.
diff --git a/translations/es-ES/content/search-github/getting-started-with-searching-on-github/about-searching-on-github.md b/translations/es-ES/content/search-github/getting-started-with-searching-on-github/about-searching-on-github.md
index c8088ea458..d83d08b6d5 100644
--- a/translations/es-ES/content/search-github/getting-started-with-searching-on-github/about-searching-on-github.md
+++ b/translations/es-ES/content/search-github/getting-started-with-searching-on-github/about-searching-on-github.md
@@ -70,13 +70,13 @@ Si utilizas tanto {% data variables.product.prodname_dotcom_the_website %} como
 
 {% else %}
 
-If you use both {% data variables.product.prodname_dotcom_the_website %} and {% data variables.product.product_name %}, and an enterprise owner has enabled {% data variables.product.prodname_unified_search %}, you can search across both environments at the same time from {% data variables.product.product_name %}. For more information about how enterprise owners can enable {% data variables.product.prodname_unified_search %}, see "[Enabling {% data variables.product.prodname_unified_search %} for your enterprise](/admin/configuration/configuring-github-connect/enabling-unified-search-for-your-enterprise)."
+Si utilizas tanto el {% data variables.product.prodname_dotcom_the_website %} como {% data variables.product.product_name %} y un propietario de empresa habilitó la {% data variables.product.prodname_unified_search %}, puedes buscar en ambos ambientes al mismo tiempo desde {% data variables.product.product_name %}. Para obtener más información sobre cómo los propietarios de las empresas pueden habilitar la {% data variables.product.prodname_unified_search %}, consulta la sección "[Habilitar la {% data variables.product.prodname_unified_search %} para tu empresa](/admin/configuration/configuring-github-connect/enabling-unified-search-for-your-enterprise)".
 
 Tu propietario de empresa en {% data variables.product.product_name %} puede separar y habilitar la {% data variables.product.prodname_unified_search %} para todos los repositorios públicos {% data variables.product.prodname_dotcom_the_website %} y para los repositorios privados que pertenecen a la organización o empresa de {% data variables.product.prodname_dotcom_the_website %} que está conectada a {% data variables.product.product_name %} mediante {% data variables.product.prodname_github_connect %}.
 
-Before you can use {% data variables.product.prodname_unified_search %} for private repositories, you must connect your personal accounts on {% data variables.product.prodname_dotcom_the_website %} and {% data variables.product.product_name %}. Para obtener más información, consulta la sección "[Habilitar la búsqueda de repositorios en {% data variables.product.prodname_dotcom_the_website %} desde tu ambiente empresarial privado](/search-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-from-your-private-enterprise-environment)".
+Antes de que puedas utilizar la {% data variables.product.prodname_unified_search %} para los repositorios privados, debes conectar tus cuenta spersonales en {% data variables.product.prodname_dotcom_the_website %} y {% data variables.product.product_name %}. Para obtener más información, consulta la sección "[Habilitar la búsqueda de repositorios en {% data variables.product.prodname_dotcom_the_website %} desde tu ambiente empresarial privado](/search-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-from-your-private-enterprise-environment)".
 
-When you search from {% data variables.product.product_name %}, only private repositories that you have access to and that are owned by the connected organization or enterprise account will be included in search results. Ni tú ni nadie más podrá buscar en los repositorios privados que le pertenezcan a tu cuenta personal de {% data variables.product.prodname_dotcom_the_website %} desde {% data variables.product.product_name %}.
+Cuando buscas desde {% data variables.product.product_name %}, solo se incluirán en los resultados de la búsqueda aquellos repositorios a los cuales tengas acceso y que le pertenezcan a la cuenta empresarial o de organización conectada. Ni tú ni nadie más podrá buscar en los repositorios privados que le pertenezcan a tu cuenta personal de {% data variables.product.prodname_dotcom_the_website %} desde {% data variables.product.product_name %}.
 
 Para limitar tu búsqueda a un solo ambiente, puedes utilizar una opción de filtro en la {% data variables.search.advanced_url %} o puedes utilizar el prefijo de búsqueda `environment:`. Para solo buscar contenido en {% data variables.product.product_name %}, usa la sintaxis de búsqueda `environment:local`. Para solo buscar contenido en {% data variables.product.prodname_dotcom_the_website %}, usa la sintaxis de búsqueda `environment:github`.
 {% endif %}
diff --git a/translations/es-ES/content/support/contacting-github-support/providing-data-to-github-support.md b/translations/es-ES/content/support/contacting-github-support/providing-data-to-github-support.md
index d36f20fc42..48f06ee2cf 100644
--- a/translations/es-ES/content/support/contacting-github-support/providing-data-to-github-support.md
+++ b/translations/es-ES/content/support/contacting-github-support/providing-data-to-github-support.md
@@ -89,7 +89,7 @@ Después de que emites tu solicitud de soporte, podríamos pedirte que compartas
 - `collectd/logs/collectd.log`: registros Collectd
 - `mail-logs/mail.log`: registros de entrega por correo electrónico SMTP
 
-For more information, see "[About the audit log for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/about-the-audit-log-for-your-enterprise)."
+Para obtener más información, consulta la sección "[Acerca de las bitácoras de auditoría de tu empresa](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/about-the-audit-log-for-your-enterprise)".
 
 Los paquetes de soporte incluyen registros de los dos últimos días. Para obtener registros de los últimos siete días, puedes descargar un paquete de soporte extendido. Para obtener más información, consulta "[Crear y compartir paquete de soporte extendido](#creating-and-sharing-extended-support-bundles)".
 
diff --git a/translations/es-ES/content/support/contacting-github-support/viewing-and-updating-support-tickets.md b/translations/es-ES/content/support/contacting-github-support/viewing-and-updating-support-tickets.md
index 3589acbaa5..014674512d 100644
--- a/translations/es-ES/content/support/contacting-github-support/viewing-and-updating-support-tickets.md
+++ b/translations/es-ES/content/support/contacting-github-support/viewing-and-updating-support-tickets.md
@@ -14,28 +14,28 @@ topics:
 
 {% data reusables.support.zendesk-old-tickets %}
 
-You can use the [GitHub Support Portal](https://support.github.com/) to view current and past support tickets and respond to {% data variables.contact.github_support %}.
+Puedes usar el [Portal de soporte de GitHub](https://support.github.com/) para ver los tickets de soporte actuales y anteriores y responder a {% data variables.contact.github_support %}.
 
 {% ifversion ghes or ghec %}
 {% data reusables.enterprise-accounts.support-entitlements %}
 {% endif %}
 
-## Viewing your support tickets
+## Ver tus tickets de soporte
 
 {% data reusables.support.view-open-tickets %}
-1. Under the text box, you can read the comment history. The most recent response is at the top. ![Screenshot of support ticket comment history, with the most recent response at the top.](/assets/images/help/support/support-recent-response.png)
+1. Debajo de la caja de texto, puedes leer el historial de los comentarios. La respuesta más reciente está hasta arriba. ![Captura de pantalla del historial de comentarios del ticket de soporte con la respuesta más reciente hasta arriba.](/assets/images/help/support/support-recent-response.png)
 
-## Updating support tickets
+## Actualizar los tickets de soporte
 
 {% data reusables.support.view-open-tickets %}
-1. Optionally, if the issue is resolved, under the text box, click **Close ticket**. ![Screenshot showing location of the "Close ticket" button.](/assets/images/help/support/close-ticket.png)
-1. To respond to GitHub Support and add a new comment to the ticket, type your response in the text box. ![Screenshot of the "Add a comment" text field.](/assets/images/help/support/new-comment-field.png)
-1. To add your comment to the ticket, click **Comment**. ![Screenshot of the "Comment" button.](/assets/images/help/support/add-comment.png)
+1. Opcionalmente, si el problema se resuelve, debajo de la caja de texto, haz clic en **Cerrar ticket**. ![Captura de pantalla que muestra la ubicación del botón "Cerrar ticket".](/assets/images/help/support/close-ticket.png)
+1. Para responder al Soporte de GitHub y agregar un comentario nuevo al ticket, escribe tu respuesta en la caja de texto. ![Captura de pantalla del campo de texto "Agregar un comentario".](/assets/images/help/support/new-comment-field.png)
+1. Para agregar tu comentario al ticket, haz clic en **Comentar**. ![Captura de pantalla del botón "Comentar".](/assets/images/help/support/add-comment.png)
 
 {% ifversion ghec or ghes %}
-## Collaborating on support tickets
+## Colaborar en los tickets de soporte
 
-You can collaborate with your colleagues on support tickets using the support portal. Owners, billing managers, and other enterprise members with support entitlements can view tickets associated with an enterprise account or an organization managed by an enterprise account. Para obtener más información, consulta la sección "[Administrar la titularidad de soporte para tu empresa](/enterprise-cloud@latest/admin/user-management/managing-users-in-your-enterprise/managing-support-entitlements-for-your-enterprise)".
+Puedes colaborar con tus colegas en los tickets de soporte utilizando el portal de soporte. Los propietarios, gerentes de facturación y otros miembros empresariales con derechos de soporte pueden ver los tickets asociados con una cuenta empresarial o una organización que administre una cuenta empresarial. Para obtener más información, consulta la sección "[Administrar la titularidad de soporte para tu empresa](/enterprise-cloud@latest/admin/user-management/managing-users-in-your-enterprise/managing-support-entitlements-for-your-enterprise)".
 
 Adicionalmente a poder ver los tickets, también puedes agregar comentarios para apoyarlos si tu dirección de correo electrónico se copia en el ticket o si la persona que lo abrió utilizó una dirección de correo electrónico con un dominio que esté verificado en la cuenta u organización empresarial que administra una cuenta empresarial. Para obtener más información sobre cómo verificar un dominio, consulta las secciones "[Verificar o aprobar un dominio para tu empresa](/enterprise-cloud@latest/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise)" y "[Verificar o aprobar un dominio para tu organización](/enterprise-cloud@latest/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization)".
 
diff --git a/translations/es-ES/content/support/learning-about-github-support/about-ticket-priority.md b/translations/es-ES/content/support/learning-about-github-support/about-ticket-priority.md
index eafaacf2d3..7934784237 100644
--- a/translations/es-ES/content/support/learning-about-github-support/about-ticket-priority.md
+++ b/translations/es-ES/content/support/learning-about-github-support/about-ticket-priority.md
@@ -57,7 +57,7 @@ Para calificar para una respuesta prioritaria, debes hacer lo siguiente:
 
 {% note %}
 
-**Note:** Questions do not qualify for a priority response if they are submitted on a local holiday in your jurisdiction.
+**Nota:** Las preguntas no califican para una respuesta prioritaria si se emiten en un día feriado local de tu jurisdicción.
 
 {% endnote %}
 
diff --git a/translations/es-ES/data/learning-tracks/admin.yml b/translations/es-ES/data/learning-tracks/admin.yml
index 3e94b82af3..ccb820d6c4 100644
--- a/translations/es-ES/data/learning-tracks/admin.yml
+++ b/translations/es-ES/data/learning-tracks/admin.yml
@@ -127,5 +127,4 @@ get_started_with_your_enterprise_account:
     - /admin/user-management/managing-users-in-your-enterprise/inviting-people-to-manage-your-enterprise
     - /admin/user-management/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise
     - /admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise
-    - /admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise
-    - /admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise
+    - /admin/policies/enforcing-policies-for-your-enterprise/about-enterprise-policies
diff --git a/translations/es-ES/data/release-notes/enterprise-server/3-1/21.yml b/translations/es-ES/data/release-notes/enterprise-server/3-1/21.yml
index 2bf7279ba8..73df7415cd 100644
--- a/translations/es-ES/data/release-notes/enterprise-server/3-1/21.yml
+++ b/translations/es-ES/data/release-notes/enterprise-server/3-1/21.yml
@@ -1,16 +1,16 @@
 date: '2022-05-17'
 sections:
   security_fixes:
-    - '**MEDIUM:** A security issue in nginx resolver was identified, where an attacker who could forge UDP packets from the DNS server could cause 1-byte memory overwrite, resulting in worker process crashes or other potentially damaging impacts. The vulnerability has been assigned [CVE-2021-23017](https://nvd.nist.gov/vuln/detail/CVE-2021-23017).'
-    - 'Updated the `actions/checkout@v2` and `actions/checkout@v3` actions to address new vulnerabilities announced in the [Git security enforcement blog post](https://github.blog/2022-04-12-git-security-vulnerability-announced/).'
+    - '**MEDIA:** Se identificó una propuesta de seguridad en el resolutor de ngnix, en donde un atacante pudo haber falsificado paquetes de UDP desde el servidor DNS y pudo ocasionar una sobre escritura de memoria en bytes, dando como resultado que fallara un proceso trabajador u otros impactos dañinos potenciales. Se asingó el [CVE-2021-23017](https://nvd.nist.gov/vuln/detail/CVE-2021-23017) a la vulnerabilidad.'
+    - 'Se actualizaron las acciones `actions/checkout@v2` y `actions/checkout@v3` para abordar las vulnerabilidades nuevas que se anunciaron en la [Publicación del blog de refuerzo de seguridad de Git](https://github.blog/2022-04-12-git-security-vulnerability-announced/).'
     - 'Los paquetes se actualizaron a las últimas versiones de seguridad.'
   bugs:
     - 'In some cluster topologies, the `ghe-cluster-status` command left behind empty directories in `/tmp`.'
     - 'SNMP incorrectly logged a high number of `Cannot statfs` error messages to syslog.'
-    - 'For instances configured with SAML authentication and built-in fallback enabled, built-in users would get stuck in a “login” loop when attempting to sign in from the page generated after logging out.'
+    - 'Para el caso de las instancias configuradas con la autenticación de SAML y con la recuperación de fallos integrada habilitada, los usuarios integrados se atoraron en un bucle de "inicio de sesión" al intentar iniciar sesión desde la página generada después de salir de sesión.'
     - 'When using SAML encrypted assertions, some assertions were not correctly marking SSH keys as verified.'
   changes:
-    - 'In high availability configurations, clarify that the replication overview page in the Management Console only displays the current replication configuration, not the current replication status.'
+    - 'En las configuraciones de disponibilidad alta, se aclara que la página de resumen de replicación en la consola de administración solo muestra la configuración de replicación actual y no el estado de replicación actual.'
     - 'When enabling {% data variables.product.prodname_registry %}, clarify that using a Shared Access Signature (SAS) token as connection string is not supported.'
     - 'Support bundles now include the row count of tables stored in MySQL.'
   known_issues:
diff --git a/translations/es-ES/data/release-notes/enterprise-server/3-3/2.yml b/translations/es-ES/data/release-notes/enterprise-server/3-3/2.yml
index 6f863263f4..0b7d03bc0d 100644
--- a/translations/es-ES/data/release-notes/enterprise-server/3-3/2.yml
+++ b/translations/es-ES/data/release-notes/enterprise-server/3-3/2.yml
@@ -11,7 +11,7 @@ sections:
     - 'Los ejecutores auto-hospedados de las acciones fallaron en actualizarse a sí mismos o en ejecutar jobs nuevos después de mejorar desde una instalación anterior de la GHES.'
     - 'Los ajustes de almacenamiento no pudieron validarse al configurar MinIO como almacenamiento de blobs para GitHub Packages.'
     - 'Los ajustes de almacenamiento de las GitHub Actions no pudieron validarse y guardarse en la Consola de Administración cuando se seleccionó "Forzar estilo de ruta".'
-    - 'Actions would be left in a stopped state after an update with maintenance mode set.'
+    - 'Las acciones se quedarán en un estado de detenido después de una actualización que se haya ajustado en modo de mantenimiento.'
     - 'El ejecutar `ghe-config-apply` pudo fallar en ocasiones debido a problemas con los permisos en /data/user/tmp/pages`.'
     - 'El botón de guardar en la consola de almacenamiento no se pudo alcanzar desplazándose en buscadores de resolución menor.'
     - 'Las gráficas de monitoreo de tráfico de almacenamiento e IOPS no se actualizaron después de la mejora de versión de collectd.'
diff --git a/translations/es-ES/data/release-notes/enterprise-server/3-3/8.yml b/translations/es-ES/data/release-notes/enterprise-server/3-3/8.yml
index 7825e41c9e..36e33217d5 100644
--- a/translations/es-ES/data/release-notes/enterprise-server/3-3/8.yml
+++ b/translations/es-ES/data/release-notes/enterprise-server/3-3/8.yml
@@ -1,13 +1,13 @@
 date: '2022-05-17'
 sections:
   security_fixes:
-    - '**MEDIUM:** A security issue in nginx resolver was identified, where an attacker who could forge UDP packets from the DNS server could cause 1-byte memory overwrite, resulting in worker process crashes or other potentially damaging impacts. The vulnerability has been assigned [CVE-2021-23017](https://nvd.nist.gov/vuln/detail/CVE-2021-23017).'
-    - 'Updated the `actions/checkout@v2` and `actions/checkout@v3` actions to address new vulnerabilities announced in the [Git security enforcement blog post](https://github.blog/2022-04-12-git-security-vulnerability-announced/).'
+    - '**MEDIA:** Se identificó una propuesta de seguridad en el resolutor de ngnix, en donde un atacante pudo haber falsificado paquetes de UDP desde el servidor DNS y pudo ocasionar una sobre escritura de memoria en bytes, dando como resultado que fallara un proceso trabajador u otros impactos dañinos potenciales. Se asingó el [CVE-2021-23017](https://nvd.nist.gov/vuln/detail/CVE-2021-23017) a la vulnerabilidad.'
+    - 'Se actualizaron las acciones `actions/checkout@v2` y `actions/checkout@v3` para abordar las vulnerabilidades nuevas que se anunciaron en la [Publicación del blog de refuerzo de seguridad de Git](https://github.blog/2022-04-12-git-security-vulnerability-announced/).'
     - 'Los paquetes se actualizaron a las últimas versiones de seguridad.'
   bugs:
     - 'In some cluster topologies, the `ghe-cluster-status` command left behind empty directories in `/tmp`.'
     - 'SNMP incorrectly logged a high number of `Cannot statfs` error messages to syslog'
-    - 'For instances configured with SAML authentication and built-in fallback enabled, built-in users would get stuck in a “login” loop when attempting to sign in from the page generated after logging out.'
+    - 'Para el caso de las instancias configuradas con la autenticación de SAML y con la recuperación de fallos integrada habilitada, los usuarios integrados se atoraron en un bucle de "inicio de sesión" al intentar iniciar sesión desde la página generada después de salir de sesión.'
     - 'Attempts to view the `git fsck` output from the `/stafftools/repositories/:owner/:repo/disk` page would fail with a `500 Internal Server Error`.'
     - 'When using SAML encrypted assertions, some assertions were not correctly marking SSH keys as verified.'
     - 'Videos uploaded to issue comments would not be rendered properly.'
@@ -15,7 +15,7 @@ sections:
     - 'When using GitHub Enterprise Importer to import a repository, some issues would fail to import due to incorrectly configured project timeline events.'
     - 'When using `ghe-migrator`, a migration would fail to import video file attachments in issues and pull requests.'
   changes:
-    - 'In high availability configurations, clarify that the replication overview page in the Management Console only displays the current replication configuration, not the current replication status.'
+    - 'En las configuraciones de disponibilidad alta, se aclara que la página de resumen de replicación en la consola de administración solo muestra la configuración de replicación actual y no el estado de replicación actual.'
     - 'When enabling {% data variables.product.prodname_registry %}, clarify that using a Shared Access Signature (SAS) token as connection string is not currently supported.'
     - 'Support bundles now include the row count of tables stored in MySQL.'
     - 'When determining which repository networks to schedule maintenance on, we no longer count the size of unreachable objects.'
@@ -30,4 +30,3 @@ sections:
     - 'El registor de npm del {% data variables.product.prodname_registry %} ya no regresa un valor de tiempo en las respuestas de metadatos. Esto se hizo para permitir mejoras de rendimiento sustanciales. Seguimos teniendo todos los datos necesarios para devolver un valor de tiempo como parte de la respuesta de metadatos y terminaremos de devolver este valor ene l futuro una vez que hayamos resuelto los problemas de rendimiento existentes.'
     - 'Los límites de recursos que son específicos para procesar ganchos de pre-recepción podrían ocasionar que fallen algunos ganchos de pre-recepción.'
     - 'Los ajustes de almacenamiento de {% data variables.product.prodname_actions %} no pueden validarse y guardarse en la {% data variables.enterprise.management_console %} cuando se selecciona "Forzar estilo de ruta" y, en su lugar, debe configurarse la utilidad de línea de comando `ghe-actions-precheck`.'
-    - '{% data variables.product.prodname_ghe_server %} 3.3 instances installed on Azure and provisioned with 32+ CPU cores would fail to launch, due to a bug present in the current Linux kernel. [Updated: 2022-04-08]'
diff --git a/translations/es-ES/data/release-notes/enterprise-server/3-4/3.yml b/translations/es-ES/data/release-notes/enterprise-server/3-4/3.yml
index 5558cff86a..06e92a019f 100644
--- a/translations/es-ES/data/release-notes/enterprise-server/3-4/3.yml
+++ b/translations/es-ES/data/release-notes/enterprise-server/3-4/3.yml
@@ -1,15 +1,15 @@
 date: '2022-05-17'
 sections:
   security_fixes:
-    - '**MEDIUM:** A security issue in nginx resolver was identified, where an attacker who could forge UDP packets from the DNS server could cause 1-byte memory overwrite, resulting in worker process crashes or other potentially damaging impacts. The vulnerability has been assigned [CVE-2021-23017](https://nvd.nist.gov/vuln/detail/CVE-2021-23017).'
-    - 'Updated the `actions/checkout@v2` and `actions/checkout@v3` actions to address new vulnerabilities announced in the [Git security enforcement blog post](https://github.blog/2022-04-12-git-security-vulnerability-announced/).'
+    - '**MEDIA:** Se identificó una propuesta de seguridad en el resolutor de ngnix, en donde un atacante pudo haber falsificado paquetes de UDP desde el servidor DNS y pudo ocasionar una sobre escritura de memoria en bytes, dando como resultado que fallara un proceso trabajador u otros impactos dañinos potenciales. Se asingó el [CVE-2021-23017](https://nvd.nist.gov/vuln/detail/CVE-2021-23017) a la vulnerabilidad.'
+    - 'Se actualizaron las acciones `actions/checkout@v2` y `actions/checkout@v3` para abordar las vulnerabilidades nuevas que se anunciaron en la [Publicación del blog de refuerzo de seguridad de Git](https://github.blog/2022-04-12-git-security-vulnerability-announced/).'
     - 'Los paquetes se actualizaron a las últimas versiones de seguridad.'
   bugs:
     - 'In some cluster topologies, the `ghe-cluster-status` command left behind empty directories in `/tmp`.'
     - 'SNMP incorrectly logged a high number of `Cannot statfs` error messages to syslog.'
     - 'When adding custom patterns and providing non-UTF8 test strings, match highlighting was incorrect.'
     - 'LDAP users with an underscore character (`_`) in their user names can now login successfully.'
-    - 'For instances configured with SAML authentication and built-in fallback enabled, built-in users would get stuck in a “login” loop when attempting to sign in from the page generated after logging out.'
+    - 'Para el caso de las instancias configuradas con la autenticación de SAML y con la recuperación de fallos integrada habilitada, los usuarios integrados se atoraron en un bucle de "inicio de sesión" al intentar iniciar sesión desde la página generada después de salir de sesión.'
     - 'After enabling SAML encrypted assertions with Azure as identity provider, the sign in page would fail with a `500` error.'
     - 'Character key shortcut preferences weren''t respected.'
     - 'Attempts to view the `git fsck` output from the `/stafftools/repositories/:owner/:repo/disk` page would fail with a `500 Internal Server Error`.'
@@ -18,7 +18,7 @@ sections:
     - 'When using GitHub Enterprise Importer to import a repository, some issues would fail to import due to incorrectly configured project timeline events.'
     - 'When using `ghe-migrator`, a migration would fail to import video file attachments in issues and pull requests.'
   changes:
-    - 'In high availability configurations, clarify that the replication overview page in the Management Console only displays the current replication configuration, not the current replication status.'
+    - 'En las configuraciones de disponibilidad alta, se aclara que la página de resumen de replicación en la consola de administración solo muestra la configuración de replicación actual y no el estado de replicación actual.'
     - 'The Nomad allocation timeout for Dependency Graph has been increased to ensure post-upgrade migrations can complete.'
     - 'When enabling {% data variables.product.prodname_registry %}, clarify that using a Shared Access Signature (SAS) token as connection string is not currently supported.'
     - 'Support bundles now include the row count of tables stored in MySQL.'
diff --git a/translations/es-ES/data/release-notes/enterprise-server/3-5/0-rc1.yml b/translations/es-ES/data/release-notes/enterprise-server/3-5/0-rc1.yml
index d445ab3f00..e203119371 100644
--- a/translations/es-ES/data/release-notes/enterprise-server/3-5/0-rc1.yml
+++ b/translations/es-ES/data/release-notes/enterprise-server/3-5/0-rc1.yml
@@ -9,7 +9,7 @@ sections:
         - "You can now configure an allow list of IP addresses that can access application services on your GitHub Enterprise Server instance while maintenance mode is enabled. Administrators who visit the instance's web interface from an allowed IP address can validate the instance's functionality post-maintenance and before disabling maintenance mode. For more information, see \"[Enabling and scheduling maintenance mode](/admin/configuration/configuring-your-enterprise/enabling-and-scheduling-maintenance-mode#validating-changes-in-maintenance-mode-using-the-ip-exception-list).\"\n"
     - heading: 'Custom repository roles are generally available'
       notes:
-        - "With custom repository roles, organizations now have more granular control over the repository access permissions they can grant to users. For more information, see \"[Managing custom repository roles for an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization).\"\n\nA custom repository role is created by an organization owner, and is available across all repositories in that organization. Each role can be given a custom name, and a description. It can be configured from a set of over 40 fine grained permissions. Once created, repository admins can assign a custom role to any user, team or outside collaborator in their repository.\n\nCustom repository roles can be created, viewed, edited and deleted via the new **Repository roles** tab in an organization's settings. A maximum of 3 custom roles can be created within an organization.\n\nCustom repository roles are also fully supported in the GitHub Enterprise Server REST APIs. The Organizations API can be used to list all custom repository roles in an organization, and the existing APIs for granting repository access to individuals and teams have been extended to support custom repository roles. For more information, see \"[Organizations](/rest/reference/orgs#list-custom-repository-roles-in-an-organization)\" in the REST API documentation.\n"
+        - "Con los roles de repositorio personalizados, las organizaciones ahora tienen un control más granular sobre los permisos de acceso a los repositorios que pueden otorgar a los usuarios. Para obtener más información, consulta la sección \"[Administrar los roles de repositorio personalizados para una organización] (/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization)\".\n\nUn organizador es quien crea el rol de repositorio personalizado y este está disponible en todos los repositorios de dicha organización. Se puede otorgar un nombre y descripción personalizados a cada rol. Este puede configurarse desde un conjunto de 40 permisos específicos. Una vez que se crea, los administradores de repositorio pueden asignar un rol personalizado a cualquier usuario, equipo o colaborador externo.\n\nLos roles de repositorio personalizados pueden crearse, verse, editarse y borrarse a través de la nueva pestaña de **Roles de repositorio** en los ajustes de una organización. Se puede crear un máximo de 3 roles personalizados dentro de una organización.\n\nLos roles de repositorio también son totalmente compatibles en las API de REST de GitHub Enterprise. La API de organizaciones se puede utilizar para listar todos los roles de repositorio personalizados en una organización y las API existentes para otorgar acceso a los repositorios para individuos y equipos tienen soporte extendido para los roles de repositorio personalizados. Para obtener más información, consulta la sección \"[Organizations](/rest/reference/orgs#list-custom-repository-roles-in-an-organization)\" en la documentación de la API de REST.\n"
     - heading: 'GitHub Container registry in public beta'
       notes:
         - "The GitHub Container registry (GHCR) is now available in GitHub Enterprise Server 3.5 as a public beta, offering developers the ability to publish, download, and manage containers. GitHub Packages container support implements the OCI standards for hosting Docker images. For more information, see \"[GitHub Container registry](/packages/working-with-a-github-packages-registry/working-with-the-container-registry).\"\n"
@@ -18,7 +18,7 @@ sections:
         - "Dependabot version and security updates are now generally available in GitHub Enterprise Server 3.5. All the popular ecosystems and features that work on GitHub.com repositories now can be set up on your GitHub Enterprise Server instance. Dependabot on GitHub Enterprise Server requires GitHub Actions and a pool of self-hosted Dependabot runners, GitHub Connect enabled, and Dependabot enabled by an admin.\n\nFollowing on from the public beta release, we will be supporting the use of GitHub Actions runners hosted on a Kubernetes setup.\n\nFor more information, see \"[Setting up Dependabot updates](https://docs.github.com/en/enterprise-server@3.5/admin/github-actions/enabling-github-actions-for-github-enterprise-server/setting-up-dependabot-updates).\"\n"
     - heading: 'Server Statistics in public beta'
       notes:
-        - "You can now analyze how your team works, understand the value you get from GitHub Enterprise Server, and help us improve our products by reviewing your instance's usage data and sharing this aggregate data with GitHub. You can use your own tools to analyze your usage over time by downloading your data in a CSV or JSON file or by accessing it using the REST API. To see the list of aggregate metrics collected, see \"[About Server Statistics](/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/about-server-statistics#server-statistics-data-collected).\" Server Statistics data includes no personal data nor GitHub content, such as code, issues, comments, or pull requests content.  For a better understanding of how we store and secure Server Statistics data, see \"[GitHub Security](https://github.com/security).\"  For more information about Server Statistics, see \"[Analyzing how your team works with Server Statistics](/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics).\" This feature is available in public beta.\n"
+        - "Ahora puedes analizar la forma en la que trabaja tu equipo, entender el valor que obtienes de GitHub Enterprise Server y ayudarnos a mejorar nuestros productos si revisas los daos de uso de tu instancia y compartes estos datos agregados con GitHub. Puedes utilizar tus propias herramientas para analizar tu uso a lo largo del tiempo si descargas los datos en un archivo CSV o JSON o si accedes a ellos utilizando la API de REST. Para ver una lista de métricas agregadas que se recolectan, consulta la sección \"[Acerca de las estadísticas de servidor](/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/about-server-statistics#server-statistics-data-collected)\". Los datos de estadística de servidor no incluyen datos personales ni contenido de GitHub, tal como código, propuestas, comentarios o contenido de solicitudes de cambios. Para entender mejor el cómo almacenamos y aseguramos datos de estadísticas de servidor, consulta la sección \"[Seguridad de GitHub](https://github.com/security)\". Para obtener más información sobre las estadísticas de servidor, consulta la sección \"[Analizar la forma en la que trabaja tu equipo con las estadísticas de servidor](/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics)\". Esta característica está disponible en beta público.\n"
     - heading: 'GitHub Actions rate limiting is now configurable'
       notes:
         - "Site administrators can now enable and configure a rate limit for GitHub Actions. By default, the rate limit is disabled. When workflow jobs cannot immediately be assigned to an available runner, they will wait in a queue until a runner is available. However, if GitHub Actions experiences a sustained high load, the queue can back up faster than it can drain and the performance of the GitHub Enterprise Server instance may degrade. To avoid this, an administrator can configure a rate limit. When the rate limit is exceeded, additional workflow runs will fail immediately rather than being put in the queue. Once the rate has stabilized below the threshold, new runs can be queued again. For more information, see \"[Configuring rate limits](/admin/configuration/configuring-your-enterprise/configuring-rate-limits#configuring-rate-limits-for-github-actions).\"\n"
@@ -76,7 +76,7 @@ sections:
         - "GitHub Advanced Security customers can now dry run custom secret scanning patterns at the organization or repository level. Dry runs allow people with owner or admin access to review and hone their patterns before publishing them and generating alerts. You can compose a pattern, then use **Save and dry run** to retrieve results. The scans typically take just a few seconds, but GitHub Enterprise Server will also notify organization owners or repository admins via email when dry run results are ready. For more information, see \"[About secret scanning](/code-security/secret-scanning/about-secret-scanning#about-secret-scanning-for-private-repositories)\" and \"[Defining custom patterns for secret scanning](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning).\"\n"
     - heading: 'Secret scanning custom pattern events now in the audit log'
       notes:
-        - "The audit log now includes events associated with secret scanning custom patterns. This data helps GitHub Advanced Security customers understand actions taken on their [repository](/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization#repository_secret_scanning_custom_pattern-category-actions)-, [organization](/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization#org_secret_scanning_custom_pattern-category-actions)-, or [enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise#business_secret_scanning_custom_pattern-category-actions)-level custom patterns for security and compliance audits. For more information, see \"[Reviewing the audit log for your organization](/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization)\" or \"[Reviewing audit logs for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise).\"\n"
+        - "La bitácora de auditoría ahora incluye los eventos asociados con los patrones personalizados del escaneo de secretos. Estos datos ayudan a que lis clientes de GitHub Advanced Security entiendan las acciones que se toman en los patrones personalizados de su [repository](/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization#repository_secret_scanning_custom_pattern-category-actions), [organization](/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization#org_secret_scanning_custom_pattern-category-actions) o [enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise#business_secret_scanning_custom_pattern-category-actions) para las auditorías de seguridad y cumplimiento. Para obtener más información, consulta la sección \"[Revisar la bitácora de auditoría para tu organización](/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization)\" o \"[Revisar las bitácoras de auditoría para tu empresa](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise)\".\n"
     - heading: 'Configure permissions for secret scanning with custom repository roles'
       notes:
         - "You can now configure two new permissions for secret scanning when managing custom repository roles.\n\n- View secret scanning results\n- Dismiss or reopen secret scanning results\n\nFor more information, see  \"[Managing custom repository roles for an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization).\"\n"
@@ -109,10 +109,10 @@ sections:
         - "The following Git-related events can now appear in the enterprise audit log. If you enable the feature and set an audit log retention period, the new events will be available for search via the UI and API, or export via JSON or CSV.\n\n- `git.clone`\n- `git.fetch`\n- `git.push`\n\nDue to the large number of Git events logged, we recommend you monitor your instance's file storage and review your related alert configurations. For more information, see \"[Audit log events for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise#git-category-actions)\" and \"[Monitoring storage](/admin/enterprise-management/monitoring-your-appliance/recommended-alert-thresholds#monitoring-storage).\"\n"
     - heading: 'Improvements to CODEOWNERS'
       notes:
-        - "This release includes improvements to CODEOWNERS.\n\n- Syntax errors are now surfaced when viewing a CODEOWNERS file from the web. Previously, when a line in a CODEOWNERS file had a syntax error, the error would be ignored or in some cases cause the entire CODEOWNERS file to not load. GitHub Apps and Actions can access the same list of errors using new REST and GraphQL APIs. For more information, see \"[Repositories](/rest/repos/repos#list-codeowners-errors)\" in the REST API documentation or \"[Objects](/graphql/reference/objects#repositorycodeowners)\" in the GraphQL API documentation.\n- After someone creates a new pull request or pushes new changes to a draft pull request, any code owners that will be requested for review are now listed in the pull request under \"Reviewers\". This feature gives you an early look at who will be requested to review once the pull request is marked ready for review.\n- Comments in CODEOWNERS files can now appear at the end of a line, not just on dedicated lines.\n\nFor more information, see \"[About code owners](/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners).\"\n"
+        - "Este lanzamiento incluye mejoras para los CODEOWNERS.\n\n- Los errores de sintaxis ahora se extienden cuando se ve un archivo de CODEOWNERS desde la web. anteriormente, cuando una línea en un archivo de CODEOWNERS tenía un error de sintaxis, este se ignoraba o, en algunos casos, ocasionaba que no cargara el archivo completo de CODEOWNERS. Las GitHub Apps y las acciones pueden acceder a la misma lista de errores utilizando API nuevas de REST y de GraphQL. Para obtener más información, consulta la sección de \"[Repositories](/rest/repos/repos#list-codeowners-errors)\" en la documentación de la API de REST u \"[Objects](/graphql/reference/objects#repositorycodeowners)\" en la documentación de la API de GraphQL.\n- Después de que alguien cree una solicitud de cambios nueva o suba cambios nuevos a un borrador de solicitud de cambios, cualquier propietario de código que se requiera para revisión ahora estará listado en la solicitud de cambios debajo de \"Revisores\". Esta característica te proporciona una vista inicial de quién se solicita para revisión una vez que la solicitud de cambios se marque como lista para revisión.\n-Los comentarios en los archivos de CODEOWNERS ahora pueden aparecer al final de una línea, no solo en las líneas dedicadas.\n\nPara obtener más información, consulta la sección \"[Acerca de los propietarios de código](/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners)\".\n"
     - heading: 'More ways to keep a pull request''s topic branch up to date'
       notes:
-        - "The **Update branch** button on the pull request page lets you update your pull request's branch with the latest changes from the base branch. This is useful for verifying your changes are compatible with the current version of the base branch before you merge. Two enhancements now give you more ways to keep your branch up-to-date.\n\n- When your pull request's topic branch is out of date with the base branch, you now have the option to update it by rebasing on the latest version of the base branch. Rebasing applies the changes from your branch onto the latest version of the base branch, resulting in a branch with a linear history since no merge commit is created. To update by rebasing, click the drop down menu next to the **Update Branch** button, click **Update with rebase**, and then click **Rebase branch**. Previously, **Update branch** performed a traditional merge that always resulted in a merge commit in your pull request branch. This option is still available, but now you have the choice. For more information, see \"[Keeping your pull request in sync with the base branch](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/keeping-your-pull-request-in-sync-with-the-base-branch).\"\n\n- A new repository setting allows the **Update branch** button to always be available when a pull request's topic branch is not up to date with the base branch. Previously, this button was only available when the **Require branches to be up to date before merging** branch protection setting was enabled. People with admin or maintainer access can manage the **Always suggest updating pull request branches** setting from the **Pull Requests** section in repository settings. For more information, see \"[Managing suggestions to update pull request branches](/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-suggestions-to-update-pull-request-branches).\"\n"
+        - "El botón de **Actualizar rama** en la página de solicitud de cambios te permite actualizar la rama de esta con los últimos cambios de la rama base. Esto es útil para verificar que tus cambios sean compatibles con la versión actual de la rama base antes de fusionar. Dos mejoras ahora te proporcionan más opciones para mantener tu rama actualizada.\n\n- Cuando la rama de tema de tu solicitud de cambios está desactualizada con la rama base, ahora tienes la opción de actualizarla si rebasas en la última versión de la rama base. El rebase aplica los cambios de tu rama en la versión más reciente de la rama base, lo cuál da como resultado una rama con un historial linear, ya que no se crea ninguna confirmación de fusión. Para actualizar por rebase, haz clic en el menú desplegable junto al botón de **Actualizar rama**, luego en **Actualizar con rebase** y luego en *rebasar rama**, Anteriormente, el botón de **Actualizar rama** realizaba una fusión tradicional que siempre daba como resultado una confirmación de fusión en la rama de tu solicitud de cambios. Esta opción aún sigue disponible, pero ahora tú tienes la elección. para obtener más información, consulta la sección \"[Mantener tu solicitud de cambios sincronizada con la rama base](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/keeping-your-pull-request-in-sync-with-the-base-branch)\".\n\n- Un nuevo ajuste de repositorio permite que el botón de **Actualizar rama** siempre esté disponible cuando la rama de tema de una solicitud de cambios no está actualizada con la rama base. Anteriormente, este botón solo estaba disponible cuando el ajuste de protección de rama **Siempre sugerir la actualización de las ramas de las solicitudes de cambio** estaba habilitado. Las personas con acceso de mantenedor o administrativo pueden administrar el ajuste de **Siempre sugerir actualizar las ramas de las solicitudes de cambio** de la sección **Solicitudes de cambio** en los ajustes de repositorio. Para obtener más información, consulta la sección \"[Administrar las sugerencias para actualizar las ramas de las solicitudes de cambios](/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-suggestions-to-update-pull-request-branches)\".\n"
     - heading: 'Configure custom HTTP headers for GitHub Pages sites'
       notes:
         - "You can now configure custom HTTP headers that apply to all GitHub Pages sites served from your GitHub Enterprise Server instance. For more information, see \"[Configuring GitHub Pages for your enterprise](/admin/configuration/configuring-your-enterprise/configuring-github-pages-for-your-enterprise#configuring-github-pages-response-headers-for-your-enterprise).\"\n"
@@ -147,7 +147,7 @@ sections:
         - "The CodeQL runner is deprecated in favor of the CodeQL CLI. GitHub Enterprise Server 3.4 and later no longer include the CodeQL runner. This deprecation only affects users who use CodeQL code scanning in 3rd party CI/CD systems. GitHub Actions users are not affected. GitHub strongly recommends that customers migrate to the CodeQL CLI, which is a feature-complete replacement for the CodeQL runner and has many additional features. For more information, see \"[Migrating from the CodeQL runner to CodeQL CLI](/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/migrating-from-the-codeql-runner-to-codeql-cli).\"\n"
     - heading: 'Theme picker for GitHub Pages has been removed'
       notes:
-        - "The theme picker for GitHub Pages has been removed from the Pages settings. For more information about configuration of themes for GitHub Pages, see \"[Adding a theme to your GitHub Pages site using Jekyll](/pages/setting-up-a-github-pages-site-with-jekyll/adding-a-theme-to-your-github-pages-site-using-jekyll).\"\n"
+        - "El selector de tema de GitHub Pages se eliminó de los ajustes de las páginas. Para obtener más información sobre la configuración de temas para GitHub Pages, consulta la sección \"[Agregar un tema a tu sitio de GitHub pages utilizando Jekyll](/pages/setting-up-a-github-pages-site-with-jekyll/adding-a-theme-to-your-github-pages-site-using-jekyll)\".\n"
   known_issues:
     - 'En una instancia recién configurada de {% data variables.product.prodname_ghe_server %} sin ningún usuario, un atacante podría crear el primer usuario adminsitrador.'
     - 'Las reglas de cortafuegos personalizadas se eliminan durante el proceso de actualización.'
diff --git a/translations/es-ES/data/reusables/actions/jobs/section-choosing-the-runner-for-a-job.md b/translations/es-ES/data/reusables/actions/jobs/section-choosing-the-runner-for-a-job.md
index f38b76d4d5..c4c3102691 100644
--- a/translations/es-ES/data/reusables/actions/jobs/section-choosing-the-runner-for-a-job.md
+++ b/translations/es-ES/data/reusables/actions/jobs/section-choosing-the-runner-for-a-job.md
@@ -1,10 +1,10 @@
-Use `jobs.<job_id>.runs-on` to define the type of machine to run the job on. {% ifversion fpt or ghec %}La máquina puede ya sea ser un ejecutor hospedado en {% data variables.product.prodname_dotcom %} o uno auto-hospedado.{% endif %} Puedes proporcionar a `runs-on` como una secuencia simple o como un arreglo de secuencias. Si especificas un arreglo de secuencias, tu flujo de trabajo se ejecutará en un ejecutor auto-hospedado cuyas etiquetas empaten con todos los valores de `runs-on` que se hayan especificado, en caso de que estén disponibles. Si te gustaría ejecutar tu flujo de trabajo en máquinas múltiples, utiliza [`jobs.<job_id>.strategy`](/actions/learn-github-actions/workflow-syntax-for-github-actions#jobsjob_idstrategy).
+Utiliza `jobs.<job_id>.runs-on` para definir el tipo de máquina en la cuál ejecutar el job. {% ifversion fpt or ghec %}La máquina puede ya sea ser un ejecutor hospedado en {% data variables.product.prodname_dotcom %} o uno auto-hospedado.{% endif %} Puedes proporcionar a `runs-on` como una secuencia simple o como un arreglo de secuencias. Si especificas un arreglo de secuencias, tu flujo de trabajo se ejecutará en un ejecutor auto-hospedado cuyas etiquetas empaten con todos los valores de `runs-on` que se hayan especificado, en caso de que estén disponibles. Si te gustaría ejecutar tu flujo de trabajo en máquinas múltiples, utiliza [`jobs.<job_id>.strategy`](/actions/learn-github-actions/workflow-syntax-for-github-actions#jobsjob_idstrategy).
 
 
 {% ifversion fpt or ghec or ghes %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-### Choosing {% data variables.product.prodname_dotcom %}-hosted runners
+### Elegir los ejecutores hospedados en {% data variables.product.prodname_dotcom %}
 
 Si usas un ejecutor alojado {% data variables.product.prodname_dotcom %}, cada trabajo se ejecuta en una nueva instancia de un entorno virtual especificado por `runs-on`.
 
@@ -12,7 +12,7 @@ Los tipos de ejecutores alojados {% data variables.product.prodname_dotcom %} di
 
 {% data reusables.actions.supported-github-runners %}
 
-#### Example: Specifying an operating system
+#### Ejemplo: Especificar un sistema operativo
 
 ```yaml
 runs-on: ubuntu-latest
@@ -22,12 +22,12 @@ Para obtener más información, consulta "[Entornos virtuales para ejecutores al
 {% endif %}
 
 {% ifversion fpt or ghec or ghes %}
-### Choosing self-hosted runners
+### Elegir los ejecutores auto-hospedados
 {% endif %}
 
 {% data reusables.actions.self-hosted-runner-labels-runs-on %}
 
-#### Example: Using labels for runner selection
+#### Ejemplo: Utilizar las etiquetas para la selección de ejecutores
 
 ```yaml
 runs-on: [self-hosted, linux]
diff --git a/translations/es-ES/data/reusables/actions/jobs/section-defining-outputs-for-jobs.md b/translations/es-ES/data/reusables/actions/jobs/section-defining-outputs-for-jobs.md
index b148a15c4a..99149138d2 100644
--- a/translations/es-ES/data/reusables/actions/jobs/section-defining-outputs-for-jobs.md
+++ b/translations/es-ES/data/reusables/actions/jobs/section-defining-outputs-for-jobs.md
@@ -1,6 +1,8 @@
 Puedes utilizar `jobs.<job_id>.outputs` para crear un `map` de salidas para un job. Las salidas de un job se encuentran disponibles para todos los jobs descendentes que dependan de este job. Para obtener más información sobre la definición de dependencias, consulta [`jobs.<job_id>.needs`](/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idneeds).
 
-Las salidas de un job son secuencias, y las salidas de un job que contienen expresiones se evalúan en el ejecutor al final de cada job. Las salidas que contienen secretos se redactan en el ejecutor y no se envían a {% data variables.product.prodname_actions %}.
+{% data reusables.actions.output-limitations %}
+
+Las salidas de job que contengan expresiones se evaluarán en el ejecutor al fin de cada job. Las salidas que contienen secretos se redactan en el ejecutor y no se envían a {% data variables.product.prodname_actions %}.
 
 Para utilizar salidas de jobs en un job dependiente, puedes utilizar el contexto `needs`. Para obtener más información, consulta "[Contextos](/actions/learn-github-actions/contexts#needs-context)".
 
diff --git a/translations/es-ES/data/reusables/actions/jobs/section-running-jobs-in-a-container-env.md b/translations/es-ES/data/reusables/actions/jobs/section-running-jobs-in-a-container-env.md
index 875af4f078..7fd54bf899 100644
--- a/translations/es-ES/data/reusables/actions/jobs/section-running-jobs-in-a-container-env.md
+++ b/translations/es-ES/data/reusables/actions/jobs/section-running-jobs-in-a-container-env.md
@@ -1 +1 @@
-Use `jobs.<job_id>.container.env` to set a `map` of environment variables in the container.
+Utiliza `jobs.<job_id>.container.env` para configurar un `map` de variables ambientales en el contenedor.
diff --git a/translations/es-ES/data/reusables/actions/jobs/section-running-jobs-in-a-container-options.md b/translations/es-ES/data/reusables/actions/jobs/section-running-jobs-in-a-container-options.md
index c1d806a66f..77f0949e7f 100644
--- a/translations/es-ES/data/reusables/actions/jobs/section-running-jobs-in-a-container-options.md
+++ b/translations/es-ES/data/reusables/actions/jobs/section-running-jobs-in-a-container-options.md
@@ -1,4 +1,4 @@
-Use `jobs.<job_id>.container.options` to configure additional Docker container resource options. Para obtener una lista de opciones, consulta las opciones "[`crear docker`](https://docs.docker.com/engine/reference/commandline/create/#options)".
+Utiliza `jobs.<job_id>.container.options` para configurar opciones adicionales de recursos para los contenedores de Docker. Para obtener una lista de opciones, consulta las opciones "[`crear docker`](https://docs.docker.com/engine/reference/commandline/create/#options)".
 
 {% warning %}
 
diff --git a/translations/es-ES/data/reusables/actions/jobs/section-running-jobs-in-a-container-volumes.md b/translations/es-ES/data/reusables/actions/jobs/section-running-jobs-in-a-container-volumes.md
index 62f02db56b..14baac2aec 100644
--- a/translations/es-ES/data/reusables/actions/jobs/section-running-jobs-in-a-container-volumes.md
+++ b/translations/es-ES/data/reusables/actions/jobs/section-running-jobs-in-a-container-volumes.md
@@ -1,4 +1,4 @@
-Use `jobs.<job_id>.container.volumes` to set an `array` of volumes for the container to use. Puedes usar volúmenes para compartir datos entre servicios u otros pasos en un trabajo. Puedes especificar volúmenes Docker con nombre, volúmenes Docker anónimos o montajes de enlace en el host.
+Utiliza `jobs.<job_id>.container.volumes` para configurar un `array` de volúmenes para que lo utilice el contenedor. Puedes usar volúmenes para compartir datos entre servicios u otros pasos en un trabajo. Puedes especificar volúmenes Docker con nombre, volúmenes Docker anónimos o montajes de enlace en el host.
 
 Para especificar un volumen, especifica la ruta de origen y destino:
 
@@ -6,7 +6,7 @@ Para especificar un volumen, especifica la ruta de origen y destino:
 
 `<source>` es un nombre de volumen o una ruta absoluta en la máquina host, y `<destinationPath>` es una ruta absoluta en el contenedor.
 
-#### Example: Mounting volumes in a container
+#### Ejemplo: Montar volúmenes en un contenedor
 
 ```yaml
 volumes:
diff --git a/translations/es-ES/data/reusables/actions/jobs/section-running-jobs-in-a-container.md b/translations/es-ES/data/reusables/actions/jobs/section-running-jobs-in-a-container.md
index 9f14d88461..30166b08e2 100644
--- a/translations/es-ES/data/reusables/actions/jobs/section-running-jobs-in-a-container.md
+++ b/translations/es-ES/data/reusables/actions/jobs/section-running-jobs-in-a-container.md
@@ -1,8 +1,8 @@
-Use `jobs.<job_id>.container` to create a container to run any steps in a job that don't already specify a container. Si tienes pasos que usan tanto acciones de script como de contenedor, las acciones de contenedor se ejecutarán como contenedores hermanos en la misma red con los mismos montajes de volumen.
+Utiliza `jobs.<job_id>.container` para crear un contenedor para ejecutar cualquier paso en un job que aún no especifique un contenedor. Si tienes pasos que usan tanto acciones de script como de contenedor, las acciones de contenedor se ejecutarán como contenedores hermanos en la misma red con los mismos montajes de volumen.
 
 Si no configuras un `container`, todos los pasos se ejecutan directamente en el host especificado por `runs-on` a menos que un paso se refiera a una acción configurada para ejecutarse en un contenedor.
 
-### Example: Running a job within a container
+### Ejemplo: Ejecutar un job dentro de un contenedor
 
 ```yaml
 jobs:
diff --git a/translations/es-ES/data/reusables/actions/jobs/section-using-a-build-matrix-for-your-jobs-failfast.md b/translations/es-ES/data/reusables/actions/jobs/section-using-a-build-matrix-for-your-jobs-failfast.md
index e1bba5d92a..3ac42d8ed2 100644
--- a/translations/es-ES/data/reusables/actions/jobs/section-using-a-build-matrix-for-your-jobs-failfast.md
+++ b/translations/es-ES/data/reusables/actions/jobs/section-using-a-build-matrix-for-your-jobs-failfast.md
@@ -1,10 +1,10 @@
-You can control how job failures are handled with `jobs.<job_id>.strategy.fail-fast` and `jobs.<job_id>.continue-on-error`.
+Puedes controlar cómo se manejan los fallos de los jobs con `jobs.<job_id>.strategy.fail-fast` y `jobs.<job_id>.continue-on-error`.
 
-`jobs.<job_id>.strategy.fail-fast` applies to the entire matrix. If `jobs.<job_id>.strategy.fail-fast` is set to `true`, {% data variables.product.product_name %} will cancel all in-progress and queued jobs in the matrix if any job in the matrix fails. This property defaults to `true`.
+`jobs.<job_id>.strategy.fail-fast` aplica a toda la matriz. Si configuras a `jobs.<job_id>.strategy.fail-fast` como `true`, {% data variables.product.product_name %} cancelará todos los jobs de la matriz que estén en cola y en progreso en caos de que cualquiera de ellos falle. Esta propiedad se predetermina en `true`.
 
-`jobs.<job_id>.continue-on-error` applies to a single job. If `jobs.<job_id>.continue-on-error` is `true`, other jobs in the matrix will continue running even if the job with `jobs.<job_id>.continue-on-error: true` fails.
+`jobs.<job_id>.continue-on-error` aplica a un solo job. Si `jobs.<job_id>.continue-on-error` es `true`, otros jobs en la matriz seguirán ejecutándose, incluso si el job con `jobs.<job_id>.continue-on-error: true` falla.
 
-You can use `jobs.<job_id>.strategy.fail-fast` and `jobs.<job_id>.continue-on-error` together. For example, the following workflow will start four jobs. For each job, `continue-on-error` is determined by the value of `matrix.experimental`. If any of the jobs with `continue-on-error: false` fail, all jobs that are in progress or queued will be cancelled. If the job with `continue-on-error: true` fails, the other jobs will not be affected.
+Puedes utilizar `jobs.<job_id>.strategy.fail-fast` y `jobs.<job_id>.continue-on-error` juntos. Por ejemplo, el siguiente flujo de trabajo iniciará cuatro jobs. Para cada job, `continue-on-error` se determina mediante el valor de `matrix.experimental`. Si cualquiera de los jobs con `continue-on-error: false` falla, todos los jobs que estén en progreso o en cola se cancelarán. Si el job con `continue-on-error: true` falla, los otros no se verán afectados.
 
 
 ```yaml
diff --git a/translations/es-ES/data/reusables/actions/jobs/section-using-a-build-matrix-for-your-jobs-max-parallel.md b/translations/es-ES/data/reusables/actions/jobs/section-using-a-build-matrix-for-your-jobs-max-parallel.md
index fd58b0c321..dbea6d921e 100644
--- a/translations/es-ES/data/reusables/actions/jobs/section-using-a-build-matrix-for-your-jobs-max-parallel.md
+++ b/translations/es-ES/data/reusables/actions/jobs/section-using-a-build-matrix-for-your-jobs-max-parallel.md
@@ -1,6 +1,6 @@
-By default, {% data variables.product.product_name %} will maximize the number of jobs run in parallel depending on runner availability. To set the maximum number of jobs that can run simultaneously when using a `matrix` job strategy, use `jobs.<job_id>.strategy.max-parallel`.
+By default, {% data variables.product.product_name %} will maximize the number of jobs run in parallel depending on runner availability. Para configurar la cantidad máxima de jobs que puedan ejecutarse simultáneamente al utilizar una estrategia de jobs de `matrix`, utiliza `jobs.<job_id>.strategy.max-parallel`.
 
-For example, the following workflow will run a maximum of two jobs at a time, even if there are runners available to run all six jobs at once.
+Por ejemplo, el siguiente flujo de trabajo ejecutará un máximo de dos jobs a la vez, incluso si hay ejecutores disponibles para ejecutar los seis jobs al mismo tiempo.
 
 ```yaml
 jobs:
diff --git a/translations/es-ES/data/reusables/actions/jobs/section-using-environments-for-jobs.md b/translations/es-ES/data/reusables/actions/jobs/section-using-environments-for-jobs.md
index ca7ed40872..1ce7b6f013 100644
--- a/translations/es-ES/data/reusables/actions/jobs/section-using-environments-for-jobs.md
+++ b/translations/es-ES/data/reusables/actions/jobs/section-using-environments-for-jobs.md
@@ -9,7 +9,7 @@ environment: staging_environment
 ```
 {% endraw %}
 
-### Example: Using environment name and URL
+### Ejemplo: Utilizar una URL y nombre de ambiente
 
 ```yaml
 environment:
@@ -19,7 +19,7 @@ environment:
 
 La URL puede ser una expresión y puede utilizar cualquier contexto, excepto el de [`secrets`](/actions/learn-github-actions/contexts#contexts). Para obtener más información sobre las expresiones, consulta la sección "[Expresiones](/actions/learn-github-actions/expressions)".
 
-### Example: Using output as URL
+### Ejemplo: Utilizar una salida como URL
 {% raw %}
 ```yaml
 environment:
diff --git a/translations/es-ES/data/reusables/actions/jobs/setting-default-values-for-jobs-defaults-job.md b/translations/es-ES/data/reusables/actions/jobs/setting-default-values-for-jobs-defaults-job.md
index 4c6d7fd2ed..d50639bc7c 100644
--- a/translations/es-ES/data/reusables/actions/jobs/setting-default-values-for-jobs-defaults-job.md
+++ b/translations/es-ES/data/reusables/actions/jobs/setting-default-values-for-jobs-defaults-job.md
@@ -1,3 +1,3 @@
-Use `jobs.<job_id>.defaults` to create a `map` of default settings that will apply to all steps in the job. También puedes configurar ajustes predeterminados para todo el flujo de trabajo. Para obtener más información, consulta [`defaults`](/actions/using-workflows/workflow-syntax-for-github-actions#defaults).
+Utiliza `jobs.<job_id>.defaults` para crear un `map` de ajustes predeterminados que aplicarán a todos los pasos del job. También puedes configurar ajustes predeterminados para todo el flujo de trabajo. Para obtener más información, consulta [`defaults`](/actions/using-workflows/workflow-syntax-for-github-actions#defaults).
 
 {% data reusables.actions.defaults-override %}
diff --git a/translations/es-ES/data/reusables/actions/jobs/setting-default-values-for-jobs-defaults.md b/translations/es-ES/data/reusables/actions/jobs/setting-default-values-for-jobs-defaults.md
index 0490f4ca0e..2145924ae4 100644
--- a/translations/es-ES/data/reusables/actions/jobs/setting-default-values-for-jobs-defaults.md
+++ b/translations/es-ES/data/reusables/actions/jobs/setting-default-values-for-jobs-defaults.md
@@ -1,3 +1,3 @@
-Use `defaults` to create a `map` of default settings that will apply to all jobs in the workflow. También puedes configurar los ajustes predeterminados que solo estén disponibles para un job. Para obtener más información, consulta la sección [`jobs.<job_id>.defaults`](/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_iddefaults).
+Utiliza `defaults` para crear un `map` mapa de ajustes predeterminados que aplicarán a todos los jobs en el flujo de trabajo. También puedes configurar los ajustes predeterminados que solo estén disponibles para un job. Para obtener más información, consulta la sección [`jobs.<job_id>.defaults`](/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_iddefaults).
 
 {% data reusables.actions.defaults-override %}
diff --git a/translations/es-ES/data/reusables/actions/output-limitations.md b/translations/es-ES/data/reusables/actions/output-limitations.md
new file mode 100644
index 0000000000..d26de54a7f
--- /dev/null
+++ b/translations/es-ES/data/reusables/actions/output-limitations.md
@@ -0,0 +1 @@
+Outputs are Unicode strings, and can be a maximum of 1 MB. The total of all outputs in a workflow run can be a maximum of 50 MB.
diff --git a/translations/es-ES/data/reusables/actions/pass-inputs-to-reusable-workflows.md b/translations/es-ES/data/reusables/actions/pass-inputs-to-reusable-workflows.md
index 895d3c1a41..cd9eecd537 100644
--- a/translations/es-ES/data/reusables/actions/pass-inputs-to-reusable-workflows.md
+++ b/translations/es-ES/data/reusables/actions/pass-inputs-to-reusable-workflows.md
@@ -13,7 +13,7 @@ jobs:
 {% endraw %}
 
 {% if actions-inherit-secrets-reusable-workflows %}
-Workflows that call reusable workflows in the same organization or enterprise can use the `inherit` keyword to implicitly pass the secrets.
+Los flujos de trabajo que llaman a los reutilizables en la misma organización o empresa pueden utilizar la palabra clave `inherit` para pasar los secretos de forma implícita.
 
 {% raw %}
 ```yaml
diff --git a/translations/es-ES/data/reusables/actions/reusable-workflow-calling-syntax.md b/translations/es-ES/data/reusables/actions/reusable-workflow-calling-syntax.md
index 846f246c25..69cd1b7723 100644
--- a/translations/es-ES/data/reusables/actions/reusable-workflow-calling-syntax.md
+++ b/translations/es-ES/data/reusables/actions/reusable-workflow-calling-syntax.md
@@ -1,4 +1,4 @@
-* `{owner}/{repo}/.github/workflows/{filename}@{ref}`{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-6000 %} for reusable workflows in public {% ifversion ghes or ghec or ghae %}or internal{% endif %} repositories.
-* `./.github/workflows/{filename}` for reusable workflows in the same repository.{% endif %}
+* `{owner}/{repo}/.github/workflows/{filename}@{ref}`{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-6000 %} para los flujos de trabajo reutilizables en repositorios públicos {% ifversion ghes or ghec or ghae %}o internos{% endif %}.
+* `./.github/workflows/{filename}` para los flujos de trabajo reutilizables en el mismo repositorio.{% endif %}
 
-`{ref}` puede ser un SHA, una etiqueta de lanzamiento o un nombre de rama. Utilizar el SHA de la confirmación es lo más seguro para la estabilidad y seguridad. Para obtener más información, consulta la sección "[Fortalecimiento de la seguridad para las GitHub Actions](/actions/learn-github-actions/security-hardening-for-github-actions#reusing-third-party-workflows)". {% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-6000 %}If you use the second syntax option (without `{owner}/{repo}` and `@{ref}`) the called workflow is from the same commit as the caller workflow.{% endif %}
+`{ref}` puede ser un SHA, una etiqueta de lanzamiento o un nombre de rama. Utilizar el SHA de la confirmación es lo más seguro para la estabilidad y seguridad. Para obtener más información, consulta la sección "[Fortalecimiento de la seguridad para las GitHub Actions](/actions/learn-github-actions/security-hardening-for-github-actions#reusing-third-party-workflows)". {% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-6000 %}Si utilizas la segunda opción de sintaxis (sin `{owner}/{repo}` ni `@{ref}`), el flujo de trabajo llamado será de la misma confirmación que el llamante.{% endif %}
diff --git a/translations/es-ES/data/reusables/actions/workflows/section-triggering-a-workflow-branches.md b/translations/es-ES/data/reusables/actions/workflows/section-triggering-a-workflow-branches.md
index 438525a074..53bef65033 100644
--- a/translations/es-ES/data/reusables/actions/workflows/section-triggering-a-workflow-branches.md
+++ b/translations/es-ES/data/reusables/actions/workflows/section-triggering-a-workflow-branches.md
@@ -51,7 +51,7 @@ El orden en que defines los patrones importa.
 - Un patrón negativo de coincidencia (con prefijo `!`) luego de una coincidencia positiva excluirá la ref de Git.
 - Un patrón positivo de coincidencia luego de una coincidencia negativa volverá a incluir la ref de Git.
 
-The following workflow will run on `pull_request` events for pull requests that target `releases/10` or `releases/beta/mona`, but not for pull requests that target `releases/10-alpha` or `releases/beta/3-alpha` because the negative pattern `!releases/**-alpha` follows the positive pattern.
+El siguiente flujo de trabajo se ejecutará en los eventos de `pull_request` para aquellas solicitudes de cambios que apunten a `releases/10` o a `releases/beta/mona`, pero no para aquellas que apunten a `releases/10-alpha` o `releases/beta/3-alpha`, ya que el patrón negativo `!releases/**-alpha` sigue el patrón positivo.
 
 ```yaml
 on:
diff --git a/translations/es-ES/data/reusables/actions/workflows/section-triggering-a-workflow-paths.md b/translations/es-ES/data/reusables/actions/workflows/section-triggering-a-workflow-paths.md
index b53e6582cf..6408434501 100644
--- a/translations/es-ES/data/reusables/actions/workflows/section-triggering-a-workflow-paths.md
+++ b/translations/es-ES/data/reusables/actions/workflows/section-triggering-a-workflow-paths.md
@@ -1,15 +1,15 @@
 
 Cuando utilices los eventos `push` y `pull_request`, puedes configurar un flujo de trabajo para que se ejecute con base en qué rutas de archivo cambiaron. Los filtros de ruta no se evalúan para subidas de etiquetas.
 
-Utiliza el filtro `paths` cuando quieras incluir los patrones de ruta de archivo o cuando quieras tanto incluirlos como excluirlos. Use the `paths-ignore` filter when you only want to exclude file path patterns. You cannot use both the `paths` and `paths-ignore` filters for the same event in a workflow.
+Utiliza el filtro `paths` cuando quieras incluir los patrones de ruta de archivo o cuando quieras tanto incluirlos como excluirlos. Utiliza el filtro `paths-ignore` cuando solo quieras excluir los patrones de ruta de archivo. No puedes utilizar tanto el filtro de `paths` como el de `paths-ignore` juntos en el mismo evento en un flujo de trabajo.
 
-If you define both `branches`/`branches-ignore` and `paths`, the workflow will only run when both filters are satisfied.
+Si defines tanto `branches`/`branches-ignore` como `paths`, el flujo de trabajo solo se ejecutará cuando ambos filtros se hayan satisfecho.
 
-The `paths` and `paths-ignore` keywords accept glob patterns that use the `*` and `**` wildcard characters to match more than one path name. Para obtener más información, consulta "[Hoja de referencia de patrones de filtro](/actions/using-workflows/workflow-syntax-for-github-actions#filter-pattern-cheat-sheet)".
+Las palabras clave `paths` y `paths-ignore` aceptan patrones globales que utilicen los caracteres de comodín `*` y `**` para empatar con más de un nombre de ruta. Para obtener más información, consulta "[Hoja de referencia de patrones de filtro](/actions/using-workflows/workflow-syntax-for-github-actions#filter-pattern-cheat-sheet)".
 
 #### Ejemplo: Incluyendo rutas
 
-Si al menos una ruta coincide con un patrón del filtro de `rutas`, se ejecuta el flujo de trabajo. For example, the following workflow would run anytime you push a JavaScript file (`.js`).
+Si al menos una ruta coincide con un patrón del filtro de `rutas`, se ejecuta el flujo de trabajo. Por ejemplo, el siguiente flujo de trabajo se ejecutaría siempre que subieras un archivo de JavaScript (`.js`).
 
 ```yaml
 on:
@@ -20,13 +20,13 @@ on:
 
 {% note %}
 
-**Note:** If a workflow is skipped due to [path filtering](/actions/using-workflows/workflow-syntax-for-github-actions#onpushpull_requestpull_request_targetpathspaths-ignore), [branch filtering](/actions/using-workflows/workflow-syntax-for-github-actions#onpull_requestpull_request_targetbranchesbranches-ignore) or a [commit message](/actions/managing-workflow-runs/skipping-workflow-runs), then checks associated with that workflow will remain in a "Pending" state. A pull request that requires those checks to be successful will be blocked from merging. For more information, see "[Handling skipped but required checks](/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/troubleshooting-required-status-checks#handling-skipped-but-required-checks)."
+**Nota:** Si se omite un flujo de trabajo debido a [filtrado de ruta](/actions/using-workflows/workflow-syntax-for-github-actions#onpushpull_requestpull_request_targetpathspaths-ignore), [filtrado de rama](/actions/using-workflows/workflow-syntax-for-github-actions#onpull_requestpull_request_targetbranchesbranches-ignore) o a un [mensaje de confirmación](/actions/managing-workflow-runs/skipping-workflow-runs), entonces las verificaciones asociadas con este flujo de trabajo permanecerán en un estado de "Pendiente". Las solicitudes de cambios que requieran que esas verificaciones tengan éxito quedarán bloqueadas para fusión. Para obtener más información, consulta la sección "[Manejar verificaciones omitidas pero requeridas](/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/troubleshooting-required-status-checks#handling-skipped-but-required-checks)".
 
 {% endnote %}
 
-#### Example: Excluding paths
+#### Ejemplo: Excluir las rutas
 
-Cuando todos los nombres de ruta coincidan con los patrones en `paths-ignore`, el flujo de trabajo no se ejecutará. If any path names do not match patterns in `paths-ignore`, even if some path names match the patterns, the workflow will run.
+Cuando todos los nombres de ruta coincidan con los patrones en `paths-ignore`, el flujo de trabajo no se ejecutará. Si alguno de los nombres de ruta no empatan con los patrones en `paths-ignore`, incluso si algunos de ellos sí lo hacen, el flujo de trabajo se ejecutará.
 
 Un flujo de trabajo con el siguiente filtro de ruta solo se ejecutará en los eventos de `subida` que incluyan al menos un archivo externo al directorio `docs` en la raíz del repositorio.
 
@@ -37,11 +37,11 @@ on:
       - 'docs/**'
 ```
 
-#### Example: Including and excluding paths
+#### Ejemplo: Incluir y excluir rutas
 
-You can not use `paths` and `paths-ignore` to filter the same event in a single workflow. If you want to both include and exclude path patterns for a single event, use the `paths` filter along with the `!` character to indicate which paths should be excluded.
+No puedes utilizar `paths` y `paths-ignore` para filtrar el mismo evento en un solo flujo de trabajo. Si quieres tanto incluir como excluir patrones de ruta para un solo evento, utiliza el filtro de `paths` en conjunto con el carácter `!` para indicar qué rutas deben excluirse.
 
-If you define a path with the `!` character, you must also define at least one path without the `!` character. If you only want to exclude paths, use `paths-ignore` instead.
+Si defines una ruta con el carácter `!`, también debes definir por lo menos una ruta sin el carácter `!`. Si solo quieres excluir rutas, utiliza `paths-ignore` en su lugar.
 
 El orden en que defines los patrones importa:
 
diff --git a/translations/es-ES/data/reusables/actions/workflows/section-triggering-a-workflow-schedule.md b/translations/es-ES/data/reusables/actions/workflows/section-triggering-a-workflow-schedule.md
index 0a399724b9..e6ec21f751 100644
--- a/translations/es-ES/data/reusables/actions/workflows/section-triggering-a-workflow-schedule.md
+++ b/translations/es-ES/data/reusables/actions/workflows/section-triggering-a-workflow-schedule.md
@@ -1,3 +1,3 @@
-You can use `on.schedule` to define a time schedule for your workflows. {% data reusables.repositories.actions-scheduled-workflow-example %}
+Puedes utilizar `on.schedule` para definir un itinerario de tiempo para tus flujos de trabajo. {% data reusables.repositories.actions-scheduled-workflow-example %}
 
 Para obtener más información acerca de la sintaxis cron, consulta la sección "[Eventos que activan flujos de trabajo](/actions/automating-your-workflow-with-github-actions/events-that-trigger-workflows#scheduled-events)".
diff --git a/translations/es-ES/data/reusables/apps/user-to-server-rate-limits.md b/translations/es-ES/data/reusables/apps/user-to-server-rate-limits.md
index 60ba02467d..22221c39b5 100644
--- a/translations/es-ES/data/reusables/apps/user-to-server-rate-limits.md
+++ b/translations/es-ES/data/reusables/apps/user-to-server-rate-limits.md
@@ -1 +1 @@
-{% ifversion ghes %}By default, user-to-server{% else %}User-to-server{% endif %} requests are limited to {% ifversion ghae %}15,000{% elsif fpt or ghec or ghes %}5,000{% endif %} requests per hour and per authenticated user. All requests from OAuth applications authorized by a user or a personal access token owned by the user, and requests authenticated with any of the user's authentication credentials, share the same quota of {% ifversion ghae %}15,000{% elsif fpt or ghec or ghes %}5,000{% endif %} requests per hour for that user.
+{% ifversion ghes %}Predeterminadamente, las solicitudes de usuario a servidor{% else %}Las solicitudes de usuario a servidor{% endif %} se limitan a {% ifversion ghae %}15 000{% elsif fpt or ghec or ghes %}5000{% endif %} solicitudes por hora y por usuario autenticado. Todas las solicitudes de las aplicaciones OAuth que autoriza un usuario o un token de acceso personal que pertenezca al usuario y las solicitudes autenticadas con cualquiera de las credenciales de autenticación de este, comparte la misma cuota de {% ifversion ghae %}15 000{% elsif fpt or ghec or ghes %}5000{% endif %} solicitudes por hora para este usuario.
diff --git a/translations/es-ES/data/reusables/billing/license-statuses.md b/translations/es-ES/data/reusables/billing/license-statuses.md
index 5b9973dc16..de8be33ede 100644
--- a/translations/es-ES/data/reusables/billing/license-statuses.md
+++ b/translations/es-ES/data/reusables/billing/license-statuses.md
@@ -1,6 +1,6 @@
 {% ifversion ghec %}
-Si tu licencia incluye {% data variables.product.prodname_vss_ghe %}, puedes identificar si una cuenta personal de {% data variables.product.prodname_dotcom_the_website %} coincidió exitosamente con un suscriptor de {% data variables.product.prodname_vs %} si descargas el archivo de CSV que contiene detalles de licencia adicionales. The license status will be one of the following.
-- "Matched": The personal account on {% data variables.product.prodname_dotcom_the_website %} is linked with a {% data variables.product.prodname_vs %} subscriber.
-- "Pending Invitation": An invitation was sent to a {% data variables.product.prodname_vs %} subscriber, but the subscriber has not accepted the invitation.
-- Blank: There is no {% data variables.product.prodname_vs %} association to consider for the personal account on {% data variables.product.prodname_dotcom_the_website %}.
+Si tu licencia incluye {% data variables.product.prodname_vss_ghe %}, puedes identificar si una cuenta personal de {% data variables.product.prodname_dotcom_the_website %} coincidió exitosamente con un suscriptor de {% data variables.product.prodname_vs %} si descargas el archivo de CSV que contiene detalles de licencia adicionales. El estado de licencia será uno de los siguientes.
+- "Matched": La cuenta personal en {% data variables.product.prodname_dotcom_the_website %} está enlazada a un suscriptor de {% data variables.product.prodname_vs %}.
+- "Pending Invitation": Una invitación se envió a un suscriptor de {% data variables.product.prodname_vs %}, pero este no la ha aceptado.
+- En blanco: No hay asociación de {% data variables.product.prodname_vs %} a considerar para la cuenta personal de {% data variables.product.prodname_dotcom_the_website %}.
 {% endif %}
diff --git a/translations/es-ES/data/reusables/code-scanning/deprecation-codeql-runner.md b/translations/es-ES/data/reusables/code-scanning/deprecation-codeql-runner.md
index ab97605dbf..4f2dcab386 100644
--- a/translations/es-ES/data/reusables/code-scanning/deprecation-codeql-runner.md
+++ b/translations/es-ES/data/reusables/code-scanning/deprecation-codeql-runner.md
@@ -2,7 +2,7 @@
 
 {% ifversion fpt or ghec %}
 
-**Note:** The {% data variables.product.prodname_codeql_runner %} is deprecated. En {% data variables.product.product_name %}, el {% data variables.product.prodname_codeql_runner %} fue compatible hasta marzo del 2022. Deberías mejorar a la última versión de [{% data variables.product.prodname_codeql_cli %}](https://github.com/github/codeql-action/releases).
+**Nota:** El {% data variables.product.prodname_codeql_runner %} es ahora obsoleto. En {% data variables.product.product_name %}, el {% data variables.product.prodname_codeql_runner %} fue compatible hasta marzo del 2022. Deberías mejorar a la última versión de [{% data variables.product.prodname_codeql_cli %}](https://github.com/github/codeql-action/releases).
 
 {% elsif ghes > 3.3 %}
 
diff --git a/translations/es-ES/data/reusables/codespaces/codespaces-machine-type-availability.md b/translations/es-ES/data/reusables/codespaces/codespaces-machine-type-availability.md
index dd7ae7435f..de84407d98 100644
--- a/translations/es-ES/data/reusables/codespaces/codespaces-machine-type-availability.md
+++ b/translations/es-ES/data/reusables/codespaces/codespaces-machine-type-availability.md
@@ -1 +1 @@
-Your choice of available machine types may be limited by a policy configured for your organization, or by a minimum machine type specification for your repository. Para obtener más información, consulta las secciones "[Restringir el acceso a los tipos de máquina](/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types)" y "[Configurar una especificación mínima para las máquinas de los codespaces](/codespaces/setting-up-your-project-for-codespaces/setting-a-minimum-specification-for-codespace-machines)".
\ No newline at end of file
+Tu elección de tipos de máquina disponible podría verse limitada por una política que se haya configurado para tu organización o por una especificación de tipo de máquina mínima para tu repositorio. Para obtener más información, consulta las secciones "[Restringir el acceso a los tipos de máquina](/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types)" y "[Configurar una especificación mínima para las máquinas de los codespaces](/codespaces/setting-up-your-project-for-codespaces/setting-a-minimum-specification-for-codespace-machines)".
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/codespaces/creating-a-codespace-in-vscode.md b/translations/es-ES/data/reusables/codespaces/creating-a-codespace-in-vscode.md
index 2531a8c427..d84e1d5bc5 100644
--- a/translations/es-ES/data/reusables/codespaces/creating-a-codespace-in-vscode.md
+++ b/translations/es-ES/data/reusables/codespaces/creating-a-codespace-in-vscode.md
@@ -1,17 +1,17 @@
-Después de que conectes tu cuenta de {% data variables.product.product_location %} a la extensión de {% data variables.product.prodname_github_codespaces %}, puedes crear un codespace nuevo. For more information about the {% data variables.product.prodname_github_codespaces %} extension, see the [{% data variables.product.prodname_vs_marketplace_shortname %} marketplace](https://marketplace.visualstudio.com/items?itemName=GitHub.codespaces).
+Después de que conectes tu cuenta de {% data variables.product.product_location %} a la extensión de {% data variables.product.prodname_github_codespaces %}, puedes crear un codespace nuevo. Para obtener más información sobre la extensión de {% data variables.product.prodname_github_codespaces %}, consulta el [{% data variables.product.prodname_vs_marketplace_shortname %} marketplace](https://marketplace.visualstudio.com/items?itemName=GitHub.codespaces).
 
 {% note %}
 
-**Nota**: Actualmente, {% data variables.product.prodname_vscode_shortname %} no te permite elegir una configuración de contenedor dev cuando creas un codespace. Si quieres elegir una configuración de contenedor dev específica, utiliza la interfaz web de {% data variables.product.prodname_dotcom %} para crear tu codespace. For more information, click the **Web browser** tab at the top of this page.
+**Nota**: Actualmente, {% data variables.product.prodname_vscode_shortname %} no te permite elegir una configuración de contenedor dev cuando creas un codespace. Si quieres elegir una configuración de contenedor dev específica, utiliza la interfaz web de {% data variables.product.prodname_dotcom %} para crear tu codespace. Para obtener más información, haz clic en la pestaña de **Buscador web** en la parte superior de esta página.
 
 {% endnote %}
 
 {% data reusables.codespaces.click-remote-explorer-icon-vscode %}
-2. Click the Add icon: {% octicon "plus" aria-label="The plus icon" %}.
+2. Haz clic en el icono de agregar: {% octicon "plus" aria-label="The plus icon" %}.
 
    ![La opciòn de crear un codespace nuevo en {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/create-codespace-vscode.png)
 
-3. Type the name of the repository you want to develop in, then select it.
+3. Escribe el nombre del repositorio en el cual quieras desarrollar y luego selecciónalo.
 
    ![Buscar un repositorio para crear un {% data variables.product.prodname_codespaces %} nuevo](/assets/images/help/codespaces/choose-repository-vscode.png)
 
@@ -19,7 +19,7 @@ Después de que conectes tu cuenta de {% data variables.product.product_location
 
    ![Buscar una rama para crear un {% data variables.product.prodname_codespaces %} nuevo](/assets/images/help/codespaces/choose-branch-vscode.png)
 
-5. Click the machine type you want to use.
+5. Haz clic en el tipo de máquina que quieras utilizar.
 
    ![Tipos de instancia para un {% data variables.product.prodname_codespaces %} nuevo](/assets/images/help/codespaces/choose-sku-vscode.png)
 
diff --git a/translations/es-ES/data/reusables/codespaces/deleting-a-codespace-in-vscode.md b/translations/es-ES/data/reusables/codespaces/deleting-a-codespace-in-vscode.md
index 6531fb1e5b..a45a5d3cc1 100644
--- a/translations/es-ES/data/reusables/codespaces/deleting-a-codespace-in-vscode.md
+++ b/translations/es-ES/data/reusables/codespaces/deleting-a-codespace-in-vscode.md
@@ -1,7 +1,7 @@
-You can delete codespaces from within {% data variables.product.prodname_vscode_shortname %} when you are not currently working in a codespace.
+Puedes borrar codespaces desde dentro de {% data variables.product.prodname_vscode_shortname %} cuando no estés trabajando actualmente en alguno de ellos.
 
 {% data reusables.codespaces.click-remote-explorer-icon-vscode %}
-1. Under "GITHUB CODESPACES", right-click the codespace you want to delete.
-1. Click **Delete Codespace**.
+1. Debajo de "GITHB CODESPACES", haz clic derecho en aquél que quieras borrar.
+1. Haz clic en **Borrar Codespace**.
 
    ![Borrar un codespace en {% data variables.product.prodname_dotcom %}](/assets/images/help/codespaces/delete-codespace-vscode.png)
diff --git a/translations/es-ES/data/reusables/enterprise/about-policies.md b/translations/es-ES/data/reusables/enterprise/about-policies.md
new file mode 100644
index 0000000000..7fd5303231
--- /dev/null
+++ b/translations/es-ES/data/reusables/enterprise/about-policies.md
@@ -0,0 +1 @@
+Each enterprise policy controls the options available for a policy at the organization level. You can choose to not enforce a policy, which allows organization owners to configure the policy for the organization, or you can choose from a set of options to enforce for all organizations owned by your enterprise.
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/organizations/security-manager-beta-note.md b/translations/es-ES/data/reusables/organizations/security-manager-beta-note.md
index 437ffe1f52..ba9f9a4e95 100644
--- a/translations/es-ES/data/reusables/organizations/security-manager-beta-note.md
+++ b/translations/es-ES/data/reusables/organizations/security-manager-beta-note.md
@@ -1,5 +1,5 @@
 {% note %}
 
-**Note:** The security manager role is in public beta and subject to change.{% ifversion fpt %} This feature is not available for organizations using legacy per-repository billing plans.{% endif %}
+**Nota:** el rol de administrador de seguridad se encuentra en beta público y está sujeto a cambios.{% ifversion fpt %} Esta característica no está disponible para las organizaciones que utilizan planes tradicionales de facturación por repositorio.{% endif %}
 
 {% endnote %}
diff --git a/translations/es-ES/data/reusables/projects/enable-basic-workflow.md b/translations/es-ES/data/reusables/projects/enable-basic-workflow.md
index a3433bcd38..d82d3242ab 100644
--- a/translations/es-ES/data/reusables/projects/enable-basic-workflow.md
+++ b/translations/es-ES/data/reusables/projects/enable-basic-workflow.md
@@ -1,6 +1,6 @@
 1. Navegar a tu proyecto.
-1. In the top-right, click {% octicon "kebab-horizontal" aria-label="The menu icon" %} to open the menu.
-1. In the menu, click {% octicon "workflow" aria-label="The workflow icon" %} **Workflows**.
+1. En la parte superior derecha, haz clic en {% octicon "kebab-horizontal" aria-label="The menu icon" %} para abrir el menú.
+1. En el menú, haz clic en {% octicon "workflow" aria-label="The workflow icon" %} **Flujos de trabajo**.
 1. Debajo de **Flujos de trabajo predeterminados**, haz clic en el flujo de trabajo que quieres editar.
 1. Si el flujo de trabajo puede aplicarse a ambos resultados y solicitudes de cambio, junto a **Dónde**, verifica el(los) tipo(s) de elemento(s) sobre el(los) cuál(es) quieres actuar.
 1. Junto a **Configurar**, elige el valor en el cual quieres configurar al estado.
diff --git a/translations/es-ES/data/reusables/projects/project-settings.md b/translations/es-ES/data/reusables/projects/project-settings.md
index 0e3f9317ea..1f7392109b 100644
--- a/translations/es-ES/data/reusables/projects/project-settings.md
+++ b/translations/es-ES/data/reusables/projects/project-settings.md
@@ -1,3 +1,3 @@
 1. Navegar a tu proyecto.
-1. In the top-right, click {% octicon "kebab-horizontal" aria-label="The menu icon" %} to open the menu.
-1. In the menu, click {% octicon "gear" aria-label="The gear icon" %} **Settings** to access the project settings.
+1. En la parte superior derecha, haz clic en {% octicon "kebab-horizontal" aria-label="The menu icon" %} para abrir el menú.
+1. En el menú, haz clic en {% octicon "gear" aria-label="The gear icon" %} **Ajustes** para acceder a los ajustes del proyecto.
diff --git a/translations/es-ES/data/reusables/pull_requests/merge-queue-merging-method.md b/translations/es-ES/data/reusables/pull_requests/merge-queue-merging-method.md
index 835c80cbc7..f0822b155d 100644
--- a/translations/es-ES/data/reusables/pull_requests/merge-queue-merging-method.md
+++ b/translations/es-ES/data/reusables/pull_requests/merge-queue-merging-method.md
@@ -1,3 +1,3 @@
-{% data variables.product.product_name %} merges the pull request according to the merge strategy configured in the branch protection once all required CI checks pass.
+{% data variables.product.product_name %} fusiona la solicitud de cambios de acuerdo con la estrategia de fusión configurada en la protección de rama una vez que todas las verificaciones de IC hayan pasado.
 
 ![Merge queue merging method](/assets/images/help/pull_requests/merge-queue-merging-method.png)
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/pull_requests/merge-queue-overview.md b/translations/es-ES/data/reusables/pull_requests/merge-queue-overview.md
index 480a435267..3640b9d761 100644
--- a/translations/es-ES/data/reusables/pull_requests/merge-queue-overview.md
+++ b/translations/es-ES/data/reusables/pull_requests/merge-queue-overview.md
@@ -1,5 +1,5 @@
-A merge queue can increase the rate at which pull requests are merged into a busy target branch while ensuring that all required branch protection checks pass.
+Una cola de fusión puede aumentar la tasa en la que se fusionan las solicitudes de cambios en una rama destino mientras se asegura de que pasen todas las verificaciones de protección de rama requeridas.
 
-Once a pull request has passed all of the required branch protection checks, a user with write access to the repository can add that pull request to a merge queue.
+Una vez que una solicitud de cambios pasa el resto de las verificaciones de protección de rama requeridas, un usuario con acceso de escritura al repositorio puede agregar dicha solicitud de cambios a una cola de fusión.
 
-A merge queue may use {% data variables.product.prodname_actions %}. Para obtener más información, consulta la sección "[{% data variables.product.prodname_actions %}](/actions/)".
+Una cola de fusión podría utilizar {% data variables.product.prodname_actions %}. Para obtener más información, consulta la sección "[{% data variables.product.prodname_actions %}](/actions/)".
diff --git a/translations/es-ES/data/reusables/pull_requests/merge-queue-references.md b/translations/es-ES/data/reusables/pull_requests/merge-queue-references.md
index ed073e1647..3c37c339a2 100644
--- a/translations/es-ES/data/reusables/pull_requests/merge-queue-references.md
+++ b/translations/es-ES/data/reusables/pull_requests/merge-queue-references.md
@@ -1,2 +1,2 @@
 
-For information about merge queue, see "[Managing a merge queue](/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-a-merge-queue)."
+Para obtener más información sobre la cola de fusión, consulta la sección "[Administrar una cola de fusión](/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-a-merge-queue)".
diff --git a/translations/es-ES/data/reusables/pull_requests/merge-queue-reject.md b/translations/es-ES/data/reusables/pull_requests/merge-queue-reject.md
index d7a40d1716..c6261d42d0 100644
--- a/translations/es-ES/data/reusables/pull_requests/merge-queue-reject.md
+++ b/translations/es-ES/data/reusables/pull_requests/merge-queue-reject.md
@@ -1,2 +1,2 @@
 
-After grouping a pull request with the latest version of the target branch and changes ahead of it in the queue, if there are failed required status checks or conflicts with the base branch, {% data variables.product.product_name %} will remove the pull request from the queue. The pull request timeline will display the reason why the pull request was removed from the queue.
+Después de agrupar una solicitud de cambios con la última versión de la rama destino y los cambios frente a ella en la cola, si es que existen verificaciones de estado requeridas fallidas o conflictos con la rama base, {% data variables.product.product_name %} eliminará la solicitud de cambios de la cola. La línea de tiempo de la solicitud de cambios mostrará la razón por la cuál se eliminó esta de la cola.
diff --git a/translations/es-ES/data/reusables/repositories/click-collaborators-teams.md b/translations/es-ES/data/reusables/repositories/click-collaborators-teams.md
index 300fea61ad..bec43313ed 100644
--- a/translations/es-ES/data/reusables/repositories/click-collaborators-teams.md
+++ b/translations/es-ES/data/reusables/repositories/click-collaborators-teams.md
@@ -1 +1 @@
-1. In the "Access" section of the sidebar, click **{% octicon "people" aria-label="The people icon" %} Collaborators & teams**.
+1. En la sección de "Acceso" de la barra lateral, haz clic en **Colaboradores & equipos {% octicon "people" aria-label="The people icon" %}**.
diff --git a/translations/es-ES/data/reusables/rest-api/always-check-your-limit.md b/translations/es-ES/data/reusables/rest-api/always-check-your-limit.md
index f16b1bcb0b..a2ce8b3790 100644
--- a/translations/es-ES/data/reusables/rest-api/always-check-your-limit.md
+++ b/translations/es-ES/data/reusables/rest-api/always-check-your-limit.md
@@ -1,5 +1,5 @@
 {% note %}
 
-**Note**: You can confirm your current rate limit status at any time. For more information, see "[Checking your rate limit status](/rest/overview/resources-in-the-rest-api#checking-your-rate-limit-status)."
+**Nota**: Puedes confirmar tu estado de límite de tasa actual en cualquier momento. For more information, see "[Checking your rate limit status](/rest/overview/resources-in-the-rest-api#checking-your-rate-limit-status)."
 
 {% endnote %}
diff --git a/translations/es-ES/data/reusables/saml/authorized-creds-info.md b/translations/es-ES/data/reusables/saml/authorized-creds-info.md
index fa8b60efc1..6eefd98194 100644
--- a/translations/es-ES/data/reusables/saml/authorized-creds-info.md
+++ b/translations/es-ES/data/reusables/saml/authorized-creds-info.md
@@ -1,7 +1,7 @@
 Antes de que puedas autorizar un token de acceso personal o llave SSH, debes haber vinculado una identidad de SAML. Si eres miembro de una organización en donde está habilitado el SSO de SAML, puedes crear una identidad vinculada autenticándote en tu organización con tu IdP por lo menos una vez. Para obtener más información, consulta la sección "[Acerca de la autenticación con el inicio de sesión único de SAML](/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on)".
 
 Después de autorizar un token de acceso personal o llave SSH. El token o llave permanecerá autorizado hasta que se revoque en una de estas formas.
-- An organization or enterprise owner revokes the authorization.
+- Un propietario de empresa u organización revoca la autorización.
 - Se te elimina de la organización.
 - Se editan los alcances en un token de acceso personal o este se regenera.
 - El token de acceso personal venció conforme a lo definido durante su creación.
diff --git a/translations/es-ES/data/reusables/secret-scanning/partner-program-link.md b/translations/es-ES/data/reusables/secret-scanning/partner-program-link.md
index 61e47fed96..15d0f7d924 100644
--- a/translations/es-ES/data/reusables/secret-scanning/partner-program-link.md
+++ b/translations/es-ES/data/reusables/secret-scanning/partner-program-link.md
@@ -1,5 +1,5 @@
 {% ifversion fpt or ghec %}
-To find out about our partner program, see "[{% data variables.product.prodname_secret_scanning_caps %} partner program](/developers/overview/secret-scanning-partner-program)."
+Para saber más sobre nuestro programa asociado, consulta "[el programa asociado de {% data variables.product.prodname_secret_scanning_caps %}](/developers/overview/secret-scanning-partner-program)".
 {% else %}
-To find out about our partner program, see "[{% data variables.product.prodname_secret_scanning_caps %} partner program](/enterprise-cloud@latest/developers/overview/secret-scanning-partner-program)" in the {% data variables.product.prodname_ghe_cloud %} documentation.
+Para saber más sobre nuestro programa asociado, consulta el "[Programa asociado de {% data variables.product.prodname_secret_scanning_caps %}](/enterprise-cloud@latest/developers/overview/secret-scanning-partner-program)" en la documentación de {% data variables.product.prodname_ghe_cloud %}.
 {% endif %}
diff --git a/translations/es-ES/data/reusables/support/premium-support-features.md b/translations/es-ES/data/reusables/support/premium-support-features.md
index 2011a45a06..2559c750c8 100644
--- a/translations/es-ES/data/reusables/support/premium-support-features.md
+++ b/translations/es-ES/data/reusables/support/premium-support-features.md
@@ -4,4 +4,4 @@ Adicionalmente a todos los beneficios de {% data variables.contact.enterprise_su
   - Un Acuerdo de nivel de servicio (SLA) con tiempos de respuesta iniciales garantizados.
   - Acceso a contenido prémium.
   - Verificaciones de salud programadas
-  - Administration assistance hours ({% data variables.product.premium_plus_support_plan %} only)
+  - Horas de asistencia (únicamente {% data variables.product.premium_plus_support_plan %})
diff --git a/translations/es-ES/data/reusables/support/view-open-tickets.md b/translations/es-ES/data/reusables/support/view-open-tickets.md
index dc00911c15..a46bb741cb 100644
--- a/translations/es-ES/data/reusables/support/view-open-tickets.md
+++ b/translations/es-ES/data/reusables/support/view-open-tickets.md
@@ -2,5 +2,5 @@
 1. En el encabezado, haz clic en **Mis tickets**. ![Captura de pantalla que muestra el enlace de "Mis Tickets" en el encabezado del Portal de GitHub Support.](/assets/images/help/support/my-tickets-header.png)
 1. Opcionalmente, para ver los tickets asociados con una cuenta organizacional o empresarial, selecciona el menú desplegable de **Mis tickets** y haz clic en el nombre de la cuenta de organización o de empresa.
 
-  You must have an enterprise support entitlement to view tickets associated with an organization or enterprise account. Para obtener más información, consulta la sección "[Administrar la titularidad de soporte para tu empresa](/enterprise-cloud@latest/admin/user-management/managing-users-in-your-enterprise/managing-support-entitlements-for-your-enterprise)". ![Captura de pantalla del menú desplegable de "Mis tickets".](/assets/images/help/support/ticket-context.png)
+  Debes tener derechos de soporte en una empresa para ver los tickets asociados con una cuenta empresarial u organizacional. Para obtener más información, consulta la sección "[Administrar la titularidad de soporte para tu empresa](/enterprise-cloud@latest/admin/user-management/managing-users-in-your-enterprise/managing-support-entitlements-for-your-enterprise)". ![Captura de pantalla del menú desplegable de "Mis tickets".](/assets/images/help/support/ticket-context.png)
 1. En la lista de tickets, haz clic en el asunto del que quieras ver. ![Captura de pantalla que muestra una lista de tickets de soporte con el asunto resaltado.](/assets/images/help/support/my-tickets-list.png)
diff --git a/translations/es-ES/data/ui.yml b/translations/es-ES/data/ui.yml
index 329d09bb0a..18a72fb0fb 100644
--- a/translations/es-ES/data/ui.yml
+++ b/translations/es-ES/data/ui.yml
@@ -36,6 +36,7 @@ search:
 homepage:
   explore_by_product: Explorar por producto
   version_picker: Versión
+  description: Ayuda para donde sea que estés en tu camino dentro de GitHub.
 toc:
   getting_started: Empezar
   popular: Popular
diff --git a/translations/ja-JP/content/actions/automating-builds-and-tests/building-and-testing-python.md b/translations/ja-JP/content/actions/automating-builds-and-tests/building-and-testing-python.md
index 726763a5ae..a536ef932a 100644
--- a/translations/ja-JP/content/actions/automating-builds-and-tests/building-and-testing-python.md
+++ b/translations/ja-JP/content/actions/automating-builds-and-tests/building-and-testing-python.md
@@ -244,7 +244,7 @@ steps:
 - run: pip test
 ```
 
-By default, the `setup-python` action searches for the dependency file (`requirements.txt` for pip or `Pipfile.lock` for pipenv) in the whole repository. For more information, see "[Caching packages dependencies](https://github.com/actions/setup-python#caching-packages-dependencies)" in the `setup-python` README.
+By default, the `setup-python` action searches for the dependency file (`requirements.txt` for pip, `Pipfile.lock` for pipenv or `poetry.lock` for poetry) in the whole repository. For more information, see "[Caching packages dependencies](https://github.com/actions/setup-python#caching-packages-dependencies)" in the `setup-python` README.
 
 If you have a custom requirement or need finer controls for caching, you can use the [`cache` action](https://github.com/marketplace/actions/cache). ランナーのオペレーティングシステムによって、pipは依存関係を様々な場所にキャッシュします。 The path you'll need to cache may differ from the Ubuntu example above, depending on the operating system you use. For more information, see [Python caching examples](https://github.com/actions/cache/blob/main/examples.md#python---pip) in the `cache` action repository.
 
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 33e887c14b..0f0fa99808 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
@@ -88,6 +88,8 @@ To access the environment variable in a Docker container action, you must pass t
 
 **オプション** アクションが設定するデータを宣言できる出力パラメータ。 ワークフローで後に実行されるアクションは、先行して実行されたアクションが設定した出力データを利用できます。  たとえば、2つの入力を加算(x + y = z)するアクションがあれば、そのアクションは他のアクションが入力として利用できる合計値(z)を出力できます。
 
+{% data reusables.actions.output-limitations %}
+
 メタデータファイル中でアクション内の出力を宣言しなくても、出力を設定してワークフロー中で利用することはできます。 アクション中での出力の設定に関する詳しい情報については「[{% data variables.product.prodname_actions %}のワークフローコマンド](/actions/reference/workflow-commands-for-github-actions/#setting-an-output-parameter)」を参照してください。
 
 ### Example: Declaring outputs for Docker container and JavaScript actions
@@ -100,16 +102,18 @@ outputs:
 
 ### `outputs.<output_id>`
 
-**必須** `文字列型`の識別子で、出力と結びつけられます。 `<output_id>`の値は、出力のメタデータのマップです。 `<output_id>`は、`outputs`オブジェクト内でユニークな識別子でなければなりません。 `<output_id>`は、文字あるいは`_`で始める必要があり、英数字、`-`、`_`しか使用できません。
+**Required** A `string` identifier to associate with the output. `<output_id>`の値は、出力のメタデータのマップです。 `<output_id>`は、`outputs`オブジェクト内でユニークな識別子でなければなりません。 `<output_id>`は、文字あるいは`_`で始める必要があり、英数字、`-`、`_`しか使用できません。
 
 ### `outputs.<output_id>.description`
 
-**必須** 出力パラメーターの`文字列`での説明。
+**Required** A `string` description of the output parameter.
 
 ## `outputs` for composite actions
 
 **Optional** `outputs` use the same parameters as `outputs.<output_id>` and `outputs.<output_id>.description` (see "[`outputs` for Docker container and JavaScript actions](#outputs-for-docker-container-and-javascript-actions)"), but also includes the `value` token.
 
+{% data reusables.actions.output-limitations %}
+
 ### Example: Declaring outputs for composite actions
 
 {% raw %}
diff --git a/translations/ja-JP/content/actions/deployment/about-deployments/deploying-with-github-actions.md b/translations/ja-JP/content/actions/deployment/about-deployments/deploying-with-github-actions.md
index 9c563e2c03..92bbdd23f6 100644
--- a/translations/ja-JP/content/actions/deployment/about-deployments/deploying-with-github-actions.md
+++ b/translations/ja-JP/content/actions/deployment/about-deployments/deploying-with-github-actions.md
@@ -156,7 +156,7 @@ You can also build an app that uses deployment and deployment status webhooks to
 
 ## ランナーの選択
 
-You can run your deployment workflow on {% data variables.product.company_short %}-hosted runners or on self-hosted runners. Traffic from {% data variables.product.company_short %}-hosted runners can come from a [wide range of network addresses](/rest/reference/meta#get-github-meta-information). If you are deploying to an internal environment and your company restricts external traffic into private networks, {% data variables.product.prodname_actions %} workflows running on {% data variables.product.company_short %}-hosted runners may not be communicate with your internal services or resources. To overcome this, you can host your own runners. For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners)" and "[About GitHub-hosted runners](/actions/using-github-hosted-runners/about-github-hosted-runners)."
+You can run your deployment workflow on {% data variables.product.company_short %}-hosted runners or on self-hosted runners. Traffic from {% data variables.product.company_short %}-hosted runners can come from a [wide range of network addresses](/rest/reference/meta#get-github-meta-information). If you are deploying to an internal environment and your company restricts external traffic into private networks, {% data variables.product.prodname_actions %} workflows running on {% data variables.product.company_short %}-hosted runners may not be able to communicate with your internal services or resources. To overcome this, you can host your own runners. For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners)" and "[About GitHub-hosted runners](/actions/using-github-hosted-runners/about-github-hosted-runners)."
 
 {% endif %}
 
diff --git a/translations/ja-JP/content/actions/using-workflows/caching-dependencies-to-speed-up-workflows.md b/translations/ja-JP/content/actions/using-workflows/caching-dependencies-to-speed-up-workflows.md
index c3f57d8a46..177d094f8b 100644
--- a/translations/ja-JP/content/actions/using-workflows/caching-dependencies-to-speed-up-workflows.md
+++ b/translations/ja-JP/content/actions/using-workflows/caching-dependencies-to-speed-up-workflows.md
@@ -37,7 +37,7 @@ To cache dependencies for a job, you can use {% data variables.product.prodname_
     <td><a href="https://github.com/actions/setup-node#caching-global-packages-data">setup-node</a></td>
   </tr>
   <tr>
-    <td>pip, pipenv</td>
+    <td>pip, pipenv, poetry</td>
     <td><a href="https://github.com/actions/setup-python#caching-packages-dependencies">setup-python</a></td>
   </tr>
   <tr>
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 0b56b43237..ec3d98130b 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
@@ -64,6 +64,8 @@ After you enable {% data variables.product.prodname_dependabot_alerts %}, you ca
 
 {% endnote %}
 
+By default, {% data variables.product.prodname_actions %} runners used by {% data variables.product.prodname_dependabot %} need access to the internet, to download updated packages from upstream package managers. For {% data variables.product.prodname_dependabot_updates %} powered by {% data variables.product.prodname_github_connect %}, internet access provides your runners with a token that allows access to dependencies and advisories hosted on {% data variables.product.prodname_dotcom_the_website %}.
+
 With {% data variables.product.prodname_dependabot_updates %}, {% data variables.product.company_short %} automatically creates pull requests to update dependencies in two ways.
 
 - **{% data variables.product.prodname_dependabot_version_updates %}**: Users add a {% data variables.product.prodname_dependabot %} configuration file to the repository to enable {% data variables.product.prodname_dependabot %} to create pull requests when a new version of a tracked dependency is released. 詳しい情報については「[{% data variables.product.prodname_dependabot_version_updates %}について](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/about-dependabot-version-updates)」を参照してください。
@@ -120,6 +122,11 @@ Before you enable {% data variables.product.prodname_dependabot_updates %}, you
 
    ![Screenshot of the dropdown menu to enable updating vulnerable dependencies](/assets/images/enterprise/site-admin-settings/dependabot-updates-button.png)
 
-{% elsif ghes > 3.2 %}
-When you enable {% data variables.product.prodname_dependabot_alerts %}, you should consider also setting up {% data variables.product.prodname_actions %} for {% data variables.product.prodname_dependabot_security_updates %}. This feature allows developers to fix vulnerabilities in their dependencies. For more information, see "[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)."
+{% endif %}
+{% ifversion ghes > 3.2 %}
+
+When you enable {% data variables.product.prodname_dependabot_alerts %}, you should consider also setting up {% data variables.product.prodname_actions %} for {% data variables.product.prodname_dependabot_security_updates %}. This feature allows developers to fix vulnerabilities in their dependencies. For more information, see "[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)."
+
+If you need enhanced security, we recommend configuring {% data variables.product.prodname_dependabot %} to use private registries. For more information, see "[Managing encrypted secrets for {% data variables.product.prodname_dependabot %}](/code-security/dependabot/working-with-dependabot/managing-encrypted-secrets-for-dependabot)."
+
 {% endif %}
diff --git a/translations/ja-JP/content/admin/enterprise-management/monitoring-your-appliance/monitoring-using-snmp.md b/translations/ja-JP/content/admin/enterprise-management/monitoring-your-appliance/monitoring-using-snmp.md
index 9c7974835d..468ea8d383 100644
--- a/translations/ja-JP/content/admin/enterprise-management/monitoring-your-appliance/monitoring-using-snmp.md
+++ b/translations/ja-JP/content/admin/enterprise-management/monitoring-your-appliance/monitoring-using-snmp.md
@@ -18,7 +18,7 @@ topics:
 
 SNMP とは、ネットワーク経由でデバイスを監視するための一般的基準です。 {% data variables.product.product_location %}のj状態を監視可能にし、いつホストのマシンにメモリやストレージ、処理能力を追加すべきかを知るために、SNMP を有効にすることを強くおすすめします。
 
-{% data variables.product.prodname_enterprise %} には標準の SNMP がインストールされているので、Nagios などのモニタリングシステムに対して利用可能な[数多くのプラグイン](http://www.monitoring-plugins.org/doc/man/check_snmp.html)を活用できます。
+{% data variables.product.prodname_enterprise %} には標準の SNMP がインストールされているので、Nagios などのモニタリングシステムに対して利用可能な[数多くのプラグイン](https://www.monitoring-plugins.org/doc/man/check_snmp.html)を活用できます。
 
 ## SNMP v2c を設定
 
@@ -66,7 +66,7 @@ SNMP v3 を有効にすると、ユーザセキュリティモデル (USM) に
 
 #### SNMP データの照会
 
-アプライアンスに関するハードウェアレベルとソフトウェアレベルの両方の情報が SNMP v3 で利用できます。 `noAuthNoPriv` と `authNoPriv` のセキュリティレベルでは暗号化とプライバシーが欠如しているため、結果の SNMP レポートから `hrSWRun` の表 (1.3.6.1.2.1.25.4) は除外されます。 セキュリティレベル `authPriv` を使用している場合は、この表が掲載されます。 詳しい情報については、「[OID のリファレンスドキュメンテーション](http://oidref.com/1.3.6.1.2.1.25.4)」を参照してください。
+アプライアンスに関するハードウェアレベルとソフトウェアレベルの両方の情報が SNMP v3 で利用できます。 `noAuthNoPriv` と `authNoPriv` のセキュリティレベルでは暗号化とプライバシーが欠如しているため、結果の SNMP レポートから `hrSWRun` の表 (1.3.6.1.2.1.25.4) は除外されます。 セキュリティレベル `authPriv` を使用している場合は、この表が掲載されます。 詳しい情報については、「[OID のリファレンスドキュメンテーション](https://oidref.com/1.3.6.1.2.1.25.4)」を参照してください。
 
 SNMP v2c では、アプライアンスに関するハードウェアレベルの情報のみが利用できます。 {% data variables.product.prodname_enterprise %} 内のアプリケーションとサービスには、メトリックスを報告するように設定された OID がありません。 いくつかの MIB が利用できます。ネットワーク内において SNMP をサポートしている別のワークステーションで `snmpwalk` を実行することで、利用できる MIB を確認できます。
 
diff --git a/translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/about-authentication-to-github.md b/translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/about-authentication-to-github.md
index 75df940d02..113e3394b5 100644
--- a/translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/about-authentication-to-github.md
+++ b/translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/about-authentication-to-github.md
@@ -84,7 +84,7 @@ You can work with all repositories on {% data variables.product.product_name %}
 
 If you authenticate with {% data variables.product.prodname_cli %}, you can either authenticate with a personal access token or via the web browser. For more information about authenticating with {% data variables.product.prodname_cli %}, see [`gh auth login`](https://cli.github.com/manual/gh_auth_login).
 
-If you authenticate without {% data variables.product.prodname_cli %}, you must authenticate with a personal access token. {% data reusables.user-settings.password-authentication-deprecation %} Every time you use Git to authenticate with {% data variables.product.product_name %}, you'll be prompted to enter your credentials to authenticate with {% data variables.product.product_name %}, unless you cache them a [credential helper](/github/getting-started-with-github/caching-your-github-credentials-in-git).
+If you authenticate without {% data variables.product.prodname_cli %}, you must authenticate with a personal access token. {% data reusables.user-settings.password-authentication-deprecation %} Every time you use Git to authenticate with {% data variables.product.product_name %}, you'll be prompted to enter your credentials to authenticate with {% data variables.product.product_name %}, unless you cache them with a [credential helper](/github/getting-started-with-github/caching-your-github-credentials-in-git).
 
 ### SSH
 
diff --git a/translations/ja-JP/content/billing/managing-billing-for-github-actions/about-billing-for-github-actions.md b/translations/ja-JP/content/billing/managing-billing-for-github-actions/about-billing-for-github-actions.md
index 1d0e9ef817..2d5feaab0a 100644
--- a/translations/ja-JP/content/billing/managing-billing-for-github-actions/about-billing-for-github-actions.md
+++ b/translations/ja-JP/content/billing/managing-billing-for-github-actions/about-billing-for-github-actions.md
@@ -48,7 +48,7 @@ Microsoft Enterprise Agreement を通じて {% data variables.product.prodname_e
 
 リポジトリが使用するストレージは、{% data variables.product.prodname_actions %}の成果物と{% data variables.product.prodname_registry %}の消費の合計のストレージです。 ストレージのコストは、アカウントが所有するすべてのリポジトリの合計の使用量です。 {% data variables.product.prodname_registry %}の価格に関する詳細な情報については、「[{% data variables.product.prodname_registry %}の支払いについて](/billing/managing-billing-for-github-packages/about-billing-for-github-packages)」を参照してください。
 
- If your account's usage surpasses these limits and you have set a spending limit above $0 USD, you will pay $0.008 USD per GB of storage per day and per-minute usage depending on the operating system used by the {% data variables.product.prodname_dotcom %}-hosted runner. {% data variables.product.prodname_dotcom %}は、各ジョブが使用する分をもっとも近い分に丸めます。
+ アカウントによる利用がこれらの制限を超え、消費の限度を0米ドル以上に設定しているなら、1日あたりストレージのGBごとに0.008米ドル、そして{% data variables.product.prodname_dotcom %}ホストランナーが使用するオペレーティングシステムに応じた分の使用量ごとに支払うことになります。 {% data variables.product.prodname_dotcom %}は、各ジョブが使用する分をもっとも近い分に丸めます。
 
 {% note %}
 
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 f3ac7bdeee..26a6e5c94e 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
@@ -55,7 +55,7 @@ topics:
 
 {% note %}
 
-**ノート:** ベータリリースの間、この機能は2022年4月14日*以降*に生成された新規のPythonアドバイザリと、過去のPythonのアドバイザリの一部に対してのみ有効です。 {% data variables.product.prodname_dotcom %} is working to backfill data across additional historical Python advisories, which are added on a rolling basis. 脆弱性のある呼び出しは、{% data variables.product.prodname_dependabot_alerts %}ページ上でのみハイライトされます。
+**ノート:** ベータリリースの間、この機能は2022年4月14日*以降*に生成された新規のPythonアドバイザリと、過去のPythonのアドバイザリの一部に対してのみ有効です。 {% data variables.product.prodname_dotcom %}は、さらなる過去のPythonアドバイザリにさかのぼってデータを加えていっています。これは、随時追加されていっています。 脆弱性のある呼び出しは、{% data variables.product.prodname_dependabot_alerts %}ページ上でのみハイライトされます。
 
 {% endnote %}
 
@@ -65,7 +65,7 @@ topics:
 
 脆弱性のある呼び出しが検出されたアラートについては、アラートの詳細ページに追加情報が表示されます。
 
-- One or more code blocks showing where the function is used.
+- 関数が使用されている場所を示す1つ以上のコードブロック。
 - 関数自体をリストしているアノテーション。関数が呼ばれている行へのリンク付きで。
 
 !["Vulnerable call"ラベルの付いたアラートのアラート詳細ページを表示しているスクリーンショット](/assets/images/help/repository/review-calls-to-vulnerable-functions.png)
diff --git a/translations/ja-JP/content/code-security/dependabot/dependabot-version-updates/about-dependabot-version-updates.md b/translations/ja-JP/content/code-security/dependabot/dependabot-version-updates/about-dependabot-version-updates.md
index 152a7623fc..1eec0c1d74 100644
--- a/translations/ja-JP/content/code-security/dependabot/dependabot-version-updates/about-dependabot-version-updates.md
+++ b/translations/ja-JP/content/code-security/dependabot/dependabot-version-updates/about-dependabot-version-updates.md
@@ -30,7 +30,7 @@ shortTitle: Dependabotバージョンアップデート
 
 {% data variables.product.prodname_dependabot %} は、依存関係を維持する手間を省きます。 これを使用して、リポジトリが依存するパッケージおよびアプリケーションの最新リリースに自動的に対応できるようにすることができます。
 
-You enable {% data variables.product.prodname_dependabot_version_updates %} by checking a _dependabot.yml_ configuration file into your repository. 設定ファイルは、リポジトリに保存されているマニフェストまたは他のパッケージ定義ファイルの場所を指定します。 {% data variables.product.prodname_dependabot %} はこの情報を使用して、古いパッケージとアプリケーションをチェックします。 {% data variables.product.prodname_dependabot %} は、依存関係のセマンティックバージョニング（[semver](https://semver.org/)）を調べて、そのバージョンへの更新の必要性を判断することにより、依存関係の新しいバージョンの有無を決定します。 特定のパッケージマネージャーでは、{% data variables.product.prodname_dependabot_version_updates %} もベンダをサポートしています。 ベンダ (またはキャッシュ) された依存関係は、マニフェストで参照されるのではなく、リポジトリ内の特定のディレクトリにチェックインされる依存関係です。 パッケージサーバーが利用できない場合でも、ビルド時にベンダ依存関係を利用できます。 {% data variables.product.prodname_dependabot_version_updates %} は、ベンダの依存関係をチェックして新しいバージョンを確認し、必要に応じて更新するように設定できます。
+{% data variables.product.prodname_dependabot_version_updates %} を有効にするには、リポジトリに`dependabot.yml` 構成ファイルをチェックインします。 設定ファイルは、リポジトリに保存されているマニフェストまたは他のパッケージ定義ファイルの場所を指定します。 {% data variables.product.prodname_dependabot %} はこの情報を使用して、古いパッケージとアプリケーションをチェックします。 {% data variables.product.prodname_dependabot %} は、依存関係のセマンティックバージョニング（[semver](https://semver.org/)）を調べて、そのバージョンへの更新の必要性を判断することにより、依存関係の新しいバージョンの有無を決定します。 特定のパッケージマネージャーでは、{% data variables.product.prodname_dependabot_version_updates %} もベンダをサポートしています。 ベンダ (またはキャッシュ) された依存関係は、マニフェストで参照されるのではなく、リポジトリ内の特定のディレクトリにチェックインされる依存関係です。 パッケージサーバーが利用できない場合でも、ビルド時にベンダ依存関係を利用できます。 {% data variables.product.prodname_dependabot_version_updates %} は、ベンダの依存関係をチェックして新しいバージョンを確認し、必要に応じて更新するように設定できます。
 
 {% data variables.product.prodname_dependabot %} が古い依存関係を特定すると、プルリクエストを発行して、マニフェストを依存関係の最新バージョンに更新します。 ベンダーの依存関係の場合、{% data variables.product.prodname_dependabot %} はプルリクエストを生成して、古い依存関係を新しいバージョンに直接置き換えます。 テストに合格したことを確認し、プルリクエストの概要に含まれている変更履歴とリリースノートを確認して、マージします。 詳しい情報については「[{% data variables.product.prodname_dependabot %}のバージョンアップデートの設定](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/enabling-and-disabling-dependabot-version-updates)」を参照してください。
 
diff --git a/translations/ja-JP/content/code-security/supply-chain-security/end-to-end-supply-chain/end-to-end-supply-chain-overview.md b/translations/ja-JP/content/code-security/supply-chain-security/end-to-end-supply-chain/end-to-end-supply-chain-overview.md
index 4b000d9818..dc1a3ba19d 100644
--- a/translations/ja-JP/content/code-security/supply-chain-security/end-to-end-supply-chain/end-to-end-supply-chain-overview.md
+++ b/translations/ja-JP/content/code-security/supply-chain-security/end-to-end-supply-chain/end-to-end-supply-chain-overview.md
@@ -19,6 +19,8 @@ topics:
 
 エンドツーエンドのソフトウェアサプライチェーンのセキュリティとは、その中核において、配布するコードが改ざんされていないことを確実にすることです。 以前は、たとえばライブラリやフレームワークなど、使用される依存関係をターゲットとすることに攻撃者は集中していました。 今日、攻撃者はその焦点を広げ、ユーザアカウントやビルドプロセスを含めているので、それらのシステムも防御されなければなりません。
 
+依存関係の保護に役立つ{% data variables.product.prodname_dotcom %}の機能に関する情報については「[サプライチェーンのセキュリティ](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-supply-chain-security)」を参照してください。
+
 ## これらのガイドについて
 
 この一連のガイドでは、エンドツーエンドのサプライチェーンである、個人アカウント、コード、ビルドプロセスの保護についての考え方を説明します。 それぞれのガイドは、その領域におけるリスクを説明し、そのリスクへの対応を支援できる{% data variables.product.product_name %}の機能を紹介します。
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 95e730d359..f58cc959d4 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
@@ -37,6 +37,8 @@ redirect_from:
 
 依存関係のレビューは、依存関係グラフと同じ言語とパッケージ管理エコシステムをサポートしています。 詳しい情報については、「[依存関係グラフについて](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph#supported-package-ecosystems)」を参照してください。
 
+{% data variables.product.product_name %}で利用できるサプライチェーンの機能に関する詳しい情報については「[サプライチェーンのセキュリティについて](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-supply-chain-security)」を参照してください。
+
 {% ifversion ghec or ghes %}
 ## 依存関係レビューの有効化
 
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 d6310a80a6..83672fd238 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
@@ -54,6 +54,10 @@ Other supply chain features on {% data variables.product.prodname_dotcom %} rely
 {% data variables.product.prodname_dependabot %} cross-references dependency data provided by the dependency graph with the list of known vulnerabilities published in the {% data variables.product.prodname_advisory_database %}, scans your dependencies and generates {% data variables.product.prodname_dependabot_alerts %} when a potential vulnerability is detected.
  {% endif %}
 
+{% ifversion fpt or ghec or ghes %}
+For best practice guides on end-to-end supply chain security including the protection of personal accounts, code, and build processes, see "[Securing your end-to-end supply chain](/code-security/supply-chain-security/end-to-end-supply-chain/end-to-end-supply-chain-overview)."
+{% endif %}
+
 ## Feature overview
 
 ### What is the dependency graph
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 1b04851134..f0b9ba9358 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
@@ -44,6 +44,8 @@ The dependency graph includes all the dependencies of a repository that are deta
 
 The dependency graph identifies indirect dependencies{% ifversion fpt or ghec %} either explicitly from a lock file or by checking the dependencies of your direct dependencies. For the most reliable graph, you should use lock files (or their equivalent) because they define exactly which versions of the direct and indirect dependencies you currently use. If you use lock files, you also ensure that all contributors to the repository are using the same versions, which will make it easier for you to test and debug code{% else %} from the lock files{% endif %}.
 
+For more information on how {% data variables.product.product_name %} helps you understand the dependencies in your environment, see "[About supply chain security](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-supply-chain-security)."
+
 {% ifversion fpt or ghec %}
 
 ## Dependents included
diff --git a/translations/ja-JP/content/codespaces/developing-in-codespaces/using-codespaces-with-github-cli.md b/translations/ja-JP/content/codespaces/developing-in-codespaces/using-codespaces-with-github-cli.md
index 35bddab124..af6afb971b 100644
--- a/translations/ja-JP/content/codespaces/developing-in-codespaces/using-codespaces-with-github-cli.md
+++ b/translations/ja-JP/content/codespaces/developing-in-codespaces/using-codespaces-with-github-cli.md
@@ -24,6 +24,7 @@ You can work with {% data variables.product.prodname_codespaces %} in the  {% da
 - [Delete a codespace](#delete-a-codespace)
 - [SSH into a codespace](#ssh-into-a-codespace)
 - [Open a codespace in {% data variables.product.prodname_vscode %}](#open-a-codespace-in-visual-studio-code)
+- [Open a codespace in JupyterLab](#open-a-codespace-in-jupyterlab)
 - [Copying a file to/from a codespace](#copy-a-file-tofrom-a-codespace)
 - [Modify ports in a codespace](#modify-ports-in-a-codespace)
 - [Access codespace logs](#access-codespace-logs)
@@ -109,6 +110,12 @@ gh codespace code -c <em>codespace-name</em>
 
 For more information, see "[Using {% data variables.product.prodname_codespaces %} in {% data variables.product.prodname_vscode %}](/codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code)."
 
+### Open a codespace in JupyterLab
+
+```shell
+gh codespace jupyter -c <em>codespace-name</em>
+```
+
 ### Copy a file to/from a codespace
 
 ```shell
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 40d24049cd..ca7f306f5b 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
@@ -89,22 +89,24 @@ The {% data variables.product.prodname_command_palette %} also gives you quick a
 
 ## コメント
 
-| キーボードショートカット                                                                                                                  | 説明                                                                                                                                                                                              |
-| ----------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| <kbd>Command</kbd>+<kbd>B</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>B</kbd> (Windows/Linux)                                   | 太字テキストの Markdown 書式を挿入します                                                                                                                                                                       |
-| <kbd>Command</kbd>+<kbd>I</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>I</kbd> (Windows/Linux)                                   | Inserts Markdown formatting for italicizing text{% ifversion fpt or ghae or ghes > 3.1 or ghec %}
-| <kbd>Command</kbd>+<kbd>E</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>E</kbd> (Windows/Linux)                                   | Inserts Markdown formatting for code or a command within a line{% endif %}
-| <kbd>Command</kbd>+<kbd>K</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>K</kbd> (Windows/Linux)                                   | リンクを作成するための Markdown 書式を挿入します                                                                                                                                                                   |
-| <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>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>Enter</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>Enter</kbd> (Windows/Linux)                           | コメントをサブミットします                                                                                                                                                                                   |
-| <kbd>Ctrl</kbd>+<kbd>.</kbd> and then <kbd>Ctrl</kbd>+<kbd>[saved reply number]</kbd>                                         | 返信テンプレートメニューを開き、コメントフィールドに返信テンプレートを自動入力します。 詳細は「[返信テンプレートについて](/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>Command</kbd>+<kbd>G</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>G</kbd> (Windows/Linux)                                   | 提案を挿入します。 詳細は「[プルリクエストで提案された変更をレビューする](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request)」を参照してください。 
+| キーボードショートカット                                                                                                                                                | 説明                                                                                                                                                                                              |
+| ----------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| <kbd>Command</kbd>+<kbd>B</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>B</kbd> (Windows/Linux)                                                                 | 太字テキストの Markdown 書式を挿入します                                                                                                                                                                       |
+| <kbd>Command</kbd>+<kbd>I</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>I</kbd> (Windows/Linux)                                                                 | Inserts Markdown formatting for italicizing text{% ifversion fpt or ghae or ghes > 3.1 or ghec %}
+| <kbd>Command</kbd>+<kbd>E</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>E</kbd> (Windows/Linux)                                                                 | Inserts Markdown formatting for code or a command within a line{% endif %}{% ifversion fpt or ghae-issue-5434 or ghes > 3.1 or ghec %}
+| <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-issue-7103 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>Opt</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>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>Enter</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>Enter</kbd> (Windows/Linux)                                                         | コメントをサブミットします                                                                                                                                                                                   |
+| <kbd>Ctrl</kbd>+<kbd>.</kbd> and then <kbd>Ctrl</kbd>+<kbd>[saved reply number]</kbd>                                                                       | 返信テンプレートメニューを開き、コメントフィールドに返信テンプレートを自動入力します。 詳細は「[返信テンプレートについて](/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>Command</kbd>+<kbd>G</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>G</kbd> (Windows/Linux)                                                                 | 提案を挿入します。 詳細は「[プルリクエストで提案された変更をレビューする](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request)」を参照してください。 
 {% endif %}
-| <kbd>R</kbd>                                                                                                                  | 返信で選択したテキストを引用します。 For more information, see "[Basic writing and formatting syntax](/articles/basic-writing-and-formatting-syntax#quoting-text)."                                               |
+| <kbd>R</kbd>                                                                                                                                                | 返信で選択したテキストを引用します。 For more information, see "[Basic writing and formatting syntax](/articles/basic-writing-and-formatting-syntax#quoting-text)."                                               |
 
 ## Issue およびプルリクエストのリスト
 
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 47e061b388..d80af2b90d 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
@@ -31,15 +31,17 @@ When you use two or more headings, GitHub automatically generates a table of con
 
 ## スタイル付きテキスト
 
-コメントフィールドと `.md` ファイルでは、太字、斜体、または取り消し線のテキストで強調を示すことができます。
+You can indicate emphasis with bold, italic, strikethrough, subscript, or superscript text in comment fields and `.md` files.
 
-| スタイル          | 構文                  | キーボードショートカット                                                                          | サンプル                      | 出力                      |
-| ------------- | ------------------- | ------------------------------------------------------------------------------------- | ------------------------- | ----------------------- |
-| 太字            | `** **`もしくは`__ __`  | <kbd>Command</kbd>+<kbd>B</kbd> (Mac) or <kbd>Ctrl</kbd>+<kbd>B</kbd> (Windows/Linux) | `**これは太字のテキストです**`        | **これは太字のテキストです**        |
-| 斜体            | `* *`あるいは`_ _`      | <kbd>Command</kbd>+<kbd>I</kbd> (Mac) or <kbd>Ctrl</kbd>+<kbd>I</kbd> (Windows/Linux) | `*このテキストは斜体です*`           | *このテキストは斜体です*           |
-| 取り消し線         | `~~ ~~`             |                                                                                       | `~~これは間違ったテキストでした~~`      | ~~これは間違ったテキストでした~~      |
-| 太字および太字中にある斜体 | `** **`及び`_ _`      |                                                                                       | `**このテキストは_きわめて_ 重要です**`  | **このテキストは_きわめて_重要です**   |
-| 全体が太字かつ斜体     | `*** ***`           |                                                                                       | `***すべてのテキストがきわめて重要です***` | ***すべてのテキストがきわめて重要です*** |
+| スタイル          | 構文                         | キーボードショートカット                                                                          | サンプル                                                | 出力                                    |
+| ------------- | -------------------------- | ------------------------------------------------------------------------------------- | --------------------------------------------------- | ------------------------------------- |
+| 太字            | `** **`もしくは`__ __`         | <kbd>Command</kbd>+<kbd>B</kbd> (Mac) or <kbd>Ctrl</kbd>+<kbd>B</kbd> (Windows/Linux) | `**これは太字のテキストです**`                                  | **これは太字のテキストです**                      |
+| 斜体            | `* *`あるいは`_ _`             | <kbd>Command</kbd>+<kbd>I</kbd> (Mac) or <kbd>Ctrl</kbd>+<kbd>I</kbd> (Windows/Linux) | `*このテキストは斜体です*`                                     | *このテキストは斜体です*                         |
+| 取り消し線         | `~~ ~~`                    |                                                                                       | `~~これは間違ったテキストでした~~`                                | ~~これは間違ったテキストでした~~                    |
+| 太字および太字中にある斜体 | `** **`及び`_ _`             |                                                                                       | `**このテキストは_きわめて_ 重要です**`                            | **このテキストは_きわめて_重要です**                 |
+| 全体が太字かつ斜体     | `*** ***`                  |                                                                                       | `***すべてのテキストがきわめて重要です***`                           | ***すべてのテキストがきわめて重要です***               |
+| Subscript     | `<sub> </sub>` |                                                                                       | `<sub>This is a subscript text</sub>`   | <sub>This is a subscript text</sub>   |
+| Superscript   | `<sup> </sup>` |                                                                                       | `<sup>This is a superscript text</sup>` | <sup>This is a superscript text</sup> |
 
 ## テキストの引用
 
@@ -90,6 +92,8 @@ git commit
 
 リンクのテキストをブラケット `[ ]` で囲み、URL をカッコ `( )` で囲めば、インラインのリンクを作成できます。 {% ifversion fpt or ghae or ghes > 3.1 or ghec %}You can also use the keyboard shortcut <kbd>Command</kbd>+<kbd>K</kbd> to create a link.{% endif %}{% ifversion fpt or ghae-issue-5434 or ghes > 3.3 or ghec %} When you have text selected, you can paste a URL from your clipboard to automatically create a link from the selection.{% endif %}
 
+{% ifversion fpt or ghae-issue-7103 or ghes > 3.5 or ghec %} You can also create a Markdown hyperlink by highlighting the text and using the keyboard shortcut <kbd>Command</kbd>+<kbd>V</kbd>. If you'd like to replace the text with the link, use the keyboard shortcut <kbd>Command</kbd>+<kbd>Shift</kbd>+<kbd>V</kbd>.{% endif %}
+
 `このサイトは [GitHub Pages](https://pages.github.com/) を使って構築されています。`
 
 ![表示されたリンク](/assets/images/help/writing/link-rendered.png)
diff --git a/translations/ja-JP/content/get-started/writing-on-github/working-with-advanced-formatting/index.md b/translations/ja-JP/content/get-started/writing-on-github/working-with-advanced-formatting/index.md
index 7e78f4a5f5..e33044f7d5 100644
--- a/translations/ja-JP/content/get-started/writing-on-github/working-with-advanced-formatting/index.md
+++ b/translations/ja-JP/content/get-started/writing-on-github/working-with-advanced-formatting/index.md
@@ -14,6 +14,7 @@ children:
   - /organizing-information-with-collapsed-sections
   - /creating-and-highlighting-code-blocks
   - /creating-diagrams
+  - /writing-mathematical-expressions
   - /autolinked-references-and-urls
   - /attaching-files
   - /creating-a-permanent-link-to-a-code-snippet
diff --git a/translations/ja-JP/content/get-started/writing-on-github/working-with-advanced-formatting/writing-mathematical-expressions.md b/translations/ja-JP/content/get-started/writing-on-github/working-with-advanced-formatting/writing-mathematical-expressions.md
new file mode 100644
index 0000000000..a5849745da
--- /dev/null
+++ b/translations/ja-JP/content/get-started/writing-on-github/working-with-advanced-formatting/writing-mathematical-expressions.md
@@ -0,0 +1,59 @@
+---
+title: Writing mathematical expressions
+intro: 'Use Markdown to display mathematical expressions on {% data variables.product.company_short %}.'
+versions:
+  feature: math
+shortTitle: Mathematical expressions
+---
+
+To enable clear communication of mathematical expressions, {% data variables.product.product_name %} supports LaTeX formatted math within Markdown. For more information, see [LaTeX/Mathematics](http://en.wikibooks.org/wiki/LaTeX/Mathematics) in Wikibooks.
+
+{% data variables.product.company_short %}'s math rendering capability uses MathJax; an open source, JavaScript-based display engine. MathJax supports a wide range of LaTeX macros, and several useful accessibility extensions. For more information, see [the MathJax documentation](http://docs.mathjax.org/en/latest/input/tex/index.html#tex-and-latex-support) and [the MathJax Accessibility Extensions Documentation](https://mathjax.github.io/MathJax-a11y/docs/#reader-guide).
+
+## Writing inline expressions
+
+To include a math expression inline with your text, delimit the expression with a dollar symbol `$`.
+
+```
+This sentence uses `$` delimiters to show math inline:  $\sqrt{3x-1}+(1+x)^2$
+```
+
+![Inline math markdown rendering](/assets/images/help/writing/inline-math-markdown-rendering.png)
+
+## Writing expressions as blocks
+
+To add a math expression as a block, start a new line and delimit the expression with two dollar symbols `$$`.
+
+```
+**The Cauchy-Schwarz Inequality**
+
+$$\left( \sum_{k=1}^n a_k b_k \right)^2 \leq \left( \sum_{k=1}^n a_k^2 \right) \left( \sum_{k=1}^n b_k^2 \right)$$
+```
+
+![Math expression as a block rendering](/assets/images/help/writing/math-expression-as-a-block-rendering.png)
+
+## Writing dollar signs in line with and within mathematical expressions
+
+To display a dollar sign as a character in the same line as a mathematical expression, you need to escape the non-delimiter `$` to ensure the line renders correctly.
+
+  - Within a math expression, add a `\` symbol before the explicit `$`.
+
+  ```
+  This expression uses `\$` to display a dollar sign: $\sqrt{\$4}$
+  ```
+
+  ![Dollar sign within math expression](/assets/images/help/writing/dollar-sign-within-math-expression.png)
+
+  - Outside a math expression, but on the same line, use span tags around the explicit `$`.
+
+  ```
+  To split <span>$</span>100 in half, we calculate $100/2$
+  ```
+
+  ![Dollar sign inline math expression](/assets/images/help/writing/dollar-sign-inline-math-expression.png)
+
+## 参考リンク
+
+* [The MathJax website](http://mathjax.org)
+* [GitHub で書き、フォーマットしてみる](/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github)
+* [GitHub Flavored Markdown Spec](https://github.github.com/gfm/)
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 300f1beadf..860041e6c4 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
@@ -30,7 +30,7 @@ shortTitle: ボード上のカードのフィルタ
 - `status:pending`、`status:success`、または `status:failure` を使用して、カードをチェックステータスでフィルタリングする
 - `type:issue`、`type:pr`、または `type:note` を使用して、カードをタイプでフィルタリングする
 - `is:open`、`is:closed`、または `is:merged`と、`is:issue`、`is:pr`、または `is:note` とを使用して、カードをステータスとタイプでフィルタリングする
-- Filter cards by issues that are linked to a pull request by a closing reference using `linked:pr`
+- `linked:pr`を使用したクローズしているリファレンスによってプルリクエストにリンクされているIssueのフィルタリング
 - `repo:ORGANIZATION/REPOSITORY` を使用して、Organization 全体のプロジェクトボード内のリポジトリでカードをフィルタリングする
 
 1. フィルタリングしたいカードが含まれるプロジェクトボードに移動します。
diff --git a/translations/ja-JP/content/issues/tracking-your-work-with-issues/about-issues.md b/translations/ja-JP/content/issues/tracking-your-work-with-issues/about-issues.md
index 3caa420549..f557123324 100644
--- a/translations/ja-JP/content/issues/tracking-your-work-with-issues/about-issues.md
+++ b/translations/ja-JP/content/issues/tracking-your-work-with-issues/about-issues.md
@@ -36,7 +36,7 @@ Issueは様々な方法で作成できるので、ワークフローで最も便
 
 ## 最新情報の確認
 
-Issueの最新のコメントの情報を得ておきたい場合には、Issueをサブスクライブして最新のコメントに関する通知を受け取ることができます。 サブスクライブした Issue の最新の更新へのリンクを素早く見つけるには、ダッシュボードにアクセスしてください。 For more information, see "[About notifications](/github/managing-subscriptions-and-notifications-on-github/about-notifications)" and "[About your personal dashboard](/articles/about-your-personal-dashboard)."
+Issueの最新のコメントの情報を得ておきたい場合には、Issueをサブスクライブして最新のコメントに関する通知を受け取ることができます。 サブスクライブした Issue の最新の更新へのリンクを素早く見つけるには、ダッシュボードにアクセスしてください。 詳しい情報については、「[通知について](/github/managing-subscriptions-and-notifications-on-github/about-notifications)」及び「[個人ダッシュボードについて](/articles/about-your-personal-dashboard)」を参照してください。
 
 ## コミュニティの管理
 
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 3b37ed1b82..f4c2ab30cb 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
@@ -27,7 +27,7 @@ shortTitle: IssueへのPRのリンク
 
 ## リンクされたIssueとPull Requestについて
 
-You can link an issue to a pull request manually or using a supported keyword in the pull request description.
+手動で、またはPull Requestの説明でサポートされているキーワードを使用して、IssueをPull Requestにリンクすることができます。
 
 Pull Requestが対処するIssueにそのPull Requestをリンクすると、コラボレータは、誰かがそのIssueに取り組んでいることを確認できます。
 
@@ -57,7 +57,7 @@ Pull Requestの説明もしくはコミットメッセージ中でサポート
 | Issueが別のリポジトリにある | *KEYWORD* *OWNER*/*REPOSITORY*#*ISSUE-NUMBER* | `Fixes octo-org/octo-repo#100`                                 |
 | 複数の Issue        | Issueごとに完全な構文を使用                              | `Resolves #10, resolves #123, resolves octo-org/octo-repo#100` |
 
-Only manually linked pull requests can be manually unlinked. To unlink an issue that you linked using a keyword, you must edit the pull request description to remove the keyword.
+手動でリンクされたPull Requestのみが手動でリンク解除できます。 キーワードを使用してリンクしたIssueのリンクを解除するには、Pull Requestの説明を編集してそのキーワードを削除する必要があります。
 
 クローズするキーワードは、コミットメッセージでも使用できます。 デフォルトブランチにコミットをマージするとIssueはクローズされますが、そのコミットを含むPull Requestは、リンクされたPull Requestとしてリストされません。
 
diff --git a/translations/ja-JP/content/issues/tracking-your-work-with-issues/viewing-all-of-your-issues-and-pull-requests.md b/translations/ja-JP/content/issues/tracking-your-work-with-issues/viewing-all-of-your-issues-and-pull-requests.md
index cdb1222e30..82bc6c4478 100644
--- a/translations/ja-JP/content/issues/tracking-your-work-with-issues/viewing-all-of-your-issues-and-pull-requests.md
+++ b/translations/ja-JP/content/issues/tracking-your-work-with-issues/viewing-all-of-your-issues-and-pull-requests.md
@@ -25,4 +25,4 @@ Issue およびPull Requestダッシュボードは、すべてのページの
 
 ## 参考リンク
 
-- "[Viewing your subscriptions](/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions#reviewing-repositories-that-youre-watching)"
+- 「[プランの表示](/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions#reviewing-repositories-that-youre-watching)」
diff --git a/translations/ja-JP/content/organizations/collaborating-with-groups-in-organizations/about-your-organization-dashboard.md b/translations/ja-JP/content/organizations/collaborating-with-groups-in-organizations/about-your-organization-dashboard.md
index f330154a85..673bac2b67 100644
--- a/translations/ja-JP/content/organizations/collaborating-with-groups-in-organizations/about-your-organization-dashboard.md
+++ b/translations/ja-JP/content/organizations/collaborating-with-groups-in-organizations/about-your-organization-dashboard.md
@@ -35,7 +35,7 @@ shortTitle: Organizationダッシュボード
 
 ニュースフィードの [All activity] セクションでは、Organization 内の他の Team やリポジトリからの更新情報を見ることができます。
 
-[All activity] セクションは、Organization 内のすべての最近のアクティビティを表示します。これにはあなたがサブスクライブしていないリポジトリでのアクティビティや、フォローしていない人々のアクティビティも含まれます。 For more information, see "[About notifications](/github/managing-subscriptions-and-notifications-on-github/about-notifications)" and "[Following people](/articles/following-people)."
+[All activity] セクションは、Organization 内のすべての最近のアクティビティを表示します。これにはあなたがサブスクライブしていないリポジトリでのアクティビティや、フォローしていない人々のアクティビティも含まれます。 詳しい情報については、「[通知について](/github/managing-subscriptions-and-notifications-on-github/about-notifications)」及び「[人をフォローする](/articles/following-people)」を参照してください。
 
 たとえば Organization のニュースフィードは Organization 内の誰かが以下のようなことをしたときに 更新情報を知らせます:
  - 新しいブランチを作成する
diff --git a/translations/ja-JP/content/pages/index.md b/translations/ja-JP/content/pages/index.md
index 64e5295d61..b0bd3c3c8c 100644
--- a/translations/ja-JP/content/pages/index.md
+++ b/translations/ja-JP/content/pages/index.md
@@ -1,7 +1,7 @@
 ---
 title: GitHub Pagesのドキュメンテーション
 shortTitle: GitHub Pages
-intro: 'Learn how to create a website directly from a repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}. Explore website building tools like Jekyll and troubleshoot issues with your {% data variables.product.prodname_pages %} site.'
+intro: '{% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}上のリポジトリから直接Webサイトを作成する方法を学んでください。 JekyllのようなWebサイトの構築ツールを調べて、{% data variables.product.prodname_pages %}サイトの問題をトラブルシュートしてください。'
 introLinks:
   quickstart: /pages/quickstart
   overview: /pages/getting-started-with-github-pages/about-github-pages
diff --git a/translations/ja-JP/content/pages/setting-up-a-github-pages-site-with-jekyll/adding-a-theme-to-your-github-pages-site-using-jekyll.md b/translations/ja-JP/content/pages/setting-up-a-github-pages-site-with-jekyll/adding-a-theme-to-your-github-pages-site-using-jekyll.md
index 02d586a5b4..ee88d5b4e1 100644
--- a/translations/ja-JP/content/pages/setting-up-a-github-pages-site-with-jekyll/adding-a-theme-to-your-github-pages-site-using-jekyll.md
+++ b/translations/ja-JP/content/pages/setting-up-a-github-pages-site-with-jekyll/adding-a-theme-to-your-github-pages-site-using-jekyll.md
@@ -49,7 +49,7 @@ shortTitle: Pagesサイトへのテーマの追加
   ---
   ---
 
-  @import "{{ site.theme }}";
+  @import "{% raw %}{{ site.theme }}{% endraw %}";
   ```
 3. カスタム CSS または Sass (インポートファイルも含む) があれば `@import` 行の直後に追加します。
 
diff --git a/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges.md b/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges.md
index 73af3a9ffd..7c69a57876 100644
--- a/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges.md
+++ b/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges.md
@@ -24,13 +24,17 @@ topics:
 
 ### squash マージのマージメッセージ
 
-squash してマージすると、{% data variables.product.prodname_dotcom %} はコミットメッセージを生成します。メッセージは必要に応じて変更できます。 メッセージのデフォルトは、プルリクエストに複数のコミットが含まれているか、1 つだけ含まれているかによって異なります。 We do not include merge commits when we count the total number of commits.
+When you squash and merge, {% data variables.product.prodname_dotcom %} generates a default commit message, which you can edit. The default message depends on the number of commits in the pull request, not including merge commits.
 
 | コミット数   | 概要                                      | 説明                                   |
 | ------- | --------------------------------------- | ------------------------------------ |
 | 単一のコミット | 単一のコミットのコミットメッセージのタイトルと、その後に続くプルリクエスト番号 | 単一のコミットのコミットメッセージの本文テキスト             |
 | 複数のコミット | プルリクエストのタイトルと、その後に続くプルリクエスト番号           | squash されたすべてのコミットのコミットメッセージの日付順のリスト |
 
+{% ifversion fpt or ghec or ghes > 3.5 or ghae-issue-7042 %}
+People with admin access to a repository can configure the repository to use the title of the pull request as the default merge message for all squashed commits. For more information, see "[Configure commit squashing](/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-squashing-for-pull-requests)".
+{% endif %}
+
 ### 長時間にわたるブランチを squash してマージする
 
 プルリクエストがマージされた後、プルリクエストの [head ブランチ](/github/getting-started-with-github/github-glossary#head-branch)で作業を継続する場合は、プルリクエストを squash してマージしないことをお勧めします。
diff --git a/translations/ja-JP/content/rest/overview/libraries.md b/translations/ja-JP/content/rest/overview/libraries.md
index a652435f64..bcf183b842 100644
--- a/translations/ja-JP/content/rest/overview/libraries.md
+++ b/translations/ja-JP/content/rest/overview/libraries.md
@@ -141,9 +141,10 @@ topics:
 
 ### Rust
 
-| ライブラリ名       | リポジトリ                                                         |
-| ------------ | ------------------------------------------------------------- |
-| **Octocrab** | [XAMPPRocky/octocrab](https://github.com/XAMPPRocky/octocrab) |
+| ライブラリ名       | リポジトリ                                                             |
+| ------------ | ----------------------------------------------------------------- |
+| **Octocrab** | [XAMPPRocky/octocrab](https://github.com/XAMPPRocky/octocrab)     |
+| **Octocat**  | [octocat-rs/octocat-rs](https://github.com/octocat-rs/octocat-rs) |
 
 ### Scala
 
diff --git a/translations/ja-JP/content/rest/overview/resources-in-the-rest-api.md b/translations/ja-JP/content/rest/overview/resources-in-the-rest-api.md
index 05837720ec..38df6d8b70 100644
--- a/translations/ja-JP/content/rest/overview/resources-in-the-rest-api.md
+++ b/translations/ja-JP/content/rest/overview/resources-in-the-rest-api.md
@@ -120,7 +120,7 @@ curl -u my_client_id:my_client_secret '{% data variables.product.api_url_pre %}/
 
 {% ifversion fpt or ghec %}
 
-Read [more about unauthenticated rate limiting](#increasing-the-unauthenticated-rate-limit-for-oauth-apps).
+[認証されていないレート制限の詳細](#increasing-the-unauthenticated-rate-limit-for-oauth-apps)をお読みください。
 
 {% endif %}
 
diff --git a/translations/ja-JP/data/features/math.yml b/translations/ja-JP/data/features/math.yml
new file mode 100644
index 0000000000..b7b89eb201
--- /dev/null
+++ b/translations/ja-JP/data/features/math.yml
@@ -0,0 +1,8 @@
+---
+#Issues 6054
+#Math support using LaTeX syntax
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '>=3.6'
+  ghae: 'issue-6054'
diff --git a/translations/ja-JP/data/release-notes/enterprise-server/3-3/0-rc1.yml b/translations/ja-JP/data/release-notes/enterprise-server/3-3/0-rc1.yml
index ba674017b6..f556a3d0fc 100644
--- a/translations/ja-JP/data/release-notes/enterprise-server/3-3/0-rc1.yml
+++ b/translations/ja-JP/data/release-notes/enterprise-server/3-3/0-rc1.yml
@@ -123,16 +123,16 @@ sections:
           For more information, see "[Security hardening for {% data variables.product.prodname_actions %}](/actions/security-guides/security-hardening-for-github-actions#auditing-github-actions-events)."
         - Performance improvements have been made to {% data variables.product.prodname_actions %}, which may result in higher maximum job concurrency.
     - 
-      heading: 'GitHub Packages changes'
+      heading: 'GitHub Packagesの変更'
       notes:
         - When a repository is deleted, any associated package files are now immediately deleted from your {% data variables.product.prodname_registry %} external storage.
     - 
-      heading: 'Dependabot and Dependency graph changes'
+      heading: 'Dependabot及び依存関係グラフの変更'
       notes:
         - Dependency review is out of beta and is now generally available for {% data variables.product.prodname_GH_advanced_security %} customers. Dependency review provides an easy-to-understand view of dependency changes and their security impact in the "Files changed" tab of pull requests. It informs you of which dependencies were added, removed, or updated, along with vulnerability information. For more information, see "[Reviewing dependency changes in a pull request](/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request)."
         - '{% data variables.product.prodname_dependabot %} is now available as a private beta, offering both version updates and security updates for several popular ecosystems. {% data variables.product.prodname_dependabot %} on {% data variables.product.prodname_ghe_server %} requires {% data variables.product.prodname_actions %} and a pool of self-hosted runners configured for {% data variables.product.prodname_dependabot %} use. {% data variables.product.prodname_dependabot %} on {% data variables.product.prodname_ghe_server %} also requires {% data variables.product.prodname_github_connect %} to be enabled. To learn more and sign up for the beta, contact the GitHub Sales team.'
     - 
-      heading: 'Code scanning and secret scanning changes'
+      heading: 'Code scanningとSecret scanningの変更'
       notes:
         - The depth of {% data variables.product.prodname_codeql %}'s analysis has been improved by adding support for more [libraries and frameworks](https://codeql.github.com/docs/codeql-overview/supported-languages-and-frameworks/) and increasing the coverage of our existing library and framework models. [JavaScript](https://github.com/github/codeql/tree/main/javascript) analysis now supports most common templating languages, and [Java](https://github.com/github/codeql/tree/main/java) now covers more than three times the endpoints of previous {% data variables.product.prodname_codeql %} versions. As a result, {% data variables.product.prodname_codeql %} can now detect even more potential sources of untrusted user data, steps through which that data flows, and potentially dangerous sinks where the data could end up. This results in an overall improvement of the quality of {% data variables.product.prodname_code_scanning %} alerts.
         - '{% data variables.product.prodname_codeql %} now supports scanning standard language features in Java 16, such as records and pattern matching. {% data variables.product.prodname_codeql %} is able to analyze code written in Java version 7 through 16. For more information about supported languages and frameworks, see the [{% data variables.product.prodname_codeql %} documentation](https://codeql.github.com/docs/codeql-overview/supported-languages-and-frameworks/#id5).'
@@ -176,7 +176,7 @@ sections:
     - pre-receive フックの処理に固有のリソース制限によって、pre-receive フックに失敗するものが生じることがあります。
   deprecations:
     - 
-      heading: Deprecation of GitHub Enterprise Server 2.22
+      heading: GitHub Enterprise Server 2.22の非推奨化
       notes:
         - '**{% data variables.product.prodname_ghe_server %} 2.22 was discontinued on September 23, 2021**. This means that no patch releases will be made, even for critical security issues, after this date. For better performance, improved security, and new features, [upgrade to the newest version of {% data variables.product.prodname_ghe_server %}](/enterprise-server@3.3/admin/enterprise-management/upgrading-github-enterprise-server) as soon as possible.'
     - 
diff --git a/translations/ja-JP/data/release-notes/enterprise-server/3-3/0.yml b/translations/ja-JP/data/release-notes/enterprise-server/3-3/0.yml
index d0bf8c7ec0..fa825092b6 100644
--- a/translations/ja-JP/data/release-notes/enterprise-server/3-3/0.yml
+++ b/translations/ja-JP/data/release-notes/enterprise-server/3-3/0.yml
@@ -116,16 +116,16 @@ sections:
         - '{% data variables.product.prodname_ghe_server %} 3.3 contains performance improvements for job concurrency with {% data variables.product.prodname_actions %}. For more information about the new performance targets for a range of CPU and memory configurations, see "[Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_server %}](/admin/github-actions/enabling-github-actions-for-github-enterprise-server/getting-started-with-github-actions-for-github-enterprise-server#review-hardware-considerations)."'
         - To mitigate insider man in the middle attacks when using actions resolved through {% data variables.product.prodname_github_connect %} to {% data variables.product.prodname_dotcom_the_website %} from {% data variables.product.prodname_ghe_server %}, the actions namespace (`owner/name`) is retired on use. Retiring the namespace prevents that namespace from being created on your {% data variables.product.prodname_ghe_server %} instance, and ensures all workflows referencing the action will download it from {% data variables.product.prodname_dotcom_the_website %}.
     - 
-      heading: 'GitHub Packages changes'
+      heading: 'GitHub Packagesの変更'
       notes:
         - When a repository is deleted, any associated package files are now immediately deleted from your {% data variables.product.prodname_registry %} external storage.
     - 
-      heading: 'Dependabot and Dependency graph changes'
+      heading: 'Dependabot及び依存関係グラフの変更'
       notes:
         - Dependency review is out of beta and is now generally available for {% data variables.product.prodname_GH_advanced_security %} customers. Dependency review provides an easy-to-understand view of dependency changes and their security impact in the "Files changed" tab of pull requests. It informs you of which dependencies were added, removed, or updated, along with vulnerability information. For more information, see "[Reviewing dependency changes in a pull request](/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request)."
         - '{% data variables.product.prodname_dependabot %} is now available as a private beta, offering both version updates and security updates for several popular ecosystems. {% data variables.product.prodname_dependabot %} on {% data variables.product.prodname_ghe_server %} requires {% data variables.product.prodname_actions %} and a pool of self-hosted runners configured for {% data variables.product.prodname_dependabot %} use. {% data variables.product.prodname_dependabot %} on {% data variables.product.prodname_ghe_server %} also requires {% data variables.product.prodname_github_connect %} to be enabled. To learn more and sign up for the beta, contact the GitHub Sales team.'
     - 
-      heading: 'Code scanning and secret scanning changes'
+      heading: 'Code scanningとSecret scanningの変更'
       notes:
         - The depth of {% data variables.product.prodname_codeql %}'s analysis has been improved by adding support for more [libraries and frameworks](https://codeql.github.com/docs/codeql-overview/supported-languages-and-frameworks/) and increasing the coverage of our existing library and framework models. [JavaScript](https://github.com/github/codeql/tree/main/javascript) analysis now supports most common templating languages, and [Java](https://github.com/github/codeql/tree/main/java) now covers more than three times the endpoints of previous {% data variables.product.prodname_codeql %} versions. As a result, {% data variables.product.prodname_codeql %} can now detect even more potential sources of untrusted user data, steps through which that data flows, and potentially dangerous sinks where the data could end up. This results in an overall improvement of the quality of {% data variables.product.prodname_code_scanning %} alerts.
         - '{% data variables.product.prodname_codeql %} now supports scanning standard language features in Java 16, such as records and pattern matching. {% data variables.product.prodname_codeql %} is able to analyze code written in Java version 7 through 16. For more information about supported languages and frameworks, see the [{% data variables.product.prodname_codeql %} documentation](https://codeql.github.com/docs/codeql-overview/supported-languages-and-frameworks/#id5).'
@@ -172,7 +172,7 @@ sections:
     - '{% data variables.product.prodname_ghe_server %} 3.3 instances installed on Azure and provisioned with 32+ CPU cores would fail to launch, due to a bug present in the current Linux kernel. [Updated: 2022-04-08]'
   deprecations:
     - 
-      heading: Deprecation of GitHub Enterprise Server 2.22
+      heading: GitHub Enterprise Server 2.22の非推奨化
       notes:
         - '**{% data variables.product.prodname_ghe_server %} 2.22 was discontinued on September 23, 2021**. This means that no patch releases will be made, even for critical security issues, after this date. For better performance, improved security, and new features, [upgrade to the newest version of {% data variables.product.prodname_ghe_server %}](/enterprise-server@3.3/admin/enterprise-management/upgrading-github-enterprise-server) as soon as possible.'
     - 
diff --git a/translations/ja-JP/data/release-notes/enterprise-server/3-3/8.yml b/translations/ja-JP/data/release-notes/enterprise-server/3-3/8.yml
index 150826850d..a390a4f554 100644
--- a/translations/ja-JP/data/release-notes/enterprise-server/3-3/8.yml
+++ b/translations/ja-JP/data/release-notes/enterprise-server/3-3/8.yml
@@ -31,4 +31,3 @@ sections:
     - '{% data variables.product.prodname_registry %}のnpmレジストリは、メタデータのレスポンス中で時間の値を返さなくなります。これは、大きなパフォーマンス改善のために行われました。メタデータレスポンスの一部として時間の値を返すために必要なすべてのデータは保持し続け、既存のパフォーマンスの問題を解決した将来に、この値を返すことを再開します。'
     - pre-receive フックの処理に固有のリソース制限によって、pre-receive フックに失敗するものが生じることがあります。
     - '{% data variables.product.prodname_actions %} storage settings cannot be validated and saved in the {% data variables.enterprise.management_console %} when "Force Path Style" is selected, and must instead be configured with the `ghe-actions-precheck` command line utility.'
-    - '{% data variables.product.prodname_ghe_server %} 3.3 instances installed on Azure and provisioned with 32+ CPU cores would fail to launch, due to a bug present in the current Linux kernel. [Updated: 2022-04-08]'
diff --git a/translations/ja-JP/data/release-notes/enterprise-server/3-4/0-rc1.yml b/translations/ja-JP/data/release-notes/enterprise-server/3-4/0-rc1.yml
index 325ffe27e2..3168a61eb7 100644
--- a/translations/ja-JP/data/release-notes/enterprise-server/3-4/0-rc1.yml
+++ b/translations/ja-JP/data/release-notes/enterprise-server/3-4/0-rc1.yml
@@ -110,13 +110,13 @@ sections:
         - The search order behavior for self-hosted runners has now changed, so that the first available matching runner at any level will run the job in all cases. This allows jobs to be sent to self-hosted runners much faster, especially for organizations and enterprises with lots of self-hosted runners. Previously, when running a job that required a self-hosted runner, {% data variables.product.prodname_actions %} would look for self-hosted runners in the repository, organization, and enterprise, in that order.
         - 'Runner labels for {% data variables.product.prodname_actions %} self-hosted runners can now be listed, added and removed using the REST API. For more information about using the new APIs at a repository, organization, or enterprise level, see "[Repositories](/rest/reference/actions#list-labels-for-a-self-hosted-runner-for-a-repository)", "[Organizations](/rest/reference/actions#add-custom-labels-to-a-self-hosted-runner-for-an-organization)", and "[Enterprises](/rest/reference/enterprise-admin#list-labels-for-a-self-hosted-runner-for-an-enterprise)" in the REST API documentation.'
     - 
-      heading: 'Dependabot and Dependency graph changes'
+      heading: 'Dependabot及び依存関係グラフの変更'
       notes:
         - Dependency graph now supports detecting Python dependencies in repositories that use the Poetry package manager. Dependencies will be detected from both `pyproject.toml` and `poetry.lock` manifest files.
         - When configuring {% data variables.product.prodname_dependabot %} security and version updates on GitHub Enterprise Server, we recommend you also enable {% data variables.product.prodname_dependabot %} in {% data variables.product.prodname_github_connect %}. This will allow {% data variables.product.prodname_dependabot %} to retrieve an updated list of dependencies and vulnerabilities from {% data variables.product.prodname_dotcom_the_website %}, by querying for information such as the changelogs of the public releases of open source code that you depend upon. For more information, see "[Enabling the dependency graph and Dependabot alerts for your enterprise](/admin/configuration/configuring-github-connect/enabling-the-dependency-graph-and-dependabot-alerts-for-your-enterprise)."
         - '{% data variables.product.prodname_dependabot_alerts %} alerts can now be dismissed using the GraphQL API. For more information, see the "[dismissRepositoryVulnerabilityAlert](/graphql/reference/mutations#dismissrepositoryvulnerabilityalert)" mutation in the GraphQL API documentation.'
     - 
-      heading: 'Code scanning and secret scanning changes'
+      heading: 'Code scanningとSecret scanningの変更'
       notes:
         - The {% data variables.product.prodname_codeql %} CLI now supports including markdown-rendered query help in SARIF files, so that the help text can be viewed in the {% data variables.product.prodname_code_scanning %} UI when the query generates an alert. For more information, see the "[{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-11-23-display-help-text-for-your-custom-codeql-queries-in-code-scanning/)."
         - The {% data variables.product.prodname_codeql %} CLI and {% data variables.product.prodname_vscode %} extension now support building databases and analyzing code on machines powered by Apple Silicon, such as Apple M1. For more information, see the "[{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-11-10-codeql-now-supports-apple-silicon-m1/)."
diff --git a/translations/ja-JP/data/release-notes/enterprise-server/3-4/0.yml b/translations/ja-JP/data/release-notes/enterprise-server/3-4/0.yml
index edec18b18b..f55ba18065 100644
--- a/translations/ja-JP/data/release-notes/enterprise-server/3-4/0.yml
+++ b/translations/ja-JP/data/release-notes/enterprise-server/3-4/0.yml
@@ -109,13 +109,13 @@ sections:
         - The search order behavior for self-hosted runners has now changed, so that the first available matching runner at any level will run the job in all cases. This allows jobs to be sent to self-hosted runners much faster, especially for organizations and enterprises with lots of self-hosted runners. Previously, when running a job that required a self-hosted runner, {% data variables.product.prodname_actions %} would look for self-hosted runners in the repository, organization, and enterprise, in that order.
         - 'Runner labels for {% data variables.product.prodname_actions %} self-hosted runners can now be listed, added and removed using the REST API. For more information about using the new APIs at a repository, organization, or enterprise level, see "[Repositories](/rest/reference/actions#list-labels-for-a-self-hosted-runner-for-a-repository)", "[Organizations](/rest/reference/actions#add-custom-labels-to-a-self-hosted-runner-for-an-organization)", and "[Enterprises](/rest/reference/enterprise-admin#list-labels-for-a-self-hosted-runner-for-an-enterprise)" in the REST API documentation.'
     - 
-      heading: 'Dependabot and Dependency graph changes'
+      heading: 'Dependabot及び依存関係グラフの変更'
       notes:
         - Dependency graph now supports detecting Python dependencies in repositories that use the Poetry package manager. Dependencies will be detected from both `pyproject.toml` and `poetry.lock` manifest files.
         - When configuring {% data variables.product.prodname_dependabot %} security and version updates on GitHub Enterprise Server, we recommend you also enable {% data variables.product.prodname_dependabot %} in {% data variables.product.prodname_github_connect %}. This will allow {% data variables.product.prodname_dependabot %} to retrieve an updated list of dependencies and vulnerabilities from {% data variables.product.prodname_dotcom_the_website %}, by querying for information such as the changelogs of the public releases of open source code that you depend upon. For more information, see "[Enabling the dependency graph and Dependabot alerts for your enterprise](/admin/configuration/configuring-github-connect/enabling-the-dependency-graph-and-dependabot-alerts-for-your-enterprise)."
         - '{% data variables.product.prodname_dependabot_alerts %} alerts can now be dismissed using the GraphQL API. For more information, see the "[dismissRepositoryVulnerabilityAlert](/graphql/reference/mutations#dismissrepositoryvulnerabilityalert)" mutation in the GraphQL API documentation.'
     - 
-      heading: 'Code scanning and secret scanning changes'
+      heading: 'Code scanningとSecret scanningの変更'
       notes:
         - The {% data variables.product.prodname_codeql %} CLI now supports including markdown-rendered query help in SARIF files, so that the help text can be viewed in the {% data variables.product.prodname_code_scanning %} UI when the query generates an alert. For more information, see the "[{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-11-23-display-help-text-for-your-custom-codeql-queries-in-code-scanning/)."
         - The {% data variables.product.prodname_codeql %} CLI and {% data variables.product.prodname_vscode %} extension now support building databases and analyzing code on machines powered by Apple Silicon, such as Apple M1. For more information, see the "[{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-11-10-codeql-now-supports-apple-silicon-m1/)."
diff --git a/translations/ja-JP/data/reusables/actions/jobs/section-defining-outputs-for-jobs.md b/translations/ja-JP/data/reusables/actions/jobs/section-defining-outputs-for-jobs.md
index ecb105ef55..1d38b80a0c 100644
--- a/translations/ja-JP/data/reusables/actions/jobs/section-defining-outputs-for-jobs.md
+++ b/translations/ja-JP/data/reusables/actions/jobs/section-defining-outputs-for-jobs.md
@@ -1,6 +1,8 @@
 You can use `jobs.<job_id>.outputs` to create a `map` of outputs for a job. ジョブの出力は、そのジョブに依存しているすべての下流のジョブから利用できます。 ジョブの依存関係の定義に関する詳しい情報については[`jobs.<job_id>.needs`](/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idneeds)を参照してください。
 
-ジョブの出力は文字列であり、式を含むジョブの出力は、それぞれのジョブの終了時にランナー上で評価されます。 シークレットを含む出力はランナー上で編集され、{% data variables.product.prodname_actions %}には送られません。
+{% data reusables.actions.output-limitations %}
+
+Job outputs containing expressions are evaluated on the runner at the end of each job. シークレットを含む出力はランナー上で編集され、{% data variables.product.prodname_actions %}には送られません。
 
 依存するジョブでジョブの出力を使いたい場合には、`needs`コンテキストが利用できます。 詳細については、「[コンテキスト](/actions/learn-github-actions/contexts#needs-context)」を参照してください。
 
diff --git a/translations/ja-JP/data/reusables/actions/output-limitations.md b/translations/ja-JP/data/reusables/actions/output-limitations.md
new file mode 100644
index 0000000000..d26de54a7f
--- /dev/null
+++ b/translations/ja-JP/data/reusables/actions/output-limitations.md
@@ -0,0 +1 @@
+Outputs are Unicode strings, and can be a maximum of 1 MB. The total of all outputs in a workflow run can be a maximum of 50 MB.
diff --git a/translations/log/cn-resets.csv b/translations/log/cn-resets.csv
index 99e7d9a1c2..45097ea936 100644
--- a/translations/log/cn-resets.csv
+++ b/translations/log/cn-resets.csv
@@ -9,6 +9,7 @@ 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-personal-account-settings/managing-the-default-branch-name-for-your-repositories.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/about-organization-membership.md,broken liquid tags
 translations/zh-CN/content/actions/automating-builds-and-tests/about-continuous-integration.md,broken liquid tags
+translations/zh-CN/content/actions/deployment/about-deployments/deploying-with-github-actions.md,broken liquid tags
 translations/zh-CN/content/actions/hosting-your-own-runners/about-self-hosted-runners.md,broken liquid tags
 translations/zh-CN/content/actions/hosting-your-own-runners/adding-self-hosted-runners.md,Listed in localization-support#489
 translations/zh-CN/content/actions/hosting-your-own-runners/adding-self-hosted-runners.md,broken liquid tags
@@ -170,6 +171,7 @@ translations/zh-CN/content/code-security/supply-chain-security/end-to-end-supply
 translations/zh-CN/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-supply-chain-security.md,broken liquid tags
 translations/zh-CN/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph.md,Listed in localization-support#489
 translations/zh-CN/content/code-security/supply-chain-security/understanding-your-software-supply-chain/troubleshooting-the-dependency-graph.md,broken liquid tags
+translations/zh-CN/content/codespaces/codespaces-reference/using-github-copilot-in-codespaces.md,broken liquid tags
 translations/zh-CN/content/codespaces/customizing-your-codespace/changing-the-machine-type-for-your-codespace.md,broken liquid tags
 translations/zh-CN/content/codespaces/customizing-your-codespace/personalizing-codespaces-for-your-account.md,broken liquid tags
 translations/zh-CN/content/codespaces/customizing-your-codespace/setting-your-default-editor-for-codespaces.md,broken liquid tags
@@ -207,6 +209,7 @@ translations/zh-CN/content/education/manage-coursework-with-github-classroom/int
 translations/zh-CN/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/using-github-codespaces-with-github-classroom.md,broken liquid tags
 translations/zh-CN/content/education/manage-coursework-with-github-classroom/learn-with-github-classroom/view-autograding-results.md,broken liquid tags
 translations/zh-CN/content/get-started/customizing-your-github-workflow/exploring-integrations/about-github-marketplace.md,broken liquid tags
+translations/zh-CN/content/get-started/customizing-your-github-workflow/exploring-integrations/github-extensions-and-integrations.md,broken liquid tags
 translations/zh-CN/content/get-started/customizing-your-github-workflow/index.md,broken liquid tags
 translations/zh-CN/content/get-started/exploring-projects-on-github/following-organizations.md,broken liquid tags
 translations/zh-CN/content/get-started/getting-started-with-git/about-remote-repositories.md,broken liquid tags
diff --git a/translations/log/es-resets.csv b/translations/log/es-resets.csv
index 33c03a3848..87c48f2d9e 100644
--- a/translations/log/es-resets.csv
+++ b/translations/log/es-resets.csv
@@ -145,6 +145,7 @@ translations/es-ES/content/discussions/index.md,Listed in localization-support#4
 translations/es-ES/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-for-your-schoolwork/why-wasnt-my-application-for-a-student-developer-pack-approved.md,broken liquid tags
 translations/es-ES/content/education/guides.md,Listed in localization-support#489
 translations/es-ES/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/about-using-makecode-arcade-with-github-classroom.md,broken liquid tags
+translations/es-ES/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/integrate-github-classroom-with-an-ide.md,rendering error
 translations/es-ES/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/connect-a-learning-management-system-to-github-classroom.md,Listed in localization-support#489
 translations/es-ES/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/connect-a-learning-management-system-to-github-classroom.md,broken liquid tags
 translations/es-ES/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-a-group-assignment.md,Listed in localization-support#489
diff --git a/translations/pt-BR/content/actions/creating-actions/metadata-syntax-for-github-actions.md b/translations/pt-BR/content/actions/creating-actions/metadata-syntax-for-github-actions.md
index 2d49269cd8..0b7859ef25 100644
--- a/translations/pt-BR/content/actions/creating-actions/metadata-syntax-for-github-actions.md
+++ b/translations/pt-BR/content/actions/creating-actions/metadata-syntax-for-github-actions.md
@@ -88,6 +88,8 @@ Por exemplo, se um fluxo de trabalho definiu as entradas `numOctocats` e `octoca
 
 **Opcional** Os parâmetros de saída permitem que você declare os dados definidos por uma ação. As ações executadas posteriormente em um fluxo de trabalho podem usar os dados de saída definidos em ações executadas anteriormente.  Por exemplo, se uma ação executou a adição de duas entradas (x + y = z), a ação poderia usar o resultado da soma (z) como entrada em outras ações.
 
+{% data reusables.actions.output-limitations %}
+
 Se você não declarar uma saída no seu arquivo de metadados de ação, você ainda poderá definir as saídas e usá-las no seu fluxo de trabalho. Para obter mais informações sobre a definição de saídas em uma ação, consulte "[Comandos do fluxo de trabalho para {% data variables.product.prodname_actions %}](/actions/reference/workflow-commands-for-github-actions/#setting-an-output-parameter)."
 
 ### Exemplo: Declarando saídas para o contêiner do Docker e ações do JavaScript
@@ -110,6 +112,8 @@ saídas:
 
 As **saídas** `opcionais` usam os mesmos parâmetros que `outputs.<output_id>` e `outputs.<output_id>escription` (consulte "[`saída` para o contêiner do Docker e ações do JavaScript](#outputs-for-docker-container-and-javascript-actions)"), mas também inclui o token do `valor`.
 
+{% data reusables.actions.output-limitations %}
+
 ### Exemplo: Declarando saídas para ações compostas
 
 {% raw %}
@@ -391,7 +395,7 @@ runs:
 
 ### `runs.pre-entrypoint`
 
-**Opcional** Permite que você execute um script antes de a ação do `entrypoint` começar. Por exemplo, você pode usar o `pre-entrypoint:` para executar um pré-requisito do script da configuração. {% data variables.product.prodname_actions %} usa a `execução do docker` para lançar esta ação e executa o script dentro de um novo contêiner que usa a mesma imagem-base. Isso significa que o momento de execução é diferente do contêiner principal do `entrypoint` e qualquer status de que você precisar devem ser acessado na área de trabalho, em `HOME`, ou como uma variável `STATE_`. A ação `pre-entrypoint:` sempre é executada por padrão, mas você pode substitui-la usando [`runs.pre-if`](#runspre-if).
+**Opcional** Permite que você execute um script antes de a ação do `entrypoint` começar. Por exemplo, você pode usar o `pre-entrypoint:` para executar um pré-requisito do script da configuração. {% data variables.product.prodname_actions %} usa a `execução do docker` para lançar esta ação e executa o script dentro de um novo contêiner que usa a mesma imagem-base. Isso significa que o momento de execução é diferente do contêiner principal do `entrypoint` e todos os status que você precisar deverão ser acessados na área de trabalho, em `HOME` ou como uma variável `STATE_`. A ação `pre-entrypoint:` sempre é executada por padrão, mas você pode substitui-la usando [`runs.pre-if`](#runspre-if).
 
 O tempo de execução especificado com a sintaxe [`em uso`](#runsusing) irá executar este arquivo.
 
diff --git a/translations/pt-BR/content/actions/using-github-hosted-runners/about-github-hosted-runners.md b/translations/pt-BR/content/actions/using-github-hosted-runners/about-github-hosted-runners.md
index ebbe380e44..e0386995c5 100644
--- a/translations/pt-BR/content/actions/using-github-hosted-runners/about-github-hosted-runners.md
+++ b/translations/pt-BR/content/actions/using-github-hosted-runners/about-github-hosted-runners.md
@@ -78,6 +78,7 @@ Para a lista geral das ferramentas incluídas para cada sistema operacional do e
 * [Ubuntu 18.04 LTS](https://github.com/actions/virtual-environments/blob/main/images/linux/Ubuntu1804-Readme.md)
 * [Windows Server 2022](https://github.com/actions/virtual-environments/blob/main/images/win/Windows2022-Readme.md)
 * [Windows Server 2019](https://github.com/actions/virtual-environments/blob/main/images/win/Windows2019-Readme.md)
+* [macOS 12](https://github.com/actions/virtual-environments/blob/main/images/macos/macos-12-Readme.md)
 * [macOS 11](https://github.com/actions/virtual-environments/blob/main/images/macos/macos-11-Readme.md)
 * [macOS 10.15](https://github.com/actions/virtual-environments/blob/main/images/macos/macos-10.15-Readme.md)
 
diff --git a/translations/pt-BR/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise.md b/translations/pt-BR/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise.md
index cd64271c31..8238abc58e 100644
--- a/translations/pt-BR/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise.md
+++ b/translations/pt-BR/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise.md
@@ -19,7 +19,9 @@ topics:
 
 {% ifversion ghec %}
 
-Os proprietários das empresas em {% data variables.product.product_name %} podem controlar os requisitos de autenticação e acesso aos recursos da empresa. Você pode optar por permitir que os integrantescriem e gerenciem contas de usuário ou sua empresa pode criar e gerenciar contas para os integrantes. Se você permitir que os integrantes gerenciem suas próprias contas, você também pode configurar a autenticação SAML para aumentar a segurança e centralizar a identidade e o acesso dos aplicativos web que sua equipe usa. Se você optar por gerenciar as contas de usuário dos seus integrantes, será necessário configurar a autenticação SAML.
+Os proprietários das empresas em {% data variables.product.product_name %} podem controlar os requisitos de autenticação e acesso aos recursos da empresa.
+
+You can choose to allow members to create and manage user accounts, or your enterprise can create and manage accounts for members with {% data variables.product.prodname_emus %}. Se você permitir que os integrantes gerenciem suas próprias contas, você também pode configurar a autenticação SAML para aumentar a segurança e centralizar a identidade e o acesso dos aplicativos web que sua equipe usa. Se você optar por gerenciar as contas de usuário dos seus integrantes, será necessário configurar a autenticação SAML.
 
 ## Métodos de autenticação para {% data variables.product.product_name %}
 
diff --git a/translations/pt-BR/content/admin/index.md b/translations/pt-BR/content/admin/index.md
index 3fde884caa..c7579e69dc 100644
--- a/translations/pt-BR/content/admin/index.md
+++ b/translations/pt-BR/content/admin/index.md
@@ -71,13 +71,13 @@ changelog:
 featuredLinks:
   guides:
     - '{% ifversion ghae %}/admin/user-management/auditing-users-across-your-enterprise{% endif %}'
+    - /admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise
+    - /admin/policies/enforcing-policies-for-your-enterprise/about-enterprise-policies
     - '{% ifversion ghae %}/admin/configuration/restricting-network-traffic-to-your-enterprise{% endif %}'
     - '{% ifversion ghes %}/admin/configuration/configuring-backups-on-your-appliance{% endif %}'
     - '{% ifversion ghes %}/admin/enterprise-management/creating-a-high-availability-replica{% endif %}'
     - '{% ifversion ghes %}/admin/overview/about-upgrades-to-new-releases{% endif %}'
     - '{% ifversion ghec %}/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise{% endif %}'
-    - '{% ifversion ghec %}/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/about-enterprise-managed-users{% endif %}'
-    - '{% ifversion ghec %}/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-identity-and-access-management-for-your-enterprise{% endif %}'
     - '{% ifversion ghec %}/admin/user-management/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise{% endif %}'
     - /admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-self-hosted-runners-for-your-enterprise
   guideCards:
diff --git a/translations/pt-BR/content/admin/overview/about-enterprise-accounts.md b/translations/pt-BR/content/admin/overview/about-enterprise-accounts.md
index d69578951d..9d9ec1d225 100644
--- a/translations/pt-BR/content/admin/overview/about-enterprise-accounts.md
+++ b/translations/pt-BR/content/admin/overview/about-enterprise-accounts.md
@@ -32,18 +32,18 @@ A conta corporativa em {% ifversion ghes %}{% data variables.product.product_loc
 
 {% endif %}
 
-As organizações são contas compartilhadas em que os integrantes da empresa podem colaborar em muitos projetos de uma só vez. Os proprietários da organização podem gerenciar o acesso aos dados e projetos da organização, com recursos sofisticados de segurança e administrativos. Para obter mais informações, consulte {% ifversion ghec %}"[Sobre as organizações](/organizations/collaborating-with-groups-in-organizations/about-organizations).{% elsif ghes or ghae %}"[Sobre as organizações](/organizations/collaborating-with-groups-in-organizations/about-organizations)" e "[Gerenciando usuários, organizações e repositórios](/admin/user-management)".{% endif %}
+As organizações são contas compartilhadas em que os integrantes da empresa podem colaborar em muitos projetos de uma só vez. Os proprietários da organização podem gerenciar o acesso aos dados e projetos da organização, com recursos sofisticados de segurança e administrativos. Para obter mais informações, consulte "[Sobre organizações](/organizations/collaborating-with-groups-in-organizations/about-organizations)".
+
+{% ifversion ghec %}
+Enterprise owners can invite existing organizations to join your enterprise account, or create new organizations in the enterprise settings.
+{% endif %}
+
+Your enterprise account allows you to manage and enforce policies for all the organizations owned by the enterprise. {% data reusables.enterprise.about-policies %} For more information, see "[About enterprise policies](/admin/policies/enforcing-policies-for-your-enterprise/about-enterprise-policies)."
 
 {% ifversion ghec %}
 
-Os proprietários das empresas podem criar organizações e vincular as organizações à empresa. Como alternativa, você pode convidar uma organização existente para participar da conta corporativa. Depois de adicionar organizações à conta corporativa, você pode gerenciar e aplicar políticas para as organizações. Opções específicas de aplicação variam de acordo com a configuração; normalmente, é possível optar por aplicar uma única política para cada organização na sua conta corporativa ou permitir que proprietários definam a política no nível da organização. Para obter mais informações, consulte "[Definindo políticas para a sua empresa](/admin/policies)".
-
 {% data reusables.enterprise.create-an-enterprise-account %} Para obter mais informações, consulte "[Criando uma conta corporativa](/admin/overview/creating-an-enterprise-account)".
 
-{% elsif ghes or ghae %}
-
-Para obter mais informações sobre o gerenciamento de políticas para a conta corporativa, consulte "[Políticas de configuração para a sua empresa](/admin/policies)".
-
 {% endif %}
 
 ## Sobre a administração da conta corporativa
diff --git a/translations/pt-BR/content/admin/overview/creating-an-enterprise-account.md b/translations/pt-BR/content/admin/overview/creating-an-enterprise-account.md
index 770889c2ce..7745c104c2 100644
--- a/translations/pt-BR/content/admin/overview/creating-an-enterprise-account.md
+++ b/translations/pt-BR/content/admin/overview/creating-an-enterprise-account.md
@@ -16,7 +16,7 @@ shortTitle: Criar conta corporativa
 
 {% data variables.product.prodname_ghe_cloud %} inclui a opção de criar uma conta corporativa, que permite a colaboração entre várias organizações e fornece aos administradores um único ponto de visibilidade e gestão. Para obter mais informações, consulte "[Sobre contas corporativas](/admin/overview/about-enterprise-accounts)".
 
-{% data reusables.enterprise.create-an-enterprise-account %} Se você pagar por fatura, você poderá criar uma conta corporativa em {% data variables.product.prodname_dotcom %}. Caso contrário, você poderá [Entrar em contato com a nossa equipe de vendas](https://github.com/enterprise/contact?ref_page=/pricing&ref_cta=Contact%20Sales&ref_loc=cards) para passar para a faturação.
+{% data reusables.enterprise.create-an-enterprise-account %} Se você pagar por fatura, você poderá criar uma conta corporativa em {% data variables.product.prodname_dotcom %}. If not, you can [contact our sales team](https://github.com/enterprise/contact?ref_page=/pricing&ref_cta=Contact%20Sales&ref_loc=cards) to create an enterprise account for you.
 
 Uma conta corporativa está incluída em {% data variables.product.prodname_ghe_cloud %}. Portanto, a criação de uma não afetará a sua conta.
 
@@ -29,7 +29,10 @@ Se a organização estiver conectada a {% data variables.product.prodname_ghe_se
 
 ## Criando uma conta corporativa em {% data variables.product.prodname_dotcom %}
 
-Para criar uma conta corporativa em {% data variables.product.prodname_dotcom %}, a sua organização deve usar {% data variables.product.prodname_ghe_cloud %} e pagar por fatura.
+To create an enterprise account, your organization must be using {% data variables.product.prodname_ghe_cloud %}.
+
+If you pay by invoice, you can create an enterprise account directly through {% data variables.product.prodname_dotcom %}. If you do not currently pay by invoice, you can [contact our sales team](https://github.com/enterprise/contact?ref_page=/pricing&ref_cta=Contact%20Sales&ref_loc=cards) to create an enterprise account for you.
+
 
 {% data reusables.organizations.billing-settings %}
 1. Clique **- Atualizar para a conta corporativa**.
diff --git a/translations/pt-BR/content/admin/policies/enforcing-policies-for-your-enterprise/about-enterprise-policies.md b/translations/pt-BR/content/admin/policies/enforcing-policies-for-your-enterprise/about-enterprise-policies.md
new file mode 100644
index 0000000000..19bbbcdaf6
--- /dev/null
+++ b/translations/pt-BR/content/admin/policies/enforcing-policies-for-your-enterprise/about-enterprise-policies.md
@@ -0,0 +1,30 @@
+---
+title: About enterprise policies
+intro: 'With enterprise policies, you can manage the policies for all the organizations owned by your enterprise.'
+versions:
+  ghec: '*'
+  ghes: '*'
+  ghae: '*'
+type: overview
+topics:
+  - Enterprise
+  - Policies
+---
+
+To help you enforce business rules and regulatory compliance, policies provide a single point of management for all the organizations owned by an enterprise account.
+
+{% data reusables.enterprise.about-policies %}
+
+For example, with the "Base permissions" policy, you can allow organization owners to configure the "Base permissions" policy for their organization, or you can enforce a specific base permissions level, such as "Read", for all organizations within the enterprise.
+
+By default, no enterprise policies are enforced. To identify policies that should be enforced to meet the unique requirements of your business, we recommend reviewing all the available policies in your enterprise account, starting with repository management policies. For more information, see "[Enforcing repository management polices in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise)."
+
+While you're configuring enterprise policies, to help you understand the impact of changing each policy, you can view the current configurations for the organizations owned by your enterprise.
+
+{% ifversion ghes %}
+Another way to enforce standards within your enterprise is to use pre-receive hooks, which are scripts that run on {% data variables.product.product_location %} to implement quality checks. For more information, see "[Enforcing policy with pre-receive hooks](/admin/policies/enforcing-policy-with-pre-receive-hooks)."
+{% endif %}
+
+## Leia mais
+
+- "[Sobre contas corporativas](/admin/overview/about-enterprise-accounts)"
diff --git a/translations/pt-BR/content/admin/policies/enforcing-policies-for-your-enterprise/index.md b/translations/pt-BR/content/admin/policies/enforcing-policies-for-your-enterprise/index.md
index f42a496789..c7b4ddd495 100644
--- a/translations/pt-BR/content/admin/policies/enforcing-policies-for-your-enterprise/index.md
+++ b/translations/pt-BR/content/admin/policies/enforcing-policies-for-your-enterprise/index.md
@@ -13,6 +13,7 @@ topics:
   - Enterprise
   - Policies
 children:
+  - /about-enterprise-policies
   - /enforcing-repository-management-policies-in-your-enterprise
   - /enforcing-team-policies-in-your-enterprise
   - /enforcing-project-board-policies-in-your-enterprise
diff --git a/translations/pt-BR/content/billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise.md b/translations/pt-BR/content/billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise.md
index 53031d388a..f0a81dfc60 100644
--- a/translations/pt-BR/content/billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise.md
+++ b/translations/pt-BR/content/billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise.md
@@ -53,7 +53,7 @@ Cada usuário em {% data variables.product.product_location %} consome uma esta
 
 {% endif %}
 
-{% data reusables.billing.about-invoices-for-enterprises %} Para mais informações sobre {% ifversion ghes %} licenciamento, uso e faturas{% elsif ghec %}uso e faturas{% endif %}, consulte o seguinte{% ifversion ghes %} na documentação de {% data variables.product.prodname_ghe_cloud %}.{% else %}.{% endif %}
+{% ifversion ghec %}For {% data variables.product.prodname_ghe_cloud %} customers with an enterprise account, {% data variables.product.company_short %} bills through your enterprise account on {% data variables.product.prodname_dotcom_the_website %}. For invoiced customers, each{% elsif ghes %}For invoiced {% data variables.product.prodname_enterprise %} customers, {% data variables.product.company_short %} bills through an enterprise account on {% data variables.product.prodname_dotcom_the_website %}. Each{% endif %} invoice includes a single bill charge for all of your paid {% data variables.product.prodname_dotcom_the_website %} services and any {% data variables.product.prodname_ghe_server %} instances. For more information about {% ifversion ghes %}licensing, usage, and invoices{% elsif ghec %}usage and invoices{% endif %}, see the following{% ifversion ghes %} in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}.{% endif %}
 
 {%- ifversion ghes %}
 - "[Sobre preços por usuário](/enterprise-cloud@latest/billing/managing-billing-for-your-github-account/about-per-user-pricing)"
diff --git a/translations/pt-BR/content/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account.md b/translations/pt-BR/content/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account.md
index 230dc2bfdc..1b15944c6b 100644
--- a/translations/pt-BR/content/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account.md
+++ b/translations/pt-BR/content/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account.md
@@ -17,7 +17,7 @@ shortTitle: Visualizar assinatura & uso
 
 ## Sobre a cobrança de contas corporativas
 
-Você pode ver a visão geral da {% ifversion ghec %}sua assinatura e da licença{% elsif ghes %}a paga{% endif %} usada para a {% ifversion ghec %}sua{% elsif ghes %}a{% endif %} conta corporativa em {% ifversion ghec %}{% data variables.product.prodname_dotcom_the_website %}{% elsif ghes %}{% data variables.product.product_location %}{% endif %}.
+You can view an overview of {% ifversion ghec %}your subscription and paid{% elsif ghes %}the license{% endif %} usage for {% ifversion ghec %}your{% elsif ghes %}the{% endif %} enterprise account on {% ifversion ghec %}{% data variables.product.prodname_dotcom_the_website %}{% elsif ghes %}{% data variables.product.product_location %}{% endif %}.{% ifversion ghec %} {% data reusables.enterprise.create-an-enterprise-account %} For more information, see "[Creating an enterprise account](/enterprise-cloud@latest/admin/overview/creating-an-enterprise-account)."{% endif %}
 
 Para {% data variables.product.prodname_enterprise %} clientes faturados{% ifversion ghes %} que usam {% data variables.product.prodname_ghe_cloud %} e {% data variables.product.prodname_ghe_server %}{% endif %}, cada fatura inclui as informações sobre os serviços cobrados para todos os produtos. Por exemplo, além do seu uso para {% ifversion ghec %}{% data variables.product.prodname_ghe_cloud %}{% elsif ghes %}{% data variables.product.product_name %}{% endif %}, você pode ter uso para {% data variables.product.prodname_GH_advanced_security %}{% ifversion ghec %}, {% elsif ghes %}. Você também pode ter uso em {% data variables.product.prodname_dotcom_the_website %}, como {% endif %}licenças pagas em organizações fora da conta corporativa, pacotes de dados para {% data variables.large_files.product_name_long %}ou assinaturas de aplicativos em {% data variables.product.prodname_marketplace %}. Para obter mais informações sobre faturas, consulte "[Gerenciando faturas para a sua empresa]({% ifversion ghes %}/enterprise-cloud@latest{% endif %}/billing/managing-billing-for-your-github-account/managing-invoices-for-your-enterprise){% ifversion ghec %}. "{% elsif ghes %}" na documentação de {% data variables.product.prodname_dotcom_the_website %} .{% endif %}
 
diff --git a/translations/pt-BR/content/code-security/dependabot/dependabot-version-updates/about-dependabot-version-updates.md b/translations/pt-BR/content/code-security/dependabot/dependabot-version-updates/about-dependabot-version-updates.md
index 6646217d48..c22896468c 100644
--- a/translations/pt-BR/content/code-security/dependabot/dependabot-version-updates/about-dependabot-version-updates.md
+++ b/translations/pt-BR/content/code-security/dependabot/dependabot-version-updates/about-dependabot-version-updates.md
@@ -30,7 +30,7 @@ shortTitle: Atualizações de versão do Dependabot
 
 O {% data variables.product.prodname_dependabot %} facilita a manutenção de suas dependências. Você pode usá-lo para garantir que seu repositório se mantenha atualizado automaticamente com as versões mais recentes dos pacotes e aplicações do qual ele depende.
 
-You enable {% data variables.product.prodname_dependabot_version_updates %} by checking a _dependabot.yml_ configuration file into your repository. O arquivo de configuração especifica a localização do manifesto ou de outros arquivos de definição de pacote, armazenados no seu repositório. O {% data variables.product.prodname_dependabot %} usa essas informações para verificar pacotes e aplicativos desatualizados. {% data variables.product.prodname_dependabot %} determina se há uma nova versão de uma dependência observando a versão semântica ([semver](https://semver.org/)) da dependência para decidir se deve atualizar para essa versão. Para certos gerentes de pacote, {% data variables.product.prodname_dependabot_version_updates %} também é compatível com armazenamento. Dependências de vendor (ou armazenadas) são dependências registradas em um diretório específico em um repositório, em vez de referenciadas em um manifesto. Dependências de vendor estão disponíveis no tempo de criação, ainda que os servidores de pacote estejam indisponíveis. {% data variables.product.prodname_dependabot_version_updates %} pode ser configurado para verificar as dependências de vendor para novas versões e atualizá-las, se necessário.
+You enable {% data variables.product.prodname_dependabot_version_updates %} by checking a `dependabot.yml` configuration file into your repository. O arquivo de configuração especifica a localização do manifesto ou de outros arquivos de definição de pacote, armazenados no seu repositório. O {% data variables.product.prodname_dependabot %} usa essas informações para verificar pacotes e aplicativos desatualizados. {% data variables.product.prodname_dependabot %} determina se há uma nova versão de uma dependência observando a versão semântica ([semver](https://semver.org/)) da dependência para decidir se deve atualizar para essa versão. Para certos gerentes de pacote, {% data variables.product.prodname_dependabot_version_updates %} também é compatível com armazenamento. Dependências de vendor (ou armazenadas) são dependências registradas em um diretório específico em um repositório, em vez de referenciadas em um manifesto. Dependências de vendor estão disponíveis no tempo de criação, ainda que os servidores de pacote estejam indisponíveis. {% data variables.product.prodname_dependabot_version_updates %} pode ser configurado para verificar as dependências de vendor para novas versões e atualizá-las, se necessário.
 
 Quando {% data variables.product.prodname_dependabot %} identifica uma dependência desatualizada, ele cria uma pull request para atualizar o manifesto para a última versão da dependência. Para dependências de vendor, {% data variables.product.prodname_dependabot %} levanta um pull request para substituir diretamente a dependência desatualizada pela nova versão. Você verifica se os seus testes passam, revisa o changelog e lança observações incluídas no resumo do pull request e, em seguida, faz a mesclagem. Para obter mais informações, consulte "[Configurando as atualizações da versão de {% data variables.product.prodname_dependabot %}](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/enabling-and-disabling-dependabot-version-updates)".
 
diff --git a/translations/pt-BR/content/developers/webhooks-and-events/webhooks/webhook-events-and-payloads.md b/translations/pt-BR/content/developers/webhooks-and-events/webhooks/webhook-events-and-payloads.md
index fe433b49be..47a2cb6ec8 100644
--- a/translations/pt-BR/content/developers/webhooks-and-events/webhooks/webhook-events-and-payloads.md
+++ b/translations/pt-BR/content/developers/webhooks-and-events/webhooks/webhook-events-and-payloads.md
@@ -1483,6 +1483,17 @@ Esse evento ocorre quando alguém aciona a execução de um fluxo de trabalho no
 
 - {% data variables.product.prodname_github_apps %} deve ter a permissão do conteúdo `` para receber este webhook.
 
+### Objeto da carga do webhook
+
+| Tecla    | Tipo     | Descrição                                                                                                              |
+| -------- | -------- | ---------------------------------------------------------------------------------------------------------------------- |
+| `inputs` | `objeto` | Inputs to the workflow. Each key represents the name of the input while it's value represents the value of that input. |
+{% data reusables.webhooks.org_desc %}
+| `ref` | `string` | The branch ref from which the workflow was run. |
+{% data reusables.webhooks.repo_desc %}
+{% data reusables.webhooks.sender_desc %}
+| `workflow` | `string` | Relative path to the workflow file which contains the workflow. |
+
 ### Exemplo de carga de webhook
 
 {{ webhookPayloadsForCurrentVersion.workflow_dispatch }}
diff --git a/translations/pt-BR/content/get-started/onboarding/getting-started-with-github-enterprise-cloud.md b/translations/pt-BR/content/get-started/onboarding/getting-started-with-github-enterprise-cloud.md
index 1266c6a19a..1e31a08bc6 100644
--- a/translations/pt-BR/content/get-started/onboarding/getting-started-with-github-enterprise-cloud.md
+++ b/translations/pt-BR/content/get-started/onboarding/getting-started-with-github-enterprise-cloud.md
@@ -56,21 +56,23 @@ A página de configurações de cobrança da sua organização permite que você
 Apenas os integrantes da organização com a função de *proprietário* ou *gerente de cobrança* podem acessar ou alterar as configurações de cobrança da sua organização. Um gerente de cobrança é um usuário que gerencia as configurações de cobrança para sua organização e não usa uma licença paga na assinatura da sua organização. Para obter mais informações sobre como adicionar um gerente de cobrança à sua organização, consulte "[Adicionando um gerente de cobrança à sua organização](/organizations/managing-peoples-access-to-your-organization-with-roles/adding-a-billing-manager-to-your-organization)".
 
 ### Configurando uma conta corporativa com {% data variables.product.prodname_ghe_cloud %}
- {% note %}
-
-Para obter uma conta corporativa criada para você, entre em contato com [a equipe de vendas de {% data variables.product.prodname_dotcom %}](https://enterprise.github.com/contact).
-
- {% endnote %}
 
 #### 1. Sobre contas corporativas
 
 Uma conta corporativa permite que você gerencie centralmente as políticas e configurações para várias organizações {% data variables.product.prodname_dotcom %}, incluindo acesso de integrantes, cobrança e uso e segurança. Para obter mais informações, consulte "[Sobre contas corporativas](/enterprise-cloud@latest/admin/overview/about-enterprise-accounts)".
-#### 2. Adicionar organizações à suas conta corporativa
+
+#### 2. Creating an enterpise account
+
+ {% data variables.product.prodname_ghe_cloud %} customers paying by invoice can create an enterprise account directly through {% data variables.product.prodname_dotcom %}. For more information, see "[Creating an enterprise account](/enterprise-cloud@latest/admin/overview/creating-an-enterprise-account)."
+
+ {% data variables.product.prodname_ghe_cloud %} customers not currently paying by invoice can contact [{% data variables.product.prodname_dotcom %}'s Sales team](https://enterprise.github.com/contact) to create an enterprise account for you.
+
+#### 3. Adicionar organizações à conta corporativa
 
 É possível criar novas organizações para serem gerenciadas em sua conta corporativa. Para obter mais informações, consulte "[Adicionando organizações à sua empresa](/enterprise-cloud@latest/admin/user-management/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise)".
 
 Entre em contato com o seu representante da conta de vendas de {% data variables.product.prodname_dotcom %} se você quiser transferir uma organização existente para a sua conta corporativa.
-#### 3. Exibir assinatura e uso da conta corporativa
+#### 4. Exibir assinatura e uso da conta corporativa
 Você pode visualizar a sua assinatura atual, uso da licença, faturas, histórico de pagamentos e outras informações de cobrança para sua conta corporativa a qualquer momento. Os proprietários da empresa e os gerentes de cobrança podem acessar e gerenciar as configurações de cobrança para contas corporativas. Para obter mais informações, consulte "[Exibir a assinatura e o uso de sua conta corporativa](/enterprise-cloud@latest/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account)".
 
 ## Parte 3: Gerenciando seus integrantes e equipes da empresa com {% data variables.product.prodname_ghe_cloud %}
diff --git a/translations/pt-BR/content/get-started/using-github/keyboard-shortcuts.md b/translations/pt-BR/content/get-started/using-github/keyboard-shortcuts.md
index e71d19d62f..cde30dc308 100644
--- a/translations/pt-BR/content/get-started/using-github/keyboard-shortcuts.md
+++ b/translations/pt-BR/content/get-started/using-github/keyboard-shortcuts.md
@@ -89,22 +89,24 @@ Para mais atalhos de teclado, consulte a [Documentação CodeMirror](https://cod
 
 ## Comentários
 
-| Atalho                                                                                                                        | Descrição                                                                                                                                                                                                                                                      |
-| ----------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| <kbd>Command</kbd>+<kbd>B</kbd> (Mac) ou </br> <kbd>Ctrl</kbd>+<kbd>B</kbd> (Windows/Linux)                                   | Insere formatação Markdown para texto em negrito                                                                                                                                                                                                               |
-| <kbd>Command</kbd>+<kbd>I</kbd> (Mac) ou </br> <kbd>Ctrl</kbd>+<kbd>I</kbd> (Windows/Linux)                                   | Insere a formatação Markdown para texto em itálico{% ifversion fpt or ghae or ghes > 3.1 or ghec %}
-| <kbd>Command</kbd>+<kbd>E</kbd> (Mac) ou </br> <kbd>Ctrl</kbd>+<kbd>E</kbd> (Windows/Linux)                                   | Insere a formatação Markdown para código ou um comando dentro da linha{% endif %}
-| <kbd>Command</kbd>+<kbd>K</kbd> (Mac) ou </br> <kbd>Ctrl</kbd>+<kbd>K</kbd> (Windows/Linux)                                   | Insere formatação Markdown para criar um link                                                                                                                                                                                                                  |
-| <kbd>Command</kbd>+<kbd>Shift</kbd>+<kbd>P</kbd> (Mac) ou </br> <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>P</kbd> (Windows/Linux) | Alterna entre as abas de comentários **Escrever** e **Visualizar**{% ifversion fpt or ghae or ghes > 3.4 or ghec %}
-| <kbd>Command</kbd>+<kbd>Shift</kbd>+<kbd>V</kbd> (Mac) ou </br> <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>V</kbd> (Windows/Linux) | Cola o link HTML como texto simples{% endif %}{% ifversion fpt or ghae or ghes > 3.2 or ghec %}
-| <kbd>Command</kbd>+<kbd>Shift</kbd>+<kbd>7</kbd> (Mac) ou </br> <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>7</kbd> (Windows/Linux) | Insere a formatação de Markdown para uma lista ordenada                                                                                                                                                                                                        |
-| <kbd>Command</kbd>+<kbd>Shift</kbd>+<kbd>8</kbd> (Mac) ou </br> <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>8</kbd> (Windows/Linux) | Insere a formatação Markdown para uma lista não ordenada{% endif %}
-| <kbd>Command</kbd>+<kbd>Enter</kbd> (Mac) ou </br> <kbd>Ctrl</kbd>+<kbd>Enter</kbd> (Windows/Linux)                           | Envia um comentário                                                                                                                                                                                                                                            |
-| <kbd>Ctrl</kbd>+<kbd>.</kbd> e, em seguida, <kbd>Ctrl</kbd>+<kbd>[salvou o número de resposta]</kbd>                          | Abre o menu de respostas salvas e autocompleta o campo de comentário com uma resposta salva. Para obter mais informações, consulte "[Sobre respostas salvas](/articles/about-saved-replies)".{% ifversion fpt or ghae or ghes > 3.2 or ghec %}
-| <kbd>Command</kbd>+<kbd>Shift</kbd>+<kbd>.</kbd> (Mac) ou </br> <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>.</kbd> (Windows/Linux) | Insere a formatação Markdown para uma citação{% endif %}{% ifversion fpt or ghec %}
-| <kbd>Command</kbd>+<kbd>G</kbd> (Mac) ou </br> <kbd>Ctrl</kbd>+<kbd>G</kbd> (Windows/Linux)                                   | Insere uma sugestão. Para obter mais informações, consulte "[Revisar alterações propostas em uma pull request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request)". 
+| Atalho                                                                                                                                                      | Descrição                                                                                                                                                                                                                                                      |
+| ----------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| <kbd>Command</kbd>+<kbd>B</kbd> (Mac) ou </br> <kbd>Ctrl</kbd>+<kbd>B</kbd> (Windows/Linux)                                                                 | Insere formatação Markdown para texto em negrito                                                                                                                                                                                                               |
+| <kbd>Command</kbd>+<kbd>I</kbd> (Mac) ou </br> <kbd>Ctrl</kbd>+<kbd>I</kbd> (Windows/Linux)                                                                 | Insere a formatação Markdown para texto em itálico{% ifversion fpt or ghae or ghes > 3.1 or ghec %}
+| <kbd>Command</kbd>+<kbd>E</kbd> (Mac) ou </br> <kbd>Ctrl</kbd>+<kbd>E</kbd> (Windows/Linux)                                                                 | Inserts Markdown formatting for code or a command within a line{% endif %}{% ifversion fpt or ghae-issue-5434 or ghes > 3.1 or ghec %}
+| <kbd>Command</kbd>+<kbd>K</kbd> (Mac) ou </br> <kbd>Ctrl</kbd>+<kbd>K</kbd> (Windows/Linux)                                                                 | Inserts Markdown formatting for creating a link{% endif %}{% ifversion fpt or ghae-issue-7103 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) ou </br> <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>P</kbd> (Windows/Linux)                               | Alterna entre as abas de comentários **Escrever** e **Visualizar**{% ifversion fpt or ghae or ghes > 3.4 or ghec %}
+| <kbd>Command</kbd>+<kbd>Shift</kbd>+<kbd>V</kbd> (Mac) ou </br> <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>V</kbd> (Windows/Linux)                               | Cola o link HTML como texto simples{% endif %}{% ifversion fpt or ghae or ghes > 3.2 or ghec %}
+| <kbd>Command</kbd>+<kbd>Shift</kbd>+<kbd>Opt</kbd>+<kbd>V</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>Alt</kbd>+<kbd>V</kbd> (Windows/Linux) | Cola o link HTML como texto simples{% endif %}{% ifversion fpt or ghae or ghes > 3.2 or ghec %}
+| <kbd>Command</kbd>+<kbd>Shift</kbd>+<kbd>7</kbd> (Mac) ou </br> <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>7</kbd> (Windows/Linux)                               | Insere a formatação de Markdown para uma lista ordenada                                                                                                                                                                                                        |
+| <kbd>Command</kbd>+<kbd>Shift</kbd>+<kbd>8</kbd> (Mac) ou </br> <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>8</kbd> (Windows/Linux)                               | Insere a formatação Markdown para uma lista não ordenada{% endif %}
+| <kbd>Command</kbd>+<kbd>Enter</kbd> (Mac) ou </br> <kbd>Ctrl</kbd>+<kbd>Enter</kbd> (Windows/Linux)                                                         | Envia um comentário                                                                                                                                                                                                                                            |
+| <kbd>Ctrl</kbd>+<kbd>.</kbd> e, em seguida, <kbd>Ctrl</kbd>+<kbd>[salvou o número de resposta]</kbd>                                                        | Abre o menu de respostas salvas e autocompleta o campo de comentário com uma resposta salva. Para obter mais informações, consulte "[Sobre respostas salvas](/articles/about-saved-replies)".{% ifversion fpt or ghae or ghes > 3.2 or ghec %}
+| <kbd>Command</kbd>+<kbd>Shift</kbd>+<kbd>.</kbd> (Mac) ou </br> <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>.</kbd> (Windows/Linux)                               | Insere a formatação Markdown para uma citação{% endif %}{% ifversion fpt or ghec %}
+| <kbd>Command</kbd>+<kbd>G</kbd> (Mac) ou </br> <kbd>Ctrl</kbd>+<kbd>G</kbd> (Windows/Linux)                                                                 | Insere uma sugestão. Para obter mais informações, consulte "[Revisar alterações propostas em uma pull request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request)". 
 {% endif %}
-| <kbd>R</kbd>                                                                                                                  | Cita o texto selecionado em sua resposta. Para obter mais informações, consulte "[Sintaxe básica de gravação e formatação](/articles/basic-writing-and-formatting-syntax#quoting-text)".                                                                       |
+| <kbd>R</kbd>                                                                                                                                                | Cita o texto selecionado em sua resposta. Para obter mais informações, consulte "[Sintaxe básica de gravação e formatação](/articles/basic-writing-and-formatting-syntax#quoting-text)".                                                                       |
 
 ## Listas de problemas e pull requests
 
diff --git a/translations/pt-BR/content/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax.md b/translations/pt-BR/content/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax.md
index bd13c371b5..af08755124 100644
--- a/translations/pt-BR/content/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax.md
+++ b/translations/pt-BR/content/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax.md
@@ -92,6 +92,8 @@ Para obter mais informações, consulte "[Criar e destacar blocos de código](/a
 
 Você pode criar um link inline colocando o texto do link entre colchetes `[ ]` e, em seguida, o URL entre parênteses `( )`. {% ifversion fpt or ghae or ghes > 3.1 or ghec %}Você também pode usar o atalho de teclado <kbd>Command</kbd>+<kbd>K</kbd> para criar um link.{% endif %}{% ifversion fpt or ghae-issue-5434 or ghes > 3.3 or ghec %} Quando você tiver selecionado texto, você poderá colar um URL da sua área de transferência para criar automaticamente um link a partir da seleção.{% endif %}
 
+{% ifversion fpt or ghae-issue-7103 or ghes > 3.5 or ghec %} You can also create a Markdown hyperlink by highlighting the text and using the keyboard shortcut <kbd>Command</kbd>+<kbd>V</kbd>. If you'd like to replace the text with the link, use the keyboard shortcut <kbd>Command</kbd>+<kbd>Shift</kbd>+<kbd>V</kbd>.{% endif %}
+
 `Este site foi construído usando [GitHub Pages](https://pages.github.com/).`
 
 ![Link renderizado](/assets/images/help/writing/link-rendered.png)
diff --git a/translations/pt-BR/data/learning-tracks/admin.yml b/translations/pt-BR/data/learning-tracks/admin.yml
index fb97a92a27..9c7defdddb 100644
--- a/translations/pt-BR/data/learning-tracks/admin.yml
+++ b/translations/pt-BR/data/learning-tracks/admin.yml
@@ -127,5 +127,4 @@ get_started_with_your_enterprise_account:
     - /admin/user-management/managing-users-in-your-enterprise/inviting-people-to-manage-your-enterprise
     - /admin/user-management/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise
     - /admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise
-    - /admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise
-    - /admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise
+    - /admin/policies/enforcing-policies-for-your-enterprise/about-enterprise-policies
diff --git a/translations/pt-BR/data/release-notes/enterprise-server/3-3/8.yml b/translations/pt-BR/data/release-notes/enterprise-server/3-3/8.yml
index 0d9ce58737..45231f3623 100644
--- a/translations/pt-BR/data/release-notes/enterprise-server/3-3/8.yml
+++ b/translations/pt-BR/data/release-notes/enterprise-server/3-3/8.yml
@@ -31,4 +31,3 @@ sections:
     - O registro npm de {% data variables.product.prodname_registry %} não retorna mais o valor de tempo em respostas de metadados. Isso foi feito para permitir melhorias substanciais de desempenho. Continuamos a ter todos os dados necessários para devolver um valor de tempo como parte da resposta aos metadados e retomaremos o retorno desse valor no futuro, assim que tivermos resolvido os problemas de desempenho existentes.
     - Os limites de recursos que são específicos para processamento de hooks pre-receive podem causar falha em alguns hooks pre-receive.
     - 'As configurações de armazenamento de {% data variables.product.prodname_actions %} não podem ser validadas e salvas no {% data variables.enterprise.management_console %} quando "Forçar estilo de caminho" for selecionado e deverão ser definidas com a ferramenta de linha de comando `ghe-actions-precheck`.'
-    - '{% data variables.product.prodname_ghe_server %} 3.3 instances installed on Azure and provisioned with 32+ CPU cores would fail to launch, due to a bug present in the current Linux kernel. [Updated: 2022-04-08]'
diff --git a/translations/pt-BR/data/reusables/actions/jobs/section-defining-outputs-for-jobs.md b/translations/pt-BR/data/reusables/actions/jobs/section-defining-outputs-for-jobs.md
index 081b4cb70c..48a894114f 100644
--- a/translations/pt-BR/data/reusables/actions/jobs/section-defining-outputs-for-jobs.md
+++ b/translations/pt-BR/data/reusables/actions/jobs/section-defining-outputs-for-jobs.md
@@ -1,6 +1,8 @@
 Você pode usar `jobs.<job_id>.outputs` para criar um `mapa` de saídas para um trabalho. As saídas de trabalho estão disponíveis para todos os trabalhos downstream que dependem deste trabalho. Para obter mais informações sobre a definição de dependências de trabalhos, consulte [`jobs.<job_id>.needs`](/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idneeds).
 
-As saídas de trabalho são strings e saídas de trabalho que contêm expressões são avaliadas no executor ao final de cada trabalho. As saídas que contêm segredos são eliminadas no executor e não são enviadas para {% data variables.product.prodname_actions %}.
+{% data reusables.actions.output-limitations %}
+
+Job outputs containing expressions are evaluated on the runner at the end of each job. As saídas que contêm segredos são eliminadas no executor e não são enviadas para {% data variables.product.prodname_actions %}.
 
 Para usar as saídas de trabalho em um trabalho dependente, você poderá usar o contexto `needs`. Para obter mais informações, consulte "[Contextos](/actions/learn-github-actions/contexts#needs-context)".
 
diff --git a/translations/pt-BR/data/reusables/actions/output-limitations.md b/translations/pt-BR/data/reusables/actions/output-limitations.md
new file mode 100644
index 0000000000..d26de54a7f
--- /dev/null
+++ b/translations/pt-BR/data/reusables/actions/output-limitations.md
@@ -0,0 +1 @@
+Outputs are Unicode strings, and can be a maximum of 1 MB. The total of all outputs in a workflow run can be a maximum of 50 MB.
diff --git a/translations/pt-BR/data/reusables/enterprise/about-policies.md b/translations/pt-BR/data/reusables/enterprise/about-policies.md
new file mode 100644
index 0000000000..7fd5303231
--- /dev/null
+++ b/translations/pt-BR/data/reusables/enterprise/about-policies.md
@@ -0,0 +1 @@
+Each enterprise policy controls the options available for a policy at the organization level. You can choose to not enforce a policy, which allows organization owners to configure the policy for the organization, or you can choose from a set of options to enforce for all organizations owned by your enterprise.
\ No newline at end of file
diff --git a/translations/pt-BR/data/ui.yml b/translations/pt-BR/data/ui.yml
index 4e623790b1..7d6ff99650 100644
--- a/translations/pt-BR/data/ui.yml
+++ b/translations/pt-BR/data/ui.yml
@@ -36,6 +36,7 @@ search:
 homepage:
   explore_by_product: Explorar por produto
   version_picker: Versão
+  description: Help for wherever you are on your GitHub journey.
 toc:
   getting_started: Introdução
   popular: Popular
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 bbf2fae874..92dd7fdc0a 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 {% data variables.product.prodname_dotcom %}, including email preferences, collaborator access for personal repositories, and organization memberships.'
+title: 在 GitHub 上设置和管理您的个人帐户
+intro: '您可以在 {% data variables.product.prodname_dotcom %} 上管理个人帐户的设置，包括电子邮件首选项、个人仓库的协作者访问权限和组织成员身份。'
 shortTitle: 个人帐户
 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-access-to-your-personal-repositories/maintaining-ownership-continuity-of-your-personal-accounts-repositories.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/maintaining-ownership-continuity-of-your-personal-accounts-repositories.md
index 68632f686b..08461f01ec 100644
--- a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/maintaining-ownership-continuity-of-your-personal-accounts-repositories.md
+++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/maintaining-ownership-continuity-of-your-personal-accounts-repositories.md
@@ -1,5 +1,5 @@
 ---
-title: Maintaining ownership continuity of your personal account's repositories
+title: 保持个人帐户仓库的所有权连续性
 intro: 如果您无法管理用户拥有的仓库，可以邀请他人管理。
 versions:
   fpt: '*'
diff --git a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/converting-a-user-into-an-organization.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/converting-a-user-into-an-organization.md
index a3e3b98311..7fe5b9ceb2 100644
--- a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/converting-a-user-into-an-organization.md
+++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/converting-a-user-into-an-organization.md
@@ -49,7 +49,7 @@ shortTitle: 用户到组织
 2.  [离开](/articles/removing-yourself-from-an-organization)要转换的个人帐户此前加入的任何组织。
 {% data reusables.user-settings.access_settings %}
 {% data reusables.user-settings.organizations %}
-5. Under "Transform account", click **Turn <username> into an organization**. ![组织转换按钮](/assets/images/help/settings/convert-to-organization.png)
+5. 在“Transform account（转换帐户）”下，单击 **Turn <username> into an organization（转换为组织）**。 ![组织转换按钮](/assets/images/help/settings/convert-to-organization.png)
 6. 在 Account Transformation Warning（帐户转换警告）对话框中，查看并确认转换。 请注意，此框中的信息与本文顶部的警告信息相同。 ![转换警告](/assets/images/help/organizations/organization-account-transformation-warning.png)
 7. 在“Transform your user into an organization（将用户转换为组织）”页面的“Choose an organization owner（选择组织所有者）”下，选择您在前面创建的备用个人帐户或您信任的其他用户来管理组织。 ![添加组织所有者页面](/assets/images/help/organizations/organization-add-owner.png)
 8. 选择新组织的订阅，并在提示时输入帐单信息。
diff --git a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/deleting-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/deleting-your-personal-account.md
index bf19520149..19bbcfc8a4 100644
--- a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/deleting-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/deleting-your-personal-account.md
@@ -1,5 +1,5 @@
 ---
-title: Deleting your personal account
+title: 删除个人帐户
 intro: '您可以随时在 {% data variables.product.product_name %} 上删除您的个人帐户。'
 redirect_from:
   - /articles/deleting-a-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-access-to-your-personal-accounts-project-boards.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-access-to-your-personal-accounts-project-boards.md
index b5cb52a5bd..bb38a1868f 100644
--- a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-access-to-your-personal-accounts-project-boards.md
+++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-access-to-your-personal-accounts-project-boards.md
@@ -1,5 +1,5 @@
 ---
-title: Managing access to your personal account's project boards
+title: 管理对个人帐户项目板的访问
 intro: 作为项目板所有者，您可以添加或删除协作者，以及自定义他们对项目板的权限。
 redirect_from:
   - /articles/managing-project-boards-in-your-repository-or-organization
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 59cc8362e9..5354201fa9 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,5 +1,5 @@
 ---
-title: Managing security and analysis settings for your personal account
+title: 管理个人帐户的安全和分析设置
 intro: '您可以控制功能以保护 {% data variables.product.prodname_dotcom %} 上项目的安全并分析其中的代码。'
 versions:
   fpt: '*'
diff --git a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/merging-multiple-personal-accounts.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/merging-multiple-personal-accounts.md
index 571041d9dd..5ff88a3f41 100644
--- a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/merging-multiple-personal-accounts.md
+++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/merging-multiple-personal-accounts.md
@@ -1,5 +1,5 @@
 ---
-title: Merging multiple personal accounts
+title: 合并多个个人帐户
 intro: 如果工作和个人分别使用不同的帐户，您可以合并这些帐户。
 redirect_from:
   - /articles/can-i-merge-two-accounts
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 f4fb4b3f8b..0d83569a08 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,5 +1,5 @@
 ---
-title: Permission levels for a personal account repository
+title: 个人帐户仓库的权限级别
 intro: 个人帐户拥有的仓库有两种权限级别：仓库所有者和协作者。
 redirect_from:
   - /articles/permission-levels-for-a-user-account-repository
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-project-board-owned-by-a-personal-account.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-project-board-owned-by-a-personal-account.md
index e4d9281708..96ec58f2aa 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-project-board-owned-by-a-personal-account.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-project-board-owned-by-a-personal-account.md
@@ -1,5 +1,5 @@
 ---
-title: Permission levels for a project board owned by a personal account
+title: 个人帐户拥有的项目板的权限级别
 intro: 个人帐户拥有的项目板有两种权限级别：项目板所有者和协作者。
 redirect_from:
   - /articles/permission-levels-for-user-owned-project-boards
diff --git a/translations/zh-CN/content/actions/automating-builds-and-tests/building-and-testing-python.md b/translations/zh-CN/content/actions/automating-builds-and-tests/building-and-testing-python.md
index 4718018caa..d5c3394172 100644
--- a/translations/zh-CN/content/actions/automating-builds-and-tests/building-and-testing-python.md
+++ b/translations/zh-CN/content/actions/automating-builds-and-tests/building-and-testing-python.md
@@ -244,7 +244,7 @@ steps:
 - run: pip test
 ```
 
-By default, the `setup-python` action searches for the dependency file (`requirements.txt` for pip, `Pipfile.lock` for pipenv or `poetry.lock` for poetry) in the whole repository. 更多信息请参阅 `setup-python` 自述文件中的“[缓存包依赖项](https://github.com/actions/setup-python#caching-packages-dependencies)”。
+默认情况下， `setup-python` 操作会在整个存储库中搜索依赖项文件（对于 pip 为`requirements.txt`，对于 pipenv 为 `Pipfile.lock`，对于 poetry 为 `poetry.lock`）。 更多信息请参阅 `setup-python` 自述文件中的“[缓存包依赖项](https://github.com/actions/setup-python#caching-packages-dependencies)”。
 
 如果您有自定义要求或需要更精确的缓存控制，则可以使用 [`cache` 操作](https://github.com/marketplace/actions/cache)。 Pip 根据运行器的操作系统将依赖项缓存在不同的位置。 您需要缓存的路径可能不同于上面的 Ubuntu 示例，具体取决于您使用的操作系统。 更多信息请参阅 `cache` 操作存储库中的 [Python 缓存示例](https://github.com/actions/cache/blob/main/examples.md#python---pip)。
 
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 f2647ba73b..1201846c24 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
@@ -88,6 +88,8 @@ inputs:
 
 **可选** 输出参数允许您声明操作所设置的数据。 稍后在工作流程中运行的操作可以使用以前运行操作中的输出数据集。  例如，如果有操作执行两个输入的相加 (x + y = z)，则该操作可能输出总和 (z)，用作其他操作的输入。
 
+{% data reusables.actions.output-limitations %}
+
 如果不在操作元数据文件中声明输出，您仍然可以设置输出并在工作流程中使用它们。 有关在操作中设置输出的更多信息，请参阅“[{% data variables.product.prodname_actions %} 的工作流程命令](/actions/reference/workflow-commands-for-github-actions/#setting-an-output-parameter)”。
 
 ### 示例：声明 Docker 容器和 JavaScript 操作的输出
@@ -108,18 +110,13 @@ outputs:
 
 ## 用于复合操作的 `outputs`
 
-**可选** `outputs` 使用与 `outputs.<output_id>` 及 `outputs.<output_id>.description` 相同的参数（请参阅“用于 Docker 容器和 JavaScript 操作的
-
-
-`outputs`”），但也包括 `value` 令牌。</p> 
-
+**Optional** `outputs` use the same parameters as `outputs.<output_id>` and `outputs.<output_id>.description` (see "[`outputs` for Docker container and JavaScript actions](#outputs-for-docker-container-and-javascript-actions)"), but also includes the `value` token.
 
+{% data reusables.actions.output-limitations %}
 
 ### 示例：声明复合操作的 outputs
 
 {% raw %}
-
-
 ```yaml
 outputs:
   random-number:
@@ -132,68 +129,47 @@ runs:
       run: echo "::set-output name=random-id::$(echo $RANDOM)"
       shell: bash
 ```
-
-
 {% endraw %}
 
-
-
 ### `outputs.<output_id>.value`
 
 **必要** 输出参数将会映射到的值。 您可以使用上下文将此设置为 `string` 或表达式。 例如，您可以使用 `steps` 上下文将输出的 `value` 设置为步骤的输出值。
 
 有关如何使用上下文语法的更多信息，请参阅“[上下文](/actions/learn-github-actions/contexts)”。
 
-
-
 ## `runs`
 
 **必要** 指定这是 JavaScript 操作、复合操作还是 Docker 容器操作以及操作的执行方式。
 
-
-
 ## 用于 JavaScript 操作的 `runs`
 
 **必要** 配置操作代码的路径和用于执行代码的运行时。
 
-
-
 ### 示例：使用 Node.js {% ifversion fpt or ghes > 3.3 or ghae-issue-5504 or ghec %}v16{% else %}v12{% endif %}
 
-
-
 ```yaml
 runs:
   using: {% ifversion fpt or ghes > 3.3 or ghae-issue-5504 or ghec %}'node16'{% else %}'node12'{% endif %}
   main: 'main.js'
 ```
 
-
-
-
 ### `runs.using`
 
-**必要** 用于执行 [`main`](#runsmain) 中指定的代码的支行时。  
+**必要** 用于执行 [`main`](#runsmain) 中指定的代码的支行时。
 
 - 将 `node12` 用于 Node.js v12。{% ifversion fpt or ghes > 3.3 or ghae-issue-5504 or ghec %}
 - 将 `node16` 用于 Node.js v16。{% endif %}
 
-
-
 ### `runs.main`
 
 **必要** 包含操作代码的文件。 [`using`](#runsusing) 中指定的运行时执行此文件。
 
-
-
 ### `runs.pre`
 
 **可选** 允许您在 `main:` 操作开始之前，在作业开始时运行脚本。 例如，您可以使用 `pre:` 运行基本要求设置脚本。 使用 [`using`](#runsusing) 语法指定的运行时将执行此文件。 `pre:` 操作始终默认运行，但您可以使用 [`runs.pre-if`](#runspre-if) 覆盖该设置。
 
 在此示例中，`pre:` 操作运行名为 `setup.js` 的脚本：
 
-
-
 ```yaml
 runs:
   using: {% ifversion fpt or ghes > 3.3 or ghae-issue-5504 or ghec %}'node16'{% else %}'node12'{% endif %}
@@ -202,9 +178,6 @@ runs:
   post: 'cleanup.js'
 ```
 
-
-
-
 ### `runs.pre-if`
 
 **可选** 允许您定义 `pre:` 操作执行的条件。 `pre:` 操作仅在满足 `pre-if` 中的条件后运行。 如果未设置，则 `pre-if` 默认使用 `always()`。 在 `pre-if` 中，状态检查函数根据作业的状态而不是操作自己的状态进行评估。
@@ -213,24 +186,17 @@ runs:
 
 在此示例中，`cleanup.js` 仅在基于 Linux 的运行器上运行：
 
-
-
 ```yaml
   pre: 'cleanup.js'
   pre-if: runner.os == 'linux'
 ```
 
-
-
-
 ### `runs.post`
 
 **可选** 允许您在 `main:` 操作完成后，在作业结束时运行脚本。 例如，您可以使用 `post:` 终止某些进程或删除不需要的文件。 使用 [`using`](#runsusing) 语法指定的运行时将执行此文件。
 
 在此示例中，`post:` 操作会运行名为 `cleanup.js` 的脚本：
 
-
-
 ```yaml
 runs:
   using: {% ifversion fpt or ghes > 3.3 or ghae-issue-5504 or ghec %}'node16'{% else %}'node12'{% endif %}
@@ -238,70 +204,44 @@ runs:
   post: 'cleanup.js'
 ```
 
-
 `post:` 操作始终默认运行，但您可以使用 `post-if` 覆盖该设置。
 
-
-
 ### `runs.post-if`
 
 **可选** 允许您定义 `post:` 操作执行的条件。 `post:` 操作仅在满足 `post-if` 中的条件后运行。 如果未设置，则 `post-if` 默认使用 `always()`。 在 `post-if` 中，状态检查函数根据作业的状态而不是操作自己的状态进行评估。
 
 例如，此 `cleanup.js` 仅在基于 Linux 的运行器上运行：
 
-
-
 ```yaml
   post: 'cleanup.js'
   post-if: runner.os == 'linux'
 ```
 
-
-
-
 ## 用于复合操作的 `runs`
 
 **必要** 配置组合操作的路径。
 
-
-
 ### `runs.using`
 
 **必要** 必须将此值设置为 `'composite'`。
 
-
-
 ### `runs.steps`
 
 {% ifversion fpt or ghes > 3.2 or ghae or ghec %}
-
-
-**必要** 您计划在此操作中的步骤。 这些步骤可以是 `run` 步骤或 `uses` 步骤。 
-
+**必要** 您计划在此操作中的步骤。 这些步骤可以是 `run` 步骤或 `uses` 步骤。
 {% else %}
-
-**必要** 您计划在此操作中的步骤。 
-
+**必要** 您计划在此操作中的步骤。
 {% endif %}
 
-
-
 #### `runs.steps[*].run`
 
 {% ifversion fpt or ghes > 3.2 or ghae or ghec %}
-
-
-**可选** 您想要运行的命令。 这可以是内联的，也可以是操作仓库中的脚本： 
-
+**可选** 您想要运行的命令。 这可以是内联的，也可以是操作仓库中的脚本：
 {% else %}
-
-**必要** 您想要运行的命令。 这可以是内联的，也可以是操作仓库中的脚本： 
-
+**必要** 您想要运行的命令。 这可以是内联的，也可以是操作仓库中的脚本：
 {% endif %}
 
 {% raw %}
-
-
 ```yaml
 runs:
   using: "composite"
@@ -309,14 +249,10 @@ runs:
     - run: ${{ github.action_path }}/test/script.sh
       shell: bash
 ```
-
-
 {% endraw %}
 
 或者，您也可以使用 `$GITHUB_ACTION_PATH`：
 
-
-
 ```yaml
 runs:
   using: "composite"
@@ -325,27 +261,17 @@ runs:
       shell: bash
 ```
 
-
 更多信息请参阅“[`github context`](/actions/reference/context-and-expression-syntax-for-github-actions#github-context)”。
 
-
-
 #### `runs.steps[*].shell`
 
 {% ifversion fpt or ghes > 3.2 or ghae or ghec %}
-
-
-**可选** 您想要在其中运行命令的 shell。 您可以使用[这里](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepsshell)列出的任何 shell。 如果设置了 `run`，则必填。 
-
+**可选** 您想要在其中运行命令的 shell。 您可以使用[这里](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepsshell)列出的任何 shell。 如果设置了 `run`，则必填。
 {% else %}
-
-**必要** 您想要在其中运行命令的 shell。 您可以使用[这里](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepsshell)列出的任何 shell。 如果设置了 `run`，则必填。 
-
+**必要** 您想要在其中运行命令的 shell。 您可以使用[这里](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepsshell)列出的任何 shell。 如果设置了 `run`，则必填。
 {% endif %}
 
 {% ifversion fpt or ghes > 3.3 or ghae-issue-5504 or ghec %}
-
-
 #### `runs.steps[*].if`
 
 **可选** 您可以使用 `if` 条件使步骤仅在满足条件时才运行。 您可以使用任何支持上下文和表达式来创建条件。
@@ -354,9 +280,7 @@ runs:
 
 **示例：使用上下文**
 
-此步骤仅在事件类型为 `pull_request` 并且事件操作为 `unassigned` 时运行。
-
-
+ 此步骤仅在事件类型为 `pull_request` 并且事件操作为 `unassigned` 时运行。
 
  ```yaml
 steps:
@@ -364,13 +288,10 @@ steps:
     if: {% raw %}${{ github.event_name == 'pull_request' && github.event.action == 'unassigned' }}{% endraw %}
 ```
 
-
 **示例：使用状态检查功能**
 
 `my backup step` 仅在组合操作的上一步失败时运行。 更多信息请参阅“[表达式](/actions/learn-github-actions/expressions#status-check-functions)”。
 
-
-
 ```yaml
 steps:
   - name: My first step
@@ -379,51 +300,36 @@ steps:
     if: {% raw %}${{ failure() }}{% endraw %}
     uses: actions/heroku@1.0.0
 ```
-
-
 {% endif %}
 
-
-
 #### `runs.steps[*].name`
 
 **可选** 复合步骤的名称。
 
-
-
 #### `runs.steps[*].id`
 
 **可选** 步骤的唯一标识符。 您可以使用 `id` 引用上下文中的步骤。 更多信息请参阅“[上下文](/actions/learn-github-actions/contexts)”。
 
-
-
 #### `runs.steps[*].env`
 
 **可选** 设置环境变量的 `map` 仅用于该步骤。 如果要修改存储在工作流程中的环境变量，请在组合运行步骤中使用 `echo "{name}={value}" >> $GITHUB_ENV`。
 
-
-
 #### `runs.steps[*].working-directory`
 
 **可选**  指定命令在其中运行的工作目录。
 
 {% ifversion fpt or ghes > 3.2 or ghae or ghec %}
-
-
 #### `runs.steps[*].uses`
 
 **可选**  选择作为作业步骤一部分运行的操作。 操作是一种可重复使用的代码单位。 您可以使用工作流程所在仓库中、公共仓库中或[发布 Docker 容器映像](https://hub.docker.com/)中定义的操作。
 
 强烈建议指定 Git ref、SHA 或 Docker 标记编号来包含所用操作的版本。 如果不指定版本，在操作所有者发布更新时可能会中断您的工作流程或造成非预期的行为。
-
 - 使用已发行操作版本的 SHA 对于稳定性和安全性是最安全的。
 - 使用特定主要操作版本可在保持兼容性的同时接收关键修复和安全补丁。 还可确保您的工作流程继续工作。
 - 使用操作的默认分支可能很方便，但如果有人新发布具有突破性更改的主要版本，您的工作流程可能会中断。
 
 有些操作要求必须通过 [`with`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepswith) 关键词设置输入。 请查阅操作的自述文件，确定所需的输入。
 
-
-
 ```yaml
 runs:
   using: "composite"
@@ -446,15 +352,10 @@ runs:
     - uses: docker://alpine:3.8
 ```
 
-
-
-
 #### `runs.steps[*].with`
 
 **可选** 输入参数的 `map` 由操作定义。 每个输入参数都是一个键/值对。  输入参数被设置为环境变量。 该变量的前缀为 INPUT_，并转换为大写。
 
-
-
 ```yaml
 runs:
   using: "composite"
@@ -466,50 +367,32 @@ runs:
         middle_name: The
         last_name: Octocat  
 ```
-
-
 {% endif %}
 
-
-
 ## 用于 Docker 容器操作的 `runs`
 
 **必要** 配置用于 Docker 容器操作的图像。
 
-
-
 ### 示例：在仓库中使用 Dockerfile
 
-
-
 ```yaml
 runs:
   using: 'docker'
   image: 'Dockerfile'
 ```
 
-
-
-
 ### 示例：使用公共 Docker 注册表容器
 
-
-
 ```yaml
 runs:
   using: 'docker'
   image: 'docker://debian:stretch-slim'
 ```
 
-
-
-
 ### `runs.using`
 
 **必要** 必须将此值设置为 `'docker'`。
 
-
-
 ### `runs.pre-entrypoint`
 
 **可选** 允许您在 `entrypoint` 操作开始之前运行脚本。 例如，您可以使用 `pre-entrypoint:` 运行基本要求设置脚本。 {% data variables.product.prodname_actions %} 使用 `docker run` 启动此操作，并在使用同一基本映像的新容器中运行脚本。 这意味着运行时状态与主 `entrypoint` 容器不同，并且必须在任一工作空间中访问所需的任何状态，`HOME` 或作为 `STATE_` 变量。 `pre-entrypoint:` 操作始终默认运行，但您可以使用 [`runs.pre-if`](#runspre-if) 覆盖该设置。
@@ -518,8 +401,6 @@ runs:
 
 在此示例中，`pre-entrypoint:` 操作会运行名为 `setup.sh` 的脚本：
 
-
-
 ```yaml
 runs:
   using: 'docker'
@@ -530,35 +411,24 @@ runs:
   entrypoint: 'main.sh'
 ```
 
-
-
-
 ### `runs.image`
 
 **必要** 要用作容器来运行操作的 Docker 映像。 值可以是 Docker 基本映像名称、仓库中的本地 `Dockerfile`、Docker Hub 中的公共映像或另一个注册表。 要引用仓库本地的 `Dockerfile`，文件必须命名为 `Dockerfile`，并且您必须使用操作元数据文件的相对路径。 `Docker` 应用程序将执行此文件。
 
-
-
 ### `runs.env`
 
 **可选** 指定要在容器环境中设置的环境变量的键/值映射。
 
-
-
 ### `runs.entrypoint`
 
 **可选** 覆盖 `Dockerfile` 中的 Docker `ENTRYPOINT`，或在未指定时设置它。 当 `Dockerfile` 未指定 `ENTRYPOINT` 或者您想要覆盖 `ENTRYPOINT` 指令时使用 `entrypoint`。 如果您省略 `entrypoint`，您在 Docker `ENTRYPOINT` 指令中指定的命令将执行。 Docker `ENTRYPOINT` 指令有 _shell_ 形式和 _exec_ 形式。 Docker `ENTRYPOINT` 文档建议使用 _exec_ 形式的 `ENTRYPOINT` 指令。
 
 有关 `entrypoint` 如何执行的更多信息，请参阅“[Dockerfile 对 {% data variables.product.prodname_actions %} 的支持](/actions/creating-actions/dockerfile-support-for-github-actions/#entrypoint)”。
 
-
-
 ### `post-entrypoint`
 
 **可选** 允许您在 `runs.entrypoint` 操作完成后运行清理脚本。 {% data variables.product.prodname_actions %} 使用 `docker run` 来启动此操作。 因为  {% data variables.product.prodname_actions %} 使用同一基本映像在新容器内运行脚本，所以运行时状态与主 `entrypoint` 容器不同。 您可以在任一工作空间中访问所需的任何状态，`HOME` 或作为 `STATE_` 变量。 `post-entrypoint:` 操作始终默认运行，但您可以使用 [`runs.post-if`](#runspost-if) 覆盖该设置。
 
-
-
 ```yaml
 runs:
   using: 'docker'
@@ -569,9 +439,6 @@ runs:
   post-entrypoint: 'cleanup.sh'
 ```
 
-
-
-
 ### `runs.args`
 
 **可选** 定义 Docker 容器输入的字符串数组。 输入可包含硬编码的字符串。 {% data variables.product.prodname_dotcom %} 在容器启动时将 `args` 传递到容器的 `ENTRYPOINT`。
@@ -584,13 +451,9 @@ runs:
 
 有关将 `CMD` 指令与 {% data variables.product.prodname_actions %} 一起使用的更多信息，请参阅“[Dockerfile 对 {% data variables.product.prodname_actions %} 的支持](/actions/creating-actions/dockerfile-support-for-github-actions/#cmd)”。
 
-
-
 #### 示例：为 Docker 容器定义参数
 
 {% raw %}
-
-
 ```yaml
 runs:
   using: 'docker'
@@ -600,37 +463,24 @@ runs:
     - 'foo'
     - 'bar'
 ```
-
-
 {% endraw %}
 
-
-
 ## `branding`
 
 您可以使用颜色和 [Feather](https://feathericons.com/) 图标创建徽章，以个性化和识别操作。 徽章显示在 [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace?type=actions) 中的操作名称旁边。
 
-
-
 ### 示例：为操作配置品牌宣传
 
-
-
 ```yaml
 branding:
   icon: 'award'  
   color: 'green'
 ```
 
-
-
-
 ### `branding.color`
 
 徽章的背景颜色。 可以是以下之一：`white`、`yellow`、`blue`、`green`、`orange`、`red`、`purple` 或 `gray-dark`。
 
-
-
 ### `branding.icon`
 
 要使用的 v4.28.0 [Feather](https://feathericons.com/) 图标的名称。 省略了品牌图标以及以下内容：
@@ -664,6 +514,7 @@ branding:
 
 以下是当前支持的所有图标的详尽列表：
 
+
 <!-- 
   This table should match the icon list in `app/models/repository_actions/icons.rb` in the internal github repo.
   To support a new icon, update `app/models/repository_actions/icons.rb` and add the svg to `/static/images/icons/feather` in the internal github repo. 
diff --git a/translations/zh-CN/content/actions/deployment/about-deployments/deploying-with-github-actions.md b/translations/zh-CN/content/actions/deployment/about-deployments/deploying-with-github-actions.md
index fee9575372..281b69f1cc 100644
--- a/translations/zh-CN/content/actions/deployment/about-deployments/deploying-with-github-actions.md
+++ b/translations/zh-CN/content/actions/deployment/about-deployments/deploying-with-github-actions.md
@@ -1,6 +1,6 @@
 ---
-title: 使用 GitHub Actions 进行部署
-intro: 了解如何使用环境和并发性等功能控制部署。
+title: Deploying with GitHub Actions
+intro: Learn how to control deployments with features like environments and concurrency.
 versions:
   fpt: '*'
   ghes: '*'
@@ -11,35 +11,35 @@ redirect_from:
   - /actions/deployment/deploying-with-github-actions
 topics:
   - CD
-shortTitle: 使用 GitHub Actions 进行部署
+shortTitle: Deploy with GitHub Actions
 ---
 
 {% data reusables.actions.enterprise-beta %}
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## 简介
+## Introduction
 
-{% data variables.product.prodname_actions %} 提供了允许您控制部署的功能。 您可以:
+{% data variables.product.prodname_actions %} offers features that let you control deployments. You can:
 
-- 使用各种事件触发工作流程。
-- 配置环境以在作业可以继续之前设置规则，并限制对机密的访问。
-- 使用并发性来控制一次运行的部署数。
+- Trigger workflows with a variety of events.
+- Configure environments to set rules before a job can proceed and to limit access to secrets.
+- Use concurrency to control the number of deployments running at a time.
 
-有关持续部署的更多信息，请参阅“[关于持续部署](/actions/deployment/about-continuous-deployment)”。
+For more information about continuous deployment, see "[About continuous deployment](/actions/deployment/about-continuous-deployment)."
 
-## 基本要求
+## Prerequisites
 
-您应该熟悉 {% data variables.product.prodname_actions %} 的语法。 更多信息请参阅“[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)”。
+You should be familiar with the syntax for {% data variables.product.prodname_actions %}. For more information, see "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)."
 
-## 触发部署
+## Triggering your deployment
 
-您可以使用各种事件来触发您的部署工作流程。 最常见的有：`pull_request`、`put` 和 `Workflow_paid`。
+You can use a variety of events to trigger your deployment workflow. Some of the most common are: `pull_request`, `push`, and `workflow_dispatch`.
 
-例如，具有以下触发器的工作流在以下情况下会运行：
+For example, a workflow with the following triggers runs whenever:
 
-- 有人推送到 `main` 分支。
-- 打开、同步或重新打开面向 `main` 分支的拉取请求。
-- 有人手动触发它。
+- There is a push to the `main` branch.
+- A pull request targeting the `main` branch is opened, synchronized, or reopened.
+- Someone manually triggers it.
 
 ```yaml
 on:
@@ -52,23 +52,23 @@ on:
   workflow_dispatch:
 ```
 
-更多信息请参阅“[触发工作流程的事件](/actions/reference/events-that-trigger-workflows)”。
+For more information, see "[Events that trigger workflows](/actions/reference/events-that-trigger-workflows)."
 
-## 使用环境
+## Using environments
 
 {% data reusables.actions.about-environments %}
 
-## 使用并发
+## Using concurrency
 
-并发确保只有使用相同并发组的单一作业或工作流程才会同时运行。 您可以使用并发，以便环境中每次最多有一个正在进行的部署和一个待处理的部署。
+Concurrency ensures that only a single job or workflow using the same concurrency group will run at a time. You can use concurrency so that an environment has a maximum of one deployment in progress and one deployment pending at a time.
 
 {% note %}
 
-**注意**：`concurrency` 和 `environment` 未连接。 并发值可以是任何字符串；它无需是环境名称。 此外，如果另一个工作流程使用相同的环境，但未指定并发性，则该工作流程将不受任何并发规则的约束。
+**Note:** `concurrency` and `environment` are not connected. The concurrency value can be any string; it does not need to be an environment name. Additionally, if another workflow uses the same environment but does not specify concurrency, that workflow will not be subject to any concurrency rules.
 
 {% endnote %}
 
-例如，当以下工作流程运行时，如果正在进行使用 `production` 并发组的任何作业或工作流程，则该工作流程将暂停，且状态为 `pending`。 它还将取消使用 `production` 并发组并且状态为 `pending` 的任何作业或工作流程。 这意味着最多将有一个正在运行的作业或工作流程和一个使用 `production` 并发组的挂起作业或工作流程。
+For example, when the following workflow runs, it will be paused with the status `pending` if any job or workflow that uses the `production` concurrency group is in progress. It will also cancel any job or workflow that uses the `production` concurrency group and has the status `pending`. This means that there will be a maximum of one running and one pending job or workflow in that uses the `production` concurrency group.
 
 ```yaml
 name: Deployment
@@ -89,7 +89,7 @@ jobs:
         # ...deployment-specific steps
 ```
 
-您也可以在作业级别指定并发性。 这将允许工作流中的其他作业继续，即使并发作业状态为 `pending`。
+You can also specify concurrency at the job level. This will allow other jobs in the workflow to proceed even if the concurrent job is `pending`.
 
 ```yaml
 name: Deployment
@@ -109,7 +109,7 @@ jobs:
         # ...deployment-specific steps
 ```
 
-还可以使用 `cancel-in-progress` 取消同一并发组中任何当前正在运行的作业或工作流程。
+You can also use `cancel-in-progress` to cancel any currently running job or workflow in the same concurrency group.
 
 ```yaml
 name: Deployment
@@ -132,42 +132,42 @@ jobs:
         # ...deployment-specific steps
 ```
 
-有关编写特定于部署的步骤的指导，请参阅“[查找部署示例](#finding-deployment-examples)”。
+For guidance on writing deployment-specific steps, see "[Finding deployment examples](#finding-deployment-examples)."
 
-## 查看部署历史记录
+## Viewing deployment history
 
-当 {% data variables.product.prodname_actions %} 工作流程部署到某个环境时，该环境将显示在存储库的主页上。 有关查看环境部署的详细信息，请参阅“[查看部署历史记录](/developers/overview/viewing-deployment-history)”。
+When a {% data variables.product.prodname_actions %} workflow deploys to an environment, the environment is displayed on the main page of the repository. For more information about viewing deployments to environments, see "[Viewing deployment history](/developers/overview/viewing-deployment-history)."
 
-## 监控工作流程运行
+## Monitoring workflow runs
 
-每个工作流程运行都会生成一个实时图表，说明运行进度。 您可以使用此图表来监控和调试部署。 更多信息请参阅“[使用可视化图](/actions/monitoring-and-troubleshooting-workflows/using-the-visualization-graph)”。
+Every workflow run generates a real-time graph that illustrates the run progress. You can use this graph to monitor and debug deployments. For more information see, "[Using the visualization graph](/actions/monitoring-and-troubleshooting-workflows/using-the-visualization-graph)."
 
-您还可以查看每个工作流程运行的日志和工作流程运行的历史记录。 更多信息请参阅“[查看工作流程运行历史记录](/actions/monitoring-and-troubleshooting-workflows/viewing-workflow-run-history)”。
+You can also view the logs of each workflow run and the history of workflow runs. For more information, see "[Viewing workflow run history](/actions/monitoring-and-troubleshooting-workflows/viewing-workflow-run-history)."
 
-## 通过应用跟踪部署
+## Tracking deployments through apps
 
 {% ifversion fpt or ghec %}
-如果您在 {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} 上的个人帐户或组织与 Microsoft Teams 或 Slack 集成，则可以通过 Microsoft Teams 或 Slack 跟踪使用环境的部署。 例如，当部署正在等待批准、部署获得批准或部署状态更改时，您可以通过应用接收通知。 有关集成 Microsoft Teams 或 Slack 的详细信息，请参阅“[GitHub 扩展和集成](/github/customizing-your-github-workflow/exploring-integrations/github-extensions-and-integrations#team-communication-tools)”。
+If your personal account or organization on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} is integrated with Microsoft Teams or Slack, you can track deployments that use environments through Microsoft Teams or Slack. For example, you can receive notifications through the app when a deployment is pending approval, when a deployment is approved, or when the deployment status changes. For more information about integrating  Microsoft Teams or Slack, see "[GitHub extensions and integrations](/github/customizing-your-github-workflow/exploring-integrations/github-extensions-and-integrations#team-communication-tools)."
 {% endif %}
 
-你还可以构建一个应用，该应用使用部署和部署状态 web 挂钩来跟踪部署。 {% data reusables.actions.environment-deployment-event %} 更多信息请参阅“[应用程序](/developers/apps)”和“[web 挂钩事件和有效负载](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#deployment)”。
+You can also build an app that uses deployment and deployment status webhooks to track deployments. {% data reusables.actions.environment-deployment-event %} For more information, see "[Apps](/developers/apps)" and "[Webhook events and payloads](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#deployment)."
 
 {% ifversion fpt or ghes or ghec %}
 
-## 选择运行器
+## Choosing a runner
 
-您可以在 {% data variables.product.company_short %} 托管的运行器或自托管运行器上运行部署工作流程。 来自 {% data variables.product.company_short %} 托管运行器的流量可以来自[广泛的网络地址](/rest/reference/meta#get-github-meta-information)。 If you are deploying to an internal environment and your company restricts external traffic into private networks, {% data variables.product.prodname_actions %} workflows running on {% data variables.product.company_short %}-hosted runners may not be able to communicate with your internal services or resources. 为了克服这一点，您可以托管自己的运行器。 更多信息请参阅“[关于自托管的运行器](/actions/hosting-your-own-runners/about-self-hosted-runners)”和“[关于 GitHub 托管的运行器](/actions/using-github-hosted-runners/about-github-hosted-runners)”。
+You can run your deployment workflow on {% data variables.product.company_short %}-hosted runners or on self-hosted runners. Traffic from {% data variables.product.company_short %}-hosted runners can come from a [wide range of network addresses](/rest/reference/meta#get-github-meta-information). If you are deploying to an internal environment and your company restricts external traffic into private networks, {% data variables.product.prodname_actions %} workflows running on {% data variables.product.company_short %}-hosted runners may not be able to communicate with your internal services or resources. To overcome this, you can host your own runners. For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners)" and "[About GitHub-hosted runners](/actions/using-github-hosted-runners/about-github-hosted-runners)."
 
 {% endif %}
 
-## 显示状态徽章
+## Displaying a status badge
 
-您可以使用状态徽章来显示您的部署工作流程状态。 {% data reusables.repositories.actions-workflow-status-badge-intro %}
+You can use a status badge to display the status of your deployment workflow. {% data reusables.repositories.actions-workflow-status-badge-intro %}
 
-更多信息请参阅“[添加工作流程状态徽章](/actions/managing-workflow-runs/adding-a-workflow-status-badge)”。
+For more information, see "[Adding a workflow status badge](/actions/managing-workflow-runs/adding-a-workflow-status-badge)."
 
-## 查找部署示例
+## Finding deployment examples
 
-本文演示了可添加到部署工作流程的 {% data variables.product.prodname_actions %} 的功能。
+This article demonstrated features of {% data variables.product.prodname_actions %} that you can add to your deployment workflows.
 
 {% data reusables.actions.cd-templates-actions %}
diff --git a/translations/zh-CN/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-nodejs-to-azure-app-service.md b/translations/zh-CN/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-nodejs-to-azure-app-service.md
index 1ef503ff69..447daa5503 100644
--- a/translations/zh-CN/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-nodejs-to-azure-app-service.md
+++ b/translations/zh-CN/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-nodejs-to-azure-app-service.md
@@ -134,4 +134,4 @@ jobs:
 * 有关原始入门工作流程，请参阅 {% data variables.product.prodname_actions %} `starter-workflows` 仓库中的 [`azure-webapps-node.yml`](https://github.com/actions/starter-workflows/blob/main/deployments/azure-webapps-node.yml)。
 * 用于部署 Web 应用的操作是正式的 Azure [`Azure/webapps-deploy`](https://github.com/Azure/webapps-deploy) 操作。
 * 有关部署到 Azure 的 GitHub 操作工作流程的更多示例，请参阅 [actions-workflow-samples](https://github.com/Azure/actions-workflow-samples) 存储库。
-* The "[Create a Node.js web app in Azure](https://docs.microsoft.com/azure/app-service/quickstart-nodejs)" quickstart in the Azure web app documentation demonstrates using {% data variables.product.prodname_vscode %} with the [Azure App Service extension](https://marketplace.visualstudio.com/items?itemName=ms-azuretools.vscode-azureappservice).
+* Azure web 应用文档中的“[在 Azure 中创建 Node.js Web 应用](https://docs.microsoft.com/azure/app-service/quickstart-nodejs)”快速入门介绍了 {% data variables.product.prodname_vscode %} 与 [Azure 应用服务扩展](https://marketplace.visualstudio.com/items?itemName=ms-azuretools.vscode-azureappservice)一起使用。
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 5cfc48630e..54a543559b 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
@@ -174,25 +174,25 @@ shortTitle: 安全日志
 {% ifversion fpt or ghec %}
 ### `sponsors` 类操作
 
-| 操作                                            | 描述                                                                                                                                                                                                                                                                                                                      |
-| --------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `custom_amount_settings_change`               | 启用或禁用自定义金额时或更改建议的自定义金额时触发（请参阅“[管理您的赞助级别](/github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship-tiers)”）                                                                                                                                                                           |
-| `repo_funding_links_file_action`              | 更改仓库中的 FUNDING 文件时触发（请参阅“[在仓库中显示赞助按钮](/articles/displaying-a-sponsor-button-in-your-repository)”）                                                                                                                                                                                                                       |
-| `sponsor_sponsorship_cancel`                  | 当您取消赞助时触发（请参阅“[降级赞助](/articles/downgrading-a-sponsorship)”）                                                                                                                                                                                                                                                             |
-| `sponsor_sponsorship_create`                  | 当您赞助帐户时触发（请参阅“[赞助开源贡献者](/sponsors/sponsoring-open-source-contributors/sponsoring-an-open-source-contributor)”）                                                                                                                                                                                                          |
-| `sponsor_sponsorship_payment_complete`        | 当您赞助一个帐户并且您的付款已经处理完毕后触发（请参阅“[赞助开源贡献者](/sponsors/sponsoring-open-source-contributors/sponsoring-an-open-source-contributor)”）                                                                                                                                                                                            |
-| `sponsor_sponsorship_preference_change`       | 当您更改是否接收被赞助开发者的电子邮件更新时触发（请参阅“[管理赞助](/sponsors/sponsoring-open-source-contributors/managing-your-sponsorship)”）                                                                                                                                                                                                          |
-| `sponsor_sponsorship_tier_change`             | 当您升级或降级赞助时触发（请参阅“[升级赞助](/articles/upgrading-a-sponsorship)”和“[降级赞助](/articles/downgrading-a-sponsorship)”）                                                                                                                                                                                                              |
-| `sponsored_developer_approve`                 | Triggered when your {% data variables.product.prodname_sponsors %} account is approved (see "[Setting up {% data variables.product.prodname_sponsors %} for your personal account](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-personal-account)")                     |
-| `sponsored_developer_create`                  | Triggered when your {% data variables.product.prodname_sponsors %} account is created (see "[Setting up {% data variables.product.prodname_sponsors %} for your personal account](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-personal-account)")                      |
-| `sponsored_developer_disable`                 | 帐户 {% data variables.product.prodname_sponsors %} 禁用时触发                                                                                                                                                                                                                                                                 |
-| `sponsored_developer_redraft`                 | 当您的 {% data variables.product.prodname_sponsors %} 帐户从已批准状态恢复为草稿状态时触发                                                                                                                                                                                                                                                   |
-| `sponsored_developer_profile_update`          | 在编辑您的被赞助开发者个人资料时触发（请参阅“[编辑 {% data variables.product.prodname_sponsors %} 的个人资料详细信息](/sponsors/receiving-sponsorships-through-github-sponsors/editing-your-profile-details-for-github-sponsors)”）                                                                                                                       |
-| `sponsored_developer_request_approval`        | Triggered when you submit your application for {% data variables.product.prodname_sponsors %} for approval (see "[Setting up {% data variables.product.prodname_sponsors %} for your personal account](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-personal-account)") |
-| `sponsored_developer_tier_description_update` | 当您更改赞助等级的说明时触发（请参阅“[管理赞助等级](/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers)”）                                                                                                                                                                                                 |
-| `sponsored_developer_update_newsletter_send`  | 当您向赞助者发送电子邮件更新时触发（请参阅“[联系赞助者](/sponsors/receiving-sponsorships-through-github-sponsors/contacting-your-sponsors)”）                                                                                                                                                                                                      |
-| `waitlist_invite_sponsored_developer`         | Triggered when you are invited to join {% data variables.product.prodname_sponsors %} from the waitlist (see "[Setting up {% data variables.product.prodname_sponsors %} for your personal account](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-personal-account)")    |
-| `waitlist_join`                               | Triggered when you join the waitlist to become a sponsored developer (see "[Setting up {% data variables.product.prodname_sponsors %} for your personal account](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-personal-account)")                                       |
+| 操作                                            | 描述                                                                                                                                                                                                                                              |
+| --------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `custom_amount_settings_change`               | 启用或禁用自定义金额时或更改建议的自定义金额时触发（请参阅“[管理您的赞助级别](/github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship-tiers)”）                                                                                                   |
+| `repo_funding_links_file_action`              | 更改仓库中的 FUNDING 文件时触发（请参阅“[在仓库中显示赞助按钮](/articles/displaying-a-sponsor-button-in-your-repository)”）                                                                                                                                               |
+| `sponsor_sponsorship_cancel`                  | 当您取消赞助时触发（请参阅“[降级赞助](/articles/downgrading-a-sponsorship)”）                                                                                                                                                                                     |
+| `sponsor_sponsorship_create`                  | 当您赞助帐户时触发（请参阅“[赞助开源贡献者](/sponsors/sponsoring-open-source-contributors/sponsoring-an-open-source-contributor)”）                                                                                                                                  |
+| `sponsor_sponsorship_payment_complete`        | 当您赞助一个帐户并且您的付款已经处理完毕后触发（请参阅“[赞助开源贡献者](/sponsors/sponsoring-open-source-contributors/sponsoring-an-open-source-contributor)”）                                                                                                                    |
+| `sponsor_sponsorship_preference_change`       | 当您更改是否接收被赞助开发者的电子邮件更新时触发（请参阅“[管理赞助](/sponsors/sponsoring-open-source-contributors/managing-your-sponsorship)”）                                                                                                                                  |
+| `sponsor_sponsorship_tier_change`             | 当您升级或降级赞助时触发（请参阅“[升级赞助](/articles/upgrading-a-sponsorship)”和“[降级赞助](/articles/downgrading-a-sponsorship)”）                                                                                                                                      |
+| `sponsored_developer_approve`                 | 当您的 {% data variables.product.prodname_sponsors %} 帐户被批准时触发（请参阅“[为您的个人帐户设置 {% data variables.product.prodname_sponsors %}](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-personal-account)”）     |
+| `sponsored_developer_create`                  | 当您的 {% data variables.product.prodname_sponsors %} 帐户创建时触发（请参阅“[为您的个人帐户设置 {% data variables.product.prodname_sponsors %}](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-personal-account)”）      |
+| `sponsored_developer_disable`                 | 帐户 {% data variables.product.prodname_sponsors %} 禁用时触发                                                                                                                                                                                         |
+| `sponsored_developer_redraft`                 | 当您的 {% data variables.product.prodname_sponsors %} 帐户从已批准状态恢复为草稿状态时触发                                                                                                                                                                           |
+| `sponsored_developer_profile_update`          | 在编辑您的被赞助开发者个人资料时触发（请参阅“[编辑 {% data variables.product.prodname_sponsors %} 的个人资料详细信息](/sponsors/receiving-sponsorships-through-github-sponsors/editing-your-profile-details-for-github-sponsors)”）                                               |
+| `sponsored_developer_request_approval`        | 在您提交 {% data variables.product.prodname_sponsors %} 申请以供审批时触发（请参阅“[为您的个人帐户设置 {% data variables.product.prodname_sponsors %}](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-personal-account)”）   |
+| `sponsored_developer_tier_description_update` | 当您更改赞助等级的说明时触发（请参阅“[管理赞助等级](/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers)”）                                                                                                                         |
+| `sponsored_developer_update_newsletter_send`  | 当您向赞助者发送电子邮件更新时触发（请参阅“[联系赞助者](/sponsors/receiving-sponsorships-through-github-sponsors/contacting-your-sponsors)”）                                                                                                                              |
+| `waitlist_invite_sponsored_developer`         | 当您从等候名单被邀请加入 {% data variables.product.prodname_sponsors %} 时触发（请参阅“[为您的个人帐户设置 {% data variables.product.prodname_sponsors %}](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-personal-account)”） |
+| `waitlist_join`                               | 当您加入成为被赞助开发者的等候名单时触发（请参阅“[为您的个人帐户设置 {% data variables.product.prodname_sponsors %}](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-personal-account)”）                                            |
 {% endif %}
 
 {% ifversion fpt or ghec %}
diff --git a/translations/zh-CN/content/code-security/dependabot/dependabot-version-updates/about-dependabot-version-updates.md b/translations/zh-CN/content/code-security/dependabot/dependabot-version-updates/about-dependabot-version-updates.md
index cd1a0ff73d..43433633f5 100644
--- a/translations/zh-CN/content/code-security/dependabot/dependabot-version-updates/about-dependabot-version-updates.md
+++ b/translations/zh-CN/content/code-security/dependabot/dependabot-version-updates/about-dependabot-version-updates.md
@@ -30,7 +30,7 @@ shortTitle: Dependabot 版本更新
 
 {% data variables.product.prodname_dependabot %} 负责维护您的依赖项。 您可以使用它来确保仓库自动跟上它所依赖的包和应用程序的最新版本。
 
-通过将 _dependabot.yml_ 配置文件检入仓库，可启用 {% data variables.product.prodname_dependabot_version_updates %}。 配置文件指定存储在仓库中的清单或其他包定义文件的位置。 {% data variables.product.prodname_dependabot %} 使用此信息来检查过时的软件包和应用程序。 {% data variables.product.prodname_dependabot %} 确定依赖项是否有新版本，它通过查看依赖的语义版本 ([semver](https://semver.org/)) 来决定是否应更新该版本。 对于某些软件包管理器，{% data variables.product.prodname_dependabot_version_updates %} 也支持供应。 供应（或缓存）的依赖项是检入仓库中特定目录的依赖项，而不是在清单中引用的依赖项。 即使包服务器不可用，供应的依赖项在生成时也可用。 {% data variables.product.prodname_dependabot_version_updates %} 可以配置为检查为新版本供应的依赖项，并在必要时更新它们。
+通过将 `dependabot.yml` 配置文件检入仓库，可启用 {% data variables.product.prodname_dependabot_version_updates %}。 配置文件指定存储在仓库中的清单或其他包定义文件的位置。 {% data variables.product.prodname_dependabot %} 使用此信息来检查过时的软件包和应用程序。 {% data variables.product.prodname_dependabot %} 确定依赖项是否有新版本，它通过查看依赖的语义版本 ([semver](https://semver.org/)) 来决定是否应更新该版本。 对于某些软件包管理器，{% data variables.product.prodname_dependabot_version_updates %} 也支持供应。 供应（或缓存）的依赖项是检入仓库中特定目录的依赖项，而不是在清单中引用的依赖项。 即使包服务器不可用，供应的依赖项在生成时也可用。 {% data variables.product.prodname_dependabot_version_updates %} 可以配置为检查为新版本供应的依赖项，并在必要时更新它们。
 
 当 {% data variables.product.prodname_dependabot %} 发现过时的依赖项时，它会发起拉取请求以将清单更新到依赖项的最新版本。 对于供应和依赖项，{% data variables.product.prodname_dependabot %} 提出拉取请求以直接将过时的依赖项替换为新版本。 检查测试是否通过，查看拉取请求摘要中包含的更改日志和发行说明，然后合并它。 更多信息请参阅“[配置 {% data variables.product.prodname_dependabot %} 版本更新](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/enabling-and-disabling-dependabot-version-updates)”。
 
diff --git a/translations/zh-CN/content/code-security/supply-chain-security/end-to-end-supply-chain/end-to-end-supply-chain-overview.md b/translations/zh-CN/content/code-security/supply-chain-security/end-to-end-supply-chain/end-to-end-supply-chain-overview.md
index d03c07e432..276f0c98cb 100644
--- a/translations/zh-CN/content/code-security/supply-chain-security/end-to-end-supply-chain/end-to-end-supply-chain-overview.md
+++ b/translations/zh-CN/content/code-security/supply-chain-security/end-to-end-supply-chain/end-to-end-supply-chain-overview.md
@@ -19,7 +19,7 @@ topics:
 
 端到端软件供应链安全的核心是确保您分发的代码未被篡改。 以前，攻击者专注于针对您使用的依赖项，例如库和框架。 攻击者现在已经扩大了他们的关注点，包括针对用户帐户和构建过程，因此这些系统也必须得到保护。
 
-For information about features in {% data variables.product.prodname_dotcom %} that can help you secure dependencies, see "[About supply chain security](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-supply-chain-security)."
+有关 {% data variables.product.prodname_dotcom %} 中可帮助您保护依赖关系的功能的信息，请参阅“[关于供应链安全](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-supply-chain-security)”。
 
 ## 关于这些指南
 
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 7e851c9dac..00efca6505 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
@@ -37,7 +37,7 @@ redirect_from:
 
 依赖项审查支持与依赖关系图相同的语言和包管理生态系统。 更多信息请参阅“[关于依赖关系图](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph#supported-package-ecosystems)”。
 
-For more information on supply chain features available on {% data variables.product.product_name %}, see "[About supply chain security](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-supply-chain-security)."
+有关 {% data variables.product.product_name %} 上可用的供应链功能的更多信息，请参阅“[关于供应链安全](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-supply-chain-security)”。
 
 {% ifversion ghec or ghes %}
 ## 启用依赖项审查
diff --git a/translations/zh-CN/content/codespaces/codespaces-reference/disaster-recovery-for-codespaces.md b/translations/zh-CN/content/codespaces/codespaces-reference/disaster-recovery-for-codespaces.md
index 143a723a10..0443a99f24 100644
--- a/translations/zh-CN/content/codespaces/codespaces-reference/disaster-recovery-for-codespaces.md
+++ b/translations/zh-CN/content/codespaces/codespaces-reference/disaster-recovery-for-codespaces.md
@@ -42,7 +42,7 @@ shortTitle: 灾难恢复
 
 ## 选项 4：对本地容器化环境使用远程容器和 Docker
 
-If your repository has a `devcontainer.json`, consider using the [Remote-Containers extension](https://code.visualstudio.com/docs/remote/containers#_quick-start-open-a-git-repository-or-github-pr-in-an-isolated-container-volume) in {% data variables.product.prodname_vscode %} to build and attach to a local development container for your repository. 此选项的设置时间将因您本地规格和开发容器设置的复杂性而异。
+如果您的存储库具有 `devconconer.json`，请考虑在 {% data variables.product.prodname_vscode %} 中使用[远程容器扩展](https://code.visualstudio.com/docs/remote/containers#_quick-start-open-a-git-repository-or-github-pr-in-an-isolated-container-volume)构建并连接到仓库的本地开发容器。 此选项的设置时间将因您本地规格和开发容器设置的复杂性而异。
 
 {% note %}
 
diff --git a/translations/zh-CN/content/codespaces/codespaces-reference/security-in-codespaces.md b/translations/zh-CN/content/codespaces/codespaces-reference/security-in-codespaces.md
index 2cf8e049fa..327fcff3a1 100644
--- a/translations/zh-CN/content/codespaces/codespaces-reference/security-in-codespaces.md
+++ b/translations/zh-CN/content/codespaces/codespaces-reference/security-in-codespaces.md
@@ -34,7 +34,7 @@ shortTitle: 代码空间中的安全性
 
 ### 身份验证
 
-You can connect to a codespace using a web browser or from {% data variables.product.prodname_vscode %}. If you connect from {% data variables.product.prodname_vscode_shortname %}, you are prompted to authenticate with {% data variables.product.product_name %}.
+您可以使用 web 浏览器或从 {% data variables.product.prodname_vscode %} 连接至代码空间。 如果从 {% data variables.product.prodname_vscode_shortname %} 连接，系统将提示您向 {% data variables.product.product_name %} 验证。
 
 每次创建或重新启动代码空间时，都会为其分配一个具有自动到期期的新 {% data variables.product.company_short %} 令牌。 此时间段允许您在代码空间中工作，而无需在典型的工作日内重新进行身份验证，但降低了在停止使用代码空间时使连接保持打开状态的可能性。
 
diff --git a/translations/zh-CN/content/codespaces/codespaces-reference/using-github-copilot-in-codespaces.md b/translations/zh-CN/content/codespaces/codespaces-reference/using-github-copilot-in-codespaces.md
index e0adf9cf1e..a6a0a614df 100644
--- a/translations/zh-CN/content/codespaces/codespaces-reference/using-github-copilot-in-codespaces.md
+++ b/translations/zh-CN/content/codespaces/codespaces-reference/using-github-copilot-in-codespaces.md
@@ -1,6 +1,6 @@
 ---
-title: 在 Codespaces 中使用 GitHub Copilot
-intro: 您可以通过添加扩展在 Codespaces 中使用 Copilot。
+title: Using GitHub Copilot in Codespaces
+intro: You can use Copilot in Codespaces by adding the extension.
 versions:
   fpt: '*'
   ghec: '*'
@@ -10,14 +10,14 @@ topics:
   - Copilot
   - Visual Studio Code
 product: '{% data reusables.gated-features.codespaces %}'
-shortTitle: Codespaces 中的 Copilot
+shortTitle: Copilot in Codespaces
 redirect_from:
   - /codespaces/codespaces-reference/using-copilot-in-codespaces
 ---
 
-## 使用 {% data variables.product.prodname_copilot %}
+## Using {% data variables.product.prodname_copilot %}
 
-[{% data variables.product.prodname_copilot %}](https://copilot.github.com/) 是 AI 对编程工具，可用于任何代码空间。 To start using {% data variables.product.prodname_copilot_short %} in {% data variables.product.prodname_codespaces %}, install the [{% data variables.product.prodname_copilot_short %} extension from the {% data variables.product.prodname_vscode_marketplace %}](https://marketplace.visualstudio.com/items?itemName=GitHub.copilot).
+[{% data variables.product.prodname_copilot %}](https://copilot.github.com/), an AI pair programmer, can be used in any codespace. To start using {% data variables.product.prodname_copilot_short %} in {% data variables.product.prodname_codespaces %}, install the [{% data variables.product.prodname_copilot_short %} extension from the {% data variables.product.prodname_vscode_marketplace %}](https://marketplace.visualstudio.com/items?itemName=GitHub.copilot).
 
-要在所有代码空间中包含 {% data variables.product.prodname_copilot_short %} 或其他扩展，请启用“设置同步”。 更多信息请参阅“[为帐户个性化 {% data variables.product.prodname_codespaces %}](/codespaces/customizing-your-codespace/personalizing-codespaces-for-your-account#settings-sync)”。 此外，要在所有用户的给定项目中包含 {% data variables.product.prodname_copilot_short %}，可以在 `devcontainer.json` 文件中指定 `GitHub.copilot` 作为扩展名。 有关配置 `devcontainer.json` 文件的信息，请参阅“[开发容器简介](/codespaces/customizing-your-codespace/configuring-codespaces-for-your-project#creating-a-custom-dev-container-configuration)”。
+To include {% data variables.product.prodname_copilot_short %}, or other extensions, in all of your codespaces, enable Settings Sync. For more information, see "[Personalizing {% data variables.product.prodname_codespaces %} for your account](/codespaces/customizing-your-codespace/personalizing-codespaces-for-your-account#settings-sync)." Additionally, to include {% data variables.product.prodname_copilot_short %} in a given project for all users, you can specify `GitHub.copilot` as an extension in your `devcontainer.json` file. For information about configuring a `devcontainer.json` file, see "[Introduction to dev containers](/codespaces/customizing-your-codespace/configuring-codespaces-for-your-project#creating-a-custom-dev-container-configuration)."
 
diff --git a/translations/zh-CN/content/codespaces/codespaces-reference/using-the-vs-code-command-palette-in-codespaces.md b/translations/zh-CN/content/codespaces/codespaces-reference/using-the-vs-code-command-palette-in-codespaces.md
index 76cfa0e0f6..c388f149db 100644
--- a/translations/zh-CN/content/codespaces/codespaces-reference/using-the-vs-code-command-palette-in-codespaces.md
+++ b/translations/zh-CN/content/codespaces/codespaces-reference/using-the-vs-code-command-palette-in-codespaces.md
@@ -17,7 +17,7 @@ redirect_from:
 
 ## 关于 {% data variables.product.prodname_vscode_command_palette %}
 
-命令调色板是 {% data variables.product.prodname_vscode %} 的重点功能之一，可用于代码空间。 {% data variables.product.prodname_vscode_command_palette %} 允许您访问 {% data variables.product.prodname_codespaces %} 和 {% data variables.product.prodname_vscode_shortname %} 的许多命令。 For more information on using the {% data variables.product.prodname_vscode_command_palette_shortname %}, see "[User Interface](https://code.visualstudio.com/docs/getstarted/userinterface#_command-palette)" in the {% data variables.product.prodname_vscode_shortname %} documentation.
+命令调色板是 {% data variables.product.prodname_vscode %} 的重点功能之一，可用于代码空间。 {% data variables.product.prodname_vscode_command_palette %} 允许您访问 {% data variables.product.prodname_codespaces %} 和 {% data variables.product.prodname_vscode_shortname %} 的许多命令。 有关使用 {% data variables.product.prodname_vscode_command_palette_shortname %} 的更多信息，请参阅 {% data variables.product.prodname_vscode_shortname %} 文档中的[用户界面](https://code.visualstudio.com/docs/getstarted/userinterface#_command-palette)。
 
 ## 访问 {% data variables.product.prodname_vscode_command_palette_shortname %}
 
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 271ce10ace..1030da66d3 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
@@ -35,7 +35,7 @@ shortTitle: 创建代码空间
 
 有关代码空间生命周期的更多信息，请参阅“[代码空间生命周期](/codespaces/developing-in-codespaces/codespaces-lifecycle)”。
 
-如果要将 Git 挂钩用于代码空间，则应在步骤 4 中使用 [`devcontainer.json` 生命周期脚本](https://code.visualstudio.com/docs/remote/devcontainerjson-reference#_lifecycle-scripts)设置挂钩，例如 `postCreateCommand`。 由于代码空间容器是在克隆仓库后创建的，因此在容器映像中配置的任何 [git template directory](https://git-scm.com/docs/git-init#_template_directory) 将不适用于代码空间。 在创建代码空间后，必须改为安装挂钩。 For more information on using `postCreateCommand`, see the [`devcontainer.json` reference](https://code.visualstudio.com/docs/remote/devcontainerjson-reference#_devcontainerjson-properties) in the {% data variables.product.prodname_vscode_shortname %} documentation.
+如果要将 Git 挂钩用于代码空间，则应在步骤 4 中使用 [`devcontainer.json` 生命周期脚本](https://code.visualstudio.com/docs/remote/devcontainerjson-reference#_lifecycle-scripts)设置挂钩，例如 `postCreateCommand`。 由于代码空间容器是在克隆仓库后创建的，因此在容器映像中配置的任何 [git template directory](https://git-scm.com/docs/git-init#_template_directory) 将不适用于代码空间。 在创建代码空间后，必须改为安装挂钩。 有关使用 `postCreateCommand` 的更多信息，请参阅 {% data variables.product.prodname_vscode_shortname %} 文档中的 [`devcontainer.json` 参考](https://code.visualstudio.com/docs/remote/devcontainerjson-reference#_devcontainerjson-properties) 。
 
 {% data reusables.codespaces.use-visual-studio-features %}
 
diff --git a/translations/zh-CN/content/codespaces/developing-in-codespaces/using-source-control-in-your-codespace.md b/translations/zh-CN/content/codespaces/developing-in-codespaces/using-source-control-in-your-codespace.md
index f495894ca5..300c065b95 100644
--- a/translations/zh-CN/content/codespaces/developing-in-codespaces/using-source-control-in-your-codespace.md
+++ b/translations/zh-CN/content/codespaces/developing-in-codespaces/using-source-control-in-your-codespace.md
@@ -19,7 +19,7 @@ shortTitle: 源控制
 
 您可以直接在代码空间内执行所需的所有 Git 操作。 例如，您可以从远程仓库获取更改、切换分支、创建新分支、提交和推送更改，以及创建拉取请求。 您可以使用代码空间内的集成终端输入 Git 命令，也可以单击图标和菜单选项以完成所有最常见的 Git 任务。 本指南解释如何使用图形用户界面来控制源代码。
 
-在 {% data variables.product.prodname_github_codespaces %} 中的源控制使用与 {% data variables.product.prodname_vscode %} 相同的工作流程。 For more information, see the {% data variables.product.prodname_vscode_shortname %} documentation "[Using Version Control in {% data variables.product.prodname_vscode_shortname %}](https://code.visualstudio.com/docs/editor/versioncontrol#_git-support)."
+在 {% data variables.product.prodname_github_codespaces %} 中的源控制使用与 {% data variables.product.prodname_vscode %} 相同的工作流程。 更多信息请参阅 {% data variables.product.prodname_vscode_shortname %} 文档“[在 {% data variables.product.prodname_vscode_shortname %} 代码中使用版本控制](https://code.visualstudio.com/docs/editor/versioncontrol#_git-support)”。
 
 使用 {% data variables.product.prodname_github_codespaces %} 更新文件的典型工作流程将是：
 
diff --git a/translations/zh-CN/content/codespaces/getting-started/deep-dive.md b/translations/zh-CN/content/codespaces/getting-started/deep-dive.md
index 8a7783e8e2..e729bee421 100644
--- a/translations/zh-CN/content/codespaces/getting-started/deep-dive.md
+++ b/translations/zh-CN/content/codespaces/getting-started/deep-dive.md
@@ -46,13 +46,13 @@ topics:
 
 ### 步骤 3：连接到代码空间
 
-创建容器并运行任何其他初始化后，您将连接到代码空间。 You can connect to it through the web or via [{% data variables.product.prodname_vscode_shortname %}](/codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code), or both, if needed.
+创建容器并运行任何其他初始化后，您将连接到代码空间。 如果需要，您可以通过 Web 和/或 [{% data variables.product.prodname_vscode_shortname %}](/codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code) 连接。
 
 ### 步骤 4：创建后设置
 
 连接到代码空间后，您的自动设置可能会根据您在 `devcontainer.json` 文件中指定的配置继续构建。 您可能会看到 `postCreateCommand` 和 `postAttachCommand` 运行。
 
-如果要在代码空间中使用 Git 挂钩，请使用 [`devcontainer.json` 生命周期脚本](https://code.visualstudio.com/docs/remote/devcontainerjson-reference#_lifecycle-scripts)设置挂钩，例如 `postCreateCommand`。 For more information, see the [`devcontainer.json` reference](https://code.visualstudio.com/docs/remote/devcontainerjson-reference#_devcontainerjson-properties) in the {% data variables.product.prodname_vscode_shortname %} documentation.
+如果要在代码空间中使用 Git 挂钩，请使用 [`devcontainer.json` 生命周期脚本](https://code.visualstudio.com/docs/remote/devcontainerjson-reference#_lifecycle-scripts)设置挂钩，例如 `postCreateCommand`。 更多信息请参阅 {% data variables.product.prodname_vscode_shortname %} 文档中的 [`devcontainer.json` 参考](https://code.visualstudio.com/docs/remote/devcontainerjson-reference#_devcontainerjson-properties)。
 
 如果您有一个用于 {% data variables.product.prodname_codespaces %} 的公共 dotfile 存储库，则可以启用它以用于新的代码空间。 启用后，您的 dotfile 将被克隆到容器中，并且将调用安装脚本。 更多信息请参阅“[为帐户个性化 {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/personalizing-codespaces-for-your-account#dotfiles)”。
 
@@ -93,7 +93,7 @@ topics:
 
 ## 提交和推送更改
 
-默认情况下，Git 在代码空间中可用，因此您可以依赖现有的 Git 工作流程。 You can work with Git in your codespace either via the Terminal or by using [{% data variables.product.prodname_vscode_shortname %}](https://code.visualstudio.com/docs/editor/versioncontrol)'s source control UI. 更多信息请参阅“[在代码空间中使用源控制](/codespaces/developing-in-codespaces/using-source-control-in-your-codespace)”。
+默认情况下，Git 在代码空间中可用，因此您可以依赖现有的 Git 工作流程。 您可以通过终端或使用 [{% data variables.product.prodname_vscode_shortname %}](https://code.visualstudio.com/docs/editor/versioncontrol) 的源代码管理 UI 在代码空间中使用 Git。 更多信息请参阅“[在代码空间中使用源控制](/codespaces/developing-in-codespaces/using-source-control-in-your-codespace)”。
 
 ![在代码空间终端中运行 git 状态](/assets/images/help/codespaces/git-status.png)
 
@@ -107,7 +107,7 @@ topics:
 
 ## 使用扩展个性化您的代码空间
 
-Using {% data variables.product.prodname_vscode_shortname %} in your codespace gives you access to the {% data variables.product.prodname_vscode_marketplace %} so that you can add any extensions you need. 有关扩展如何在 {% data variables.product.prodname_codespaces %} 中运行的信息，请参阅 {% data variables.product.prodname_vscode_shortname %} 文档中的[支持远程开发和 GitHub 代码空间](https://code.visualstudio.com/api/advanced-topics/remote-extensions) 。
+在代码空间中使用 {% data variables.product.prodname_vscode_shortname %} 可以访问 {% data variables.product.prodname_vscode_marketplace %}，以便您可以添加所需的任何扩展。 有关扩展如何在 {% data variables.product.prodname_codespaces %} 中运行的信息，请参阅 {% data variables.product.prodname_vscode_shortname %} 文档中的[支持远程开发和 GitHub 代码空间](https://code.visualstudio.com/api/advanced-topics/remote-extensions) 。
 
 如果您已使用 {% data variables.product.prodname_vscode_shortname %}，则可以使用[设置同步](https://code.visualstudio.com/docs/editor/settings-sync)在本地实例和您创建的任何 {% data variables.product.prodname_codespaces %} 之间自动同步扩展程序、设置、主题和键盘快捷键。
 
diff --git a/translations/zh-CN/content/codespaces/getting-started/quickstart.md b/translations/zh-CN/content/codespaces/getting-started/quickstart.md
index 5eb2d0faa4..2b1878f3d3 100644
--- a/translations/zh-CN/content/codespaces/getting-started/quickstart.md
+++ b/translations/zh-CN/content/codespaces/getting-started/quickstart.md
@@ -72,7 +72,7 @@ redirect_from:
 
 ## 使用扩展进行个性化设置
 
-Within a codespace, you have access to the {% data variables.product.prodname_vscode_marketplace %}. 在本示例中，您将安装可更改主题的扩展，但您可以安装对工作流程有用的任何扩展。
+在代码空间中，您可以访问 {% data variables.product.prodname_vscode_marketplace %}。 在本示例中，您将安装可更改主题的扩展，但您可以安装对工作流程有用的任何扩展。
 
 1. 在左侧栏中，单击扩展图标。
 
@@ -84,7 +84,7 @@ Within a codespace, you have access to the {% data variables.product.prodname_vs
 
   ![选择 fairyfloss 主题](/assets/images/help/codespaces/fairyfloss.png)
 
-4. Changes you make to your editor setup in the current codespace, such as theme and keyboard bindings, are synced automatically via [Settings Sync](https://code.visualstudio.com/docs/editor/settings-sync) to any other codespaces you open and any instances of {% data variables.product.prodname_vscode %} that are signed into your GitHub account.
+4. 在当前代码空间中对编辑器设置所做的更改，如主题和键盘绑定，将通过 [Settings Sync（设置同步）](https://code.visualstudio.com/docs/editor/settings-sync)自动同步到您打开的任何其他代码空间以及登录到您 GitHub 帐户的任何 {% data variables.product.prodname_vscode %} 实例。
 
 ## 后续步骤
 
diff --git a/translations/zh-CN/content/codespaces/managing-codespaces-for-your-organization/managing-billing-for-codespaces-in-your-organization.md b/translations/zh-CN/content/codespaces/managing-codespaces-for-your-organization/managing-billing-for-codespaces-in-your-organization.md
index 72ccdb769d..a85bbca434 100644
--- a/translations/zh-CN/content/codespaces/managing-codespaces-for-your-organization/managing-billing-for-codespaces-in-your-organization.md
+++ b/translations/zh-CN/content/codespaces/managing-codespaces-for-your-organization/managing-billing-for-codespaces-in-your-organization.md
@@ -41,7 +41,7 @@ topics:
 
 ## 删除未使用的代码空间
 
-Your users can delete their codespaces in https://github.com/codespaces and from within {% data variables.product.prodname_vscode %}. To reduce the size of a codespace, users can manually delete files using the terminal or from within {% data variables.product.prodname_vscode_shortname %}.
+您的用户可以在 https://github.com/codespaces 中以及从 {% data variables.product.prodname_vscode %} 中删除代码空间。 要减小代码空间的大小，用户可以使用终端或从 {% data variables.product.prodname_vscode_shortname %} 中手动删除文件。
 
 {% note %}
 
diff --git a/translations/zh-CN/content/codespaces/managing-your-codespaces/managing-repository-access-for-your-codespaces.md b/translations/zh-CN/content/codespaces/managing-your-codespaces/managing-repository-access-for-your-codespaces.md
index 3e48e427ec..5bc8691cc8 100644
--- a/translations/zh-CN/content/codespaces/managing-your-codespaces/managing-repository-access-for-your-codespaces.md
+++ b/translations/zh-CN/content/codespaces/managing-your-codespaces/managing-repository-access-for-your-codespaces.md
@@ -25,7 +25,7 @@ redirect_from:
 若要创建定义了自定义权限的代码空间，必须使用下列方法之一：
 * {% data variables.product.prodname_dotcom %} web UI
 * [{% data variables.product.prodname_dotcom %} CLI](https://github.com/cli/cli/releases/latest) 2.5.2 或更高版本
-* [{% data variables.product.prodname_github_codespaces %} {% data variables.product.prodname_vscode %} extension](https://marketplace.visualstudio.com/items?itemName=GitHub.codespaces) 1.5.3 or later
+* [{% data variables.product.prodname_github_codespaces %} {% data variables.product.prodname_vscode %} 扩展](https://marketplace.visualstudio.com/items?itemName=GitHub.codespaces) 1.5.3 或更高版本
 
 ## 设置其他存储库权限
 
diff --git a/translations/zh-CN/content/codespaces/overview.md b/translations/zh-CN/content/codespaces/overview.md
index 1800b80d11..72dccf2892 100644
--- a/translations/zh-CN/content/codespaces/overview.md
+++ b/translations/zh-CN/content/codespaces/overview.md
@@ -34,7 +34,7 @@ topics:
 
 如果不添加开发容器配置， {% data variables.product.prodname_codespaces %} 会将存储库克隆到具有默认代码空间映像的环境中，该映像包含许多工具、语言和运行时环境。 更多信息请参阅“[开发容器简介](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)”。
 
-您还可以通过使用公共 [dotfiles](https://dotfiles.github.io/tutorials/) 存储库和[设置同步](https://code.visualstudio.com/docs/editor/settings-sync)来个性化代码空间环境的各个方面。 Personalization can include shell preferences, additional tools, editor settings, and {% data variables.product.prodname_vscode_shortname %} extensions. 更多信息请参阅“[自定义代码空间](/codespaces/customizing-your-codespace)”。
+您还可以通过使用公共 [dotfiles](https://dotfiles.github.io/tutorials/) 存储库和[设置同步](https://code.visualstudio.com/docs/editor/settings-sync)来个性化代码空间环境的各个方面。 个性化可以包括 shell 首选项、其他工具、编辑器设置和 {% data variables.product.prodname_vscode_shortname %} 扩展。 更多信息请参阅“[自定义代码空间](/codespaces/customizing-your-codespace)”。
 
 ## 关于 {% data variables.product.prodname_codespaces %} 的计费
 
diff --git a/translations/zh-CN/content/codespaces/prebuilding-your-codespaces/configuring-prebuilds.md b/translations/zh-CN/content/codespaces/prebuilding-your-codespaces/configuring-prebuilds.md
index 0d6d194897..91eca5bdcb 100644
--- a/translations/zh-CN/content/codespaces/prebuilding-your-codespaces/configuring-prebuilds.md
+++ b/translations/zh-CN/content/codespaces/prebuilding-your-codespaces/configuring-prebuilds.md
@@ -94,7 +94,7 @@ permissions: People with admin access to a repository can configure prebuilds fo
 
 ## 配置要包含在预构建中的耗时任务
 
-您可以在 `devcontainer.json` 中使用 `onCreateCommand` 和 `updateContentCommand` 命令，以将耗时的过程作为预构建模板创建的一部分包括在内。 For more information, see the {% data variables.product.prodname_vscode %} documentation, "[devcontainer.json reference](https://code.visualstudio.com/docs/remote/devcontainerjson-reference#_lifecycle-scripts)."
+您可以在 `devcontainer.json` 中使用 `onCreateCommand` 和 `updateContentCommand` 命令，以将耗时的过程作为预构建模板创建的一部分包括在内。 更多信息请参阅 {% data variables.product.prodname_vscode %} 文档“[devcontainer.json 参考](https://code.visualstudio.com/docs/remote/devcontainerjson-reference#_lifecycle-scripts)”。
 
 `onCreateCommand` 仅在创建预构建模板时运行一次，而 `updateContentCommand` 在模板创建和后续模板更新时运行。 增量构建应包含在 `updateContentCommand` 中，因为它们表示项目的源代码，并且需要包含在每个预构建模板更新中。
 
diff --git a/translations/zh-CN/content/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers.md b/translations/zh-CN/content/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers.md
index 91af0f889a..4527cd3b20 100644
--- a/translations/zh-CN/content/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers.md
+++ b/translations/zh-CN/content/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers.md
@@ -110,7 +110,7 @@ RUN apt-get update && bash /tmp/library-scripts/github-debian.sh
 }
 ```
 
-For more information about using a Dockerfile in a dev container configuration, see the {% data variables.product.prodname_vscode_shortname %} documentation "[Create a development container](https://code.visualstudio.com/docs/remote/create-dev-container#_dockerfile)."
+有关在开发容器配置中使用 Dockerfile 的详细信息，请参阅 {% data variables.product.prodname_vscode_shortname %} 文档“[创建开发容器](https://code.visualstudio.com/docs/remote/create-dev-container#_dockerfile)”。
 
 ## 使用默认开发容器配置
 
@@ -122,7 +122,7 @@ For more information about using a Dockerfile in a dev container configuration,
 
 ## 使用预定义的开发容器配置
 
-可以从预定义配置列表中进行选择，以便为存储库创建开发容器配置。 These configurations provide common setups for particular project types, and can help you quickly get started with a configuration that already has the appropriate container options, {% data variables.product.prodname_vscode_shortname %} settings, and {% data variables.product.prodname_vscode_shortname %} extensions that should be installed.
+可以从预定义配置列表中进行选择，以便为存储库创建开发容器配置。 这些配置为特定项目类型提供了常见设置，并可以帮助您快速开始使用已具有相应容器选项、{% data variables.product.prodname_vscode_shortname %} 设置和应安装的 {% data variables.product.prodname_vscode_shortname %} 扩展的配置。
 
 如果您需要一些额外的扩展性，使用预先定义的配置是一个好主意。 您也可以从预定义的配置开始，然后根据项目的需要对其进行修改。
 
@@ -192,9 +192,9 @@ For more information about using a Dockerfile in a dev container configuration,
 
 ### 编辑 devcontainer.json 文件
 
-You can add and edit the supported configuration keys in the `devcontainer.json` file to specify aspects of the codespace's environment, like which {% data variables.product.prodname_vscode_shortname %} extensions will be installed. {% data reusables.codespaces.more-info-devcontainer %}
+您可以在 `devcontainer.json` 文件中添加和编辑支持的配置键，以指定代码空间环境的各个方面，例如将安装哪些 {% data variables.product.prodname_vscode_shortname %} 扩展。 {% data reusables.codespaces.more-info-devcontainer %}
 
-`devcontainer.json` 文件是使用 JSONC 格式编写的。 这允许您在配置文件中包含注释。 For more information, see "[Editing JSON with {% data variables.product.prodname_vscode_shortname %}](https://code.visualstudio.com/docs/languages/json#_json-with-comments)" in the {% data variables.product.prodname_vscode_shortname %} documentation.
+`devcontainer.json` 文件是使用 JSONC 格式编写的。 这允许您在配置文件中包含注释。 更多信息请参阅 {% data variables.product.prodname_vscode_shortname %} 文档中的“[使用 {% data variables.product.prodname_vscode_shortname %} 编辑 JSON](https://code.visualstudio.com/docs/languages/json#_json-with-comments)”。
 
 {% note %}
 
@@ -202,11 +202,11 @@ You can add and edit the supported configuration keys in the `devcontainer.json`
 
 {% endnote %}
 
-### Editor settings for {% data variables.product.prodname_vscode_shortname %}
+### {% data variables.product.prodname_vscode_shortname %}的编辑器设置
 
 {% data reusables.codespaces.vscode-settings-order %}
 
-You can define default editor settings for {% data variables.product.prodname_vscode_shortname %} in two places.
+您可以在两个地方定义 {% data variables.product.prodname_vscode_shortname %} 的默认编辑器设置。
 
 * 在存储库的 `.vscode/settings.json` 文件中定义的编辑器设置将作为代码空间中_工作区_范围的设置进行应用。
 * `devcontainer.json` 文件的 `settings` 键中定义的编辑器设置在代码空间中用作 _Remote [Codespaces]_ 范围的设置。
diff --git a/translations/zh-CN/content/codespaces/troubleshooting/troubleshooting-prebuilds.md b/translations/zh-CN/content/codespaces/troubleshooting/troubleshooting-prebuilds.md
index 38ead679c2..c182a38d34 100644
--- a/translations/zh-CN/content/codespaces/troubleshooting/troubleshooting-prebuilds.md
+++ b/translations/zh-CN/content/codespaces/troubleshooting/troubleshooting-prebuilds.md
@@ -22,11 +22,11 @@ miniTocMaxHeadingLevel: 3
 
 ![可用计算机类型的列表](/assets/images/help/codespaces/choose-custom-machine-type.png)
 
-If you have your {% data variables.product.prodname_codespaces %} editor preference set to "{% data variables.product.prodname_vscode %} for Web" then the "Setting up your codespace" page will show the message "Prebuilt codespace found" if a prebuild is being used.
+如果将 {% data variables.product.prodname_codespaces %} 编辑器首选项设置为“{% data variables.product.prodname_vscode %} for Web”，则“设置代码空间”页面将显示消息“找到预构建的代码空间”（如果正在使用预构建）。
 
 ![“找到预构建的代码空间”消息](/assets/images/help/codespaces/prebuilt-codespace-found.png)
 
-Similarly, if your editor preference is "{% data variables.product.prodname_vscode_shortname %}" then the integrated terminal will contain the message "You are on a prebuilt codespace defined by the prebuild configuration for your repository" when you create a new codespace. 更多信息请参阅“[设置代码空间的默认编辑器](/codespaces/customizing-your-codespace/setting-your-default-editor-for-codespaces)”。
+同样，如果您的编辑器首选项是“{% data variables.product.prodname_vscode_shortname %}”，则当您创建新代码空间时，集成终端将包含消息“您正在使用由存储库的预构建配置定义的预构建代码空间”。 更多信息请参阅“[设置代码空间的默认编辑器](/codespaces/customizing-your-codespace/setting-your-default-editor-for-codespaces)”。
 
 创建代码空间后，可以通过在终端中运行以下 {% data variables.product.prodname_cli %} 命令来检查它是否是从预构建创建的：
 
diff --git a/translations/zh-CN/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/about-using-visual-studio-code-with-github-classroom.md b/translations/zh-CN/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/about-using-visual-studio-code-with-github-classroom.md
index e8ac979c34..913fa99fd6 100644
--- a/translations/zh-CN/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/about-using-visual-studio-code-with-github-classroom.md
+++ b/translations/zh-CN/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/about-using-visual-studio-code-with-github-classroom.md
@@ -1,7 +1,7 @@
 ---
 title: 关于将 Visual Studio Code 与 GitHub Classroom 配合使用
 shortTitle: 关于使用 Visual Studio Code
-intro: 'You can configure {% data variables.product.prodname_vscode %} as the preferred editor for assignments in {% data variables.product.prodname_classroom %}.'
+intro: '您可以将 {% data variables.product.prodname_vscode %} 配置为 {% data variables.product.prodname_classroom %} 中任务的首选编辑器。'
 versions:
   fpt: '*'
 redirect_from:
@@ -10,30 +10,30 @@ redirect_from:
 
 ## 关于 {% data variables.product.prodname_vscode %}
 
-{% data variables.product.prodname_vscode %} is a lightweight but powerful source code editor which runs on your desktop and is available for Windows, macOS and Linux. With the [GitHub Classroom extension for {% data variables.product.prodname_vscode_shortname %}](https://aka.ms/classroom-vscode-ext), students can easily browse, edit, submit, collaborate, and test their Classroom Assignments. 有关 IDE 和 {% data variables.product.prodname_classroom %} 的更多信息，请参阅“[集成 {% data variables.product.prodname_classroom %} 与 IDE](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/integrate-github-classroom-with-an-ide)”。
+{% data variables.product.prodname_vscode %} 是一个轻量级但功能强大的源代码编辑器，可在桌面上运行，适用于 Windows、macOS 和 Linux。 借助 [{% data variables.product.prodname_vscode_shortname %} 的 GitHub Classroom 扩展](https://aka.ms/classroom-vscode-ext)，学生可以轻松浏览、编辑、提交、协作和测试他们的课堂作业。 有关 IDE 和 {% data variables.product.prodname_classroom %} 的更多信息，请参阅“[集成 {% data variables.product.prodname_classroom %} 与 IDE](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/integrate-github-classroom-with-an-ide)”。
 
 ### 您学生的首选编辑器
-The GitHub Classroom integration with {% data variables.product.prodname_vscode_shortname %} provides students with an extension pack which contains:
+GitHub Classroom 与 {% data variables.product.prodname_vscode_shortname %} 的集成为学生提供了一个扩展包，其中包含：
 
 1. [GitHub 课程扩展](https://aka.ms/classroom-vscode-ext)，其中包含自定义摘要，便于学生轻松入门。
 2. [Visual Studio 实时分享扩展](https://marketplace.visualstudio.com/items?itemName=MS-vsliveshare.vsliveshare-pack)，集成到学生视图中，以便轻松获取助教和同学的帮助与协作。
 3. [GitHub 拉取请求扩展](https://marketplace.visualstudio.com/items?itemName=GitHub.vscode-pull-request-github)，允许学生在编辑器中查看教师的反馈。
 
-### How to launch the assignment in {% data variables.product.prodname_vscode_shortname %}
-When creating an assignment, {% data variables.product.prodname_vscode_shortname %} can be added as the preferred editor for an assignment. 有关详细信息，请参阅“[集成 {% data variables.product.prodname_classroom %} 与 IDE](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/integrate-github-classroom-with-an-ide)”。
+### 如何在 {% data variables.product.prodname_vscode_shortname %} 中启动作业
+创建任务时，可以将 {% data variables.product.prodname_vscode_shortname %} 添加为任务的首选编辑器。 有关详细信息，请参阅“[集成 {% data variables.product.prodname_classroom %} 与 IDE](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/integrate-github-classroom-with-an-ide)”。
 
-This will include an "Open in {% data variables.product.prodname_vscode_shortname %}" badge in all student repositories. This badge handles installing {% data variables.product.prodname_vscode_shortname %}, the Classroom extension pack, and opening to the active assignment with one click.
+这将包括所有学生存储库中的“在 {% data variables.product.prodname_vscode_shortname %} 中打开”徽章。 此徽章处理安装 {% data variables.product.prodname_vscode_shortname %}（课堂扩展包）以及一键打开活动的作业。
 
 {% note %}
 
-**Note:** The student must have Git installed on their computer to push code from {% data variables.product.prodname_vscode_shortname %} to their repository. This is not automatically installed when clicking the **Open in {% data variables.product.prodname_vscode_shortname %}** button. 学生可以从[这里](https://git-scm.com/downloads)下载 Git。
+**注意：**学生必须在其计算机上安装 Git 才能将代码从 {% data variables.product.prodname_vscode_shortname %} 推送到其存储库。 单击**在 {% data variables.product.prodname_vscode_shortname %} 代码中打开**按钮时不自动安装。 学生可以从[这里](https://git-scm.com/downloads)下载 Git。
 
 {% endnote %}
 
 ### 如何使用 GitHub 课堂扩展包
 GitHub 课堂扩展有两个主要组件：“课堂”视图和“活动的作业”视图。
 
-When the student launches the extension for the first time, they are automatically navigated to the Explorer tab in {% data variables.product.prodname_vscode_shortname %}, where they can see the "Active Assignment" view alongside the tree-view of files in the repository.
+当学生首次启动扩展时，他们将自动导航到 {% data variables.product.prodname_vscode_shortname %} 中的 Explorer 选项卡，在其中可以看到“活动的作业”视图以及存储库中文件的树视图。
 
 ![GitHub 课堂活动作业视图](/assets/images/help/classroom/vs-code-active-assignment.png)
 
diff --git a/translations/zh-CN/content/get-started/customizing-your-github-workflow/exploring-integrations/github-extensions-and-integrations.md b/translations/zh-CN/content/get-started/customizing-your-github-workflow/exploring-integrations/github-extensions-and-integrations.md
index d775663d97..19f6ecfba3 100644
--- a/translations/zh-CN/content/get-started/customizing-your-github-workflow/exploring-integrations/github-extensions-and-integrations.md
+++ b/translations/zh-CN/content/get-started/customizing-your-github-workflow/exploring-integrations/github-extensions-and-integrations.md
@@ -1,6 +1,6 @@
 ---
-title: GitHub 扩展和集成
-intro: '通过 {% data variables.product.product_name %} 扩展可在第三方应用程序中无缝使用 {% data variables.product.product_name %} 仓库。'
+title: GitHub extensions and integrations
+intro: 'Use {% data variables.product.product_name %} extensions to work seamlessly in {% data variables.product.product_name %} repositories within third-party applications.'
 redirect_from:
   - /articles/about-github-extensions-for-third-party-applications
   - /articles/github-extensions-and-integrations
@@ -9,20 +9,19 @@ redirect_from:
 versions:
   fpt: '*'
   ghec: '*'
-shortTitle: 扩展和集成
+shortTitle: Extensions & integrations
 ---
-
-## 编辑器工具
+## Editor tools
 
 You can connect to {% data variables.product.product_name %} repositories within third-party editor tools, such as Atom, Unity, and {% data variables.product.prodname_vs %}.
 
 ### {% data variables.product.product_name %} for Atom
 
-使用 {% data variables.product.product_name %} for Atom 扩展，您可以从 Atom 编辑器中提交、推送、拉取和解决合并冲突等。 更多信息请参阅官方 [{% data variables.product.product_name %} for Atom 站点](https://github.atom.io/)。
+With the {% data variables.product.product_name %} for Atom extension, you can commit, push, pull, resolve merge conflicts, and more from the Atom editor. For more information, see the official [{% data variables.product.product_name %} for Atom site](https://github.atom.io/).
 
 ### {% data variables.product.product_name %} for Unity
 
-使用 {% data variables.product.product_name %} for Unity 编辑器扩展，您可以在开源游戏开发平台 Unity 上进行开发，在 {% data variables.product.product_name %} 查看您的工作。 更多信息请参阅官方 Unity 编辑器扩展[站点](https://unity.github.com/)或[文档](https://github.com/github-for-unity/Unity/tree/master/docs)。
+With the {% data variables.product.product_name %} for Unity editor extension, you can develop on Unity, the open source game development platform, and see your work on {% data variables.product.product_name %}. For more information, see the official Unity editor extension [site](https://unity.github.com/) or the [documentation](https://github.com/github-for-unity/Unity/tree/master/docs).
 
 ### {% data variables.product.product_name %} for {% data variables.product.prodname_vs %}
 
@@ -32,26 +31,26 @@ With the {% data variables.product.product_name %} for {% data variables.product
 
 With the {% data variables.product.prodname_dotcom %} for {% data variables.product.prodname_vscode %} extension, you can review and manage {% data variables.product.product_name %} pull requests in {% data variables.product.prodname_vscode_shortname %}. For more information, see the official {% data variables.product.prodname_vscode_shortname %} extension [site](https://vscode.github.com/) or [documentation](https://github.com/Microsoft/vscode-pull-request-github).
 
-## 项目管理工具
+## Project management tools
 
-您可以将 {% data variables.product.product_location %} 上的个人或组织帐户与第三方项目管理工具（如 Jira）集成。
+You can integrate your personal or organization account on {% data variables.product.product_location %} with third-party project management tools, such as Jira.
 
-### Jira Cloud 与 {% data variables.product.product_name %}.com 集成
+### Jira Cloud and {% data variables.product.product_name %}.com integration
 
-您可以将 Jira Cloud 与个人或组织帐户集成，以扫描提交和拉取请求，在任何提及的 Jira 议题中创建相关的元数据和超链接。 更多信息请访问 Marketplace 中的 [Jira 集成应用程序](https://github.com/marketplace/jira-software-github)。
+You can integrate Jira Cloud with your personal or organization account to scan commits and pull requests, creating relevant metadata and hyperlinks in any mentioned Jira issues. For more information, visit the [Jira integration app](https://github.com/marketplace/jira-software-github) in the marketplace.
 
-## 团队通信工具
+## Team communication tools
 
-您可以将 {% data variables.product.product_location %} 上的个人或组织帐户与第三方团队通信工具（如 Slack 或 Microsoft Teams）集成。
+You can integrate your personal or organization account on {% data variables.product.product_location %} with third-party team communication tools, such as Slack or Microsoft Teams.
 
-### Slack 与 {% data variables.product.product_name %} 集成
+### Slack and {% data variables.product.product_name %} integration
 
-Slack + {% data variables.product.prodname_dotcom %} 应用可让您订阅存储库或组织，并获取有关议题、拉取请求、提交、讨论、发布、部署审查和部署状态的实时更新。 您还可以执行打开和关闭议题等活动，并且可以在不离开 Slack 的情况下查看对议题和拉取请求的详细引用。 如果您在频道或个人聊天中收到的任何 {% data variables.product.prodname_dotcom %} 通知中被提及，该应用程序还将在 Slack 中向您私发 ping。
+The Slack + {% data variables.product.prodname_dotcom %} app lets you subscribe to your repositories or organizations and get realtime updates about issues, pull requests, commits, discussions, releases, deployment reviews and deployment statuses. You can also perform activities like opening and closing issues, and you can see detailed references to issues and pull requests without leaving Slack. The app will also ping you personally in Slack if you are mentioned as part of any {% data variables.product.prodname_dotcom %} notifications that you receive in your channels or personal chats.
 
-Slack + {% data variables.product.prodname_dotcom %} 应用程序还与 [Slack Enterprise Grid](https://slack.com/intl/en-in/help/articles/360000281563-Manage-apps-on-Enterprise-Grid)兼容。 有关详细信息，请访问市场中的 [Slack + {% data variables.product.prodname_dotcom %} 应用](https://github.com/marketplace/slack-github)。
+The Slack + {% data variables.product.prodname_dotcom %} app is also compatible with [Slack Enterprise Grid](https://slack.com/intl/en-in/help/articles/360000281563-Manage-apps-on-Enterprise-Grid). For more information, visit the [Slack + {% data variables.product.prodname_dotcom %} app](https://github.com/marketplace/slack-github) in the marketplace.
 
-### Microsoft Teams 与 {% data variables.product.product_name %} 集成
+### Microsoft Teams and {% data variables.product.product_name %} integration
 
-通过适用于团队 {% data variables.product.prodname_dotcom %} 应用，您可以订阅存储库或组织，并获取有关议题、拉取请求、提交、讨论、发布、部署评审和部署状态的实时更新。 你还可以执行打开和关闭议题、评论议题和拉取请求等活动，并且可以在不离开 Microsoft Teams 的情况下查看对议题和拉取请求的详细引用。 如果您在频道或个人聊天中收到的任何 {% data variables.product.prodname_dotcom %} 通知中被提及，该应用程序还将在 Microsoft Teams 中向您私发 ping。
+The {% data variables.product.prodname_dotcom %} for Teams app lets you subscribe to your repositories or organizations and get realtime updates about issues, pull requests, commits, discussions, releases, deployment reviews and deployment statuses. You can also perform activities like opening and closing issues, commenting on your issues and pull requests, and you can see detailed references to issues and pull requests without leaving Microsoft Teams. The app will also ping you personally in Teams if you are mentioned as part of any {% data variables.product.prodname_dotcom %} notifications that you receive in your channels or personal chats.
 
-有关详细信息，请访问 Microsoft AppSource 中的 [Teams 应用的 {% data variables.product.prodname_dotcom %}](https://appsource.microsoft.com/en-us/product/office/WA200002077)。
+For more information, visit the [{% data variables.product.prodname_dotcom %} for Teams app](https://appsource.microsoft.com/en-us/product/office/WA200002077) in Microsoft AppSource.
diff --git a/translations/zh-CN/content/get-started/exploring-projects-on-github/following-people.md b/translations/zh-CN/content/get-started/exploring-projects-on-github/following-people.md
index 68ceafd5d1..1aed992c01 100644
--- a/translations/zh-CN/content/get-started/exploring-projects-on-github/following-people.md
+++ b/translations/zh-CN/content/get-started/exploring-projects-on-github/following-people.md
@@ -17,7 +17,7 @@ topics:
 
 ## 关于 {% data variables.product.product_name %} 上的关注者
 
-When you follow people, you'll see their public activity on your personal dashboard.{% ifversion fpt or ghec %} If someone you follow stars a public repository, {% data variables.product.product_name %} may recommend the repository to you.{% endif %} For more information, see "[About your personal dashboard](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/about-your-personal-dashboard#staying-updated-with-activity-from-the-community)."
+关注用户后，您会在个人仪表板看到他们的公开活动。{% ifversion fpt or ghec %} 如果您关注的人将某个公共存储库标星， {% data variables.product.product_name %} 可能会向您推荐该存储库。{% endif %} 更多信息请参阅“[关于个人仪表板](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/about-your-personal-dashboard#staying-updated-with-activity-from-the-community)”。
 
 如果您不希望在 {% data variables.product.product_name %} 上看到某人的公开活动，则可以取消关注他们。
 
diff --git a/translations/zh-CN/content/get-started/getting-started-with-git/associating-text-editors-with-git.md b/translations/zh-CN/content/get-started/getting-started-with-git/associating-text-editors-with-git.md
index 58175b2bd1..daed128a6c 100644
--- a/translations/zh-CN/content/get-started/getting-started-with-git/associating-text-editors-with-git.md
+++ b/translations/zh-CN/content/get-started/getting-started-with-git/associating-text-editors-with-git.md
@@ -28,9 +28,9 @@ shortTitle: 关联文本编辑器
   $ git config --global core.editor "atom --wait"
   ```
 
-## Using {% data variables.product.prodname_vscode %} as your editor
+## 使用 {% data variables.product.prodname_vscode %} 作为编辑器
 
-1. Install [{% data variables.product.prodname_vscode %}](https://code.visualstudio.com/) ({% data variables.product.prodname_vscode_shortname %}). For more information, see "[Setting up {% data variables.product.prodname_vscode_shortname %}](https://code.visualstudio.com/Docs/setup/setup-overview)" in the {% data variables.product.prodname_vscode_shortname %} documentation.
+1. 安装 [{% data variables.product.prodname_vscode %}](https://code.visualstudio.com/) ({% data variables.product.prodname_vscode_shortname %})。 更多信息请参阅 {% data variables.product.prodname_vscode_shortname %} 文档中的“[设置 {% data variables.product.prodname_vscode_shortname %}](https://code.visualstudio.com/Docs/setup/setup-overview)”。
 {% data reusables.command_line.open_the_multi_os_terminal %}
 3. 输入此命令：
   ```shell
@@ -68,9 +68,9 @@ shortTitle: 关联文本编辑器
   $ git config --global core.editor "atom --wait"
   ```
 
-## Using {% data variables.product.prodname_vscode %} as your editor
+## 使用 {% data variables.product.prodname_vscode %} 作为编辑器
 
-1. Install [{% data variables.product.prodname_vscode %}](https://code.visualstudio.com/) ({% data variables.product.prodname_vscode_shortname %}). For more information, see "[Setting up {% data variables.product.prodname_vscode_shortname %}](https://code.visualstudio.com/Docs/setup/setup-overview)" in the {% data variables.product.prodname_vscode_shortname %} documentation.
+1. 安装 [{% data variables.product.prodname_vscode %}](https://code.visualstudio.com/) ({% data variables.product.prodname_vscode_shortname %})。 更多信息请参阅 {% data variables.product.prodname_vscode_shortname %} 文档中的“[设置 {% data variables.product.prodname_vscode_shortname %}](https://code.visualstudio.com/Docs/setup/setup-overview)”。
 {% data reusables.command_line.open_the_multi_os_terminal %}
 3. 输入此命令：
   ```shell
@@ -107,9 +107,9 @@ shortTitle: 关联文本编辑器
   $ git config --global core.editor "atom --wait"
   ```
 
-## Using {% data variables.product.prodname_vscode %} as your editor
+## 使用 {% data variables.product.prodname_vscode %} 作为编辑器
 
-1. Install [{% data variables.product.prodname_vscode %}](https://code.visualstudio.com/) ({% data variables.product.prodname_vscode_shortname %}). For more information, see "[Setting up {% data variables.product.prodname_vscode_shortname %}](https://code.visualstudio.com/Docs/setup/setup-overview)" in the {% data variables.product.prodname_vscode_shortname %} documentation.
+1. 安装 [{% data variables.product.prodname_vscode %}](https://code.visualstudio.com/) ({% data variables.product.prodname_vscode_shortname %})。 更多信息请参阅 {% data variables.product.prodname_vscode_shortname %} 文档中的“[设置 {% data variables.product.prodname_vscode_shortname %}](https://code.visualstudio.com/Docs/setup/setup-overview)”。
 {% data reusables.command_line.open_the_multi_os_terminal %}
 3. 输入此命令：
   ```shell
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 646bb7c088..35cec3fd21 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
@@ -89,22 +89,24 @@ versions:
 
 ## 评论
 
-| 键盘快捷键                                                                                                                        | 描述                                                                                                                                                                           |
-| ---------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| <kbd>Command</kbd>+<kbd>B</kbd> (Mac) 或 </br> <kbd>Ctrl</kbd>+<kbd>B</kbd> (Windows/Linux)                                   | 插入 Markdown 格式用于粗体文本                                                                                                                                                         |
-| <kbd>Command</kbd>+<kbd>I</kbd> (Mac) 或 </br> <kbd>Ctrl</kbd>+<kbd>I</kbd> (Windows/Linux)                                   | 插入斜体文本的 Markdown 格式{% ifversion fpt or ghae or ghes > 3.1 or ghec %}
-| <kbd>Command</kbd>+<kbd>E</kbd> (Mac) 或 </br> <kbd>Ctrl</kbd>+<kbd>E</kbd> (Windows/Linux)                                   | 在行内插入代码或命令的 Markdown 格式{% endif %}
-| <kbd>Command</kbd>+<kbd>K</kbd> (Mac) 或 </br> <kbd>Ctrl</kbd>+<kbd>K</kbd> (Windows/Linux)                                   | 插入 Markdown 格式用于创建链接                                                                                                                                                         |
-| <kbd>Command</kbd>+<kbd>Shift</kbd>+<kbd>P</kbd> (Mac) 或 </br> <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>P</kbd> (Windows/Linux) | 在 **Write（撰写）**和 **Preview（预览）**评论选项卡之间切换{% ifversion fpt or ghae or ghes > 3.4 or ghec %}
-| <kbd>Command</kbd>+<kbd>Shift</kbd>+<kbd>V</kbd> (Mac) 或 </br> <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>V</kbd> (Windows/Linux) | 将 HTML 链接粘贴为纯文本{% endif %}{% ifversion fpt or ghae or ghes > 3.2 or ghec %}
-| <kbd>Command</kbd>+<kbd>Shift</kbd>+<kbd>7</kbd> (Mac) 或 </br> <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>7</kbd> (Windows/Linux) | 为有序列表插入 Markdown 格式                                                                                                                                                          |
-| <kbd>Command</kbd>+<kbd>Shift</kbd>+<kbd>8</kbd> (Mac) 或 </br> <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>8</kbd> (Windows/Linux) | 为无序列表插入 Markdown 格式{% endif %}
-| <kbd>Command</kbd>+<kbd>Enter</kbd> (Mac) 或 </br> <kbd>Ctrl</kbd>+<kbd>Enter</kbd> (Windows/Linux)                           | 提交评论                                                                                                                                                                         |
-| <kbd>Ctrl</kbd>+<kbd>.</kbd>，然后 <kbd>Ctrl</kbd>+<kbd>[保存的回复编号]</kbd>                                                         | 打开已保存回复菜单，然后使用已保存回复自动填写评论字段。 更多信息请参阅“[关于已保存回复](/articles/about-saved-replies)”。{% ifversion fpt or ghae or ghes > 3.2 or ghec %}
-| <kbd>Command</kbd>+<kbd>Shift</kbd>+<kbd>.</kbd> (Mac) 或 </br> <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>.</kbd> (Windows/Linux) | 为报价插入 Markdown 格式{% endif %}{% ifversion fpt or ghec %}
-| <kbd>Command</kbd>+<kbd>G</kbd> (Mac) 或 </br> <kbd>Ctrl</kbd>+<kbd>G</kbd> (Windows/Linux)                                   | 插入建议。 更多信息请参阅“[审查拉取请求中提议的更改](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request)”。 
+| 键盘快捷键                                                                                                                                                       | 描述                                                                                                                                                                           |
+| ----------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| <kbd>Command</kbd>+<kbd>B</kbd> (Mac) 或 </br> <kbd>Ctrl</kbd>+<kbd>B</kbd> (Windows/Linux)                                                                  | 插入 Markdown 格式用于粗体文本                                                                                                                                                         |
+| <kbd>Command</kbd>+<kbd>I</kbd> (Mac) 或 </br> <kbd>Ctrl</kbd>+<kbd>I</kbd> (Windows/Linux)                                                                  | 插入斜体文本的 Markdown 格式{% ifversion fpt or ghae or ghes > 3.1 or ghec %}
+| <kbd>Command</kbd>+<kbd>E</kbd> (Mac) 或 </br> <kbd>Ctrl</kbd>+<kbd>E</kbd> (Windows/Linux)                                                                  | Inserts Markdown formatting for code or a command within a line{% endif %}{% ifversion fpt or ghae-issue-5434 or ghes > 3.1 or ghec %}
+| <kbd>Command</kbd>+<kbd>K</kbd> (Mac) 或 </br> <kbd>Ctrl</kbd>+<kbd>K</kbd> (Windows/Linux)                                                                  | Inserts Markdown formatting for creating a link{% endif %}{% ifversion fpt or ghae-issue-7103 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) 或 </br> <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>P</kbd> (Windows/Linux)                                | 在 **Write（撰写）**和 **Preview（预览）**评论选项卡之间切换{% ifversion fpt or ghae or ghes > 3.4 or ghec %}
+| <kbd>Command</kbd>+<kbd>Shift</kbd>+<kbd>V</kbd> (Mac) 或 </br> <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>V</kbd> (Windows/Linux)                                | 将 HTML 链接粘贴为纯文本{% endif %}{% ifversion fpt or ghae or ghes > 3.2 or ghec %}
+| <kbd>Command</kbd>+<kbd>Shift</kbd>+<kbd>Opt</kbd>+<kbd>V</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>Alt</kbd>+<kbd>V</kbd> (Windows/Linux) | 将 HTML 链接粘贴为纯文本{% endif %}{% ifversion fpt or ghae or ghes > 3.2 or ghec %}
+| <kbd>Command</kbd>+<kbd>Shift</kbd>+<kbd>7</kbd> (Mac) 或 </br> <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>7</kbd> (Windows/Linux)                                | 为有序列表插入 Markdown 格式                                                                                                                                                          |
+| <kbd>Command</kbd>+<kbd>Shift</kbd>+<kbd>8</kbd> (Mac) 或 </br> <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>8</kbd> (Windows/Linux)                                | 为无序列表插入 Markdown 格式{% endif %}
+| <kbd>Command</kbd>+<kbd>Enter</kbd> (Mac) 或 </br> <kbd>Ctrl</kbd>+<kbd>Enter</kbd> (Windows/Linux)                                                          | 提交评论                                                                                                                                                                         |
+| <kbd>Ctrl</kbd>+<kbd>.</kbd>，然后 <kbd>Ctrl</kbd>+<kbd>[保存的回复编号]</kbd>                                                                                        | 打开已保存回复菜单，然后使用已保存回复自动填写评论字段。 更多信息请参阅“[关于已保存回复](/articles/about-saved-replies)”。{% ifversion fpt or ghae or ghes > 3.2 or ghec %}
+| <kbd>Command</kbd>+<kbd>Shift</kbd>+<kbd>.</kbd> (Mac) 或 </br> <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>.</kbd> (Windows/Linux)                                | 为报价插入 Markdown 格式{% endif %}{% ifversion fpt or ghec %}
+| <kbd>Command</kbd>+<kbd>G</kbd> (Mac) 或 </br> <kbd>Ctrl</kbd>+<kbd>G</kbd> (Windows/Linux)                                                                  | 插入建议。 更多信息请参阅“[审查拉取请求中提议的更改](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request)”。 
 {% endif %}
-| <kbd>R</kbd>                                                                                                                 | 在您的回复中引用所选的文本。 更多信息请参阅“[基本撰写和格式语法](/articles/basic-writing-and-formatting-syntax#quoting-text)”。                                                                             |
+| <kbd>R</kbd>                                                                                                                                                | 在您的回复中引用所选的文本。 更多信息请参阅“[基本撰写和格式语法](/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 ac8a170a32..17321ca215 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
@@ -31,17 +31,17 @@ shortTitle: 基本格式语法
 
 ## 样式文本
 
-You can indicate emphasis with bold, italic, strikethrough, subscript, or superscript text in comment fields and `.md` files.
+您可以在评论字段和 `.md` 文件中以粗体、斜体、删除线、下标或上标的文字表示强调。
 
-| 样式          | 语法                         | 键盘快捷键                                                                                | 示例                                                  | 输出                                    |
-| ----------- | -------------------------- | ------------------------------------------------------------------------------------ | --------------------------------------------------- | ------------------------------------- |
-| 粗体          | `** **` 或 `__ __`          | <kbd>Command</kbd>+<kbd>B</kbd> (Mac) 或 <kbd>Ctrl</kbd>+<kbd>B</kbd> (Windows/Linux) | `**这是粗体文本**`                                        | **这是粗体文本**                            |
-| 斜体          | `* *` 或 `_ _`              | <kbd>Command</kbd>+<kbd>I</kbd> (Mac) 或 <kbd>Ctrl</kbd>+<kbd>I</kbd> (Windows/Linux) | `*这是斜体文本*`                                          | *这是斜体文本*                              |
-| 删除线         | `~~ ~~`                    |                                                                                      | `~~这是错误文本~~`                                        | ~~这是错误文本~~                            |
-| 粗体和嵌入的斜体    | `** **` 和 `_ _`            |                                                                                      | `**此文本 _非常_ 重要**`                                   | **此文本_非常_重要**                         |
-| 全部粗体和斜体     | `*** ***`                  |                                                                                      | `***所有这些文本都很重要***`                                  | ***所有这些文本都是斜体***                      |
-| Subscript   | `<sub> </sub>` |                                                                                      | `<sub>This is a subscript text</sub>`   | <sub>This is a subscript text</sub>   |
-| Superscript | `<sup> </sup>` |                                                                                      | `<sup>This is a superscript text</sup>` | <sup>This is a superscript text</sup> |
+| 样式       | 语法                         | 键盘快捷键                                                                                | 示例                              | 输出                |
+| -------- | -------------------------- | ------------------------------------------------------------------------------------ | ------------------------------- | ----------------- |
+| 粗体       | `** **` 或 `__ __`          | <kbd>Command</kbd>+<kbd>B</kbd> (Mac) 或 <kbd>Ctrl</kbd>+<kbd>B</kbd> (Windows/Linux) | `**这是粗体文本**`                    | **这是粗体文本**        |
+| 斜体       | `* *` 或 `_ _`              | <kbd>Command</kbd>+<kbd>I</kbd> (Mac) 或 <kbd>Ctrl</kbd>+<kbd>I</kbd> (Windows/Linux) | `*这是斜体文本*`                      | *这是斜体文本*          |
+| 删除线      | `~~ ~~`                    |                                                                                      | `~~这是错误文本~~`                    | ~~这是错误文本~~        |
+| 粗体和嵌入的斜体 | `** **` 和 `_ _`            |                                                                                      | `**此文本 _非常_ 重要**`               | **此文本_非常_重要**     |
+| 全部粗体和斜体  | `*** ***`                  |                                                                                      | `***所有这些文本都很重要***`              | ***所有这些文本都是斜体***  |
+| 下标       | `<sub> </sub>` |                                                                                      | `<sub>这是下标文本</sub>` | <sub>这是下标文本</sub> |
+| 上标       | `<sup> </sup>` |                                                                                      | `<sup>这是上标文本</sup>` | <sup>这是上标文本</sup> |
 
 ## 引用文本
 
@@ -92,6 +92,8 @@ git commit
 
 通过将链接文本包含在方括号 `[ ]` 内，然后将 URL 包含在括号 `( )` 内，可创建内联链接。 {% ifversion fpt or ghae or ghes > 3.1 or ghec %}您还可以使用键盘快捷键 <kbd>Command</kbd>+<kbd>K</kbd> 创建链接。{% endif %}{% ifversion fpt or ghae-issue-5434 or ghes > 3.3 or ghec %} 选择文本后，可以从剪贴板粘贴 URL，以自动从所选内容创建链接。{% endif %}
 
+{% ifversion fpt or ghae-issue-7103 or ghes > 3.5 or ghec %} You can also create a Markdown hyperlink by highlighting the text and using the keyboard shortcut <kbd>Command</kbd>+<kbd>V</kbd>. If you'd like to replace the text with the link, use the keyboard shortcut <kbd>Command</kbd>+<kbd>Shift</kbd>+<kbd>V</kbd>.{% endif %}
+
 `本站点是使用 [GitHub Pages](https://pages.github.com/) 构建的。`
 
 ![渲染的链接](/assets/images/help/writing/link-rendered.png)
diff --git a/translations/zh-CN/content/get-started/writing-on-github/working-with-advanced-formatting/writing-mathematical-expressions.md b/translations/zh-CN/content/get-started/writing-on-github/working-with-advanced-formatting/writing-mathematical-expressions.md
index 99872a8016..319d2ea380 100644
--- a/translations/zh-CN/content/get-started/writing-on-github/working-with-advanced-formatting/writing-mathematical-expressions.md
+++ b/translations/zh-CN/content/get-started/writing-on-github/working-with-advanced-formatting/writing-mathematical-expressions.md
@@ -1,28 +1,28 @@
 ---
-title: Writing mathematical expressions
-intro: 'Use Markdown to display mathematical expressions on {% data variables.product.company_short %}.'
+title: 编写数学表达式
+intro: '使用 Markdown 在 {% data variables.product.company_short %} 上显示数学表达式。'
 versions:
   feature: math
-shortTitle: Mathematical expressions
+shortTitle: 数学表达式
 ---
 
-To enable clear communication of mathematical expressions, {% data variables.product.product_name %} supports LaTeX formatted math within Markdown. For more information, see [LaTeX/Mathematics](http://en.wikibooks.org/wiki/LaTeX/Mathematics) in Wikibooks.
+为了清晰地沟通数学表达式，{% data variables.product.product_name %} 在 Markdown 中支持 LaTeX 格式的数学。 更多信息请参阅维基教科书中的 [LaTeX/Math](http://en.wikibooks.org/wiki/LaTeX/Mathematics)。
 
-{% data variables.product.company_short %}'s math rendering capability uses MathJax; an open source, JavaScript-based display engine. MathJax supports a wide range of LaTeX macros, and several useful accessibility extensions. For more information, see [the MathJax documentation](http://docs.mathjax.org/en/latest/input/tex/index.html#tex-and-latex-support) and [the MathJax Accessibility Extensions Documentation](https://mathjax.github.io/MathJax-a11y/docs/#reader-guide).
+{% data variables.product.company_short %} 的数学渲染能力使用 MathJax；这是一个开源、基于JavaScript 的显示引擎。 MathJax 支持广泛的 LaTeX 宏，以及几个有用的可访问性扩展。 更多信息请参阅 [MathJax 文档](http://docs.mathjax.org/en/latest/input/tex/index.html#tex-and-latex-support) 和 [MathJax 辅助功能扩展文档](https://mathjax.github.io/MathJax-a11y/docs/#reader-guide)。
 
-## Writing inline expressions
+## 编写内联表达式
 
-To include a math expression inline with your text, delimit the expression with a dollar symbol `$`.
+要在文本中包含内联的数学表达式，请使用美元符号 `$` 分隔表达式。
 
 ```
-This sentence uses `$` delimiters to show math inline:  $\sqrt{3x-1}+(1+x)^2$
+此句子使用 `$` 分隔符来显示内联数学：$\sqrt{3x-1}+(1+x)^2$
 ```
 
-![Inline math markdown rendering](/assets/images/help/writing/inline-math-markdown-rendering.png)
+![内联数学 Markdown 渲染](/assets/images/help/writing/inline-math-markdown-rendering.png)
 
-## Writing expressions as blocks
+## 将表达式编写为块
 
-To add a math expression as a block, start a new line and delimit the expression with two dollar symbols `$$`.
+要将数学表达式添加为块，请开始一个新行，并使用两个美元符号 `$$` 分隔表达式。
 
 ```
 **The Cauchy-Schwarz Inequality**
@@ -30,30 +30,30 @@ To add a math expression as a block, start a new line and delimit the expression
 $$\left( \sum_{k=1}^n a_k b_k \right)^2 \leq \left( \sum_{k=1}^n a_k^2 \right) \left( \sum_{k=1}^n b_k^2 \right)$$
 ```
 
-![Math expression as a block rendering](/assets/images/help/writing/math-expression-as-a-block-rendering.png)
+![作为块渲染的数学表达式](/assets/images/help/writing/math-expression-as-a-block-rendering.png)
 
-## Writing dollar signs in line with and within mathematical expressions
+## 联接数学表达式以及在数学表达式内编写美元符号
 
-To display a dollar sign as a character in the same line as a mathematical expression, you need to escape the non-delimiter `$` to ensure the line renders correctly.
+要将美元符号显示为与数学表达式相同的行中的字符，需要对非分隔符 `$` 进行转义，以确保该行正确呈现。
 
-  - Within a math expression, add a `\` symbol before the explicit `$`.
+  - 在数学表达式中，在显式 `$`之前添加 `\` 符号。
 
   ```
-  This expression uses `\$` to display a dollar sign: $\sqrt{\$4}$
+  此表达式使用 `\$` 来显示美元符号：$\sqrt{\$4}$
   ```
 
-  ![Dollar sign within math expression](/assets/images/help/writing/dollar-sign-within-math-expression.png)
+  ![数学表达式中的美元符号](/assets/images/help/writing/dollar-sign-within-math-expression.png)
 
-  - Outside a math expression, but on the same line, use span tags around the explicit `$`.
+  - 在数学表达式之外，但在同一行上，在显式 `$` 周围使用 span 标记。
 
   ```
-  To split <span>$</span>100 in half, we calculate $100/2$
+  要 <span>$</span>100 分成两半，我们计算 $100/2$
   ```
 
-  ![Dollar sign inline math expression](/assets/images/help/writing/dollar-sign-inline-math-expression.png)
+  ![数学表达式中嵌入的美元符号](/assets/images/help/writing/dollar-sign-inline-math-expression.png)
 
 ## 延伸阅读
 
-* [The MathJax website](http://mathjax.org)
+* [MathJax 网站](http://mathjax.org)
 * [开始在 GitHub 上编写和格式化](/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github)
-* [GitHub Flavored Markdown Spec](https://github.github.com/gfm/)
+* [GitHub Flavored Markdown 规格](https://github.github.com/gfm/)
diff --git a/translations/zh-CN/content/github/copilot/about-github-copilot-telemetry.md b/translations/zh-CN/content/github/copilot/about-github-copilot-telemetry.md
index 63d1ee158a..87c9413c7b 100644
--- a/translations/zh-CN/content/github/copilot/about-github-copilot-telemetry.md
+++ b/translations/zh-CN/content/github/copilot/about-github-copilot-telemetry.md
@@ -9,7 +9,7 @@ versions:
 
 ## 哪些数据会被收集？
 
-收集的数据在“[{% data variables.product.prodname_copilot %} 遥测术语](/github/copilot/github-copilot-telemetry-terms)”中进行了描述。 此外，{% data variables.product.prodname_copilot %} 扩展/插件从用户的集成开发环境 (IDE) 收集活动（绑定到时间戳）以及扩展/插件遥测包收集的元数据。 When used with {% data variables.product.prodname_vscode %}, IntelliJ, NeoVIM, or other IDEs, {% data variables.product.prodname_copilot %} collects the standard metadata provided by those IDEs.
+收集的数据在“[{% data variables.product.prodname_copilot %} 遥测术语](/github/copilot/github-copilot-telemetry-terms)”中进行了描述。 此外，{% data variables.product.prodname_copilot %} 扩展/插件从用户的集成开发环境 (IDE) 收集活动（绑定到时间戳）以及扩展/插件遥测包收集的元数据。 当与 {% data variables.product.prodname_vscode %}、IntelliJ、NeoVIM 或其他 IDE 一起使用时，{% data variables.product.prodname_copilot %} 会收集这些 IDE 提供的标准元数据。
 
 ## {% data variables.product.company_short %} 如何使用数据
 
diff --git a/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges.md b/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges.md
index 3a1844d9f6..502bad4198 100644
--- a/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges.md
+++ b/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges.md
@@ -24,7 +24,7 @@ topics:
 
 ### 合并压缩合并的消息
 
-When you squash and merge, {% data variables.product.prodname_dotcom %} generates a default commit message, which you can edit. The default message depends on the number of commits in the pull request, not including merge commits.
+在压缩与合并时，{% data variables.product.prodname_dotcom %} 生成默认提交消息，您可以进行编辑。 默认消息取决于拉取请求中的提交次数，不包括合并提交。
 
 | 提交数  | 摘要                   | 描述                  |
 | ---- | -------------------- | ------------------- |
@@ -32,7 +32,7 @@ When you squash and merge, {% data variables.product.prodname_dotcom %} generate
 | 多个提交 | 拉取请求标题，后接拉取请求编号      | 按日期顺序列出所有被压缩提交的提交消息 |
 
 {% ifversion fpt or ghec or ghes > 3.5 or ghae-issue-7042 %}
-People with admin access to a repository can configure the repository to use the title of the pull request as the default merge message for all squashed commits. For more information, see "[Configure commit squashing](/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-squashing-for-pull-requests)".
+对存储库具有管理员访问权限的人员可以将存储库配置为使用拉取请求的标题作为所有压缩提交的默认合并消息。 更多信息请参阅“[配置提交压缩](/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-squashing-for-pull-requests)”。
 {% endif %}
 
 ### 压缩与合并长运行分支
diff --git a/translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule.md b/translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule.md
index dada98ac8e..cab4aad1b0 100644
--- a/translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule.md
+++ b/translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule.md
@@ -63,9 +63,9 @@ shortTitle: 分支保护规则
    - （可选）要在将代码修改提交推送到分支时忽略拉取请求批准审查，请选择 **Dismiss stale pull request approvals when new commits are pushed（推送新提交时忽略旧拉取请求批准）**。 ![在推送新提交时，关闭旧拉取请求批准的复选框](/assets/images/help/repository/PR-reviews-required-dismiss-stale.png)
    - （可选）要在拉取请求影响具有指定所有者的代码时要求代码所有者审查，请选择 **Require review from Code Owners（需要代码所有者审查）**。 更多信息请参阅“[关于代码所有者](/github/creating-cloning-and-archiving-repositories/about-code-owners)”。 ![代码所有者的必需审查](/assets/images/help/repository/PR-review-required-code-owner.png)
 {% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5611 %}
-   - Optionally, to allow specific actors to push code to the branch without creating pull requests when they're required, select **Allow specified actors to bypass required pull requests**. Then, search for and select the actors who should be allowed to skip creating a pull request. ![Allow specific actors to bypass pull request requirements checkbox]{% if integration-branch-protection-exceptions %}(/assets/images/help/repository/PR-bypass-requirements-with-apps.png){% else %}(/assets/images/help/repository/PR-bypass-requirements.png){% endif %}
+   - （可选）若要允许特定参与者在需要时将代码推送到分支而不创建拉取请求，请选择 **Allow specific actors to bypass required pull requests（允许特定参与者绕过所需的拉取请求）**。 然后，搜索并选择应被允许跳过创建拉取请求的参与者。 ![允许特定参与者绕过拉取请求要求复选框]{% if integration-branch-protection-exceptions %}(/assets/images/help/repository/PR-bypass-requirements-with-apps.png){% else %}(/assets/images/help/repository/PR-bypass-requirements.png){% endif %}
 {% endif %}
-   - （可选）如果仓库属于组织，请选择 **Restrict who can dismiss pull request reviews（限制谁可以忽略拉取请求审查）**。 Then, search for and select the actors who are allowed to dismiss pull request reviews. 更多信息请参阅“[忽略拉取请求审查](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/dismissing-a-pull-request-review)”。 ![Restrict who can dismiss pull request reviews checkbox]{% if integration-branch-protection-exceptions %}(/assets/images/help/repository/PR-review-required-dismissals-with-apps.png){% else %}(/assets/images/help/repository/PR-review-required-dismissals.png){% endif %}
+   - （可选）如果仓库属于组织，请选择 **Restrict who can dismiss pull request reviews（限制谁可以忽略拉取请求审查）**。 然后，搜索并选择有权忽略拉取请求审查的参与者。 更多信息请参阅“[忽略拉取请求审查](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/dismissing-a-pull-request-review)”。 ![限制谁可以关闭拉取请求评审复选框]{% if integration-branch-protection-exceptions %}(/assets/images/help/repository/PR-review-required-dismissals-with-apps.png){% else %}(/assets/images/help/repository/PR-review-required-dismissals.png){% endif %}
 1. （可选）启用必需状态检查。 更多信息请参阅“[关于状态检查](/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks)”。
    - 选中 **Require status checks to pass before merging（合并前必需状态检查通过）**。 ![必需状态检查选项](/assets/images/help/repository/required-status-checks.png)
    - （可选）要确保使用受保护分支上的最新代码测试拉取请求，请选择 **Require branches to be up to date before merging（要求分支在合并前保持最新）**。 ![宽松或严格的必需状态复选框](/assets/images/help/repository/protecting-branch-loose-status.png)
@@ -95,7 +95,7 @@ shortTitle: 分支保护规则
 {% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5624 %}
   然后，选择谁可以强制推送到分支。
     - 选择 **Everyone（每个人）**以允许至少具有存储库写入权限的每个人强制推送到分支，包括具有管理员权限的人员。
-    - Select **Specify who can force push** to allow only specific actors to force push to the branch. Then, search for and select those actors. ![Screenshot of the options to specify who can force push]{% if integration-branch-protection-exceptions %}(/assets/images/help/repository/allow-force-pushes-specify-who-with-apps.png){% else %}(/assets/images/help/repository/allow-force-pushes-specify-who.png){% endif %}
+    - 选择 **Specify who can force push（指定谁可以强制推送）**，仅允许特定参与者强制推送到分支。 然后，搜索并选择这些参与者。 ![指定谁可以强制推送的选项的屏幕截图]{% if integration-branch-protection-exceptions %}(/assets/images/help/repository/allow-force-pushes-specify-who-with-apps.png){% else %}(/assets/images/help/repository/allow-force-pushes-specify-who.png){% endif %}
 {% endif %}
 
     有关强制推送的详细信息，请参阅“[允许强制推送](/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches/#allow-force-pushes)”。
diff --git a/translations/zh-CN/content/repositories/releasing-projects-on-github/about-releases.md b/translations/zh-CN/content/repositories/releasing-projects-on-github/about-releases.md
index 1c89e67c25..35cf3cda24 100644
--- a/translations/zh-CN/content/repositories/releasing-projects-on-github/about-releases.md
+++ b/translations/zh-CN/content/repositories/releasing-projects-on-github/about-releases.md
@@ -41,7 +41,7 @@ topics:
 {% endif %}
 
 {% ifversion fpt or ghec or ghes > 3.6 or ghae-issue-7054 %}
-When viewing the details for a release, the creation date for each release asset is shown next to the release asset.
+查看发行版的详细信息时，每个发行版资产的创建日期显示在发行版资产旁边。
 {% endif %}
 
 {% ifversion fpt or ghec %}
diff --git a/translations/zh-CN/content/site-policy/privacy-policies/github-codespaces-privacy-statement.md b/translations/zh-CN/content/site-policy/privacy-policies/github-codespaces-privacy-statement.md
index 2716a91784..0fdb852ad2 100644
--- a/translations/zh-CN/content/site-policy/privacy-policies/github-codespaces-privacy-statement.md
+++ b/translations/zh-CN/content/site-policy/privacy-policies/github-codespaces-privacy-statement.md
@@ -18,6 +18,6 @@ github.dev 上的活动受 [GitHub 测试预览版条款](/github/site-policy/gi
 
 ## 使用 {% data variables.product.prodname_vscode %}
 
-GitHub Codespaces and github.dev allow for use of {% data variables.product.prodname_vscode %} in the web browser. When using {% data variables.product.prodname_vscode_shortname %} in the web browser, some telemetry collection is enabled by default and is [explained in detail on the {% data variables.product.prodname_vscode_shortname %} website](https://code.visualstudio.com/docs/getstarted/telemetry). 用户可以通过转到左上角菜单下的 File > Preferences > Settings（文件首选项设置）来选择退出遥测。
+GitHub Codespaces 和 github.dev 允许在 Web 浏览器中使用 {% data variables.product.prodname_vscode %}。 在 Web 浏览器中使用 {% data variables.product.prodname_vscode_shortname %} 时，默认情况下会启用某些遥测集合，[{% data variables.product.prodname_vscode_shortname %} 网站上对此进行了详细解释](https://code.visualstudio.com/docs/getstarted/telemetry)。 用户可以通过转到左上角菜单下的 File > Preferences > Settings（文件首选项设置）来选择退出遥测。
 
-If a user chooses to opt out of telemetry capture in {% data variables.product.prodname_vscode_shortname %} while inside of a codespace as outlined, this will sync the disable telemetry preference across all future web sessions in GitHub Codespaces and github.dev.
+如果用户选择在代码空间内选择退出 {% data variables.product.prodname_vscode_shortname %} 中的遥测捕获（如前所述），这将在 GitHub Codespaces 和 github.dev 中的所有未来 Web 会话中同步禁用遥测首选项。
diff --git a/translations/zh-CN/content/site-policy/privacy-policies/github-privacy-statement.md b/translations/zh-CN/content/site-policy/privacy-policies/github-privacy-statement.md
index dfee84791c..ffcbb1e7ef 100644
--- a/translations/zh-CN/content/site-policy/privacy-policies/github-privacy-statement.md
+++ b/translations/zh-CN/content/site-policy/privacy-policies/github-privacy-statement.md
@@ -65,7 +65,7 @@ topics:
 #### 支付信息
 如果您注册我们的付费帐户、通过 GitHub 赞助计划汇款或在 GitHub Marketplace 上购买应用程序，我们将收集您的全名、地址和信用卡信息或 PayPal 信息。 请注意，GitHub 不会处理或存储您的信用卡信息或 PayPal 信息，但我们的第三方付款处理商会这样做。
 
-如果您在 [GitHub Marketplace](https://github.com/marketplace) 上列出并销售应用程序，我们需要您的银行信息。 If you raise funds through the [GitHub Sponsors Program](https://github.com/sponsors), we require some [additional information](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-personal-account#submitting-your-bank-information) through the registration process for you to participate in and receive funds through those services and for compliance purposes.
+如果您在 [GitHub Marketplace](https://github.com/marketplace) 上列出并销售应用程序，我们需要您的银行信息。 如果您通过 [GitHub 赞助计划](https://github.com/sponsors)筹集资金，我们需要您在注册过程中提供一些[其他信息](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-personal-account#submitting-your-bank-information)，以便您参与这些服务并通过这些服务获取资金以及满足合规要求。
 
 #### 个人资料信息
 您可以选择在帐户个人资料中向我们提供更多信息，例如您的全名、头像等，可包括照片、简历、地理位置、公司和第三方网站的 URL。 此类信息可能包括用户个人信息。 请注意，您的个人资料信息可能对我们服务的其他用户显示。
diff --git a/translations/zh-CN/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-personal-account.md b/translations/zh-CN/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-personal-account.md
index a7363a0331..af9b078ebd 100644
--- a/translations/zh-CN/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-personal-account.md
+++ b/translations/zh-CN/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-personal-account.md
@@ -1,5 +1,5 @@
 ---
-title: Setting up GitHub Sponsors for your personal account
+title: 为您的个人帐户设置 GitHub Sponsors
 intro: '要成为被赞助的开发者，请加入 {% data variables.product.prodname_sponsors %}、填写被赞助开发者个人资料、创建赞助等级、提交您的银行和税务信息并为您在 {% data variables.product.product_location %} 上的帐户启用双重身份验证。'
 redirect_from:
   - /articles/becoming-a-sponsored-developer
diff --git a/translations/zh-CN/content/sponsors/receiving-sponsorships-through-github-sponsors/tax-information-for-github-sponsors.md b/translations/zh-CN/content/sponsors/receiving-sponsorships-through-github-sponsors/tax-information-for-github-sponsors.md
index 113803cae8..31885715a1 100644
--- a/translations/zh-CN/content/sponsors/receiving-sponsorships-through-github-sponsors/tax-information-for-github-sponsors.md
+++ b/translations/zh-CN/content/sponsors/receiving-sponsorships-through-github-sponsors/tax-information-for-github-sponsors.md
@@ -28,7 +28,7 @@ W-9 税表中的信息有助于 {% data variables.product.prodname_dotcom %} 使
 
 W-8 BEN 和 W-8 BEN-E 税单有助于 {% data variables.product.prodname_dotcom %} 确定须扣缴金额的受益所有者。
 
-如果你是美国以外任何其他地区的纳税人， 必须提交 [W-8 BEN](https://www.irs.gov/pub/irs-pdf/fw8ben.pdf) (个人) 或 [W-8 BEN-E](https://www.irs.gov/forms-pubs/about-form-w-8-ben-e) (公司) 表单才能发布您的 {% data variables.product.prodname_sponsors %} 个人资料。 For more information, see "[Setting up {% data variables.product.prodname_sponsors %} for your personal account](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-personal-account#submitting-your-tax-information)" and "[Setting up {% data variables.product.prodname_sponsors %} for your organization](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization#submitting-your-tax-information)." {% data variables.product.prodname_dotcom %} 将向您发送适当的表格，在到期时通知您，并给您合理的时间填写和发送表格。
+如果你是美国以外任何其他地区的纳税人， 必须提交 [W-8 BEN](https://www.irs.gov/pub/irs-pdf/fw8ben.pdf) (个人) 或 [W-8 BEN-E](https://www.irs.gov/forms-pubs/about-form-w-8-ben-e) (公司) 表单才能发布您的 {% data variables.product.prodname_sponsors %} 个人资料。 更多信息请参阅“[为个人帐户设置 {% data variables.product.prodname_sponsors %}](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-personal-account#submitting-your-tax-information)”和”[为组织设置 {% data variables.product.prodname_sponsors %}](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization#submitting-your-tax-information)”。 {% data variables.product.prodname_dotcom %} 将向您发送适当的表格，在到期时通知您，并给您合理的时间填写和发送表格。
 
 如果您被分配了不正确的税单， [请联系 {% data variables.product.prodname_dotcom %} 客服](https://support.github.com/contact?form%5Bsubject%5D=GitHub%20Sponsors:%20tax%20form&tags=sponsors) 来为您的情况重新分配正确的税单。
 
diff --git a/translations/zh-CN/data/release-notes/enterprise-server/3-3/8.yml b/translations/zh-CN/data/release-notes/enterprise-server/3-3/8.yml
index 96950f12a4..d5f3738591 100644
--- a/translations/zh-CN/data/release-notes/enterprise-server/3-3/8.yml
+++ b/translations/zh-CN/data/release-notes/enterprise-server/3-3/8.yml
@@ -31,4 +31,3 @@ sections:
     - '{% data variables.product.prodname_registry %} npm 注册表不再返回元数据响应的时间值。这样做是为了大幅改善性能。作为元数据响应的一部分，我们继续拥有返回时间值所需的所有数据，并将在我们解决现有性能问题后恢复返回这个值。'
     - 特定于处理预接收挂钩的资源限制可能会导致某些预接收挂钩失败。
     - '{% data variables.product.prodname_actions %} storage settings cannot be validated and saved in the {% data variables.enterprise.management_console %} when "Force Path Style" is selected, and must instead be configured with the `ghe-actions-precheck` command line utility.'
-    - '{% data variables.product.prodname_ghe_server %} 3.3 instances installed on Azure and provisioned with 32+ CPU cores would fail to launch, due to a bug present in the current Linux kernel. [Updated: 2022-04-08]'
diff --git a/translations/zh-CN/data/reusables/actions/jobs/section-defining-outputs-for-jobs.md b/translations/zh-CN/data/reusables/actions/jobs/section-defining-outputs-for-jobs.md
index 9c0aab05fe..feef0f0abb 100644
--- a/translations/zh-CN/data/reusables/actions/jobs/section-defining-outputs-for-jobs.md
+++ b/translations/zh-CN/data/reusables/actions/jobs/section-defining-outputs-for-jobs.md
@@ -1,6 +1,8 @@
 You can use `jobs.<job_id>.outputs` to create a `map` of outputs for a job. 作业输出可用于所有依赖此作业的下游作业。 有关定义作业依赖项的更多信息，请参阅 [`jobs.<job_id>.needs`](/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idneeds)。
 
-作业输出是字符串，当每个作业结束时，在运行器上评估包含表达式的作业输出。 包含密码的输出在运行器上编辑，不会发送至 {% data variables.product.prodname_actions %}。
+{% data reusables.actions.output-limitations %}
+
+Job outputs containing expressions are evaluated on the runner at the end of each job. 包含密码的输出在运行器上编辑，不会发送至 {% data variables.product.prodname_actions %}。
 
 要在依赖的作业中使用作业输出, 您可以使用 `needs` 上下文。 更多信息请参阅“[上下文](/actions/learn-github-actions/contexts#needs-context)”。
 
diff --git a/translations/zh-CN/data/reusables/actions/output-limitations.md b/translations/zh-CN/data/reusables/actions/output-limitations.md
new file mode 100644
index 0000000000..d26de54a7f
--- /dev/null
+++ b/translations/zh-CN/data/reusables/actions/output-limitations.md
@@ -0,0 +1 @@
+Outputs are Unicode strings, and can be a maximum of 1 MB. The total of all outputs in a workflow run can be a maximum of 50 MB.